Tuesday, November 22, 2011

Processing Constraints in Oracle Order Management

Processing Constraints are a security framework where you can define rules in Oracle Order Management that validate back-end operations such as Create, Update, Delete and Cancel.
Examples:
You cannot change the Order Type in the order header once the order is Booked.
You cannot delete the line in an order once the Order Status is Closed (if the order is ship confirmed or invoice interfaced).
Here, I’ve explained about Processing Constraints with an example.
Navigate to Order Management à Setup à Rules à Security à Processing Constraints
Query the Application as Order Management
Create a New Line on the Constraints region:
Operation = Update
Attribute = Order Type
User Action = Not Allowed
Enabled check box = Selected
Create a New Line on Conditions tab:
Group Number = 101
Scope = Any
Validation Entity = Order Header
Record Set = Order
Validation Template = Booked
Enabled check box = Selected
User Message = Order is Booked

Create another New Line on Conditions tab:
Group Number = 102
Scope = Any
Validation Entity = Order Header
Record Set = Order
Validation Template = Lines Exist
Enabled check box = Selected
User Message = Order has Lines

Navigate to Order, Returns à Sales Order
Create a Sales Order with Order Type as Mixed
Enter the Item Number and Save the Record (i.e., the order will be in Entered Stage)

Now, you try to change the Order Type. It will give you the error that "You are not allowed to update the Order Type because: Lines exist for this Order".

Now, Book the Order and try to change the Order Type. 

It will give you the error that "You are not allowed to update the Order Type because: Order is Booked"

Enjoy Learning Oracle Apps J

1 comment:

  1. Thank you for the information and the effort! :)

    ReplyDelete