Business Event: oracle.apps.ont.oi.xml_int.status is not firing For Minor Lines In Case Of ShipsetID
(Doc ID 2250323.1)
Last updated on SEPTEMBER 22, 2023
Applies to:
Oracle Order Management - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Transaction Fulfillment
ACTUAL BEHAVIOR
---------------
Customer used the business event: oracle.apps.ont.oi.xml_int.status to capture the shipset change to a customized table: xxodi_oe_order_lines_history. Processing constraints have been setup accordingly.
When update ship set information from front end, Id can be changed successfully for major line 1.1, however, no change for minor line 1.1.20 for example.
EXPECTED BEHAVIOR
-----------------------
XML works for both major line and also Minor line.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Customer used the business event: oracle.apps.ont.oi.xml_int.status to capture the shipset change to a customized table: xxodi_oe_order_lines_history.
2. Change ship set information from front end
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |