You are on page 1of 6

Item Orderability Rule in R12

Item Orderability - This is new feature introduced in Oracle R12.1.1.This is the rule that user can define to restrict the items/group of item (Category) that can be ordered from the Sales Order form. Because of the complex business scenario in the Modern time organization want to control which customer are allowed to order which product. Consider below scenarios: If a company is developing customer specific items, then specific item shall be sold to specific customer only. Few products may be banned in specific region. Few items may be sold thru specific channel only. Example: Online, Distributors, franchises, Sales Executive etc. Now Order management Provide a new utility in R12.1.1 to define the rule to restrict the Item to be sold, based on rules, this utility is name as Item Orderability Rules. It allows user to Order the Item based on the Rules. Item Orderability rules are defined at Operating Unit (OU) Level. Now lets have a deeper look at Item Orderability: Level at which rule can be built: As of Now Oracle has provided rules to control only at 11 attributes 01. Customer 02. Customer Class 03. Customer Category 04. Region 05. Order Type 06. Ship To 07. Bill To 08. Deliver To 09. Sales Channel 10. Sales Representative 11. End Customer Rule can be defined based on any combination of above attributes: Example:

Suppose one rule is built based on multiple attributes as done in above example: The OR condition is applicable when evaluating multiple conditions. In the example above, either the Customer Category OR Customer OR Sales Channel is taken into consideration. Criteria for the rule: Criteria can be Item or Item Category

If you select Category as a criterion then you will see Item Categories Codes from the Category Set which is assigned as Default Category Set for Order Entry functional area for that OU. Example: In our case Order Entry has Inv.Item category set assigned so we will be able see category codes from Inv.Item Category set only.

Item Validation Organization is referred to validate Item + Category combination Generally Available Flag: We can set up rules to define when an item or item category is generally not available (the Generally Available box is unselected) with the conditions available for that rule. For example, Item X is generally not available, however, since you have set up conditions at the Rule Level, it is available for a particular customer, or region or customer class. Conclusion: Generally Available box is unselected: Oracle will allow putting order for Criteria + ruling combination Generally Available box is Selected: Oracle will not allow putting order for Criteria + Rule combination This is illustrated in the example below: Case 1: Unselect Generally Available

This means, Item AS54999 is generally not available for all, but you want to sell it to Customer A. C. Networks only. So this rule allows putting order for Customer + Item combination.

Case 2: Select Generally Available

This means, Item AS54999 is generally available but you do not want Customer A. C. Networks to order it. So this rule does not allow putting order for Customer + Item combination

Effect of OM: Use Materialized View for Items LOV (Honors Item Orderability Rules) If the value of the profile option OM: Use Materialized View for Items LOV (Honors Item Orderability Rules) is set to Yes, then the Ordered Item LOV displays only those items which are based on the rules defined. The Ordered Item LOV is then dynamically populated based on Item Orderability Rules and the current attribute values on the line. If the value of the profile option OM: Use Materialized View for Items LOV (Honors Item Orderability Rules) is set to No, then the Ordered Items LOV lists all the items of the item validation organization of the current operating unit. This doesn't consider the defined item orderability rules, however if there is a defined rule that prevents the item from being ordered, then an error message is displayed while saving the order. You will not be able to save the order. Below is Simple test case for Item Orderability feature. Steps to Define the Item Orderability Rule1. 2. 3.

Select the Criteria (Item or Category. And Generally Available or not) Select criteria values (Item Number / Category Code) Select the Rules Level/s (by selecting any combinations of above 11 attributes)

4.

Select Rules Level value.

You might also like