Oracle Apps R12 - Order Management Tables and Description

The blog post details all the tables in Order management:

Table Name

Description

OE_ACTIONS_IFACE_ALL

This is the open interface table for Order Management action requests. User can populate this table with data to perform a variety of actions such as booking, hold application and removal, automatic attachments, fulfillment set application and removal, match and reserve for Configured items, get ship method and freight rates (both individually and together), and the linking and delinking of Configured items.

Oracle Apps Order Management - Overview of Price Lists

Price lists are essential to ordering products because each item entered on an order must have a price. Each price list contains basic list information and one or more pricing lines, price breaks, pricing attributes, qualifiers, and secondary price lists. Basic information includes the price list name, effective dates, currency, pricing controls, rounding factor, and shipping defaults such as freight terms and freight carrier.

Deferred COGS in Oracle Apps R12

The deferred COGS account is the new feature introduced in Release 12. The key fundamental behind the feature is that the COGS is now directly matched to the Revenue. In simple terms, this means, COGS for an order line will be recognized only if the revenue is recognized for that line making sure that the revenue and COGS are posted in the same month. Matching percentage is also taken care which ensures that revenue and cost are always in sync.

Oracle Order Management Item Orderability rule in R12

There is a new interface provided by oracle to define rules to restrict certain kind of items to be ordered based on certain rules / criteria.

Example:

Customer A may purchase all items except for repair items and promotional items.

Alternatively, Customer B buys only repair parts but is restricted from buying promotional items.

Oracle Apps - Standard order fulfillment process

Following are the steps involved in the standard order process:

Step 1: Enter/Book an Order

·    In this stage, sales order information is entered into the Order Entry system, including such things as Customer Name, Ship to Address, Bill to Address, Order Type, Pricing Agreement, Customer Purchase Order Number, Order Date, Currency, Price list, etc.

·     Much of this information will default in from the Transaction Type, the Customer, or defaulting rules. Check the blog post for defaulting rules

Validation Template for Processing Constraints in Oracle OM

Order Management provides you the ability to define your own validation conditions by the use of validation templates. A validation template names a condition and defines the semantics of how to validate that condition. Validation templates can be used in the processing constraints framework to specify the constraining conditions for a given constraint.