My Oracle Support Banner

Processing Constraint Not Working For User Action - Require Reason, History & Raise Integration Event (Doc ID 2572391.1)

Last updated on DECEMBER 15, 2020

Applies to:

Oracle Order Management - Version 12.2.8 and later
Information in this document applies to any platform.


Processing Constraint is not working for user action - Require Reason, History and Raise Integration Event for a sales order header DFF attribute update when seeded template - BOOKED is used . So, whenever we update this DFF attribute for a booked order, it should ask me for a reason code however, it is not asking me to enter the reason code for the attribute value change. Moreover, it did not fire the integration event.
I used another processing constraint user action- generate version, require reason and raise integration for the same DFF attribute and same seeded template - BOOKED and it worked fine. On updating the same DFF attribute for a booked order, it did ask me for a reason code and it also fired the integration event successfully.


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.