Understanding data flow for Standard Order

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

Last week, got a mail from one of reader who requested for providing data flow of standard orders and Return Orders. o,here are the information for data flow. !ormally standard sales order "an be split into nine sub steps , whi"h #ointly "arried out by some module like $!%,O&, Pri"ing, hipping and 'R. Lets take ea"h sub steps with data flow "onditions. These are based out of the flow whi"h is available in ((.).(*.+. 1. Order ntr!

This is first stage when Order in enter in system.,hen the order is entered it basi"ally "reate a re"ord in order headers and Order Lines table. oe-order-headers-all ./ere the flow-status-"ode as entered0 oe-order-lines-all .flow-status-"ode as entered0 . order number is generated0

2.Order "oo#ing This is ne1t stage , when Order whi"h is entered in step ( is booked and 2low status "hanged from Entered to3ooked.'t this stage , these table get affe"ted. oe-order-headers-all .flow-status-"ode asbooked ,booked-flag updated0 oe-order-lines-all .flow-status-"ode as awaiting

shipping, booked-flag updated0 wsh-new-deliveries .status-"ode OP open0 wsh-delivery-details .released-status 456R457 ready to release0

ame time, 8emand interfa"e program runs in ba"kground 'nd insert into inventory tables mtl-demand $. %eser&ation

This step is required for doing reservations 9/E8:LE OR8ER PRO;R'& runs in the ba"kground and quantities are reserved.On"e this program get su""essfully get "ompleted , the mtl-reservations table get updated. '. (i)# %elease $deally pi"k release is the pro"ess whi"h is defined in whi"h the items on the sales order are taken out from inventory. !ormally pi"k release R program runs in ba"kground . On"e the program get

"ompleted these are the table get affe"ted< oe-order-lines-all .flow-status-"ode 456P$9=E8457 0 wsh-delivery-details .released-status 456 457 456submitted for release457 0 mtl-t1n-request-headers mtl-t1n-request-lines .move order tables./ere request is generated to move item from saleble to staging sub inventory0 &tl-material-transa"tions-temp .link to above tables through move-order-header-id>line-id 5.(i)# *onfir+ $tems are transferred from saleble to staging mtl-material-transa"tions mtl-transa"tion-a""ounts wsh-delivery-details .released-status 456?457456Released457 0 wsh-delivery-assignments ubinventory.

,.Shi- *onfir+ /ere ship "onfirm interfa"e program runs in ba"kground . 8ata removed from wsh-new-deliveries oe-order-lines-all .flow-status-"ode 456shipped4570 wsh-delivery-details .released-status 4569457 456 hipped4570 mtl-transa"tion-interfa"e mtl-material-transa"tions.linked through Transa"tion sour"e header id0 mtl-transa"tion-a""ounts 8ata deleted from mtl-demand,mtl-reservations $tem dedu"ted from mtl-onhand-quantities

7. nter .n&oi)e This is also "alled Re"eivables interfa"e, that mean information moved to a""ounting area for invoi"ing details. $nvoi"ing workflow a"tivity transfers shipped item information to Ora"le Re"eivables. ra-interfa"e-lines-all .interfa"e table into whi"h the data is transferred from order management0T Then 'utoinvoi"e program imports data from this Table whi"h get affe"ted into this stage are re"ievables base table. o ra-"ustomer-tr1-all ."ust-tr1-id is primary key to link it to tr1-lines o table and tr1-number is the invoi"e number0 ra-"ustomer-tr1-lines-all .line-attribute-( and line-attribute-@ are linked to header-id .or order number0 and line-id of the orders0 /.*o+-lete 0ine $n this stage order line leval table get updated with 2low status and open flag. oe-order-lines-all .flow-status-"ode 456shipped457, open-flag 45A!450

1.*lose Order This is last step of Order Pro"essing . $n this stage only oe-order-lines-all table get updated. These are the table get affe"ted in this step. oe-order-lines-all .flow-status-"ode 456"losed457,open-flag 45A!450

These are the typi"ally data flow of a order to "ash model for a standard order.