Professional Documents
Culture Documents
• Problem Description
• Background
• Workarounds
o Option1: Disable all email communication on the
Procurement domain. Stops Approval emails as well.
o Option2: Update the Supplier email address on the
Purchasing document. Does not impact Approval emails.
• Customer Situations and Workarounds
Problem Description
On the Cloud test pods, customers need the ability to not send email to suppliers or send the email to a
common email address. Currently we do not have a good solution in Purchasing, to stop just the supplier
email communication from test instance without updating the email address/email communication method
on the purchase orders. There is no option to send all supplier email communications to a common email
address.
Background
Purchasing documents can be communicated to Supplier, manually from the Manage Orders page or by
an ESS program or when the document, with communication method set as Email, is submitted and
implemented(i.e. document status is open). This Email communication to Supplier functionality uses the
UMS (User Messaging Service) component in Oracle Fusion Middleware to send emails. The Supplier
email communication flow does not use the Human Task component of the Oracle Fusion Middleware.
So, even if you had set the Human Task Notification properties as "None", the supplier email
communication will still happen. The Supplier Email communication can be switched off by setting the
Communication method on the Purchasing document as "None" or by setting the UMS Email Driver
properties.
Human tasks also uses the UMS component to communicate via email. When you stop the supplier
communication by setting the UMS email driver property, you will end up stopping the Human Task Email
notifications as well - this means the document approver will not receive email notifications to approve the
document. Users can still approve the document from the Applications home page by clicking the bell
icon or from the Worklist task in the navigator. If customers have a requirement to stop supplier
communication but keep the approval email notifications working, then the UMS setup will not help. In this
case, customer will need the datafix scripts (provided in this page) that updates the supplier email
address to be an invalid email address
Workarounds
Purchasing Development is looking into options to stop email communication on the test pods, even if the
communication method is set as email. The following options are workarounds until we come up with a
solution to this problem.
Option1: Disable all email communication on the Procurement domain. Stops Approval emails as
well.
1. Login into EM. Navigate to 'Email Driver Properties' under 'User Messaging Service' ->
'usermessagingdriver-email'
2. Scroll through the properties under 'Driver-Specific Configuration' and update OutgoingMailServer
with a dummy (invalid) smtp server address. Refer attached (email.jpg) screenshot.
3. Bounce the SOA Server for changes to take effect.
Note: Above steps disable both Supplier Communication emails to external users and Approval (Human
Workflow) emails for the entire Procurement domain
Option2: Update the Supplier email address on the Purchasing document. Does not impact
Approval emails.
Log an SR to perform the below steps to update the supplier email address on the purchasing document
to a non-existing email address.
What we do ?
Note: The datafix scripts appends a text to the current supplier email addresses on the purchasing
documents to stop communication to the supplier. This does not stop communication if customer
updates/creates documents with a valid email address after the datafix was run.
Customer Situations and Workarounds
There are several situations when customer would want to switch off the supplier communication on a
Test instance