Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

‘Drop Shipment’, ‘BackOrders’ and ‘Back to Back Order’ …

Posted on April 11th, 2008 by Sanjit Anand ||Email This Post Email This Post

This was yet another query asked by one of the thought to combine in a post so that others can also understand.

Lets try to understand these key terms from Oracle Apps Product side:

1 Back Orders

  • The Oracle “term” backorder is a “status” on the order line or delivery line indicating that you have tried to release an order for picking in your warehouse, but that the pick release was UNSUCCESSFUL because there was no available inventory.(Backorder can be partial or complete). The Oracle term backorder does NOT mean that you have open purchase orders for the out-of-stock item from your vendors.
  • The term backorder is also used in business a little differently than in Oracle. The term “An item is on backorder” usually means that the item is not in stock, but the shipping company has already placed purchase orders from their suppliers to restock the item.
  • Back Order is when you do not fulfill the Sales Order, or if the inventory is out of stock for delivery to customer.

2 Drop Shipment

  • Drop shipment on the other hand is a method of order fulfillment where the organization taking the order does NOT maintain their own inventory for the drop-shipped product, but fulfill their orders through 3rd party vendors who directly ship to the end customer ordering the product.

For example,

  • A orders item x from B
  • B orders item x from C
  • C ships Item x to A.
  • B bills A for the order, C bills B for the order

3 Back to Back Orders

In Back to Back order the shipment process is also completed through OM as a standard order after the item is received against a PO.

greyBarrow What is the major difference between drop shipment and back to back order ?

  • In B2B the source will be internal but the item would be procured after the order is created or after the demand is made.
  • In Drop Ship the source will be external
  • In Drop Ship orders, material is directly shipped to the customer from the supplier. Thus, inventory is not affected. In this case, only logical receiving is done. But in the case of Back-to-Back orders, material is taken from inventory.
  • Drop Ship orders may have many Purchase Orders connected to them. In Back-to-Back orders one PO is tied to one Sales Order.

greyBarrowMore on Drop Shipment & Back to Back Orders(Functional)

High Points for EBS Base Functionality for Drop Shipment

  • Drop shipment order processing in EBS is managed using workflow
  • Drop ship functionality is based on source type of an order line (Internal/External)
  • You can automate your PO/BPA release creation based on ASL/sourcing rule information
  • Drop ship process uses standard OM workflows.
  • You can use Sales order Purchase order discrepancy report to identify discrepancies between the OM and the PO
  • There is a links OM and PO to provide visibility through entire supply chain Flow.

The entire Drop shipment process flow can be best understood as figure below:

drop shipment


greyBarrowPoints for Implementation Considerations

  • Order line attribute: Source Type (need to be external). You can be defaulted from item or order type
    • Menu -> Responsibility Order Entry Super User/setup/Orders/Types
    • Setup an order type using the cycle defined in the previous step (a),an order number source, a valid standard value rule set.
  • Item attributes (OM and Purchasing)

You need to do the setup for these attributes:

-Purchased (PO) Enabled
-Purchasable (PO) Enabled
-Transactable (INV) Enabled
-Stockable (INV) Optional
-Reservable (INV) Optional
-Inventory Item (INV) Optional
-Customer Ordered (OE) Enabled
-Customer Orders Enabled (OE) Enabled
-Internal Ordered (OE) Disabled
-Internal Orders Enabled (OE) Disabled
-Shippable (OE) Optional
-OE Transactable (OE) Enabled

  • Setup requisition import parameters
  • You can also use grouping by Vendor
  • You can also set the multiple distributions set to No
  • ASL and/or Sourcing rule relationship need to be setup for Automatic PO creation
  • Oracle recommends using a logical organization for drop shipment. Exclude this organization for planning purposes. It can be worked around using non nettable Dropship subinventory

greyBarrowBack to Back Order

As mention above this is ability to create specific supply orders for customer sales orders.
These are main features avaible in EBS

  • Designate specific items as B2B orderable
  • Enter sales order lines for these items, and have the supply automatically created via a requisition
  • Have the requisition converted into a Purchase Order or a release of a blanket Purchase Order
  • View the requisition number or PO number and its status from the Sales Order (using reservation details window)
  • Reserve the supply from the Requisition to the PO and finally to the Sales Order once the PO is received
  • Pick, ship and finally invoice the customer for the product.
  • Note to Buyer’s field in the requisition captures the Sales order information
  • Line status information shows the progress of the order
    PO Req Created
    PO Req Requested
    PO Created
    PO Received
  • If line is manually reserved it progresses to “Awaiting Shipping”
  • Changes and Cancellations on sales orders:
    • Reservation is changed
    • Notification sent to Buyer

Back to Back orders

Hope this makes a clarity on topics.

Posted in Oracle Order Management | 13 Comments »

Understand “Drop Shipment” in Order Management? -Part II

Posted on April 5th, 2008 by Sanjit Anand ||Email This Post Email This Post

Most of us heard about e-commerce site like ebay,,amazon,com which is very common place in advance countries like USA, UK & Singapore where people can sell or buy there product. Have you ever think ,what is similar situation in real world , when the the word ‘drop shipment’ comes to your mind. ……a business situation when the retailer or trader has no stock himself, instead giving customer details directly to the seller, and then saler than fills the order and send it to customer directly.How its sounds…

Drop shipping still remains a hot topic among SCM practitioner and apps Implementer , but even though it has many benefits, it isn’t the best option for every business. I am not going to walk through the pros and cons of the process , rather would like to walk through some of the key steps and processes which exist in real world which is important to understand the concept which helps during configuration with the product.

As in one of the last post , we have seen drop shipments is a method of fulfilling sales orders by selling products without the order taker handling, stocking, or delivering the products. The seller buys a product and the supplier ships the product directly to the seller’s customer .

In other word ,drop Shipment is a process where the customer places a purchase order on a company and this company instructs its supplier to directly ship the items to the customer.

Drop shipments are done because of the following reasons:

  • Customer requires an item that is not normally stocked
  • Customer requires a large quantity of the item which is not available with you
  • It is more economical when the supplier ships directly to the customer








double-arrow Types of drop shipment

If you see the real world scenarios this can be best categorize as mainly under three heads as:

  • Type 1 : Full Drop Shipment

Where the seller sends the purchase order to the supplier for the full quantity that the customer had ordered

  • Type 2 : Normal Shipments and Partial Drop Shipment

Under this scenario, If the seller has only part of the quantity available for shipping to the customer, then that quantity is shipped; a purchase order is created for the remaining quantity which the seller was not able to fulfill. This is typically true for single based item.

  • Type 3 : Normal Shipments and Full Drop Shipment

In this scenario, the seller ships some goods from inventory to the customer, and the other goods are always shipped from an external source (supplier).

double-arrowProcess Flow for Drop Shipment (Adopted from User Guide)

1Drop Shipments for Standard Items

  1. Enter an order for drop ship item
  2. Book the order
  3. Run Requisition Import
  4. Create a purchase order from the requisition
  5. Approve the purchase order
  6. Receive against the purchase order

2Forward drop ship flow for ATO model

  1. Enter a sales order for your drop shipped ATO model.
  2. Select your options.
  3. Schedule and book order (schedule date should default to request date for all lines).
  4. Create you configured item by progressing your order ATO Model line or running the Autocreate Configuration batch process.
  5. Verify order and line status.
  6. Create a supply order (dropship requisition) by progressing your configuration item line or running the Autocreate Dropship Requisition batch process
  7. Run the Oracle Purchasing Requisition Import to create a purchase requisition.
  8. Create a purchase order for the requisition.
  9. Approve the purchase order.
  10. Receive the purchase order.

3Forward drop ship flow for ATO Item

  1. Enter a sales order for your drop shipped ATO item
  2. Schedule and book order (schedule date should default to request date for all lines).
  3. Create a supply order (dropship requisition) by progressing your configuration item line or running the Autocreate Dropship Requisition batch process.
  4. Run the Oracle Purchasing Requisition Import to create a purchase requisition.
  5. Create a purchase order for the requisition.
  6. Approve the purchase order.
  7. Receive the purchase order.

4Non-SMC PTO model with drop shipped standard options

  1. Enter a sales order for your PTO model.
  2. Select options; source type on the components will default.
  3. Schedule and book the order.
  4. Run requisition import to create a purchase requisition.
  5. Create a purchase order for the requisition.
  6. Approve the purchase order.
  7. Receive the purchase order.

double-arrow Drop Shipment (Technical)

This section is going to help those who asked to provide some more granular details for drop shipment some time back.

As discussed above and in last post drop shipment is the process by which an organization takes orders from their customer and gets it fulfilled by a 3rd party. The selling organizatoin places a purchase order to teh 3rd party (supplier) who ships the ordered products to the end customer directly. There are a large number of tables that contain data related to drop ship orders. For example:

  • oe_order_headers_all and lines_all (order info)
  • po_requisition_lines_all, headers_all etc.( req. info)
  • po_headers_all, lines_all (po info)
  • oe_drop_ship_sources_all (this table contains the link between the req, po and the original order)

Moreover, there are many more tables involved in this therefore its better to have a understanding by corresponding ER diagram.


There is always a need to develop some of the custom report, therefore understanding of understanding table is very very important. Here are the same of underline tables details.

    • This table stores document shipment schedules for purchase orders, purchase agreements, quotations, and RFQs.
    • This table stores purchase document lines for purchase orders, purchase agreements, quotations, and RFQs.
    • This table stores document headers for purchase orders, purchase agreements, quotations, and RFQs.
    • This table stores purchase order distributions.
    • This table stores requisition headers.
    • This table stores requisition lines.
    • This table stores requisition distributions.
    • This is the Requisition Import interface table.
    • This table stores information for all order lines in Oracle Order Management.
    • This table stores relationships between order lines in oe_order_lines_all table and associated oracle purchasing requisitions in PO_REQUISITIONS_ALL and Oracle purchasing purchase orders in PO_LINES_ALL.
    • This table stores receiving shipment line information.

double-arrow Drop Ship @Release 12
There are no Changes in R12 for Drop Ship Flow same as R11 only

double-arrow Date flow for Drop Shipment

Reference Notes

  • Note 225434.1 : Drop Ship FAQ document
  • Note 130702.1 :Drop Shipments process

Posted in Oracle Order Management | 16 Comments »

Order Management(OM) Integration Options

Posted on February 25th, 2008 by Sanjit Anand ||Email This Post Email This Post

OM is one of the most complex modules in EBS, and in typical complex business model, the integration of other product or third party can’t be denied. Processing an Order requires integration with many other business areas. Most integration points with other Oracle products are implemented via PL/SQL-based APIs.Here is brief discussion for Order Management EBS Integration points.

OM Integration

double-arrowHow Order Management integrated with iStore?

OM records customer orders placed via iStore, Order Capture and other CRM applications. It validates setup for shipping and payment options along with providing order status and the shipping information to customers. Once the quote is converted into an order, you can only make changes to the order through Order Management, prior to booking.

double-arrowHow Order Management integrated with Telesales?

Telesales’ eBusiness Center has several integrations with Order Management. There is an Order tab to view order history and create new orders.

double-arrowHow Order Management integrated with Cost Management?

OM call the the Cost Management CST_COST_API to obtain cost from cst_item_costs or cst_quantity_layers when the Gross Margin feature of OM is enabled.

double-arrowHow Order Management integrated with Field Service?

Field Service Report requires specifically that you setup Price Lists, Units of Measure (UOM), and two Inventory Item Attributes in Order Management. Price Lists contain the list price for an item. Items could be material, but also labor and expenses like units of driving distance. Once material, expense and labor transactions for a task have been taken down on the Field Service Debrief, this information is updated to Charges. In Charges the list price for the item is received from Order Management and is used to generate an invoice for a customer.

double-arrowHow Order Management integrated with Depot Repair?

This is used by Depot Repair to create RMA and Sales Orders, validate customer accounts, and invoice customers for repairs.

double-arrowHow Order Management integrated with Install Base?

Information about Install Base trackable items is interfaced to Install Base in the following ways:

  • Shippable Items: For both orders and returns, information is interfaced to Install Base via Inventory Interface.
  • Non-Shippable Items: For both order and returns, information is interfaced to Install Base via the Order Management Fulfillment workflow activity Install Base also supports Internal Sales Order transactions by appropriately creating /updating item instances as a result of transactions between internal organizations such as pick transactions, shipments, and receipts.

double-arrowHow Order Management integrated with Service Contracts?

Service Contracts need to pulls information from the Install Base newly created customer records and creates an ownership record.

  • Warranty: A Warranty contract is created when a Serviceable product is shipped.
  • Extended Warranty: An Extended Warranty contract is created when an Extended Warranty is sold on a sales order. Oracle EAM & OM integration
  • Subscription: Fulfillment starts after the contract approval process.
  • RMA: Service Contracts sends Order Management RMA information

double-arrowHow Order Management integrated with Advanced Planning System/Global Order Promising/ ASCP?

Order Management uses Advanced Supply Chain Planning’s Global Order Promising functionality to check the availability of ordered items and to schedule order lines.Scheduled Order Lines are viewed as demand by the Advanced Planning System.

double-arrowHow Order Management integrated with Purchasing?

Order Management integrates with Oracle Purchasing in the following functional areas:

  • Return Receipts: Order Management uses the Oracle Purchasing Receipt functionality to handle Return receipts. When an item is received, Purchasing calls Order Management to indicate delivery and to get COGS information.
  • Internal Orders: Oracle Purchasing uses Order Import to create internal orders.
  • Drop-Ship Orders: Order Management integrates with Purchasing to fulfill drop-ship orders. It populates the PO requisitions interface table with information for order lines that need to be fulfilled via an external source.

double-arrowHow Order Management integrated with Bills of Material ?

This is integrated with BOM when models and kits are entered on sales orders.Normally OM uses the Bill of Material defined for the model or kit or explode the model into its components, for the purpose of the user selecting options and for shipping purposes.

double-arrowHow Order Management integrated with Workflow ?

Oracle Workflow is heavily used in EBS and specially to manage Order and Line processing. These PL/SQL based Workflow is a natural replacement for Order Cycles functionality. It provides a Graphical User Interfaces for defining activities, notifications, flows and viewing flow status.

double-arrowHow Order Management integrated with Advanced Pricing ?

OM is tightly integrated with Advance Pricing which includes price lists, modifiers, and agreements. Order Management, through its Sales Agreement functionality, creates price lists and pushes them into the Advanced Pricing tables. Order Management calls the Pricing Engine to make pricing requests during the processing of orders, and receives pricing information back from Advanced Pricing.

double-arrowHow Order Management integrated with Configurator ?

Order Management integrates with Oracle Configurator to support ordering and validation of configurations. The Configurator window is a Java Applet that can be launched from the Sales Order form.

double-arrowHow Order Management integrated with Oracle Payment ?

As we know Oracle payment is new product and OM accepts Credit Card information when entered on orders. It integrates with Oracle Payment to validate this information and get Credit Card authorizations. This information is then interfaced to Receivables.

double-arrowHow Order Management integrated with Receivables ?

Order Management integrates with Oracle Receivables in the following function areas:

  • Invoice Interface: Order Management sends invoices and credit memos to Receivables via the Invoice Interface workflow activity. The seeded Invoice Interface – Line workflow sub-process populates the Receivables interface table.
  • Receipts: Order Management calls Receivables’ Receipt API to create receipts for prepaid credit card orders. Order Management receives a payment-set id from AR when the receipt is created, and then passes that id back to AR in the autoinvoice tables at invoicing time so that the invoice can be matched to the receipt.
  • Tax: Order Management calls the Global Tax Engine APIs to default the Tax Code (ARP_TAX.GET_DEFAULT_TAX_CODE) and to calculate estimated tax (ARP_PROCESS_TAX.SUMMARY) for the order Line. The estimated tax value is now stored on the line and re-calculated only when any of the attributes affecting tax change. Information about the tax value is also stored as Line Price Adjustments.
  • Credit Management: If the Credit Management product is installed, notifications are sent to it by Order Management when an order or line goes on credit hold, to initiate a credit review. If the credit review results in a decision to approve the order, a business event is posted which OM subscribes to and then releases the credit hold.

double-arrowHow Order Management integrated with Payables ?

OM accesses the AP Bank Accounts table to populate the Credit Card LOV when an order is being entered with a payment type of Credit Card. Additionally, if a new credit card number is entered and the authorization of that card through iPayment is successful, Order Management calls an AR API to create a new bank account record for the customer in the Bank Accounts table.

double-arrowHow Order Management integrated with Inventory Management ?

  • Order Management integrates with Oracle Inventory Management through Managing Reservations.
  • You can create reservations to on-hand quantities from the Sales Orders form.

double-arrowHow Order Management integrated with Trade Management ?

Order Management can receive RMA orders and lines from Oracle Trade Management as part of its dispute handling functionality.

Posted in Integration, Oracle Order Management | 6 Comments »

Quick notes : ‘Order 2 Cash’ Cycle

Posted on February 21st, 2008 by Sanjit Anand ||Email This Post Email This Post

Things you should Know about Order to Cash Cycle.

double-arrowOrder Management

  • You enter sales and return orders within an operating unit.
  • You define price list and discount names for the entire instance. You can also define price list lines, discount lines, and quantity breaks for the entire instance. If you have more than one validation organization in the instance, you may experience error messages when querying a price list if the inventory item is not valid in your operating unit’s OM validation organization. Thus it is best to define price lists by operating unit.
  • You can check credit within an operating unit.
  • You assign order lines and shipments to a specific warehouse (inventory organization).
  • You pick release orders and print pick slips by operating unit.
  • You ship confirm orders and print shipping documents by inventory organization. You can ship from another operating unit, even if in a different set of books.
  • You receive returned goods in the inventory organization specified on the return.
  • Inventory and Manufacturing integration functions, such as reservations, available to promise checking, sales order demand, and assemble to order job creation are processed in the appropriate inventory organization.

double-arrow Order Management /Account Receivable

  • You setup customers for the entire instance but addresses for each operating unit.
  • You merge customers and addresses within an operating unit.
  • You report supplier/customer netting within an operating unit.

double-arrowAccount Receivable

  • You setup receivable account defaults within an operating unit.
  • You produce invoices, statements, and dunning letters within an operating unit.
  • You enter and track customer commitments within an operating unit.
  • You setup bank accounts and associated cash accounts within an operating unit till Release 11i, as subsequent changes has been made in R12.
  • Till Release 11i you can enter deposits and individual receipts by bank account within an operating unit.

Similar Post

Posted in Oracle Order Management, Oracle Receivable | 2 Comments »

Managing Return Material Authorization (RMA)

Posted on December 13th, 2007 by Sanjit Anand ||Email This Post Email This Post

Order Management provides sophisticated tracking of your return material authorizations (RMA). Returns from a customer occur for a variety of reasons including damage, shipment error, or sampling. Return material processing functionality enables you to manage customer expectations while controlling inventory receipts and customer credit processing.

These are the different types of senarios of Return Material Authorization (RMA) type which may exist :

  1. RMA with Credit Only : Your company issues a credit without the customer returning the product.
  2. RMA with Repair : Your customer returns a damaged product. Your company repairs and returns the product to the customer.
  3. RMA with Replacement : Your customer returns a product and your company sends a replacement product rather than issuing a credit.
  4. RMA With Receipt and Credit : Customer returns a product and receives credit.
  5. Returned Item Fails Inspection (Exception case) :Rarely happen , here your customer returns product, Company inspects product and rejects it. Company scraps product or sends product back to Customer. In this case, you have the option of performing an RMA transaction of type:
    • RMA with Repair,
    • RMA with Replacement,
    • RMA with Receipt and Credit.

dgreybarrow Below are setup features that have a significant impact on RMA processing.

  • Return Order Type/Line type for return order
  • Document Sequence
  • Item Attribute in Master Item
  • Price List for return order
  • Return reason codes

dgreybarrow Process Flow:

  • Create RMA Order using sales order window in Order Management
  • Book RMA Order
  • Receipt the RMA using receipts window in Purchasing
  • Check the on hand quantity of the item in Inventory to verify that correct quantity was received
  • Generate credit memo in Accounts Receivable (If Applicable)
  • View the credit memo in order management
  • Check the shipped and fulfilled quantity on the RMA line


dgreybarrow Below is accounting entry get created in this process

  • During receipt of RMA in Receiving Inventory
    • Receiving Inventory Dr.
    • COGS Cr.
  • During receipt into Subinventory
    • Material Dr.
    • Receiving Inventory Cr.
  • During generation of Credit Memo
    • Revenue a/c Dr.
    • Receivables a/c Cr.

dgreybarrow Below is the tables used in this process


Posted in Oracle Order Management | No Comments »

The Newbie’s technical Guide for Oracle OM

Posted on October 5th, 2007 by Sanjit Anand ||Email This Post Email This Post

Newbie, feel comfortable with this post. This is handy note for technical details for Order Management Tables.

When you create an Order with “Entered” status.

  • oe_order_headers_all 1 record created in header table
  • oe_order_lines_all Lines for particular records lines details is there
  • oe_price_adjustments When discount gets applied
  • oe_order_price_attribs If line has price attributes then populated
  • oe_order_holds_all If any hold applied for order like credit check etc.

Order Booking: This is next stage, when Order is booked then the Flow status changed from Entered to Booked.

  • oe_order_headers_all Booked_flag=Y Order booked.
  • wsh_delivery_details Released_status Ready to release

here is few things you will notice for this stage:

  • The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would be ‘BOOKED’
  • Record(s) will be created in the table WSH_DELIVERY_DETAILS with RELEASED_STATUS=’R’ (Ready to Release)
  • Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS.

Pick Released :Pick Release is the process of putting reservation on on-hand quantity available in the inventory and pick them for particular sales order

  • wsh_delivery_details Released_status=Y Released to Warehouse (Line has been released to Inventory for processing)
  • wsh_picking_batches After batch is created for pick release.
  • mtl_reservations This is only soft reservations. No physical movement of stock

Full Transaction

  • mtl_material_transactions No records in mtl_material_transactions
  • mtl_txn_request_headers
  • mtl_txn_request_lines
  • wsh_delivery_details Released to warehouse.
  • wsh_new_deliveries if Auto-Create is Yes then data populated.
  • wsh_delivery_assignments deliveries get assigned

Credit Chk Details

  • oe_credit_check_rules To get the Credit Check Againt Customer.

Cancel Orders details

  • oe_order_lines_all

Hold Relaese

  • oe_hold_releases_all Hold released Sales Order.

Pick Confirm/ Move Order Transaction: Here items are transferred from source sub-inventory to staging Sub-inventory.

  • wsh_delivery_details Released_status=Y Hard Reservations. Picked the stock. Physical movement of stock

Ship Confirm: Items are loaded in Truck/ Transportations Mode for the delivery to Customers

  • wsh_delivery_details Released_status=C Y To C:Shipped ;Delivery Note get printed Delivery assigned to trip stopquantity will be decreased from staged
  • mtl_material_transactions On the ship confirm form, check Ship all box
  • wsh_new_deliveries If Defer Interface is checked I.e its deferred then OM & inventory not updated. If Defer Interface is not checked.: Shipped
  • oe_order_lines_all Shipped_quantity get populated.
  • wsh_delivery_legs 1 leg is called as 1 trip.1 Pickup & drop up stop for each trip.
  • oe_order_headers_all If all the lines get shipped then only flag N

Price Details

  • qp_list_headers_b To Get Item Price Details.
  • qp_list_lines

Items On Hand Qty

  • mtl_onhand_quantities TO check On Hand Qty Items.

Sales Credit Sales -Credit Information(How much credit can get)

  • oe_sales_credits

If you have any attachment , then these tables are used

  • fnd_attached_documents Attched Documents and Text information
  • fnd_documents_tl
  • fnd_documents_short_text

Blanket Sales Order

  • oe_blanket_headers_all Blanket Sales Order Information.
  • oe_blanket_lines_all


Invoice is generated in ERP once Autoinvoice has been run

  • wsh_delivery_details Released_status=I Need to run workflow background process.
  • ra_interface_lines_all Data will be populated after wkfw process.
  • ra_customer_trx_all After running Autoinvoice Master Program for
  • ra_customer_trx_lines_all specific batch transaction tables get populated

Payment Terms

  • ra_terms Payment terms

dgreybarrow Let took the flow part for O2C.

Here are assocaited tables and underline details. for more insight on O2C, refer to this post.

The Order To Cash cycle of any industry includes following steps:

  • Order Entry: This is first stage, When the order is entered in the system
  • Order Booking: This is next stage, when Order is booked then the Flow status changed from Entered to Booked.
  • Pick Release: Pick Release is the process of putting reservation on on-hand quantity available in the inventory and pick them for particular sales order
  • Pick Confirm/ Move Order Transaction: Items are transferred from source sub-inventory to staging Sub-inventory.
  • Ship Confirm: Items are loaded in Truck/ Transportations Mode for the delivery to Customers
  • Invoice Generation: Invoice is generated
  • Close Order


Hope this helps.

Posted in Oracle Order Management | 4 Comments »

Understanding data flow for “Internal Orders”

Posted on August 6th, 2007 by Sanjit Anand ||Email This Post Email This Post

The process flow for Internal OrdersInternalOrderFlow

Internal orders normally start with creation of requisitions in Oracle Purchasing (which is created as Internal Sales Orders) .

Once the requisitions created from the MRP and Inventory modules, the Requisition Import program must be run in order to move records from the requisition interface tables to the historical PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL and PO_REQ_DISTRIBUTIONS_ALL.

Now next is to create internal requisitions from Purchasing module.When each requisition is approved, data will be inserted into the MTL_SUPPLY table. When the items on the requisition are stocked in inventory, the supply data can be viewed from the inventory form called Item Supply/Demand.

Once the Internal Requisition is approved, a user should run Create Internal Sales Orders (from a Purchasing responsibility) to load the internal sales orders interface tables called in Order Entry.

After the Creation of Internal Sales Orders has completed, a Import Orders concurrent program need to run from an Order Management.

at this stage, Oracle order Workflow will process the internal sales order using the workflow definition listed for the Transaction Type definition in Order Management. When the workflow completes the Shipping Network is checked to see if the Transfer Type between the source and destination organization is In transit or Direct.

You can use Oracle Order Entry/Shipping to define order cycles, approvals and holds.

Internal Requisitions use the Account Generator, which automatically builds account distributions. You can specify only one accounting distribution per inventory sourced line.

This internal requisition process provides the features needed to define your inter- organization shipping network. For transfers between two organizations, you can specify whether to use in transit or direct shipments. You can also require internal requisitions for transfers between specific organization.

The Data Flow for Internal orders


Posted in Oracle Order Management | 6 Comments »

Understanding data flow for “Standard Order”

Posted on August 5th, 2007 by Sanjit Anand ||Email This Post Email This Post

Last week, got a mail from one of reader who requested for providing data flow of standard orders and Return Orders. So,here are the information for data flow. Normally standard sales order can be split into nine sub steps , which jointly carried out by some module like INV,OM, Pricing, Shipping and AR. Lets take each sub steps with data flow conditions. These are based out of the flow which is available in

1. Order Entry

This is first stage when Order in enter in system.When the order is entered it basically create a record in order headers and Order Lines table.

  • oe_order_headers_all (Here the flow_status_code as entered)
  • oe_order_lines_all (flow_status_code as entered) ( order number is generated)

2.Order Booking

This is next stage , when Order which is entered in step 1 is booked and Flow status changed from Entered to Booked.At this stage , these table get affected.

  • oe_order_headers_all (flow_status_code as booked ,booked_flag updated)
  • oe_order_lines_all (flow_status_code as awaiting shipping, booked_flag updated)
  • wsh_new_deliveries (status_code OP open)
  • wsh_delivery_details (released_status ‘R’ ready to release)

Same time, Demand interface program runs in background And insert into inventory tables mtl_demand

3. Reservation

This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background and quantities are reserved.Once this program get successfully get completed , the mtl_reservations table get updated.

4. Pick Release

Ideally pick release is the process which is defined in which the items on the sales order are taken out from inventory.

Normally pick release SRS program runs in background . Once the program get completed these are the table get affected:

  • oe_order_lines_all (flow_status_code ‘PICKED’ )
  • wsh_delivery_details (released_status ‘S’ ‘submitted for release’ )
  • mtl_txn_request_headers
  • mtl_txn_request_lines
    (move order tables.Here request is generated to move item from saleble to staging sub inventory)
  • Mtl_material_transactions_temp (link to above tables through move_order_header_id/line_id

5.Pick Confirm

Items are transferred from saleble to staging Subinventory.

  • mtl_material_transactions
  • mtl_transaction_accounts
  • wsh_delivery_details (released_status ‘Y’‘Released’ )
  • wsh_delivery_assignments

6.Ship Confirm

Here ship confirm interface program runs in background . Data removed from wsh_new_deliveries

  • oe_order_lines_all (flow_status_code ‘shipped’)
  • wsh_delivery_details (released_status ‘C’ ‘Shipped’)
  • mtl_transaction_interface
  • mtl_material_transactions(linked through Transaction source header id)
  • mtl_transaction_accounts
  • Data deleted from mtl_demand,mtl_reservations
  • Item deducted from mtl_onhand_quantities

7.Enter Invoice

This is also called Receivables interface, that mean information moved to accounting area for invoicing details.

  • Invoicing workflow activity transfers shipped item information to Oracle Receivables.
  • ra_interface_lines_all (interface table into which the data is transferred from order management)T
  • Then Autoinvoice program imports data from this
  • Table which get affected into this stage are recievables base table.
    • ra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table and trx_number is the invoice number)
    • ra_customer_trx_lines_all (line_attribute_1 and line_attribute_6 are linked to header_id (or order number) and line_id of the orders)

8.Complete Line

In this stage order line leval table get updated with Flow status and open flag.

  • oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)

9.Close Order

This is last step of Order Processing . In this stage only oe_order_lines_all table get updated.

These are the table get affected in this step.

  • oe_order_lines_all (flow_status_code ‘closed’,open_flag “N”)

These are the typically data flow of a order to cash model for a standard order.

Posted in Oracle Order Management | 24 Comments »

Understand “Drop Shipment” in Order Management?

Posted on July 4th, 2007 by Sanjit Anand ||Email This Post Email This Post

Order Management allows you to enter drop-ship sales orders as well as standard sales orders.

It means you can receive orders for items that you do not stock or for which you lack sufficient inventory, and have a supplier provide the items directly to your customer.



The best can be described as:


These are the following activity takes place when you have drop shipment

  • Supplier
    • Warehouse Item
    • Ship order
    • Shipment notification
  • Order Entry
    • Enter customer
    • Enter order
    • Demand order (optional)
    • Cancel order (optional)
    • Close order
  • Purchasing
    • Create and send Purchase Order
    • Enter shipment notification in system
  • Receivables
    • Create invoice
    • Collection of payment
    • Receipt

hence, drop ship order items ship directly from a supplier to the customer of the order processing company. A purchase requisition, then a purchase order, is generated to notify the supplier of the requirement. After the supplier ships the order, it notifies Purchasing to enter this information in the Purchasing module.

What are the advantages of Drop Shipment Orders?

These are the benefits:

  • No inventory is required
  • Reduced order fulfillment processing costs
  • Reduced flow times
  • Elimination of losses on non-sellable goods
  • Elimination of packing and shipping costs
  • Reduced inventory space requirements
  • Reduced shipping time to your customer
  • Allows you to offer a variety of products to your customers

How to understand the dataflow for Drop shipment Orders?

To understand, here are the processes divided in sub process and the underline activity is highlighted here:

DpshipmentflowHere are the Details as per Mark

1.Order Entry

Here the activity is entering process where oe_order_headers_all (flow_status_code as entered) oe_order_lines_all . The order is booked as DROP SHIP

2. Order Booking

3. The Purchase Release program passes information about eligible drop-ship order lines to Oracle Purchasing.The interface table which gets populated is

4. After Purchase Release has completed successfully, run Requisition Import in Oracle Purchasing to generate purchase requisitions for the processed order lines. The Requisition Import program reads the table po_requisitions_interface_all validates your data, derives or defaults additional information and writes an error message for every validation that fails into the po_interface_errors table.The validated data is then inserted into the requisition base tables po_requisition_headers_all,po_requisition_lines_all,po_requisition_distributions_all.Then use autocreate PO fuctionality to create purchase orders and then perform receipts against these purchase orders

7. After the goods are successfully received invoices for vendors are created in accounts payables as in normal purchase orders.

8. Invoices are generated for customers In account receivables.

9. oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)

10. oe_order_lines_all (flow_status_code ‘closed’, open_flag “N”)

Hope this is great help to understand the flow.

Posted in Beginner, Oracle Order Management | 29 Comments »

What is In “Order Import”

Posted on May 27th, 2007 by Sanjit Anand ||Email This Post Email This Post

This is yet another powerful tool in EBS to quickly new, changed, and completed Sales Orders or Returns from

  • Legacy System
  • EDI Gateway transactions
  • Other EBS applications like purchasing, contracts etc
  • Other front end applications (web based, 3rdparty )

Order Import Interface consists of Open Interface tables.

Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting the Orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within Order Management. Valid transactions are then converted into Orders with Lines, Reservations, Price Adjustments, and Sales Credits in the base Order Management tables.

dgreybarrow Features of Order Import

  • Have status of imported orders and Workflow
  • use for Cancellation
  • This update existing orders
  • This importing closed orders
  • This add customer
  • This importing Price Adjustments
  • this importing returns (referenced and non referenced)
  • This is use Manual and Automatic Pricing
  • This will do Price Comparison (with customer price)
  • This also check Payment term comparison (with customer terms)
  • Credit Checking , holds and releases
  • Notes and attachments
  • Validating data
  • Defaulting rules
  • Processing constraints
  • Customer item number
  • Corrections form
  • Validate Only Mode
  • Order Import Statistics Concurrent Program


Interface tables for Order Import


dgreybarrow First timer

These are the steps associated in doing interfacing :

  • Set up Order Source
  • Populate data into interface tables for that source
  • Run the order import concurrent request or Import using the corrections form
  • Query the imported or updated order in Order Organizer

In any time if you encounter error you can use the Order Import Correction window to examine the Order and optionally correct data, if it fails the Import process. You can use the Error Message window to determine if your data failed to import.

dgreybarrowSteps by step

Step 1 :Pre-Requisite setup

The following steps are prerequisites to importing Orders:

  • You can set up every aspect of Order Management that you want to use with imported Orders, including Customers, Pricing, Items, and Bills.
  • You can define and enable your Order Import sources using the Order Import Sources window.
  • Determine if you should submit the Order Import Statistics concurrent program.

Before that , the following Profile Options must be set-up prior to importing Orders:

  • OM: Item Validation Organization – Determines the Organization used for validating Items and Bills of Material structures.
  • OM: Reservation Time Fence – This profile option controls automatic Reservations during scheduling.
  • OM: Apply Automatic Attachments – This profile option determines whether Rule-based attachments are applied without user intervention.

Step 2 :Populate data into interface tables for that source

Importing Order Header Information into OE_HEADERS_IFACE_ALL Table

  • Populate your data into table OE_HEADERS_IFACE_ALL which is a multi-org table for Sales Order Headers Open Interface.
  • This table stores Order Header information that is imported from a feeder system into Oracle Order Management using Order Import
  • A record has be inserted into Order Headers Interface table, for any operation on the Order. The orig_sys_document_ref column is referred when submitting the Order Import Concurrent program

Importing Order Lines Information into OE_LINES_IFACE_ALL Table

  • Populate your data into table OE_LINES_IFACE_ALL which is a multi-org table for Sales Order Lines Open Interface.
  • This table stores Order Lines information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Customer Information into OE_CUSTOMER_INFO_IFACE_ALL Table

Importing Customer related information is optional. Use this step, only if Customer Accounts / Contacts / Addresses need to be imported, while importing Orders into Oracle Applications.

  • Populate your data into table OE_CUSTOMER_INFO_IFACE_ALL is used to add new Customer, its Address and Contact information.
  • New Customer can be added by populating the required columns in this table, for that Customer new Address can be added, and for these new Account and Addresses, Contact information can also be added using this table
  • If you are importing make sure parent_Customer_Ref must be populated in case the current record needs to be linked to a Parent Customer record.
  • In case the Customer is a Person, columns First_Name, Last_Name, etc. must be populated for Customer_Info_Type_Code = ACCOUNT.

Importing Pricing Adjustments into OE_PRICE_ADJS_IFACE_ALL Table

Importing Pricing Adjustments is an optional .This should be included in Order Import, only if Price Adjustments need to be imported

  • Populate your data into table OE_PRICE_ADJS_IFACE_ALL is a multi-org open interface table for Sales Order/Line Price Adjustments.
  • This table stores Price Adjustment information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Pricing Attributes into OE_PRICE_ATTS_IFACE_ALL Table

Importing Pricing Attributes is an optional . Include this step, if Pricing Attributes need to be imported for the Order.

  • Populate your data into table OE_PRICE_ATTS_IFACE_ALL .
  • This Table stores Pricing Attributes information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Lot Serial Information into OE_LOTSERIALS_IFACE_ALL Table

Importing Lot Serials is an optional step. Include this step, only if Lots/Serial Number information needs to be imported for the Order.

  • Populate your data into table OE_LOTSERIALS_IFACE_ALL table .
  • This table used for Return Line Lot Serials Open Interface.
  • This table stores Return Line Lot Serial information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Reservation Information into OE_RESERVTNS_IFACE_ALL Table

This is an optional step. Include this step, only if Reservation information needs to be imported for the Order.

  • OE_RESERVTNS_IFACE_ALL need to be populated.
  • This table stores Reservation details that need to be imported.

Importing Sales Credit Information into OE_CREDITS_IFACE_ALL Table

Importing Sales Credits is an optional . use this step, only if Sales Credits information needs to be imported for the Order.

  • This is a multi-org table for Sales Order/Line Credits Open Interface.
  • This table stores Sales Credits information that need to be imported.

Step 3 :Populate data into interface tables for that source

You can initiated by submitting a Order Import Concurrent program.

Navigate to Order Management Super User : Orders, Returns : Import Orders : Order Import Request.

This program have these parameters:

  • Order Source : Choose a specific Order Import source that you have defined in step 1 which you setup via Order Import Sources window.
  • Order References: You can enter the System Document Reference, if you want to run Order Import for a specific Order.
  • Validate Only (Yes/No): Choose whether to validate only the data in the interface tables. If ‘Yes’, the Order will be validated, but not imported into the base Orders tables. The default value is ‘No’.

If you are first timer , you can run the Order Import process in the Validation-only mode. This mode allows the transaction to be validated against all the Order ManWelcome to It’s All In OrderIt’s All In Orderagement Rules, but does not pass valid transactions to the base Order Management tables.

If you choose, you can run production transactions in Validation-only mode for a preview of exceptions. This will allow you to make necessary corrections to the transactions in the Order Import window, then choose the Validate button to perform a validation check.

The Validation-only mode may also facilitate testing of transactions through Order Import even in a production environment to take advantage of all the setup in the production environment.

Step 4 :Corrections to Imported Data from Order Import Corrections Window

If is needed if you stuck or encountered error in the concurrent program. Navigation would be

Navigate to Order Management Super User : Orders, Returns : Import Orders : Corrections .

If any corrections to the imported data are required, changes to the data can be done from the Corrections window. Once the required changes are made, the same window can be used to launch the Order Import Process again.

You can use the request id of step 3 and click on find button to view the corrections window.

Step 5 :Verify the Imported Order Information

Once the Order Import process has been completed successfully, the same can be verified with the following screens :

Navigate to Order Management Super User : Orders, Returns : Order Organizer.

In the Find window, enter values in Order Source and Order Source Reference fields.

Posted in Oracle Order Management | No Comments »

« Previous Entries Next Entries »