By: Ajay Kheldar

This presentation is will introduce a built in feature of processing constraints in 11.5.10.2 and release 12 .

Useful for following Skill set: Distribution Functional Consultants Finance Functional Consultants OPM Functional Consultants Manufacturing Functional Consultants

Overview Processing Constraints Terminology Introduction Usage Set Up Architecture Seeded Constraints an Example How to Set Up Processing Constraints How Constraints Works during order processing (Test PC which is Created ) Processing Constraints Access Report Reference

Processing Constraints:

Enable you to control changes to sales documents in Oracle Order Management.

Control the complete process from ordering to closing in order management. Define whether a change is allowed to an order after certain activities have

been completed, as well as the level of responsibility required to make the change.

Processing Constraints are very powerful and setting them up is not difficult however, knowledge of the following terms is helpful:

Entity

A group of related attributes that roughly correspond to a table or a window in Order Management. The entities that can be managed using processing constraints are Order Header, Order Line, Order Price Adjustment, Line Price Adjustment, Order Sales Credit, Line Sales Credit, Order Payment, Line Payment, Sales Agreement Header, and Sales Agreement Line. Entities correspond to 'objects' in the old security rules.

Attribute

A field or column that belongs to an entity. For example, the ordered unit of measure is an attribute of the Order Line entity. Attributes correspond to fields in the old security rules.

Operation

An action that you can take on an entity. The operations that can be controlled by processing constraints are Create, Update, Delete, Cancel and Split.

Processing Constraints Framework: It includes the set of APIs that will enable you to query the existence of any constraint against the operations you wish to perform on that entity or its attributes. Seeded constraints have the System box checked and cannot be modified.

Validation Template: Names a condition and defines the semantics of how to validate that condition. These validation templates can be used in the processing constraints framework to specify the conditions for a given constraint.

Record Set: A record set is a set of records that are bound by some common attribute values (for example all lines on an order). In the processing constraints framework, when you define constraining conditions, you may specify a record set to be validated for a given condition as defined by its validation template.

Scope: Given a record set and a condition, the scope (Any/All) defines how the validation should be performed on records of the record set. "All" requires the validation to be TRUE for every record in the set. "Any" requires the validation to be TRUE for at least one record in the set.

Conditions: The test(s) which must be passed for a constraint to be active. For example, a condition for a constraint might be that the order is booked.

Processing constraints are rules that control who can change what and when they

can change it. Processing constraints can prevent certain changes, but can also be set up to perform actions based on those changes.

With processing constraints, you can control: Who can make changes based on responsibility. A constraint (rule) may apply

to all responsibilities, to only a list of constrained responsibilities or to all

except a list of authorized responsibilities.

Who can make the change

More than just what can be updated. The following operations can be controlled: Create, update, delete, cancel, and split all at the entity level. For example, given a set of conditions you may not want to allow a user to create a new order line.

You can also control the update operation down to the attribute level. For example, given a set of conditions, you could choose to allow update to the warehouse field of an order line but not to the price list field.

Changes to entities. An entity roughly corresponds to a table or window. The entities you can control in Order Management are:

• Order Header• Order Line• Order Sales Credit• Line Sales Credit• Order Price Adjustment• Line Price Adjustment• Order Payment• Line Payment• Sales Agreement Header• Sales Agreement Line

Some scenarios where we can used processing constraints are given below.

1. No one can change the customer purchase order at the line level; your company requires that one sales order can relate to only one customer purchase order.

2. No one can add a line to an order after any of the lines on the order have been invoice interfaced.

3. A reason is required to cancel an order line after it has been booked. Navigate to the processing constraints window

4. Only the Customer Service Manager can change the discount percentage on an order line after the line has been shipped.

Processing Constraints Architecture

System will not allow to change the order type when order get booked. This is oracle seeded constraints as System Check box is checked.

While Order processing the above constraints will worked as soon as order type get changed on order header.

Business Requirement is client want to restrict a specific warehouse (warehouse id-100) for specific order type order type i.e. “Standard Sales Order”

To achieve this we need to set up: Validation Template Record Set Processing Constraints

Validation Template: Names a condition and defines the semantics of how to validate that condition. These validation templates can be used in the processing constraints framework to specify the conditions for a given constraint.

Created validation template with validation type as table for the column Order Type, Status and Warehouse with values as below.

Record Set: A record set is a set of records that are bound by some common attribute values (for example all lines on an order). In the processing constraints framework, when you define constraining conditions, you may specify a record set to be validated for a given condition as defined by its validation template.

N:Oracle Order Management: Setup: Rules :Security:Record Set Based On Primary Key check Box if this record set is selected using the primary key. There

can be only one primary record set for a given entity.

Processing Constraints: Set up processing constraints based on the condition and validation defined in validation template.

Before Defining Processing Constraints Run concurrent program “Generate Constraints Validation Package” which is required for creation of new validation templates or record sets. Run this program from the Tools option on the menu bar of either the Validation Templates or Record Sets window or from the navigation menu by selecting

Setup :Rules :Security :Generate Constraints Package. Run this program anytime you create, update, or modify your processing constraints.

Processing Constraints: Set up processing constraints based on the condition and validation defined in validation template.

Setup :Rules :Security :Processing Constraints : query the form Choose the Entity: Order Header

This means rule is system is using while order processing

Processing Constraints: Set up processing constraints based on the condition and validation defined in validation template.

Setup :Rules :Security :Processing Constraints : query the form : Applicable To

Here we can set the access of processing Constraints All Responsibilities: Constraint will Applicable to all user Authorized Responsibilities: only the responsibilities that you list will be allowed to perform

the action. All other users will be stopped from performing the action by the constraint. Constrained Responsibilities: all users except for the responsibilities defined will be able to

perform the action. The users that you list will be stopped from performing the action by the constraint.

Create Sales Order With Order Type “Standard Sales Order”

Enter restricted warehouse ID in the warehouse field on sales order header form i.e. 100 then after pressing tab system will raised an error message which we configured in PC.

“Processing Constraints Listing report” a seeded report present in the system which will used to collect all the information about all the processing constraints defined in the system based on the parameter selected

“Processing Constraints Listing report” Output

Oracle® Order Management Implementation Manual Release 12 Part No. B25975-03

THANK YOU!

Ajay KheldarSCM FUNCTIONAL CONSULTANT