Movement Types MM-IM Task Force Logistics SAP AG Page 1 Movement Types MM-IM This document was created in the context of the Retail Task Force Logistics. Its aim is to help con- sultants solve concrete problems in customer projects. You can find more documents on the Task Force Logistics under the Expert Knowledge Corner in http://service.sap.com/retail.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Movement Types MM-IM Task Force Logistics
SAP AG Page 1
Movement Types MM-IM
This document was created in the context of the Retail Task Force Logistics. Its aim is to help con-sultants solve concrete problems in customer projects.
You can find more documents on the Task Force Logistics under the Expert Knowledge Corner inhttp://service.sap.com/retail.
Movement Types MM-IM Task Force Logistics
SAP AG Page 2
DescriptionThe following questions are dealt with in the presentation:
• What are movement types?• What influences them and how are they influenced (possible configurations)?• How are movement types classified?• Which are the most important tables/transactions?
The configurations are also explained by numerous examples.
Important terms that are used in this environment include:
• Value and quantity update• Movement indicator• Special stock indicator• Receipt indicator• Consumption indicatoramong many others.
(Comment: Read the notes in the presentation.)
MovementTypes_MM-IM.ppt
®
� SAP AG 2000 BWART 05/2000
SAP AG
Movement Types in MM-IM
®
� SAP AG 2000 BWART 05/2000
Contents
� Introduction
� Table T156SY with value strings/quantity strings
� Other movement type tables
®
� SAP AG 2000 BWART 05/2000
What is a Movement Type?
� Key for a specific goods movement (incomplete)
� Quantity update (stock tables)
� Value update (FI document, account determination)
� Contains the complete key for a specific movement
� T156S was split in 4.6A into� T156SY: client-independent, system table BUSTW/BUSTM,...� T156SC: client-dependent, customizable WM mvt types, ...
� Key field BUSTR for T156SY derived from T156
� Old customer mvt types have their own BUSTR
� New customer mvt type: BUSTR for T156SY is copiedfrom standard mvt type
®
� SAP AG 2000 BWART 05/2000
Key for T156SY and T156SC
BWART101901
BUSTR101101
T156
BUSTR ...101 ...
BUSTWWE01T156SY
BWART ...101 ...901 ...
Avail. check0102
T156SC
®
� SAP AG 2000 BWART 05/2000
From Movement Type to Value/Quantity String
User enters data
Movement type 201
Transaction MB1A
No special stock
Plant 0001
Material XYZ
Program reads T156SY (old: T156S)
Value string ref. BUSTR 201
Mvt indicator KZBEW space
Special stock SOBKZ space
Value update WERTU X
Quantity update MENGU X
Receipt indicator KZZUG space
Consumption indic. KZVBR space
and finds…
Value string BUSTW WA01Quantity string BUSTM MA01
T158-KZBEW (transaction)
T134M (material type)
T156-BUSTR (mvt type)
®
� SAP AG 2000 BWART 05/2000
®
� SAP AG 2000 BWART 05/2000
Movement Indicator KZBEW
� Needed to differentiate between� GR for purchase order (101 B)� GR for production order (101 F)
� Depends on transaction (T158) for MB transactions
� Filled by MB_CREATE callers in IMSEG(variable in VL02 / VL32)
� Possible values:� B = purchase order� F = production order (not repetitive manufacturing)� L = LE-SHP delivery� Space= movement without purchase/production order
� L/Space: will probably merge together in next releases
®
� SAP AG 2000 BWART 05/2000
Receipt Indicator KZZUG
� Filled only in case of transport orders
� Movement types 351/641/643 (GI) and 101 (GR)
� MB_CREATE: filled for T156-KZBWA 1,3,4,5(set in MB_CREATE_GOODS_ISSUE_ITEM_TRA)
� MB11/MB01: is not set by purchase order interface(EBEFU/BBEFU). It is set internally by SAPMM07M
®
� SAP AG 2000 BWART 05/2000
Consumption Indicator KZVBR (1)
� GR for PO: depends on assignment category in T163K(OME9). Table T163K also sets special stock SOBKZ.
� SD and PP also work with table T163K
� Values:� space normal goods issue with MB1A� V account assignment K (normal consumption)� A account assignment A (assets)� E/P used for non-valuated special stocks E/Q
� Valuated special stock E/Q (KZBWS not initial):T156SY is read with KZVBR space
� Used by SD and QM to determine if an assignment toCO object is necessary
®
� SAP AG 2000 BWART 05/2000
Consumption Indicator KZVBR (2)
� Set externally by LE-SHP, MM-PUR, PP
� Database checks with SE16:� LIPS-KZVBR inbound/outbound delivery� EKPO-KZVBR purchase order� AFPO-KZVBR production order
T156X: Account Modifier (KOMOK)� Counter CNT02 in T156X refers to counter in T156W
(= identifier for processing key)
� Only possible for GBB, PRD, KON, AUM, (WRX?)
� SD/QM: KZVBR leads to different account modifiersdepending on KZVBR (set if CO object needed):� SD uses VAX and VAY (CO object for VAY) (movement type 601)� QM uses VQP and VQY (CO object for VQY) (movement type 331)
� In case of valuated special stock E/Q (KZBWS set), we read� Table T156SY w/o KZVBR� Table T156X with KZVBR (E/P/V)
®
� SAP AG 2000 BWART 05/2000
T156X: Indicator XPKON (1)
� XPKON = X means account assignment data (CO object) willbe copied to XACCIT of that processing key (usually GBB)
� Copying of CO object also depends on field selection inT156B (OMBW). See note 117596 for special stock E/Q.
= possible solution to message KI235 for GBB line
� Manual account is also be copied to that line
� Can also be set for PRD/AUM if customer wants thesame CO object for price differences(possible for AUM since 30F, note 13984)
= possible solution to message KI235 for PRD/AUM line
®
� SAP AG 2000 BWART 05/2000
T156X: Indicator XPKON (2)
� Entry 101 is necessary for GR for PO with accountassignment (value string WE06 processing key KBS)
� KBS means we copy the account from the PO, so noaccount determination is necessary (already done)
®
� SAP AG 2000 BWART 05/2000
Check Strings in Material Documents
� SE16 MSEG contains� All T156SY fields (Bwart, Mengu, Wertu, Kzbew, Kzvbr, Kzzug)� Value string BUSTW� Quantity string BUSTM
301: Transfer from plant to plant in one step (no PO, unrestricted stock)411K: Transfer from vendor consignment to unrestricted storage location413Q: Transfer from project stock (Q) to customer order stock (E) - unrestricted453: Transfer from returns stock to unrestricted storage location
®
� SAP AG 2000 BWART 05/2000
Other Movement Type Tables
®
� SAP AG 2000 BWART 05/2000
T156N: Subsequent Movement Types
� Key: FCODE + BWART
� ST 601 > 602: cancel movement type (used inMB_CANCEL_GOODS_MOVEMENT)
� RL 101 > 122: return delivery transaction MBRL
� Special codes for automatic movements:� WEUB 647-> 101 (one-step transfer with transfer PO)� LBWA -> 543 (GI of components during GR subcontracting)
®
� SAP AG 2000 BWART 05/2000
T156B: Screen Layout
� Field modification for MB11 transactions
� Not possible for MB01 (101 mvt types) as accountassignment is copied from PO
� Determines also which account assignments will becopied to FI document
� Not used in MB_CREATE_GOODS_MOVEMENT
� MIGO: new table MIGO_CUST_FIELDS
®
� SAP AG 2000 BWART 05/2000
T158B: Allowed Movement Types
� Allowed movement types per transaction
� MB_CREATE callers are responsible for creating theentries in T158B for their own transaction