Warehouse Management Scenario: Organizational Hierarchy and Processes in SAP

SAP TERP10 Preparation Presentation 8 Dr. Gábor Pauler, Associate Professor, Private Entrepeneur Tax Reg. No.: 63673852-3-22 Bank account: 50400113-11065546 Location: 1st Széchenyi str. 7666 Pogány, Hungary Tel: +36-309-015-488 E-mail: pauler@t-online.hu

Content of the presentation • 6.Warehouse Management Scenario • 6.1.Plot of Scenario • 6.2.Organizational hierarchy of IM • 6.3.Organizational hierarchy of WM • 6.4.Measure unit conversion problems between IM and WM • 6.5.Defining IM/WM organizational hierarchy in SAP Customizing • 6.6.Checking stocks and material movements in IM/WM • 6.7.Goods movements in IM • 6.8.Goods movements in WM • 6.9.Automated IM-WM goods movements processes • 6.10.MM:Maintain master data • 6.10.1.MM:Extend material master to new plant: GigaBike-Name, Plant1100:MM01 • 6.11.LO:Warehouse management • 6.11.1.LO:Display stock overview: GigaBike-Name: MMBE • 6.11.2.LO:Create stock transport order: GigaBike-Name: 1000PC: ME21N • 6.11.3.LO:Post Goods Issue: GigaBike-Name: Plant1000, Storage1010, 1000PC: MIGO • 6.11.4.LO:Display material document: 4900039891: MB03 • 6.11.5.LO:Display material document: 4900039891: MIGO • 6.11.6.LO:Post Goods Receipt: GigaBike-Name: Plant1100, Storage1110, 1000PC: MIGO

6.Warehouse Management Scenario: 6.1.Plot of Scenario • 6.1.Plot of Scenario • 6.1.1.MM:Material master: • Create material GigaBike-Name at new organizational level: • Plant = 1100(Munich) • Storage location = 1110 • Warehouse number = 001 • Storage type = 002 • 6.1.2.LE:Inventory Management: • Make stock transfer order 1000PC of GigaBike-Name To: • Plant = 1100(Munich) • Storage location = 1110 • Warehouse number = 001 • Storage type = 002 • From: • Plant = 1000(Hamburg) • Storage location = 0110 • Warehouse number = 110 • 6.1.3.LE:Warehouse Management: • Make storage bin BinName into Wareh=001|StorTyp=002|StorSec=001 • Put away 1000PCGigaBike-Name into BinName • Make storage bin BinName2 into Wareh=001|StorTyp=002|StorSec=001 • Move 100PCGigaBike-Name from BinName to BinName2 • Block 100PCGigaBike-Name inStorage location = 1110 • Observe where 1000PCGigaBike-Name was put in WM by the IM block • Put away 100PCGigaBike-Name into BinName • 6.1.4.LE:Physical inventory management • Perform PI for material GigaBike-Name, Plant1000, Storage0110: • Minus 21 difference (350 instead 371) found, post it • Set cycle counting for all FERT materials at Plant 1000 based on consumption from 2004

6.Warehouse Management Scenario: 6.2.Organizational hierarchy of IM: 1 Client Mandt MatMast Matnr Desc PlanPlant Plant Location VendMast Vendor Address GlobComp Comp InTaxParadise BranchComp CompCode HostCountry ManufPlant Plant Location • 6.2.DEF:Organizational hierarchy/basic definitions of SAP Inventory Management (IM) system:This tracks stocks (Készlet) mainly by purpose of their usage, instead of their physical location. • 6.2.1.Client (Kliens): group of companies owned by the same Holding. • 6.2.1.1.Company (Cég):Client:Comp = 1:m At most multinational companies, one Global company owns several local Branch companies:GlobComp:BranchComp = 1:m, due to tax optimization reasons (they create costs for each other, enabling Profit remittance (Profitkivonás) from host countries into offshore tax paradises. • 6.2.1.1.1.DEF:Plant (Gyár):Comp:Plant = 1:m, a logical plant. At most multinational companies, one physical plant is defined as two logical plants due to tax optimization reasons: • DEF:Manufacturing plant(Gyártó gyár): It is owned by local Branch company: BranchComp:ManufPlant = 1:m It has machines, hires workforce, has MatMast, BOM, Routing, Product costing defined. But it never owns and stores any stock (except spare parts for machines). Raw materials, and central manage-ment/advisory services are bought from Global company to generate local costs. • DEF:Planing plant(Tervező gyár): owned by Global company: GlobComp:PlanPlant = 1:m It purchases raw material stocks, therefore it has MatMaster, VendorMaster, PIR, BOM defined. But it does not have any machines, therefore local Manufacturing plants are hired, and finished goods are purchased from there to generate huge manufacturing costs globally. Then it has Custo-merMaster, SOP, SalesOrders,MRP defined to sell finished goods to end-user via globally owned Distribution Plants (Elosztó gyár). • PIR • Matnr • Plant • Vendor • PurchOrd • Matnr • Plant • Vendor • BOM • Matnr • Plant • BOM • Matnr • Plant • Routing • Matnr • Plant • SOP • Matnr • Plant • SalesOrd • Matnr • Plant • Custmr CustMast Custmr Address • ProdCost • Matnr • Plant

6.Warehouse Management Scenario: 6.2.Organizational hierarchy of IM: 2 Client Mandt GlobComp Comp InTaxParadise BranchComp CompCode HostCountry PlanPlant Plant Location ManufPlant Plant Location • 6.2.1.Client(Kliens): • 6.2.1.1.Company(Cég):Client:Comp = 1:m • 6.2.1.1.1.DEF:Plant (Gyár):Comp:Plant = 1:m • 6.2.1.1.1.1.DEF:StorageLocation(Tárhely): Plant:Sloc = 1:m, a center of quantitative inventory management • ALT:Ifit is notcross-connectedwith SAP Warehouse Management (WM), THEN itmeansphysicallocationalso. Thissolution is usedonlyatinventory of low-valued, unimportant, easy-to-storematerialwithlowcapitalinvestment & costofstock. • ALT:Itcan be cross-connectedwithsingleWarehouse (Wareh:Sloc= 1:m), then – againstitsname - it DOES NOT meanphysicallocationanymore (itwill be handledby WM), but a special PURPOSE alongMateriallifecycle (Anyag életciklus), forwhichthehigh-valued, important, perishablestockwill be usedfor. ExamplesforusualSlocpurposesdefinedinPlanPlant: • A101:GoodsReceipt (Érkeztet, GR) rawmaterialfromvendors, orkeepfinishedgoodsonstockwhoseProducttax/ Excise (Jövedéki adó) is paidbymanufacturer • X101:Holds +/- quantitydifferencedetectedduring GR, to negotiatewithvendor • P101:Stage (Előkészít) rawmat/semifinishedformachines, GR finishedgoodsfrommachine. ForOrgLev=Material|Plant, wecanassignitTRN:MM02|TAB:MRP2|DDN:ProdStorLoc=P101 • A201:Storeuntaxedfinishedgoods • S201:QualityAssurance (Minőség-ellenőrzés, QA) samples, theyaredamaged, sotheycannever go back to production • A1R1:InternalScrap (Selejt) fordestruction/repair. • A1R4:Scrappurchased back fromcustomerfordestruction/rep. • ExamplesforusualSlocpurposesdefinedinManufPlant: • A102:GR and storage of correctsparepartsofmachines • R101:FaultysparepartsforGoodsIssue (GI) to subcontractor • R1V1:Spare part underrepairatSubcontractor (Alvállalkozó) WareHous Wareh Location • StoreLoc • Sloc • Wareh • Purpose • StoreLoc • Sloc • Wareh • Purpose • A102 • A101 • X101 • R101 • R1V1 • P101 • S201 • A201 • A1R1 • A1R4

6.Warehouse Management Scenario: 6.2.Organizational hierarchy of IM: 3 Client Mandt Comp Comp Plant Plant Location • 6.2.1.Client(Kliens): • 6.2.1.1.Company(Cég):Client:Comp = 1:m • 6.2.1.1.1.DEF:Plant (Gyár):Comp:Plant = 1:m • 6.2.1.1.1.1.DEF:StorageLocation(Tárhely): Plant:Sloc = 1:m, • 6.2.1.1.1.1.1.DEF:Batch (Sarzs/Termelési sorozat azonosító): a subsystem of SAP MM enabling to trackmaterial flow forward/ backwardinsupplychain, and clarifyresoposibilityforfaultyproductsatcustomeramongvendors/ manufactrer/ subcontractors: Plant:Material|Batch = 1:m, Sloc:Material|Batch = m:m • Itcan be turnedonforOrgLevel=Material|Plant|SlocatTRN:MM02|TAB:Purchasing|CHK:Batch=OK IF (atbeginning of a month& has zerostock& no materialmovementsdoneyet) • Thenitwillrequireateach GR doneautomatic/manualfilling of BatchIDfield: • Atrawmaterials,Vendor batch: eg. FactoryYYYYMMDD • Atfinished/semi finised goods, Own batch: eg. FactoryYYYYMMDDMachineShiftWorker • AtTRN:DVS01, wecansetuprules, whichdata to extract and auto-sendfromVendor batch IDsforwardtowardsrecieverOwn batch IdssetbyTRN:DVR01 • Batch ID masterscreatedcan be viewedbyTRN:MSC3N • Batch IDsintheirlifecyclecan be trackedbyTRN:DVMO • For batch IDs, SAP MM modulecanstoreadditionalnumeric/text/datedatafieldsabouttheirvaryingproperties: • ForOrgLev=Material|Plant, TRN:MM02| TAB:Class| FRM:MaterialClasscanstoredataabouthowthematerialshouldlooklike IDEALLY • ForOrgLev=Material|Plant|BatchID, TRN:MM02| TAB:Class| FRM:BatchClasscanstoredatafields, howdidwe SUCCEED to manufacturethegiven batch (eg. Werecievedinferiorqualitytobaccoleaf, sowecouldmakecigarette batch withhigher-than-average tar content) MatMast Matnr Desc StoreLoc Sloc Purpose • MM|Purch • Matrnr • Sloc • Batch MatClass Matnr FieldNam FieldType FieldValue • BatchMast • BatchID • Matrnr • Plant • BatchClass • BatchID • Matrnr • FieldNam • FieldType • FieldValue • BatchDeriv • DerivID • FromBatch • ToBatch • FromField • FromValue • ToField • ToValue

6.Warehouse Management Scenario: 6.2.Organizational hierarchy of IM: 4 Client Mandt Comp Comp Plant Plant Location • 6.2.1.Client(Kliens): • 6.2.1.1.Company(Cég):Client:Comp = 1:m • 6.2.1.1.1.DEF:Plant (Gyár):Comp:Plant = 1:m • 6.2.1.1.1.1.DEF:StorageLocation(Tárhely): Plant:Sloc = 1:m, • 6.2.1.1.1.1.1.DEF:Batch (Sarzs/Termelési sorozat azonosító): Plant:Material|Batch = 1:m, Sloc:Material|Batch = m:m • 6.2.1.1.1.1.1.1.DEF:Stock UsabilityCategories, SUC (Készlet felhasználási kategóriák): set of ruleswhatMovementtypes (Mozgástípusok)can be donewith IM stockwithinSloc: Material|Batch:Sloc|SUT = m:m • Onorder: Rawmaterial is ordered, buttransportationisnotyetstarted • Intransit: Orderedrawmaterial is onthevehicle • Unrestricted: Correctrawmaterial/ semifinishedGR-ed, buttheProdOrder, whichwilluseit, has notbeenreleasedyet • Blocked: Incorrectrawmaterial/ semifinishedGR-ed, close out fromproductionuntilrepaired/destructed, OR: • Blocked: Correctrawmaterial/ semifinishedGR-ed, and theProdOrdusingit is released, soitwillblockit, to preventsomebodyelseconsumingit • Qualityinspection: raw/semi-finished/finishedmaterialsseparatedfor QA inspection. Usuallytheydonotreturnintoproductionastheyaredestructed. Iftheyreturn, Block is usedinstead of it. • IM stockforOrgLev=Material|Plant|Sloc|Batch|SUCcan be checkedwithTRN:MMBE, this is thepossible most detailedresolution of infoin SAP IM system • 6.2.1.1.2.DEF:TransportationPlanningPoint (Fuvarszervezési pont):Settlement unit of transportation costs/profits: Comp:TransPlanPoint= 1:m • 6.2.1.1.2.1.DEF:Shipping Points (Leszállítási pont):Physicallocation to shipinto:TransPlanPoint:ShipPoint= 1:m • It can serve multiple Plants: Plant:ShipPoint = m:m • TranPlanPt • TRPRIID • Company StoreLoc Sloc Purpose • ShipPt • ShPtID • TRPPID • BatchMast • BatchID • Matrnr • Plant • PlantShPt • PlShPID • Plant • ShPtID • IMStock • StockID • Matrnr • Plant • Sloc • BatchID • SUC • Quantity • MeasUnit MM|Basic1 Matnr MeasUnit SUC SUC

6.Warehouse Management Scenario: 6.3.Organizational hierarchy WM 1 WareHous Wareh Location Client Mandt Comp Comp • 6.3.DEF:Organizational hierarchy/basicdefinitions of SAP WarehouseManage-ment (WM) system:Subsystem of SAP LE, whichtracksstocksbyphysicallocation • 6.3.1.Client (Kliens) • 6.3.1.1.Company (Cég):Client:Comp = 1:m • 6.3.1.1.3.DEF:Warehouse (Raktár):Physicalwarehouse building in a givengeographiclocation, whichcanservemultiplePlants, StorageLoc and ShipPoints: Comp:Wareh = 1:m, Wareh:Sloc = 1:m, Wareh:Plant = m:m, Wareh:TranspPlanPt = m:m, Wareh:ShipPoint = m:m • 6.3.1.1.3.1.DEF:Storage type (Raktár típus):Wareh:StorType= 1:m Set of rulesdescribingdifferentphysicalconstraintsofstorage (eg. Shelfstorage, Freezer, Vacuumchamber) orrules to handlestock: • 3-digit codedStorTypeslooselyfollowmateriallifecycle, eg: • GXX – areusedfor GR rawmatfromvendor, • 101 – stagerawmat to machines, • PXX – GR finishedgoodsfrommachines, • LXX – loadfinishedgoods to trucks, • QXX – quarantinescrap • OXX – open, mixed storage • ZXX – overflowstorageinemergency • StorTypecontrols, whatcan be stored, mixed witheachother: • 101, PXX, LXX – Only1Material| 1 Batch • GXX, QXX - Only1Material| More Batches • OXX, ZXX - MoreMaterials| MoreBatches • SU-StorTypescanonlyacceptmaterialpackedintoStorage Units, SU (Raktáregység) (eg. Youcanputmaterialon a griddedshelfonlypackedonpallett, otherwiseitfalls.). • SU requirement is denotedbyletterS (eg. GS1, OS1, PS1) • SUsareidentifiedbyinternational standard SSCC labels (SSCC címke), whichcontain: UniqueSSCCID, MaterialID/SKU, BestBefore, Batch, Quantity, ManufacturerID(notshown) • StorTypedetermines, whichStorage Unit Types, SUT (Raktár-egység típus) areaccepted: (eg.:EU pallet,US pallet,GB pallet) • StorTyp • StorTyp • Wareh • SUHandl • SKUmix • Batchmix SUT SUT

6.Warehouse Management Scenario: 6.3.Organizational hierarchy WM 2 WareHous Wareh Location Plant Plant Location Client Mandt Comp Comp • 6.3.1.Client (Kliens) • 6.3.1.1.Company (Cég):Client:Comp = 1:m • 6.3.1.1.3.DEF:Warehouse (Raktár):Physicalwarehouse building in a givengeographiclocation, whichcanservemultiplePlants, StorageLoc and ShipPoints: Comp:Wareh = 1:m, Wareh:Sloc = 1:m, Wareh:Plant = m:m, Wareh:TranspPlanPt = m:m, Wareh:ShipPoint = m:m • 6.3.1.1.3.1.DEF:Storage type (Raktár típus):Wareh:StorTyp = 1:m • 6.3.1.1.3.1.1.DEF:Storage section (Tároló szekció): A givenphysical part of a StorTyp: (eg.: Shelf 3): StorTyp:StorSec = 1:m • 6.3.1.1.3.1.1.1.DEF:StorageBin (Tároló): The smallest part of StorSec, whichcan be loadedseparately: (eg.: Position 6 of Shelf 3) StorSec:Bin = 1:m • The highflexibility of SAP IM-WM sytem is ensuredbythatStorLoc(IM):Bin(WM) = m:m. (Eg. Sloc=P101 can be phy-sicallystoredthrough 12 Binsifwefeed12machinesfromthere. And a veryexpensive Bin (eg.: vacuumchamber) cancontainmaterialassignedforseveralSlocpurpuses (eg. A101, A201) inthesametime to useitscapacityoptimally) • 6.3.1.1.3.1.1.1.1.DEF:StorageUnit (Raktáregység):package of materialsidentifiedby SSCC label, putonproperStorage Unit Type, SUT (Raktáregység típus), createdbytherules of StorType|Section|Bin: (eg.: PEU European pallettloadedintoPosition6 of Shelf 3) Bin:SU = 1:m, (ForNonSU-Bins, itdoesnotexistatall) • 6.3.1.1.3.1.1.1.1.1.DEF:Quant (Kvant): A given part of stockfrom IM hierachyMaterial|Plant|Sloc|Batchstoredphysicallyinone WM Bin|SU(eg. A large batch of gearshiftscan be loadedon 100s of palletts, and onepallettcancontainseveralcomplete batches fromsmallermaterialseg. medicine): Bin|SU:Quant = 1:m, Material|Plant|Sloc|Batch:Quant = 1:m (Existence of Batch and SUdependsonsettings) StoreLoc Sloc Purpose • StorTyp • StorTyp • Wareh • SUT • SUHandl • SKUmix • Batchmix • BatchMast • BatchID • Matrnr • Plant SUT SUT • Quant • Quant • Matrnr • Plant • Sloc • BatchID • Bin • SU • Quantity • WMUnit • StorSect • StorSect • StorTyp • Bin • Bin • StorSect • MM|WH1 • Maternr • Wareh • WMUnit • SU • SSCC • Bin

6.Warehouse Management Scenario: 6.3.Organizational hierarchy WM 3 • 6.3.1.Client (Kliens) • 6.3.1.1.Company (Cég):Client:Comp = 1:m • 6.3.1.1.3.Warehouse (Raktár):Comp:Wareh = 1:m • Wareh:Sloc = 1:m, Wareh:Plant = m:m, Wareh:ShipPt = m:m • 6.3.1.1.3.1.1.2.DEF:GoodsReceiptArea (Érkeztető): Severalvirtualstoragetypescalled9XX (eg. 912, 971, or TR-ZONE) storingmaterial, whicharecurrentlynotputawaycorrectlyyetin WM. Theirnaming is relatedwithsourceoperation (eg. GR fromvendor) of material. TheycontainvirtualBins, wherename of the bin is ID ifthepreceedingdocument (eg. Bin=PurchaseOrderNumber): Wareh:GRArea = 1:m • 6.3.1.1.3.1.1.3.DEF:Pickingarea (Összekészítő): VirtualstoragetypeforassemblingmaterialsforOutbounddeliveries. ItcontainsvirtualbinsnamedafterOutBoundDeliveryNumber: Wareh:PickArea= 1:m • 6.4.Measure unit conversionproblemsbetween IM and WM systems: • 6.4.1.Sources of differentmeasureunits • IM: ForOrgLevel=Material, TRN:MM01|TAB:Basic1|DDN:Base Unit of Measure=PC – (BUoM, BMU) basisfor IM handling is defined (eg. An elasticducttapein IM measuredaspieces of rollsputonstorage) • WM internal: ForOrgLevel=Material|Plant|Warehouse, TRN:MM01|TAB:WM1|DDN:WM Unit=KM – Basic WM unit, DDN:ProposedUoMfrommat=Feet – alternative unit of measureoriginatesfrom MM (eg. Asdifferentducttape SKU canhavevarying roll lengthdependingonven-dor, WM measuresit more exactlyintotal KM, orinfeetfor US vendor) • WM in/outbound: |TAB:WM1|DDN:UnitofIssue=M – howourWarehissuesit to anotheroneortocustomer – itgoestoOut/InboundDeliverydocument • MM Puchasing: ForOrgLevel=Material|Plant|PurchOrg, TRN:MM01| TAB:Purchasing|DDN:OrderUnit=Yard – unit usedatPurchOrders, DDN:VariableOrder Unit=True – allow SAP to auto-convertintointernal unit • PurchaseInfoRecord: ForOrgLevel=Material×Vendor, TRN:ME11|FRM:Main|DDN:OrderUnit=Yard – a specificmaterialcan be deliveredbyspecificvendorinseparatemeasure unit, DDN:VariableOrder Unit=True – allow SAP to auto-convertfromvendors unit to internal Client Mandt Comp Comp WareHous Wareh Location GRArea GRArID POBin PrchOrd PickArea PkArID • MM|WH1 • Matnr • Wareh • WmUnit • PropUom • UnitOfIss • MM|Purch • Matnr • Plant • PurchOrg • OrdUnit • VarOrdUn • PIR • Matnr • Vendor • UnitPrice • OrdUnit • VarOrdUn

6.Warehouse Management Scenario: 6.4.IM-WM measure unit conversion Client Mandt VendMast Vendor Address GlobComp Comp TaxParad BranchComp CompCode HostCountry PlanPlant Plant Location ManufPlant Plant Location • 6.4.2.Conversion of measure units across different sources • SAP auto-converts measure units with the help of conversions given for OrgLev=Material, TRN:MM01|BTN:Aditional data|TAB:Measure unit|LIN:1| • COL:QuantityTo, COL:MeasUnitTo, COL:QuantityFrom, COL:MeasUnitFrom • But, this is ONLY done WHEN VariableOrderUnit indicator is checked in MM|TAB:Purch or in the PIR, otherwise it replaces measure unit without conversion! • 6.4.3.Summary of IM-WM organizational hierarchy: MM|Basic1 Matnr MeasUnit MatClass Matnr FieldNam FieldType FieldValue • TranPlanPt • TRPRIID • Company WareHous Wareh Location • MM|WH1 • Matnr • Wareh • WmUnit • PropUom • UnitOfIss PickArea PkArID StoreLoc Sloc Purpose • StorTyp • StorTyp • Wareh • SUT • SUHandl • SKUmix • Batchmix • ShipPt • ShPtID • TRPPID GRArea GRArID • BatchClass • BatchID • Matrnr • FieldNam • FieldType • FieldValue • MM|Purch • Matnr • Plant • PurchOrg • OrdUnit • VarOrdUn • Batch • Routing • Matnr • Plant • BatchMast • BatchID • Matrnr • Plant POBin PrchOrd • PlantShPt • PlShPID • Plant • ShPtID SUT SUT • BOM • Matnr • Plant • Quant • Quant • Matrnr • Plant • Sloc • BatchID • Bin • SU • Quantity • WMUnit • StorSect • StorSect • StorTyp • IMStock • StockID • Matrnr • Plant • Sloc • BatchID • SUC • Quantity • MeasUnit SUC SUC • BatchDeriv • DerivID • FromBatch • ToBatch • FromField • FromValue • ToField • ToValue • PIR • Matnr • Vendor • Plant • UnitPrice • OrdUnit • VarOrdUn • ProdCost • Matnr • Plant • Bin • Bin • StorSect • SU • SSCC • Bin

6.Warehouse Management Scenario: 6.6.Checking IM-WM stocks/movements • 6.6.Checking stocks and material movements in IM/WM:

6.Warehouse Management Scenario: 6.7.Goods Movements in IM 1 • 6.7.Goods Movements in IM • 6.7.1.IM movement types • There are lot of possible IM material movements (we will show just the most frequently used ones in detail) identified by IM Material Movement Type (IM-es mozgástípus) 3-digit codes.

6.Warehouse Management Scenario: 6.7.Goods Movements in IM 2 • 6.7.2.Possible groupings of IM goods movements • 6.7.2.1.By direction: • 6.7.2.1.1.Goods Receipt, GR (Áru érkeztetés): Checking Inbound (Bejövő) materials in quantity, masure unit, quality. Reject if faulty. In case of accept, increase IM stock, update MRP, update product costing to incorporate accepted loss, trigger FI module for increasing value of stock. • 6.7.2.1.2.Goods Issue, GI (Áru kiadás): Assembling Outbound (Kimenő) materials, decrese IM stock, update MRP, trigger FI module to reduce value of stock. GR is more long, complicated, costy than GI. • 6.7.2.2.Number of steps: • 6.7.2.2.1.ONE: If material goes from one Storloc to another within the same plant (Plnt|SlocSloc), GI and GR documents can be prepared in the same time. • 6.7.2.2.2.TWO: At Inter-Plant (Comp|PlntPlnt) or Inter-Company (CompComp) stock transfer, with considerable geographical distance, GI document is done, then material goes in In transit status while on vehicle, then GR document is done. • 6.7.2.3.Accounting document involved: • 6.7.2.3.1.NONE:At Plant|SlocSloc, value of the material is unchanged, so no FI document creation is needed • 6.7.2.3.2.ONE:At Comp|PlntPlnt, different plants can have different product costing for the same material, so an FI document is created to settle the value difference6.7.2.3.3.TWO: At CompComp, they can use General ledger, G/L (Számlakeret) of different host countries, therefore material is transeferred with 2 FI documents

6.Warehouse Management Scenario: 6.7.Goods Movements in IM 3 • 6.7.2.4.Physical materialmovementinvolved: • 6.7.2.4.1.Transfer Posting (Készlet Átsorolás): Materialdoesnotmovephysically, justshifts status, using an IM movementtypeTRN:MIGO|DDN:Operation=TransferPosting|DDN:MovementTyp= • 311:UnrestrictedUnrestricted • 323:QualInspQualInsp • 325:RestrictedRestricted • 321: QualInspUnrestricted • 349: RestrictedQualInsp • DDN:Material=GigaBike-Paul, TBX:Quantity=1000PC, CHK:ItemOK=True, BTN:Save • 6.7.2.4.2.Stock Transfer (Készlet Áthelyezés): Involvesphysicalmaterialmovement of Unrestricted/Intransitstockonly, IM MovementTypedependsonfromwhere to wherematerial is put (seefigure) • 6.7.2.5.Manual orautomatedprocess: • 6.7.2.5.1.Manual Stock Transfer: time-consuming, should be usedminimally: TRN:MIGO|DDN:Operation=Transferposting, DDN:Reason=Other, DDN:Movement=301 (Plant Plant) • 6.7.2.5.2.Automatic Stock Transfer: Will be showninPart 6.9

6.Warehouse Management Scenario: 6.8.Goods Movements in WM 1 • 6.8.Goods Movementsin WM • 6.8.1.WM MovementTypes • WM movementtypesaredifferentfrom IM movementtypes, butsomeelements (e.g. 101 GoodsReceipt) arecommon. • 6.8.2.Possible groupings of WM movements • 6.8.2.1.By direction • 6.8.2.1.1.Inbound (Raktárba Bejövő) GR • 6.8.2.1.2.Outbound (Raktárból Kimenő) GI • 6.8.2.2.By number of steps • 6.8.2.2.1.Multi-step: • TRN:LT06:WM TransferRequirement, TR • TRN:LB11: WM TransferOrder, TOfrom TR • TRN:LT12: ConfirmWM TO • 6.8.2.2.2.Single-step • TRN:LT01:Create & confirm TO

6.Warehouse Management Scenario: 6.9.Automated IM-WM Process 1 • 6.9.Automated IM-WM movementprocesses • Thereareparentdocuments/settings, whichautomaticallycreateof childdocuments: • 6.9.1.Assymetric relationship IM-WM movements • 6.9.1.1.Effect of WM movementon IM: • WM BinBinmovement has no anyeffectonthestocksin IM. TRN:MMBEwill show thesame IM stocklevelafter WM movementthanbefore. At WM movement – TRN:LT01 – youhave to providethePlant|SlocbesidesWareh|StorTyp|StorSec|Binonthematerialsenderside, to point out, whichIM-related part (whichpurpose!) of theBin’s WM stockyouwant to movetoanotherBin. ButitwillresidetheverysamePlant|SloceveninthenextBin, Sloccannot be changedduring LT01. • 6.9.1.2.Effect of IM movementon WM: • Ifonemakesonly a TransferPostingin IM – whichdoesnotevenmovesIMstockphysically, justshiftsitstockusabilitycategory – itwillimmediatelyaffectWM. SAP assumesthatifthere is anychangein IM (purpose) of stock, it is soimportant, thataffected WM stockcannot be leftunchanged, becausethere is a bigdanger of confusingitup. Thereforeit „tears” WM stockfromitsoriginalBinintovirtualstoragetypes9XXorTR-ZONE (dependingonwhatoperationyou made in IM), and intotheirvirtualBins, whose ID will be thecorresponding IM documentnumber (eg. STO number). Fromthere, youcanPut Back (Burogatás) WM stockintoitsoriginalBinwithTRN:LT01ifyouwant. So, unfortunately, because of theuser-unfriendlyness and outdatedmood of SAP GUI, a complete IM-WM movementrequiresrunning 3 transactionsin a sequence: • TRN:MIGO_TR: to generate IM movement, recordresultingMatDocNum • TRN:MB51|DDN:Document=MatDocNum: Check out frommaterialdocument, inwhich9XXvirtualstoragetypethe WM stockwastearedup, becauseMIGOdoesnotgiveanysignalaboutit. • TRN:LT01: Nowyoucanmove WM stockfrom9XX|MatDocNum to thefinaltarget Bin.

6.Warehouse Management Scenario: 6.9.Automated IM-WM Process 2 • Because of thedependencybetween IMWM, whenyouareplanning to makemovements, it is advisable to writethem down inthefollowingformat: • 6.9.2.Special Procurement Key, SPK: • AsManufPlant has themachines, butitdoesnothaveanymaterials, allraw/semifinishedmaterialshave to be movedfromPlanPlantforstaging. Sothedoublelogicalplanscreatedbytaxoptimizationwillresultinhighcontinousmanualworkload. ButforOrgLevel=Material|ManufPlant, atTRN:MM02|TAB:MRP2| • AtDDN:Sourceplant=PlanPlant, I cantellmanually „ifyoudonothavestockthisplant, turn to thepreceedingone”. More plantscan be chainedtogetherpullinginmaterialfromeachother: ExternalStoragePlantPlanPlantManufPlant • AtDDN:SpecialProcurmtKey=PlanToManuf I cangivepre-determinedmaterial flow pathsvalidforthewholeclient, fromwhere to pullinmaterial. Thesepathscan be preliminaryeditedinTRN:OMD9 • 6.9.3.TRN:ME21N|DDN:Operation=STO:IM Stock TransportOrder, STO (Készlet Áthelyezés Elrendelés): • Itcanhandleshipping and itscosts, canhandlehistory of order, moreoveritcanauto-create WM movementdocuments, ifinvolvedSlocsareattached to Warehouse: • 6.9.3.1.TRN:MIGO|DDN:Operation=Good Issue|DDN:Reason=For STO • 6.9.3.2.TRN:LT06: CreateTransferRequisition, TR (Transzport igény) • 6.9.3.3.TRN:LB11: WM TransferOrder, TO (Transzport rendelés) fromTR • 6.9.3.4.TRN:LT12: ConfirmWM TO

6.Warehouse Management Scenario: 6.9.Automated IM-WM Process 3 • 6.9.4.TRN:ME21N|DDN:Operation=PurchaseOrder (Beszerzési megrendelés) ininboundlogisticsorTRN:VA01:SalesOrder (Vevői megrendelés) inoutboundlogistics: • Theycreate an STO plus handleloading/unloadingdata of transportingvehicle • 6.9.4.1.Documents generatedonmaterialsenderside: • 6.9.4.1.1.TRN:VL10B:OutboundDelivery, OBD (Kimenő szállítmány): a virtualStorType|Bin to collectmaterialforPurchOrd/SalOrd. • 6.9.4.1.2.TRN:VLPOD:Proof Of Delivery, POD (Leszállítási igazolás) thisdocumentwill be usedlaterbytherecievingside to report back to sender, whatis acceptedat GR and what is not. • 6.9.4.1.3.TRN:LT03:WM Pick (Összeválogatás): Material is Packed (Csomagol): 1ormoreSU|Quantareputinto1Handling Unit, HU (Szállítmány kezelési Egység), whichcan be trackedintransitwithTRN:HUMO.ThenmaterialsaretransferredfromtheirBins to OBD: • WM TransferRequirements, TRauto-created (manuallyTRN:LT06) • WM TransferOrders, TOauto-createdfrom TR (manually: TRN:LB11) • WM TOsauto-confirmed (manually: TRN:LT12) • Incase of anypicking/packingproblem, youcanrevokeitwithTRN:LT0G, whichputs back everythinginitsoriginal Bin unpacked. • 6.9.4.1.4.TRN:VL02N:GI of OBD • 6.9.4.1.4.TRN:VL31N:CreateInboundDelivery, IBD (Bejövő Szállítmány) • Ifthere is anyproblemwith OBD, sendercanrevokeitwithTRN:VL09aslastchance • 6.9.4.2.Documents generatedonmaterialrecieverside: • 6.9.4.2.1.TRN:LT03:WM Putaway (Elpakolás) • WM TransferRequirements, TRauto-created (manuallyTRN:LT06) • WM TransferOrders, TOauto-createdfrom TR (manually: TRN:LB11) • WM TOsauto-confirmed (manually: TRN:LT12) • 6.9.4.2.2.TRN:VL32N:WM GR for IBD, thendoitfor IM: • 6.9.4.2.3.TRN:MIGO|DDN:Operation=GoodsReceipt|DDN:Reason=STO • Ifthere is anyproblemwith GR, recievercanmakeReturnPurchOrd (Visszirányú beszerzés megrendelés) withTRN:ME21N

6.Warehouse Management: 6.5.MM:Maintain master data Click Click • 6.10.MM:Maintain master data • 6.10.1.MM:Extend material master to new plant:GigaBike-NamePlant1100:MM01 • LO|MM|Master|Material|Material|Create|MM01 • 6.10.1.1.SCR:Start • DDN:Material = GigaBike-Name • DDN:Sector = Mechanical engineering • DDN:Type = FERT(Finished product) • DDN:Copy from = GigaBike-Name • BTN:Views: Select the usual set at FERT type material + General plant1-2 • BTN:Organizational levels • FRM:Organizational levels • DDN:Plant = 1100(Berlin) • DDN:Storage location = 1110 • DDN:Warehouse number = 001 • DDN:Storage type = 002(Shelf stor.) • FRM:Copy from • DDN:Plant = 1000(Hamburg) • DDN:Storage location = 0110 • DDN:Warehouse number = 110 • 6.10.1.2.SCR:Main • 6.10.1.2.1.TAB:General plant1: • KEY:Enter to copy • 6.10.1.2.2.TAB:General plant2: • KEY:Enter to copy • 6.10.1.2.3.TAB:Warehouse1: • KEY:Enter to copy • 6.10.1.2.4.TAB:Warehouse2: • KEY:Enter to copy • 6.10.1.2.5.TAB:Accounting1: • KEY:Enter to copy • 6.10.1.2.6.BTN:Save( ) Click Click Click Click Click Click MM01: Copy Material Giga- Bike- Name Click Click Click MMBE: Stock OverView Giga- Bike- Name Click ME21N: Stock Transp Order Giga- Bike- Name 1000PC Plnt1100 Stor1110 Click Click MIGO: Goods Issue Giga- Bike- Name 1000PC Plnt1000 Stor1010 Click Click Click Click

6.Warehouse Management: 6.6.Process: 6.6.1.Stock overview Click • 6.11.LO:Warehouse managementprocess • 6.11.1.LO:Display stock overview: GigaBike-Name: MMBE • LO|LO Ex|Internal Warehouse Proc|Bins and Stock|Display|MMBE Total stock per material • 6.11.1.1.SCR:Start • DDN:Material = GigaBike-Name • DDN:Plant = 1000 – 1100, BTN:Run( ) • 6.11.1.2.SCR:Main • GigaBike-Name • Plant 1000(Hamburg) • Storage 0110:1380PC • 6.11.2.LO:Create stock transport order:GigaBike-Name:1000PC: ME21N • LO|MM|Purchase|Purchase Order|Create|ME21N Vendor/Plant known • 6.11.2.1.SCR:Main • DDN:Document = EUB(Stock Transp.Ord.) • DDN:Suppl Plant = 1000 • 6.11.2.1.1.FRM:Head • 6.6.2.1.1.1.TAB:Org.Data • DDN:Company = 1000 • DDN:Purch.Org = 1000 • DDN:Purch.Group = 001(Dietl) • 6.11.2.1.2.FRM:Item • 6.6.2.1.2.1.LIN:10: • COL:Material = GigaBike-Name • COL:PO quantity = 1000 • COL:Plant (Plnt)= 1100 (Berlin) • COL:Storage location (SLoc) = 1110 (Munich) • 6.11.2.1.3.BTN:Save( )Ignorewarnings! • Take note of stock transport order number: • 1380PC will stay unrestricted stock in Plant 1000 • 1000PC will be stock on order in Plant 1100 Click Click Click Click Click MM01: Copy Material Giga- Bike- Name Click Click MMBE: Stock OverView Giga- Bike- Name Click Click Click Click Click Click ME21N: Stock Transp Order Giga- Bike- Name 1000PC Plnt1100 Stor1110 Click Click Click MIGO: Goods Issue Giga- Bike- Name 1000PC Plnt1000 Stor1010 4500000178

6.Warehouse Management: 6.7.Process: 6.7.3.Goods Issue Click Click • 6.11.3.LO:Post Goods Issue:GigaBike-Name:Plant1000, Storage1010, 1000PC: MIGO • LO|MM|Inventory|Goodsmovement|Goodsreceipt|For purchase order|MIGO PO number known • 6.11.3.1.SCR:Main • DDN:Document = Goods Issue • DDN:Reason = Purchase order • DDN:Doc.number = 4500019088 • DDN:Plant = Empty!!!!,KEY:Enter • 6.11.3.1.1.FRM:item detail • 6.6.3.1.1.1.TAB:Where • DDN:Storage = 0110!!!!! • CHK:ItemOK = True • 6.11.3.1.2.BTN:Save( ) • Take note of material document of 1ststep: • 380PC will stay unrestricted stock in Plant 1000 • 1000PC will be stock on order in Plant 1100 • 6.11.4.LO:Display material document:4900039891:MB03 • LO|MM|Inventory|material doc|MB03 Display • 6.11.4.1.SCR:Start • DDN:Material doc number = 4900039891 • DDN:Year = Current • 6.11.4.2.SCR:Main • 6.11.4.2.1.BTN:Accounting documents • 6.11.4.2.1.1.SCR:List documents in accounting • LIN:Accountingdocument|DoubleClick| Click Click Click Click Click MMBE: Stock OverView Giga- Bike- Name Click Click Click IF ERR:"No posting period open" THEN: SPRO| Financial Accounting (New)| Financial Accounting Global Settings (New)| Ledgers| Fiscal Year and Posting Periods| Posting Periods| Open and Close Posting Periods| LIN:1000, +|BTN:Edit| COL:ToPer1=12, COL:ToYear1=CurrYr ME21N: Stock Transp Order Giga- Bike- Name 1000PC Plnt1100 Stor1110 4900039891 Click Click Click MIGO: Goods Issue Giga- Bike- Name 1000PC Plnt1000 Stor1010 Click Click Click Click Click MB03: Display Mat.Doc Giga- Bike- Name 1000PC Plnt1000 Stor1010 Plnt1100 Stor1110

6.Warehouse Management: 6.7.Process: 6.7.6.Goods Receipt • 6.11.5.Practice:LO:Display material document:4900039891: MIGO • LO|MM|Inventory|Goodsmovement|Goodsreceipt|For purchase order|MIGO PO number known • 6.11.5.1.SCR:Main • DDN:Document = Display • DDN:Reason = Material document • DDN:Document number = 4900039891 • 6.11.5.1.1.FRM:Item • 6.11.5.1.1.1.TAB:Transfer posting • FRM:Destination • BTN:View|SCR:Item detail screen • LIN: 1100 Berlin|BTN:Detailed Display • Take note of on-order stock quantity:1000PC • 6.11.6.Practice:LO:Post Goods Receipt: GigaBike-Name: Plant1100, Storage1110, 1000PC: MIGO • LO|MM|Inventory|Goodsmovement|Goodsreceipt|For purchase order|MIGO PO number known • 6.11.6.1.SCR:Main • DDN:Document = Goods receipt • DDN:Reason = Purchase order • DDN:Stock transport order number = 4500019088 • DDN:Plant = Leaveitempty!!!! • 6.11.6.1.1.FRM:Head • TBX:Delivery note = * • 6.11.6.1.2.FRM:item detail • 6.11.6.1.2.1.TAB:Material • DDN:Material = GigaBike-Name • 6.11.6.1.2.2.TAB:Quantity:TBX:Quantity = 1000 • 6.11.6.1.2.3.TAB:Where • DDN:Plant = 1100 • DDN:Storage = 1110 • CHK:ItemOK = True • 6.11.6.1.3.BTN:Save( ) • Take note of material document of 2ndstep: ME21N: Stock Transp Order Giga- Bike- Name 1000PC Plnt1100 Stor1110 MIGO: Goods Issue Giga- Bike- Name 1000PC Plnt1000 Stor1010 MB03: Display Mat.Doc Giga- Bike- Name 1000PC Plnt1000 Stor1010 Plnt1100 Stor1110 MIGO: Goods Receipt Giga- Bike- Name 1000PC Plnt1100 Stor1110 5000013590

References • http://www.sap-img.com/abap.htm • http://erpgenie.com/ • http://help.sap.com/search/sap_trex.jsp • http://sap.ittoolbox.com/groups/technical-functional/sap-abap/

Object Symbols for IM/WM, Hungarian Translations • Anyagtörzs (Material master) • Beszállító törzs (Vendor master) • Rendel.könyv(Purch Info Record) • Darabjegyzék (Bill of materials) • Műveleti terv(Routing) • Termék költségvetés (Product costing) • Levél(Leaf) • Csom.anyag(Wrapper) • Vágat(Cutred) • Filter(Filter) • Cigaretta készter.(Cigarette FG) • Szivarka késztermék(Cigarillo) • Zsákos késztermék(OTP) • Vág.mterm(Cutr.bypr.) • Készt.mterm(FG.bypr.) • Minőségellenőrzési minta (QA sample) • Megsemmisít(Ripping) • Pótalkatr.(Sparepart) • Értékesítési) szervezet (Sales org) • Vevőtörzs (Customer master) • Vevői megrendelés (Sales Order) • Szállítmány (Delivery) • Szállítási ütem (Delivery sched. line) • Szállítmány kezelési egység(Handling unit) • Számlázás (Invoicing) • Fizetés(Payment) • Kattintás (Click) • Dupla kattintás (Double Click) • Adatbevitel (Write) • Ne módosítsd (Read Only) • Cég (Company) • Gyáregység (Plant) • Tárhely (Storage loc) • Sarzs (Batch) • Készlet felhasználás (Stock Usability Type) • Raktár (Warehouse) • Raktártípus(Str.Type) • R.szekció(Stor.Sect) • Tároló (Bin) • Raktáregység (Storage Unit) • Kvant (Quant) • Érkeztető (GR area) • Összerakó(Pick area) • Csatorna (Channel) • Árucsoport (Division) • Értékesítési terület (Sales Area) • Spedíció pont(Trans-portation plan point) • Kiszállítási hely (Shipping point) • Rakodási pont (Loading Point) Click Dbl Click

GUI Symbols • To make GUI usage descriptions more short and straightforward, we will use standardized denotions of GUI controls, which can be nested into each other: • DEF:-definition, • PRC:-process, • ALT:-alternatives, • CYC:-cycle, • -follows, •  -(dis)advantage, • Aaa|Bbb|-Menu/Submenu, • SCR:-Screen, • FRM:-Frame, • ID-UniqueID, • BTN:-Button, • TXB:-Textbox, • DDN:-Dropdown, • TAB:-Page tab, • CHK:-Checkbox (any of them can be checked) • RAD:-Radiobox (one can be checked only), • LIN:-Tableline, • KEY:-Hotkey, • WRN:-Warning box • ERR:-Errorbox

Warehouse Management Scenario: Organizational Hierarchy and Processes in SAP