Want To Disable Seeded Processing Constraints For Customer PO Update At Ship Confirm
Last updated on MAY 15, 2017
Applies to:Oracle Order Management - Version 11.5 to 12.1.2 [Release 11.5 to 12.1]
Oracle Order Management - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
FORM:OEXOEORD.FMB - Sales Orders
When attempting to change the value of the Customer PO at the sales order line after the line has
progressed to ship confirm the following error occurs due to a seeded system processing constraint.
You are not allowed to update Customer PO because: Line is Ship Confirmed.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Create a sales order with a line
2. Progress to through ship confirm, Line status = shipped
3. change customer PO at header
Prompt: do you want to cascade changes to line? YES
NOTE: You are not allowed to update Customer PO because: Line is Ship Confirmed.
If Prompt: do you want to cascade changes to line? NO, order header customer PO does save with new value.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms