I came across this document in the blog http://functionalguy.blogspot.com/2008/05/data-flow-for-order-to-cash-cycle.html.
1. Order Entry
This is first stage, when the order is entered in the system; it creates a record in order headers and Order Lines table.
Enter header details: Once you enter details on the order header and save it or move it to lines, record goes to one table OE_ORDER_HEADERS_ALL FLOW_STATUS_CODE = ENTERED, BOOKED_FLAG = N), Primary key=HEADER_ID
No record exists in any other table for this order till now.
Enter Line details for this order: Enter different item numbers, quantity and other details in line tab. When the record gets saved, it goes to one table. Order header details will be linked with line details by order HEADER_ID. OE_ORDER_LINES_ALL (FLOW_STATUS_CODE = ENTERED, BOOKED_FLAG = N, OPEN_FLAG = Y) Primary key= LINE_ID
2. Order Booking
This is next stage, when Order is booked then the Flow status changed from Entered to Booked. At this stage, these below table get affected.
OE_ORDER_HEADERS_ALL
OE_ORDER_LINES_ALL
WSH_DELIVERY_DETAILS
WSH_DELIVERY_ASSIGNMENTS
In shipping transaction form order status remains "Ready to Release".
At the same time, Demand interface program runs in background and insert into inventory tables MTL_DEMAND, here LINE_ID come as a reference in DEMAND_SOURCE_LINE
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_DEMAND and MTL_RESERVATIONS table get updated. LINE_ID gets updated in DEMAND_SOURCE_LINE_ID in both the tables.
4. 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 release can be done from 'Release Sales Order' form or 'Pick release SRS' program can be scheduled in background. In both of these cases all lines of the order gets pick released depending on the Picking rule used. If specific line/s needs to be pick release it can be done from 'Shipping Transaction form. For this case Pick Release is done from 'Release Sales Order' form with Pick Confirm=NO.
Once pick release is done these are the tables getting affected:
If step 3 is not done then MTL_RESERVATIONS gets updated now.
WSH_NEW_DELIVERIES
WSH_DELIVERY_ASSIGNMENTS
WSH_DELIVERY_DETAILS
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES (LINE_ID goes as TXN_SOURCE_LINE_ID)
(Move order tables: Here request is generated to move item from Source (RM or FG) sub-inventory to staging sub-inventory)
MTL_MATERIAL_TRANSACTIONS_TEMP
MTL_SERIAL_NUMBERS_TEMP
MTL_SERIAL_NUMBERS
In shipping transaction form order status remains "Released to Warehouse" and all the material still remains in source sub-inventory. We need to do Move Order Transaction for this order. Till this no material transaction has been posted to MTL_MATERIAL_TRANSACTIONS
5. Pick Confirm/ Move Order Transaction
Items are transferred from source sub-inventory to staging Sub-inventory. Here material transaction occurs.
Order line status becomes 'Picked' on Sales Order and 'Staged/Pick Confirmed' on Shipping Transaction Form.
MTL_MATERIAL_TRANSACTIONS_TEMP
OE_ORDER_LINES_ALL
MTL_MATERIAL_TRANSACTIONS
MTL_TRANSACTION_ACCOUNTS
WSH_DELIVERY_DETAILS
WSH_DELIVERY_ASSIGNMENTS
MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP
MTL_SERIAL_NUMBERS
This step can be eliminated if we set Pick Confirm=YES at the time of Pick Release
6. Ship Confirm
Here ship confirms interface program runs in background. Data removed from WSH_NEW_DELIVERIES.
The item on the delivery gets shipped to customer at this stage.
OE_ORDER_LINES_ALL
WSH_DELIVERY_DETAILS
WSH_SERIAL_NUMBERS
MTL_TRANSACTION_INTERFACE
MTL_MATERIAL_TRANSACTIONS
MTL_TRANSACTION_ACCOUNTS
Data deleted from MTL_DEMAND, MTL_RESERVATIONS
Item deducted from MTL_ONHAND_QUANTITIES
MTL_SERIAL_NUMBERS_TEMP
MTL_SERIAL_NUMBERS
7. Enter Invoice
After shipping the order the order lines gets eligible to get transfered to RA_INTERFACE_LINES_ALL. Workflow background engine picks those records and post it to RA_INTERFACE_LINES_ALL. 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. At the same time records also goes in the table RA_INTERFACE_SALESCREDITS_ALL which hold details of sales credit for the particular order.
RA_INTERFACE_LINES_ALL (interface table into which the data is transferred from order management) Then Autoinvoice program imports data from this table which get affected into this stage are receivables base table. At the same time records goes in
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
8. Complete Line
In this stage order line level 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 gets updated. These are the table get affected in this step.
OE_ORDER_LINES_ALL
OE_ORDER_HEADERS_ALL
No comments:
Post a Comment