Transmit Change Orders Happen When Not Specified

(Doc ID 1992939.1)

Last updated on JULY 14, 2015

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 and later
Information in this document applies to any platform.


We have an issue with the transmit change orders fix delivered in 9.2 PUM image 8.  
The new information that has come to light is:
- When I previously tested the fix, I didn't realize our vendors were set to not transmit change orders and the BU setting I was changing basically had no effect
- After the vendor records are updated, the BU setting is not found (seen in trace file).  This is because our Purchasing Option ID does not match the business unit value.  Does it have to?  I don't see anything anywhere that forces them to be in sync.  Our current setup does not match the BU.
- The SQL added to determine the change order flag looks for the max effective date, not the current effective date.
- The if statement added around the line that creates the PDF files is outside of the for loop.  This means the determination on whether to create the PDF files for all the POs in the dispatch is based on the DISP_CO_FLAG of the last PO in the batch.

The Transmit Change Order functionality / Dispatch Open at the Business Unit
 level will only will only work if the Process Option on the PO Business Unit
 Purchasing Definition has the same name as the Purchasing Options|Processing
 Option ID.  
 For example:US001 must have US001 as the process option in order to work; in
 customer testing they use process option STAND. Their setup has Transmit
 Change Orders checked for Dispatch Options however the Purchasing Options for
 US001 does not have the Transmit Change Orders checked for Dispatch Options.  

The issue can be reproduced at will with the following steps:
*Set Vendor to NOT transmit change orders
*Set Business Unit option to NOT transmit change orders
*Create PO
*Dispatch PO via EDX
*Transmit PO with Publish Outbound message
*Go back into PO and change the quantity
*Status goes back to Approved; Dispatch again
*Note on run control in replication that Change Orders set to Changed and  
Unchanged; but Vendor and BU Options are set to Not send.
*PO has been dispatched again
*the change order has been transmitted again even though it's not supposed to.

Due to this issue, change orders are dispatched when they should not be.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms