My Oracle Support Banner

Order Header Changes Cascade To Lines But Raising Only One Integration Event (Doc ID 1405117.1)

Last updated on AUGUST 29, 2021

Applies to:

Oracle Order Management - Version 12.1.2 to 12.2.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.


On : 12.1.2 version, Transaction Control


A processing constraint is defined for two fields at the Sales order line level, PO Number and Payment Terms, such that an integration event is raised every time the fields are updated.
The expectation is if a header level change of these fields cascades to multiple sales order lines, then an integration event should be raised for each line.
However, the current behavior is that only one event is being raised, regardless of the number of lines on the order. The user has verified that the changes were applied to every line of the multi-line order.

Expect to see multiple business events raised based on the process constraint created.

The issue can be reproduced at will with the following steps:
1. Entered a change on a sales order at the header (PO Number, Payment terms).
2. Sales order has multiple lines (lines 1.1, 2.1, 3.1, 4.1, 5.1).
3. Changes cascaded to all lines successfully - As expected.
4. We have a constraint set-up for these 2 fields at the Sales order Line level to raise an integration event every time they are updated.
5. Only first line raised an integration event. No other events were raised. - Not working as expected. Expected to see 5 integration events (in this example).




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.