Procurement - EBS (MOSC)

MOSC Banner

PO communication method re-defaulting after it is changed

edited Dec 15, 2017 4:02AM in Procurement - EBS (MOSC) 1 commentAnswered

Hi all,

We are on 12.2.5, and we have been using a method to suppress re-communicating certain PO changes to suppliers that no longer works.  Before, if a PO change should not be communicated, a buyer would update the PO in BWC to change the communication method to "None" and save this change.  Then the requisitioner would make a change, and it would auto-change and approve the PO.  The communication would not go out.

But now (and we're not sure what change went in to make this start happening), even if the buyer changes the PO communication to "none", when the requisitioner makes a change it is being sent to the supplier via the original default communication method.  We are not using iSupplier Portal.  PO: Communication Email Default is set to Site.  PO: Default Communication method from Order document during revision is set to No.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Procurement Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center