Item Orderability in Order Management R12.

An Oracle White Paper

May 2009

Summary
Item Orderability is one of the new features that come with Order Management Release
12.1. With this release, Oracle provides an easy way to define orderable products, based
on exceptions defined in the item orderability rules. It would be possible to apply
orderable products business rules to Items or Item Categories defined for an organization.
Based on the rules defined in the Orderability window, the user would be able to restrict
the Items that can be ordered from the sales order and quick sales orders windows.

Setup
I.
II.
III.

Define an Orderability Rule

Set the Profile OM: Use Materialized View for Items LoV
Run Refresh Order Management Materialized Views

I. Define an Orderability Rule

The purpose of Orderability Rule is to restrict the items that can be ordered from the sales
order and quick sales orders windows.
In Release 12.1 a new form has been introduced: Item Orderability form
(OEXITORD.fmb) and can be accessed from the following:
Order Management > Setup> Rules > Item Orderability

Figure1 Item Orderability Form

Every Orderability Rule is specific to an Operating Unit.

If the same rule needs to be applied on a different Operating Unit, this needs to be
specifically defined in the new OU.
The Ordered Item List of Values is populated by listing all the items available in the Item
Validation Organization of the current operating unit.

Figure 2 OM System Parameters form where Item Validation Org is set

The logic of the Orderability Rule is driven by the option Generally Available (a
checkbox in Item Orderability form OEXITORD.fmb):
a) If the Generally Available checkbox is checked:
The item (or item category) is available to ALL customers EXCEPT the ones that meet the
criteria mentioned at Rule Level region.
It is possible to provide multiple criteria when defining an orderability rule. The OR
condition is applicable when evaluating rule level combinations.
b) If the Generally Available checkbox is unchecked:
The item (or item category) is restricted to customers EXCEPT the ones that meet the
criteria mentioned at Rule Level region.
It is possible to provide multiple rule levels when defining an orderability rule. The OR
condition is applicable when evaluating multiple rule level combinations.
There are 11 Rule Levels that can be combined to create an Orderability Rule:
CUSTOMER,
CUSTOMER CLASS,
CUSTOMER CATEGORY,
END CUSTOMER,
ORDER TYPE,
SALES CHANNEL,
SALES PERSON,
SHIP TO LOCATION,
BILL TO LOCATION,
DELIVER TO LOCATION
and REGIONS.
(here REGIONS level is based on Shipping Regions defined in Oracle Shipping ).

If an Orderability Rule is already set for an item category, it is no possible to set a

different rule for an item which belongs to this category. The system will display the
following message:

Figure 3 Message displayed when an OR is already set at item category level

Also, if an orderability rule is already set for an item, it is not possible to set a different
rule for an item category which includes this item. The system will display the following
message:

Figure 4 Message displayed when an OR is already set at item level

Important: If you choose to enable this functionality, Sales orders created by any one of
the online or batch means, namely: Quick Sales Order form, Order Import, HVOP, EDI,
XML, APIs etc or orders coming from other order capturing applications such as Quoting,
iStore or third party applications will not be accepted in Order Management if the
incoming orders do not comply with item orderability rules.
The information regarding Item Orderability Rule is stored in the following tables:
OE_ITEM_ORDERABILITY (parent table) and OE_ITEM_ORDERABILITY_RULES
(child table). Orderability_ID column (present in both tables) maps parent and child
records.
OE_ITEM_ORDERABILITY table stores the item orderability header information such
as Operationg Unit, Item Level, Enabled Flag, Generally Available Flag.
OE_ITEM_ORDERABILITY _RULES table stores the item orderability rules
information and the descriptive flexfield columns.
Customers can use the public api OE_ITORD_PUB.Import_Item_orderability_rules to
import item orderability rules from external systems into OM.
In order to review the Item Orderability Rules already defined, Order Management
introduced a new report in R12.1 : Item Orderability Rules Listing Report
(OEXITORD.rdf ) which lists the item orderability rules by item or item category.

II. Set the Profile OM: Use Materialized View for Items LoV(Honours
Item Orderability Rules)
This is a site level profile option and controls the display of the Orderd Items list of values
from sales order line level.
1. If the profile OM: Use Materialized View for Items LoV (Honours Item
Orderability Rules) is set to No or null, then the followig logic is used:
1.1 If an Orderability Rule is defined for the item or item category, the restricted item
is visible in Ordered Item list of values at Sales Order line level, but the item will be
validated against the Orderability Rule. A message is displayed when saving the sales
order line having this item.

Figure 5 Message displayed when trying to save a SO having an OR in place

1.2 If there is no Orderability Rule defined for the item or item category, then the
Ordered Items LOV lists all the items of the item validation organization of the current
operating unit.
2. If the profile OM: Use Materialized View for Items LoV (Honours Item
Orderability Rules) is set to Yes, the Ordered Item list of value from Sales Order line is
based on the materialized view OE_ITEMS_MV and the following logic is used:
2.1 If an Orderability Rule is defined for the item or item category: On the Sales
Order level, The Ordered Item LOV displays only those items which are not restricted
by the orderability rules.
2.2 If there is no Orderability Rule defined for the item or item category: then the
Ordered Items LOV lists all the items of the item validation organization of the current
operating unit.
Note: using the materialized view by setting the profile option OM: Use Materialized
View for Items LoV(Honours Item Orderability Rules) to Yes gives a better
performance when entering Sales Order Lines and choosing the Items.

III. Run Refresh Order Management Materialized Views

Refresh Order Management Materialized Views (OEXITORDMV ) is a new
concurrent program in Order Management R12.1 which updates the item list of values,
displayed in the order entry form.

If the profile OM: Use Materialized View for Items LoV is set to Yes, the concurrent
request Refresh Order Management Materialized Views needs to be run in order to
refresh OM materialized views OE_ITEMS_ORD_MV, OE_ITEMS_MV.
The concurrent request needs to be run after changes are made to the item master, cross
reference, Customer Items or to the item orderability rules, to ensure that the item list of
values displays the latest items on the order entry form, based on orderability rules.

Simple test case performed in a Vision Demo instance, R12.1

Item MS_ASSEMB_ITEM needs to be restricted for order by all the customers, except for
the customer: A. C. Networks.
1. All the relevant item attributes have been checked in Item Master form, Order
Management tab. Also, make sure that the item is on a price list.

Figure 6 Item attributes at Item Master level

2. Create an Item Orderability Rule

Order Management> Setup > Rules > Item Orderability

Figure 7 Defining an Orderability Rule for MS_ASSEMB_ITEM

3. Go to Sales Order form and fill in a sales order for item MS_ASSEMB_ITEM, for
customer: A. C. Networks.
3.1 If the site level profile option: OM: Use Materialized View for Items LoV is set to
No or has a null value, the following behaviour is seen:
a) the item is visible on the list of values:

Figure 8 Ordered Item list of value from SO line level

b) The Item Orderability Rule is enforced when trying to save the Sales Order:

Figure 9 Message displayed when trying to save a SO line with an item having an OR in place

Despite the fact that the item is visible on the Ordered Item list of values, it cannot be
placed on the sales order line if the customer is A. C. Networks.
3.2 If the site level profile option: OM: Use Materialized View for Items LoV is set to
Yes, the following behaviour is seen:

Figure 10 Item MS_ASSEMB_ITEM is not displayed in Orderd Item LOV

The MS_ASSEMB_ITEM is not visible on the Ordered Item list of values for sales orders
filled for the customer: A. C. Networks.
4. Whenever a change is made on the Item level or Orderability Rule level, please run
Refresh Order Management Materialized Views concurrent request, if the profile OM:
Use Materialized View for Items LoV (Honours Item Orderability Rules) is enabled.

Diagnosing issues related to Item Orderability

1. Provide the output of Item Orderability Rules Listing Report.
Navigation: Order Management> View menu > Requests > Submit a new request.
Query for: Item Orderability Rules Listing Report
This report lists the item orderability rules by item or item category
2. Check if the Materialized View is used or not. Get the value for the profile option:
OM: Use Materialized View for Items LoV (Honours Item Orderability Rules).
Use the following query:
select p.profile_option_name , v.profile_option_value PROFILE_VALUE
from fnd_profile_options p , fnd_profile_option_values v
where p.profile_option_id = v.profile_option_id
and
p.profile_option_name = 'ONT_USE_MVIEW_FOR_ITEMS_LOV' ;
3. If the Materialized View is used, check when it was refreshed last time:
Use the following query:
select MVIEW_NAME , LAST_REFRESH_DATE FROM all_mviews where
mview_name = 'OE_ITEMS_MV' ;
8

Item Orderability in Order Management R12.1

Author: Marian Stan
Senior Technical Support Engineer
Global Product Support
Special thanks to Aditya Mallik, Manager of OM Development team for his great
help in reviewing and providing valuable suggestions for improving this whitepaper.

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
www.oracle.com
Copyright 2008, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only and the contents hereof are
subject to change without notice.
This document is not warranted to be error-free, nor subject to any other warranties
or conditions, whether expressed orally or implied in law, including implied
warranties and conditions of merchantability or fitness for a particular purpose. We
specifically disclaim any liability with respect to this document and no contractual
obligations are formed either directly or indirectly by this document.
This document may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.