Oracle Order Management (OM)

The process flow for Internal Orders

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 organizations.





The Data Flow for Internal orders

Understanding data flow for “Standard Order”

August 5th, 2007 by Anand Print-Friendly Version 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 11.5.10.2.

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.
o ra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table and trx_number is the invoice number)
o 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
Understand “Drop Shipment” in Order Management?
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:
Here 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 ispo_requisitions_interface_all

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.