Or ac l eI n vent or y
Move Order Process Move order Tables 1) MTL_TXN_REQUEST_HEADERS: Move order headers, this stores the move order number in column (REQUEST_NUMBER)
!) MTL_TXN_REQUEST_LINES: Move order lines, this is the one that drives most "ueries and status chec#s $or the move order as each line can be transacted individuall% &) MTL_MATERIAL_TRANSACTIONS_TEMP: 'endin material transactions table also called the transaction temorar% table, this holds allocations that act li#e reservations on inventor% How to check whether move order is allocated? Quantity Detailed In the move order o rder lines table (MTL_TXN_REQUEST_LINES), the qantit! detailed re"le#ts the allo#ated qantit! "or a move order line$ The qantit! detailed mi%ht be %reater than the qantit! delivered i" a move order is allo#ated bt not transa#ted$ What happens when move order order is allocated? allocated? &hen a move order is allo#ated, allo#ated, a #orres'ondin% re#ord re#ord is inserted into the 'endin% 'endin% table (MTL_MTERIL_TRNSTI*NS_TEM+ (MTL_MTERIL_TRNS TI*NS_TEM+ as ell as lot-serial tables i" reqired)$ reqired)$ &hen the move order is transa#ted, the re#ord moves "rom the 'endin% table to the histor! table (MTL_MTERIL_TRNSTI*NS)$ Move order line status codes: The move order table (MTL_TXN_REQUEST_LINES) 'rovides the stats o" the move order in the LINE_STTUS #olmn as a nmeri#$ . In#om'lete / +endin% ''roval 0 ''roved 1 Not ''roved 2 losed 3 an#eled 4 +re ''roved 5 +artiall! ''roved 6 an#eled b! Sor#e 7o #an loo8 the stats #ode sin% sin% the belo sql SELECT lookup_code, substr(meaning, 1, 60) "eaning" !# m$g_lookups %&EE lookup_t'pe TL_T*+_E-EST_ST.T-S #/E lookup_code2
Move Order Status Verification - WIP Quantity Delivered vs Detailed in Move Order Lines (MTL_TXN_REQUEST_LINES) A !"at ta#les are used in t"e $ove order %ro&ess' 1) MTL_TXN_REQUEST_HEADERS:Move order headers, this stores the move order number in column (REQUEST_NUMBER). t has a status, but this is not used as much as the lines status to drive !unctionalit". 2) MTL_TXN_REQUEST_LINES: Move order lines, this is the one that drives most #ueries and status chec$s !or the move order as each line can be transacted individuall". 3) MTL_MATERIAL_TRANSACTIONS_TEMP:%endin& material transactions table also called the transaction tem'orar" table, this holds allocations that act li$e reservations on inventor". n allocation is here "ou 'ic$ a s'eci*c item in inventor" don to the lot, locator, serial, revision to move, but "ou do not actuall" 'er!orm. the move "et. 1. Create moe or!er: Q"a#t$t%: 1& Q"a#t$t% De'$ere!: NULL Q"a#t$t% Deta$'e!: NULL Q"a#t$t% Re("$re!: NULL L$#e Stat": 1 *I#+om,'ete) 2. A,,roe moe or!er: Q"a#t$t%: 1& Q"a#t$t% De'$ere!: NULL Q"a#t$t% Deta$'e!: NULL Q"a#t$t% Re("$re!: NULL L$#e Stat": 3 *A,,roe!) 3. A''o+ate moe or!er -or -"'' ("a#t$t%: Q"a#t$t%: 1& Q"a#t$t% De'$ere!: NULL Q"a#t$t% Deta$'e!: 1& Q"a#t$t% Re("$re!: NULL L$#e Stat": 3 *A,,roe!) . Tra#a+t moe or!er: Q"a#t$t%: 1& Q"a#t$t% De'$ere!: 1& Q"a#t$t% Deta$'e!: 1& Q"a#t$t% Re("$re!: NULL L$#e Stat": / *C'oe!)
NOTE: 0e# a moe or!er $ a''o+ate! a +orre,o#!$# re+or! $ $#erte! $#to te ,e#!$# ta4'e *MTL_MATERIAL_TRANSACTIONS_TEMP a 5e'' a 'ot6er$a' ta4'e $- re("$re!). 0e# te moe or!er $ tra#a+te! te re+or! moe -rom te ,e#!$# ta4'e to te $tor% ta4'e *MTL_MATERIAL_TRANSACTIONS).
a) E+am'le #uer" !or lin$in& move orders ith the 'endin& table SELECT mmtt.transaction_temp_id, to.or!ani"ation_id, to#.re$uest_num%er, to#.#eader_id, to.ine_num%er, to.ine_id, to.inventor&_item_id, to#.description, to#.move_order_t&pe, to.ine_status, to.$uantit&, to.$uantit&_deivered, to.$uantit&_detaied '(OM mt_t)n_re$uest_#eaders to#, mt_t)n_re$uest_ines to, mt_materia_transactions_temp mmtt W*E(E to#.#eader_id + to.#eader_id to#.or!ani"ation_id + to.or!ani"ation_id to.ine_id + mmtt.move_order_ine_id/
b) E+am'le #uer" lin$in& MT-_MTER-_TRNST/NS to the move order SELECT mmt.transaction_id, to.or!ani"ation_id, to#.re$uest_num%er, to#.#eader_id, to.ine_num%er, to.ine_id, to.inventor&_item_id, to#.description, to#.move_order_t&pe, to.ine_status, to.$uantit&, to.$uantit&_deivered, to.$uantit&_detaied '(OM mt_t)n_re$uest_#eaders to#, mt_t)n_re$uest_ines to, mt_materia_transactions mmt W*E(E to#.#eader_id + to.#eader_id to#.or!ani"ation_id + to.or!ani"ation_id
to.ine_id + mmt.move_order_ine_id to#.re$uest_num%er + 01MOum%er0/ 2
ind a *losed Move Order+ #ut No Sta,ed Inventory' T#ere are times 3#en a move order 3i cose, %ut t#e $uantit& is not moved from finis#ed !oods to a sta!in! su% inventor&. T#e most common case of t#is is a move order for a su% inventor& or item t#at is OT reserva%e. If t#e item is not reserva%e, no inventor& is sta!ed and t#e move order simp& coses 3it#out doin! an&t#in!. *o3ever, t#ere are rare occasions 3#en a move order coses 3it#out movin! $uantit& to sta!in! %ut s#oud #ave. In t#e case of a move order reated to a saes order, t#e saes order deiver& detai s#o3s pic4ed and (eeased to Ware#ouse after t#e move order is transacted.
0. 1hat is code !or move order status2 The move order table (MT-_T3N_REQUEST_-NES) 'rovides the status o! the move order in the -NE_STTUS column as a numeric. The !olloin& lists the various statuses as ell as 'rovides a SQ- to loo$ them u'. t the time this #uestion as entered, here are a list o! the statuses and codes 4 ncom'lete 5 %endin& ''roval 6 ''roved 7 Not ''roved 0 losed 8 ancelled 9 %re:''roved ; %artiall" ''roved < ancelled b" Source
Move order can be treated as a demand in the Min:ma+ 'lannin&, and %urchase Re#uisition can be created based on the Move order re#uisition demand. This !eature ill be use!ul, i! the Move order is created b" the end user and the material:issuin& authorit" ants to convert the move order into a %.R automaticall", hen su''l" is not available !or this Move order. But, there on=t be an" lin$ beteen the Move order number > the %urchase re#uisition number The drabac$s o! Move order arei) ?urin& Move order a''roval, the a''rover has to a''rove line b" line. This ill be a tiresome 'rocess, i! there are more than 4@@ lines in the Move order ii) There can be onl" one move order a''rover ('lanner) assi&ned !or one item. This ill be a 'roblem, i! the same item has to be used in diAerent de'artments > the Move order !or this item : !rom each de'artment has to be a''roved b" the res'ective de'artment head iii) There is no a''roval:hierarch" !or move:order.