This chapter covers the following topics:
The Oracle Applications organization models define organizations and the relationships among them in arbitrarily complex enterprises. It determines how transactions flow through different organizations and how these organizations interact with each other.
Operating Units and Pricing Security
Pricing security features are provided that enable you to:
Assign or reassign a single operating unit to price lists and modifiers.
Control which operating units can use pricing entities when pricing transactions.
If Multi-Org Access Control (MOAC) is enabled, the operating unit that can be assigned to a price list or modifier is based on the MO: Security Profile option. The operating unit value, which is set in the MO: Default Operating Unit profile option, appears if you clear the Global check box.
Using Qualifiers to Assign Multiple Operating Units
By using qualifiers, you can create price lists and modifiers that are operating unit specific. Operating unit is not a seeded qualifier. It is necessary to set up the attribute and mapping rules. Once the qualifier attribute of operating unit is available for use, it can be applied to price lists and modifiers. When a call is made to the pricing engine for a transaction in an operating unit, only those price lists and modifiers for the specified operating unit and global price lists/modifiers (applicable to all operating units) are evaluated by the engine.
Cross Order Volume Loader
The concurrent program accumulates all cross order totals for an operating unit, but does not summarize them across operating units. The engine considers only orders that a customer places with this sales organization; the engine does not consider orders that the customer places with other operating units. When running the cross order volume loader, you may specify that the load run for one operating unit. If specified as null, the engine summarizes for all operating units for which there are orders (assuming there is a multi-org install). If loading for multiple operating units, each summary is within an operating unit.
Operating Unit Specific Seeded Qualifiers and Pricing Attributes
Some of the seeded qualifiers attributes and pricing attributes in Oracle Advanced Pricing are specific to an operating unit. The following is a list of some seeded qualifier and pricing attributes that are operating unit specific:
| Type | Context | Qualifier Attribute |
|---|---|---|
| Qualifier | Customer | Site use |
| Qualifier | Customer | Bill to |
| Qualifier | Order | Line type |
| Qualifier | Order | Ship from |
| Qualifier | Volume | Period 1 order amount |
| Qualifier | Volume | Period 2 order amount |
| Qualifier | Volume | Period 3 order amount |
| Pricing | Volume | Period 1 item quantity |
| Pricing | Volume | Period 2 item quantity |
| Pricing | Volume | Period 3 item quantity |
| Pricing | Volume | Period 1 item amount |
| Pricing | Volume | Period 2 item amount |
| Pricing | Volume | Period 3 item amount |
QP: Item Validation Organization
You must set the profile option QP: Item Validation Organization to the level in your organization hierarchy at which you set prices when using Oracle Inventory. This profile value indicates the Oracle Manufacturing organizations that items are validated and viewed against when entering price lists or modifiers. You should set this profile value should be set to the master organization.
Note: If MOAC is enabled, each responsibility can have access to multiple operating units, and each operating unit can have its own item validation organization. However, profile QP: Item Validation Org can be set only at the responsibility or site level. Therefore, you should assign only operating units that share a common pricing item validation organization should be assigned to one pricing responsibility.
Modifier Type of Item Upgrade
When you define item relationships for item upgrade type of modifiers, the item relationship must belong to the same item organization as specified in QP: Item Validation Organization.
Related Topics