Purchasing

Get Involved. Join the Conversation.

Topic

    Henny Bastiaansen
    Override email addresses in SaaS test instanceAnswered
    Topic posted November 12, 2015 by Henny Bastiaansen, tagged Setup 
    482 Views, 5 Comments
    Title:
    Override email addresses in SaaS test instance
    Summary:
    Override e-mail address
    Content:

    Hi all,

    Does anyone know how email addresses from suppliers/customers can be overridden with a generic internal one when SaaS production instance is cloned to a test instance? In other words “how to prevent emails being sent to suppliers/customers when performing test cyclus?

    Thanks in advance for an answer.

     

    Best Regards,

    Henny

    Best Comment

    Vijay Goodavagaram

    Currently it is not possible to override the supplier email address to a generic email address. We are working on solution for this problem. For now, customers have used one of the workarounds listed below. Both of these workarounds require Cloud Ops assistance and has some downsides.

    1. Disable all emails on the Procurement Test POD after a Production to Test(P2T) clone, so that emails are not sent to the supplier from Purchasing application. Cloud Ops can specify an invalid SMTP server on the "Email driver properties" page of the "User Messaging Service" in the Enterprise Manager. The downside is, even the approval emails will stop working on the test instance and users have to use the application (Bell icon or Worklist task in the navigator) to approve the documents on the Test pod.

    2. Some customers who needed approval emails to work on test pod, had to ask cloud ops to run a data update script(provided by development) as part of the P2T clone. The data update script updated the email address for the supplier to an invalid email address on the test pod. This does not help the situation when you override the email address to a valid email address on the test pod after the data update script was run, in which case the only option to handle this situation is Option-1 (i.e. Disable all emails on test pod)

    Support is documenting the problem and the workaround in a support note. We are expecting it to be published next week If one of these workaround will help you for now and you need more information sooner, let me know - i can get you the draft.

    Comment

     

    • Vijay Goodavagaram

      Currently it is not possible to override the supplier email address to a generic email address. We are working on solution for this problem. For now, customers have used one of the workarounds listed below. Both of these workarounds require Cloud Ops assistance and has some downsides.

      1. Disable all emails on the Procurement Test POD after a Production to Test(P2T) clone, so that emails are not sent to the supplier from Purchasing application. Cloud Ops can specify an invalid SMTP server on the "Email driver properties" page of the "User Messaging Service" in the Enterprise Manager. The downside is, even the approval emails will stop working on the test instance and users have to use the application (Bell icon or Worklist task in the navigator) to approve the documents on the Test pod.

      2. Some customers who needed approval emails to work on test pod, had to ask cloud ops to run a data update script(provided by development) as part of the P2T clone. The data update script updated the email address for the supplier to an invalid email address on the test pod. This does not help the situation when you override the email address to a valid email address on the test pod after the data update script was run, in which case the only option to handle this situation is Option-1 (i.e. Disable all emails on test pod)

      Support is documenting the problem and the workaround in a support note. We are expecting it to be published next week If one of these workaround will help you for now and you need more information sooner, let me know - i can get you the draft.

    • Vijay Goodavagaram

      With Release-11, July bundle, these 2 profile options are now available to help with this situation. With the below 2 profile options, you will be able to suppress email communication to supplier, in Procurement. This does not have any impact on the approval email notifications.

      1. Control Supplier Communication: values=Disable, Enable, Override E-mail Recipient
      2. Override E-mail Address

      There is also an additional parameter ("Communicate Orders"=Yes/No) in the Import Orders/Agreements ESS program, to not communicate to suppliers when importing purchasing documents. This is useful, when you want to migrate documents (using Import Orders/Agreements) from an existing instance to your cloud production instance and not communicate them to supplier again.

       

      • Reina van Ewijk

        hi Vijay

        that is promising news! thanks for the update. We're upgrading our test environment to R11 end august so will test it then.

         

        Thanks and best regards

        Reina

      • Juan Miguel Isip

        Hi Vijay,

        I think Document 2089867.1 (How To Disable All The Supplier E-mails(For Purchase Orders) on Test Instances - Post P2T) is the document that you mentioned, is this correct?

        I would like to know if there's an equivalent of this for Customers? We would want to suppress the sending of Dunning Letters from a Test POD.

        Please advise.