The following interface programs are involved in Order Management process..
1. Interface Trip Stop.
2. Inventory Interface
3. Order Management Interface
4. Workflow Background Engine.
The tables effected are
oe_hold_definitions (contains hold name would be defined as apart of setup)
oe_hold_sources (hold applied info would be saved in this)
oe_order_holds (contins the hold info in this as well)
Data to be passed sales order header id order line id hold id (type of hold) hold code like OEOH means hold at the header level OEOL hold at the line level.
OE_ORDER_PUB is the main API in OM. Using this API all data manipulation (Inserts updates deletes can be performed on a Sales Order and it's attributes. Besides these certain other action requests such as applying holds attachments booking etc. can also be processed using the Sales Order API. After this in Shipping we have WSH_DELIVERIES_PUB.CREATE_UPDATE_DELIVERIES for creating and updating deliveries for picked lines WSH_DELIVERIES_PUB.DELIVERY_ACTION for actions on created deliveries like PICK_RELEASE SHIP_CONFIRM
ONT is the application short name for Order Management in Oracle.
Create Sale order > in the Header Level - enter customer name whos should be having both Bill to and Sit to Address> enter Payment Terms> enter the pricing > enter the transaction Type of that sale, then go to Line item and pick the invenotiable ( or ono inventoribale item) items from item master from the Sub Inventroy Orginsation, then attch this line to a particular sales man or collection agent.
Save the data, ( Line statius is 'Entered') then book the order ( shows the line status as " line is awating shippment" ( order status will be 'booked' > release the sales order > ( Line status will be " Picked") and ship the Materail which eventually show the line status as 'closed'. this shows the inventroy is credited with inventory Cost and COGS is Debited
The next face is interfacing to AR ( Autoinvoicing Rule) - Customer is Debited and Sales is Credited.
enter the order:
oe-order-lines-all(flow_status_code = entered)
book the order:
oe_order_lines_all(flow_status_code = booked)
wsh_delivery_details(releases_status = R 'ready to release)
which items on sales order we need to take out from inventory.
normally pick release SRS program run from backend once this over.
wsh_delivery_detalis(release_status = S 'submitted for release)
items are transfered from salable to staging sub inventory.
wsh_delivery_details(released_status = Y 'released')
here ship confirm program run from backend and data removed from wsh_new_deliveries.
oe_order_lines_all ( flow_status_code =shipped)
wsh_delivery_details (released_status = shipped)
mtl_material_transactions (linked through source_header_id)
data deleted from mtl_demand & mtl_reservations
item deducted from mtl_onhand_quantities
this is also called recivables interface,that mean information moved to accounting area for invoicing details.
invoicing workflow activity transfers shipped item info to recevables.
then auto-invoice program imports data from this.
then effected tables : ra_customer_trx_all (trx_number is the invoice number)
ra_customer_trx_lines_all (line_attribute 1 & 6 ) linked to header_id
and lined_id for orders....
order line level table get updated with flow status & open flag.
oe_ordr_lines_all ( flow_status_code = shipped & open flag = N)
once we close the order oe_order_lines_all table get updated with flow_status_code as closed.