Automation Of Sto Process

Transcript

AUTOMATION OF STO PROCESS. • Stock Transport Process in SAP ERP System • Basic Scenarios STO can be categorized into four types depending on different scenarios. Scenarios SD/LE MM Intra-company STO Delivery type: NL PO type: In two steps Delivery item category: NLN  !B Stoc" transport or#$% wit& '!' '!' item category Billing relevance: Not relevant  NB Stan#ar# PO% wit& '(lan"' '(lan"' item category Movement type: )*+ Intra-company STO Delivery type: NL PO type: In two steps Delivery item category: NLN  !B Stoc" transport or#$% wit& '!' '!' item category Billing relevance: Not relevant  NB Stan#ar# PO% wit& '(lan"' '(lan"' item category Movement type: )*, ross-company STO Delivery type: NL PO type: in one step  NB Stan#ar# PO% wit& '(lan"' '(lan"' item category Delivery item category: NL Billing relevance: relevant to (illing Movement type: )*. ross-company STO Delivery type: NL in two steps Delivery item category: NL PO type:  NB Stan#ar# PO% wit& '(lan"' '(lan"' item category Billing relevance: relevant to (illing Movement type: )* Shipping Data and Dei!ery Due "nde# • o To deliver STO, it's necessary to have shipping data (EKPV table entry) tab in the STO. o I there is still open !"antity to be delivered, #deliv. creation date# (EKPV$%E&T) illed has val"e. hen all the !"antity has been delivered, the date ill be cleared. o I STO is ready to be delivered, syste* ill "pdate delivery d"e inde+ table VETV. • o Shipping Data Determination Shipping data (table EKPV) in STO is deter*ined depending on- $. S"pplying Plant %. Ship$to (c"sto*er o the receiving plant) (I $/  $/ P"rchasing $/ P"rchasing Order $Set "p Stoc0 Transer Order $/ &eine Shipping &ata or Plants) &. aterial aster &ata '. &elivery Type (I $/  $/ P"rchasing $/ P"rchasing Order $Set "p Stoc0 Transer Order $/ ssign &elivery Type and 1hec0ing 2"le) o Shipping data deter*ination- $. Sales rea- ro* s"pplying plant (T334) (See SP notes 456785, 4933:6, 493397, 49338:, ;3;679) %. Shipping 1ondition- dea"lt order type (<&%=) or delivery type (TV%K$&2T), otherise c"sto*er *aster data (K>VV$VS?E&)&elivery priority*aterial@c"sto*er@distrib"tion chain (K>T), otherise c"sto*er *aster data (K>VV$%P2IO) &. Anloading Point- ro* Ship$to, i available '. Shipping Point- loading gro"p@shipping condition@s"pplying plant (TVSTB) (. 2o"te- "s"al criteria or ro"te deter*ination (T2O%B) ). &elivery Type- P"rchase order category@doc"*ent type@s"pplying plant (T454V, dierent delivery types) *. 2o"te Sched"le- ith delivery sched"ling (T454V) +. %oading ro"p and Transportation ro"p- *aterial *aster data (2, 21) ,. %ang"age o aterial &escription- c"sto*er *aster data (K>4$SP2S) (to read *aterial *aster data ro* KT) $-. Incoter*s- c"sto*er *aster data, ro* p"rchase order  $$. Indicator or Order 1o*bination- c"sto*er *aster data $%. Indicator or Partial &eliveries- *aterial@c"sto*er@distrib"tion chain (K>T), otherise c"sto*er *aster data (K>VV$KBT%C) • Dei!ery Due "nde# ET/ o &ierent ro* delivery d"e inde+ o sales doc"*ent, VETV is the delivery d"e inde+ or stoc0 transport orders and contains the POs that are d"e or delivery. o Inde+ VETV is needed or selection in V%43D@V%3. I a STO cannot be listed in V%43D @ V%3, please chec0 hether the inde+ are "pdated correctly. o 2eport BKO2VETV o note 5448 can be "sed to reorganiFe the delivery d"e inde+ VETV. o Precondition o VETVVETV ill be illed (STO is relevant to delivery) i- / shipping data (EKPV) is illed, / delivery date in EKPV is not 33.33.3333 •  0reate Repenishment Dei!ery o 2eplenish*ent delivery can only be created by collective transaction. o Tcodes- $. V%43D (V%43?, V%43&, V%43C...) In "ser role, #ith p"rchase orders# indicator is lagged. %. V%3 (O"t o date) &. There is no dialog transaction to deliver STO. '. 1haracteristics o replenish*ent deliveries ro* STO (>ote- 8:8:6) 0ontro of Repenishment • Dei!ery • /oods 1o!ement o oods iss"e ith 54 creates a special stoc0 type, called Gstoc0$in$transitH in the receiving plant (?7T) o I replenish*ent delivery contains A, ater goods iss"e ith 54 *ove*ent, the A ill have stat"s #in transit#. (VEKP$STTAS J 3). o oods iss"e ith 5; (cross$co*pany) doesn=t create s"ch a stoc0 and contains only one line in the I *aterial doc"*ent o oods iss"e ith 5; (cross$co*pany) is nearly the sa*e as goods iss"e ith 534 to an e+ternal c"sto*er yo" can only s"* "p the stoc0 transport orders that are open or goods receipt to deter*ine hat is Gin transitH (stoc0 type- Gstoc0$in$transit$11H) o oods receipt (ith 434) is done via ?3@IO ith respect to the replenish*ent delivery. o Lo" can also "se inbo"nd delivery to post goods receipt. (Si*ilar as nor*al p"rchasing order) • o 2o3 Repenishment Dei!ery 4pdates STO PO istory (table EK?E) / hen replenish*ent delivery is created, it ill "pdate PO history ith delivery n"*ber, ite* n"*ber and delivery !"antity. / hen posting I, the *aterial doc"*ent ill also be "pdated to PO history. • o PO &elivery Sched"le (table EKET) / hen replenish*ent delivery is created, the delivery !"antity ill be c"*"lated to corresponding delivery sched"le. (EKET$%> ield). / hen posting I, the !"antity ill be c"*"lated to corresponding delivery sched"le. (EKET$ >). o • &elivery sched"le (EKET) *"st be consistent ith PO history (EK?E), otherise, short d"*p (*essageMtypeM+ E83;) *ight occ"r. One5step /oods "ssue o Set T454$A%4S J 1@>> that belongs to ite* category >%1@>%> in TVEPB (tcode VOV5) Automaticay 0reation of "nbound Dei!ery during %5step STO •  s o 2elease E11 5.33, yo" can also "se the a"to*atic inbo"nd delivery creation d"ring to$step stoc0 transers. The inbo"nd delivery is created "sing the o"tp"t deter*ination in the o"tbo"nd delivery. ter the goods iss"e has been posted s"ccess"lly, the syste* "ses a special "nction (o"tp"t type SPE&) to create the inbo"nd delivery. Pease read SAP note ,)($*) for more information. LOG_MM_SIT: Inbound Delivery with Stock in Transit (New ( !"LNMM_#$%_LOGMMSIT_IN&  Cill 2ES?& Str"ct"re ro* E?P 1o*ponent Str"ct"re 2O?I%%S $ SynchroniFe billing plans This doc"*entation is copyright by SP . Short text LOG_MM_SIT: Inbound Delivery with Stock in Transit (New Use  s o SP enhance*ent pac0age 7 or SP E2P 5.3 (SPMPP%M537), ?"siness C"nction MM, Stock in Transit, and Actual Costing , yo" can "se condition type SPE& (Stock Transfer Generates Inbound Delivery  to speciy that inbo"nd deliveries ith reerence to an o"tbo"nd delivery are a"to*atically created or stoc0 transer processes ith receiving val"ated stoc0 in transit. The olloing "nctions are available or inbo"nd deliveries ith stoc0 in transit•  t goods receipt yo" can post an inbo"nd delivery either in the standard ay (*ove*ent type 434), or via the receiving stoc0 in transit to the receiving plant (*ove*ent type 436). • I the !"antity changes d"ring the proo$o$delivery, the syste* "pdates the inbo"nd delivery. In transaction V%PO& (Proof of Delivery ), the syste* displays the dierence (PO& Overvie tab, Variance ro* ct"al &elivered "antity in Sales Anit). • The ne transaction ?7SIT (Display Stock in Transit ) allos yo" to • o &isplay receiving stoc0 in t ransit or the intra$co*pany and cross$co*pany process, by entering the inbo"nd delivery n"*ber  o &isplay iss"ing val"ated and receiving val"ated stoc0 in transit I yo" have created an inbo"nd delivery "sing condition type SPE&, yo" can post the *aterial ro* iss"ing val"ated stoc0 in transit to receiving val"ated stoc0 in transit in transaction V%PO&. To post into the receiving plant, yo" *"st "se *ove*ent t ype 436 in transaction V%;:> or IO. >ote- I yo" have to enter a handling "nit or the storage location in the receiving plant, post irst into t he val"ated stoc0 in transit o the receiving plant. Cro* the val"ated stoc0 in transit o the receiving plant, yo" can then post the goods receipt ith reerence to the inbo"nd delivery into the storage location ith *andatory handling "nit. Effects on Effects on Effects on Effects on Existing Data Data Transfer System Administration Customizing To set "p inbo"nd deliveries ith stoc0 in transit, yo" need to *a0e the olloing settings in 1"sto*iFing4. 1hec0 conir*ation control 0eyIn 1"sto*iFing, choose aterials anage*ent $/ P"rchasing $/ 1onir*ations $/ Set Ap 1onir*ation 1ontrol Cor the conir*ation control 0ey 333 (Inbound Delivery ), the olloing *"st be lagged "nder 1onir*ation Se!"ence- 4. o 1onir*ation is 2$2elevant chec0bo+ o 2 ith 2eerence to 1onir*ation chec0bo+ &eine condition type SPE&In 1"sto*iFing, choose %ogistics E+ec"tion $/ Shipping $/ ?asic Shipping C"nctions $/ O"tp"t 1ontrol $/ O"tp"t &eter*ination $/ aintain O"tp"t &eter*ination or O"tbo"nd &eliveries $/ aintain O"tp"t &eter*ination Proced"re. Select sche*a V43333 (Header utput ) and choose Control Data. 1hec0 that an entry e+ists ith condition type SPE& (Stock Transfer Generates Inbund Delivery ) and 2e!"ire*ent 38 (Stock Transfer Attac!"ent ID). 4. &eine delivery type In 1"sto*iFing, choose aterials anage*ent $/ P"rchasing $/ 1onir*ations $/ &eine Internal 1onir*ation 1ategories. 1hec0 that or conir*ation category % (Inbound Delivery ), the ne ield&elivery Type Inbo"nd Stoc0 in Transit (SiT) contains a delivery type or the process ith stoc0 in transit (or e+a*ple Inbound Delivery of #eceiving $aluated Stock in Transit  (E%ST). This delivery type *"st "se an ite* category (or e+a*ple E%ST) that "ses *ove*ent type 436 or another *ove*ent type ith posting string reerence 436. 1hec0 the olloingo In 1"sto*iFing or %ogistics E+ec"tion, "nder Shipping $/ &eliveries $/ &eine Ite* 1ategory &eter*ination in &eliveries, chec0 the ite* category that is assigned to this delivery type. o In 1"sto*iFing, "nder %ogistics E+ec"tion $/ Shipping $/ &eliveries $/&eine Ite* 1ategories or &eliveries, chec0 that *ove*ent type 436 or a *ove*ent type ith posting string reerence 436 is assigned to t his ite* category. 4. Set "p condition record Lo" create inbo"nd deliveries ith t his ite* category hen processing o"tp"t type SPE& d"ring the goods iss"e o an o"tbo"nd delivery. In transaction VV:: (C!ange utput % Condition #ecords& S!ipping ), ens"re that the correct condition records or the o"tbo"nd delivery type "sed (>112, >11;, >%I2, or >%I;) have been created or o"tp"t type SPE& or o"tp"t deter*ination. O"tp"t type SPE& ith role E (oods 2eceiver), *edi"* 8 (Special 'unction) and ti*e  (Send I""ediately ()!en Saving Application). Cor *ore inor*ation, see the olloing release noteso 1ross$1o*pany$1ode Stoc0 Transer and 1"sto*er &elivery (>e) o Intra$1o*pany$1ode Stoc0 Transer (>e) Further Information • SP %ibrary or SP E2P on elp Portal "nder http-@@help.sap.co*@erp $/ SP E2P 1entral 1o*ponent $/ SP E2P Enhance*ent Pac0ages $/ E2P 1entral 1o*ponent Enhance*ent Pac0age 7 $/ SP E2P 1entral 1o*ponent $/ %ogistics $/ aterials anage*ent () $/ Inventory anage*ent ($I) $/ anaging Special Stoc0s ($I) $/ Stoc0 Transer Asing a Stoc0 Transport Order  $/Processes ith Val"ated Stoc0 in Transit • 2elease note %OMMSIT- ?"siness C"nction , Stoc0 in Transit and ct"al 1osting SA?STME2EM%IST $ *erge e+ternal lists to one co*plete list ith i... logic or 2;"p  ddresses (?"siness ddress Services) This doc"*entation is copyright by SP . 4. SP2O /  / P"rchasing / PO / Set "p STO / ctivate "to*atic &elivery 1reation and 12 ?illing a0e s"re that yo" "se the proper doc"*ent type (#C#), s"pplying plant, and creation indicator (#L# in @ SPE@VMT454V$ATOM&E%V) Activate Automatic Delivery Creation and CRM Billin U!e In t"i! IM# activity$ you can activate t"e automatic creation o%  re&leni!"ment deliverie! and CRM Billin %or !toc' tran!&ort order!.   Re(uirement! o )ou mu!t u!e SAP CRM to e*ecute CRM Billin. o +"en you create an in,ound delivery %rom an out,ound delivery in SPM$ you mu!t de-ne a ne document ty&e in Cu!tomi/in %or Material! Manaement$ ,y c"oo!in Purc"a!in 01 Purc"a!e Order 01 De-ne Document Ty&e. )ou may co&y t"e document ty&e Stoc' tran!&ort order 23UB34$ ,ut you mu!t !et t"e 5endor indicator$ to en!ure t"at t"e intra0com&any !toc' tran!&ort order co&ie! t"e value! %rom t"e vendor in%ormation record. T"i!$ in turn$ en!ure! t"at t"e Con-rmation Control -eld in t"e !toc' tran!&ort order i! !et to In,ound delivery 23666734.   Activitie! I% you ant to create a re&leni!"ment delivery immediately a%ter creation o% t"e !toc' tran!&ort order$ !et t"e Auto Delv. indicator. T"i! doe! not a&&ly %or &urc"a!e order! t"at are not yet relea!ed and on   "old. I% ,illin i! re(uired in CRM Billin 2%or e*am&le$ %or cro!!0com&any and cro!!0,order !toc' tran!%er!4$ !et t"e CRM Bill indicator. Furt"er note! o I% you u!e t"i! %unction t"e !y!tem doe! not &er%orm an availa,ility 2ATP4 c"ec' "en it create! t"e delivery. It a!!ume! t"at t"e availa,ility "a! already ,een c"ec'ed durin !toc' tran!&ort order   &roce!!in. o T"e route i! determined in E*tended +are"ou!e Manaement 2SAP E+M4 only i% t"e automatic creation o% re&leni!"ment deliverie! i!   active. :. SP2O /  / P"rchasing / PO / Set "p STO / ctivate "to*atic &elivery 1reation or PO type and Shipping Point >OTE $There's one prere!"isite- please chec0 OSS note 43568. ;. o to t he transaction V%431A1, choose the delivery creation proile 'STO' and "nchec0 t he indicator 'eoro"te'. Auto picking 4) Shipping points(VMTVST) details screen enter the belo details "nder #Print pic0ing %ist# O"tp"t Type EK33 essage %ang"age E> >"*ber o essages 4 Send Ti*e  Trans*ission edi"* 4 :) via transaction VP!S"P under #shipping (special case)(V) and pic0ing list (EK33) enter yo"r shipping point, o"tp"t device, >a*e, S"i+4, S"i+ : Shipping Point $ O"tp"t&evice $ %P34 >a*e $ %IST4S S"i+ 4 $ EK33 S"i+ : $ KOI%ISTE The above setting sho"ld trigger a"to*atic pic0ing in &O Automatic P/"  yo" can create the PI to*atically by BATCH JOB "sing the progra* nder the VL23 transaction code. oto the Transaction code S;5 to create a Qob or the progra* SAPMSSY0 hich is the progra* or the ATO PI create a variant or t he &elivery doc"*ent types and sales organisation co*binatioans and add this variant to the bath Qob created in S;5. Set the ti*e o the Rob to r"n ater every 7 *in"tes, so once the Qob e+ected it ill pci0 all the &eliveries hich are pending or the PI. Automatic Biing  ter the PI done yo" can r"n S&?I%%&% progra* to create the ?illing or all the doc"*ent hich ere cleared and d"e or ?illing.VC3 $. R1-)BB&-671E(,89 %. SD-&-%67STO:%9 &. R(-R$-067;$-B<7;$-D9 '. =S:1O8"TOR:O4TB:DE;:/DS"67;%&9 (. SDB";;D;< R)-SBAT67>-)9< BAP":B";;"8/DO0:0REATE14;T"P;E67BAP":B";;"8/DO0:0REATE14;T"P;9 ). ?$"&