By transaction type group (shared with material doc)
OMBA
Reservation (预留)
Single number range, internal only
OMH6
Number Assignment for Accounting Documents (会计凭证编号)
FI Document Types predefined for Inventory Management:
Doc Type
Description
Usage
WA
Goods issues, transfer postings, other GR
发货/转储/其他收货
WE
Goods receipts w/ ref to PO
采购订单收货
WI
Inventory differences
盘点差异
WL
Goods issues for deliveries
交货发货
WN
Net postings of GR
收货净额过账
PR
Revaluation documents
重估凭证
💡Number range intervals are defined per company code and fiscal year for each document type.
1 2 3 4
Doc Type ──► Number Range ──► Interval (per CoCd + Fiscal Year) WA 01 0100000000 - 0199999999 WE 02 5000000000 - 5999999999 ...
Number Assignment for Material & Inventory Documents (物料/盘点凭证编号)
Number assignment depends on transaction type. Transaction types are grouped into number range groups.
Number Range Group
Interval Range
Transaction Types
Physical inventory docs
0100000000-0199999999
IB, ID, IN, IZ, WV
Material docs (GI/transfer/other)
4900000000-4999999999
WA, WI, WL, WR
Material docs (GR)
5000000000-5999999999
WE, WF, WO
Inventory sampling
0200000000-0299999999
SI
Transaction Types Detail
Physical inventory transaction types:
Type
Description
IB
Physical inventory document
ID
Count & difference without reference
IN
Recount document
IZ
Count without reference
WV
Difference posting (WM)
Material document transaction types:
Type
Description
WA
Goods issues, transfers, other GR
WI
Inventory adjustment postings
WL
GI for delivery documents (SD)
WR
Goods movements for PP confirmations
WE
GR for purchase orders
WF
GR for production orders
WO
Subsequent adjustment (subcontracting)
📌You cannot change transaction types, but you can change number range intervals or assign transaction types to new groups.
Number Assignment for Reservations (预留编号)
1 2 3 4 5 6 7 8
Reservation Number Assignment ┌─────────────────────────────────────┐ │ Only ONE number range is active │ │ (Standard: NR 01) │ │ │ │ Internal assignment ONLY │ │ Valid for ALL plants in client │ └─────────────────────────────────────┘
Feature
Detail
Active number range
01 (standard)
Assignment type
Internal only (for manual reservations)
Scope
All reservations, all plants in the client
External assignment
Only via BAPI BAPI_RESERVATION_CREATE1 using NR RB
⚠️Reservation number assignment is client-level – one setting covers all plants.
考试高频考点 (考试高频考点)
Scenario/Keyword
Answer
“Which doc type for GR with PO?”
WE
“Which doc type for inventory differences?”
WI (accounting) / IB/ID/IN/IZ (physical inventory)
“Can you change transaction types?”
No, only number range intervals and group assignments
When copying a plant, parameters are also copied from reference plant
Negative stock
Cannot be activated here; must use specific IMG activity
⚠️You should make actual settings in the relevant IMG activities (not in plant parameters), because dependent entries cannot be maintained from the central screen.
Storage Location Field Settings (存储地点字段设置)
Part of MIGO field selection configuration. You can control which fields appear and whether they are:
Hidden (隐藏)
Optional entry (可选)
Required entry (必填)
💡In standard SAP, all configurable fields are optional except the Goods Receipt/Issue Slip field, which is hidden (only needed in some countries like Italy).
Settings for Enjoy transactions are divided into three sections:
Section 1: Field Selection for Header Fields
Setting
Description
Hide fields/buttons
Remove unnecessary UI elements
Required entry
Force entry (e.g., delivery note, bill of lading)
Field name pattern
GOHEAD… (header) / GOITEM… (item)
📌Required entry field attribute is only evaluated for fields named GOHEAD… and GOITEM… Unfilled required fields automatically get the “HiLi” (highlight) attribute.
Section 2: Field Selection per Movement Type
Action
How-to
Make field optional/required
Select optional or required entry
Hide a field
Delete the required entry from the table
Show a hidden field
Choose New Entry → enter movement type + field
Special stock fields
Always shown automatically (no configuration needed)
1 2 3 4 5 6 7 8 9 10 11
Field Selection per Movement Type ┌──────────────────────────────────────┐ │ Movement Type: Z01 │ │ ┌──────────────┬──────────────────┐ │ │ │ Field │ Setting │ │ │ ├──────────────┼──────────────────┤ │ │ │ Goods Recpt │ Required Entry │ │ │ │ Cost Center │ Optional Entry │ │ │ │ [hidden] │ (deleted) │ │ │ └──────────────┴──────────────────┘ │ └──────────────────────────────────────┘
Section 3: Transactions & Reference Documents
You can restrict selectable transactions and reference documents for each Enjoy transaction:
Transaction
Purpose
MIGO
Create all goods movements
MIGO_GR
Enter all GR from external procurement
MIGO_GO
Enter all GR for production orders
MIGO_GI
Enter all GI and other GR
MIGO_GS
Subsequent adjustment of material provided (subcontracting)
💡You can also specify the default movement type the system should propose for each reference document.
Automatic Creation of Storage Location Data (自动创建存储地点数据)
When a goods movement is posted to a new storage location, the system can automatically create the storage location data in the material master record. This is controlled by a setting on the movement type.
Setting
Effect
Activated on movement type
Storage location view auto-created in material master at first posting
Not activated
Manual creation (MM01) required before posting
考试高频考点 (考试高频考点)
Scenario/Keyword
Answer
“Central plant IM settings?”
Plant Parameters (OMNH) – view-only overview
“Can you activate negative stock in plant parameters?”
GR Against PO with LE (IM-Posting-Driven) ┌──────────────┐ │ Post GR in │ MIGO (mvt 101) │ IM (MIGO) │ └──────┬───────┘ │ System checks: Is SLoc assigned to warehouse number? │ ├── YES: WM tab page appears at item level │ ▼ ┌──────────────┐ ┌──────────────────────┐ │ Material Doc │ │ Stock booked into │ │ + Acct Doc │ │ interim storage area │ │ generated │ │ (type 902, GR zone) │ └──────┬───────┘ │ as a QUANT │ │ └──────────────────────┘ ▼ ┌──────────────┐ │ Transfer │ Auto-generated │ Requirement │ Reference for TO └──────┬───────┘ │ ▼ ┌──────────────┐ │ Transfer │ Created with ref to TR (LT03/LB11) │ Order (TO) │ Stock = "in transit" (removal + putaway) └──────┬───────┘ │ ▼ ┌──────────────┐ │ Confirm TO │ LT12 │ (putaway) │ Stock now in final storage bin └──────────────┘
Step 1: GR Posting in IM (IM收货过账)
When posting GR (movement type 101), the system checks for each PO item:
Check
Result if YES
Is plant-SLoc assigned to a warehouse number?
WM tab page appears at item level in MIGO
Is GR posted to WM-managed SLoc?
Transfer requirement is auto-generated
Stock booked to interim storage area 902 (goods receiving zone)
📌The stock in the interim storage area is represented as a quant – the smallest unit of managed stock in WM.
Step 2: Transfer Requirement (转储需求)
Property
Detail
Generated by
System automatically at GR posting
Purpose
Planning and posting basis for warehouse activities
Contains
IM movement type + WM movement type (both in document header)
Reference for
Transfer Order
WM Movement Types Linked to IM Movement Types
1 2 3 4 5
IM Movement Type 101 (GR for PO) │ └──► Linked WM Movement Type (configured in Customizing) │ └──► Both displayed in Transfer Requirement header
💡WM has its own set of movement types that are linked to IM movement types in Customizing tables. Both are shown in the transfer requirement header.
Step 3: Transfer Order and Putaway (转储订单与上架)
The Transfer Order (TO) is the key document for physical warehouse movements:
Property
Detail
Nature
Handling instruction for the storeperson
Created with reference to
Transfer Requirement
Can be created
In foreground or background
Auto-creation
Can be triggered directly after GR posting
Putaway Strategy (上架策略)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Putaway Process: ┌──────────────────┐ │ 1. Determine │ Destination Storage Type │ destination │ │ storage type │ └───────┬──────────┘ ▼ ┌──────────────────┐ │ 2. Determine │ Storage Section (if configured) │ storage section│ └───────┬──────────┘ ▼ ┌──────────────────┐ │ 3. Determine │ Based on Putaway Strategy │ storage bin │ assigned to storage type └──────────────────┘
Stock Status During Putaway
Phase
Stock Status in WM
After GR posting (before TO)
Stock in interim storage area 902 (quant)
After TO creation (before confirm)
Stock shown as both: removal from 902 + putaway at destination
After TO confirmation
Stock in final storage bin (e.g., rack storage area)
⚠️After TO is created but before confirmation, the stock is in transit. You cannot access these stocks until the putaway process is completed (TO confirmed).
Key Transactions
T-code
Function
MIGO
Post GR against PO
LB11
Display/create TO for material (transfer requirement)
LT03
Create TO in foreground
LT12
Confirm TO (single document, one step)
LS26
WM stock overview per material
考试高频考点 (考试高频考点)
Scenario/Keyword
Answer
“GR with LE: first step?”
IM posting (MIGO, mvt 101)
“What triggers TR creation?”
GR posting to WM-managed storage location
“Interim storage area for GR?”
Type 902 (goods receiving zone for external receipts)
“Stock in interim area is called?”
A quant
“What is a transfer order?”
Handling instruction for physical warehouse movement
GI for Sales Order with LE (Delivery-Driven) ┌──────────────┐ │ Sales Order │ VA01 │ (TA type) │ └──────┬───────┘ │ ▼ ┌──────────────┐ │ Outbound │ VL01N (ref to sales order) │ Delivery │ - Picks up scheduled dates │ │ - Determines picking SLoc │ │ - Assigns warehouse number │ │ - Sets picking status + removal status └──────┬───────┘ │ ▼ ┌──────────────┐ │ Transfer │ LT03 (ref to outbound delivery) │ Order (TO) │ Stock removal instruction │ for picking │ └──────┬───────┘ │ ▼ ┌──────────────┐ │ Confirm TO │ VL06O → Confirm Picking │ (picking) │ Status: A → C (Fully picked) └──────┬───────┘ │ ▼ ┌──────────────┐ │ Post GI for │ VL02N → Post Goods Issue │ Outbound Del │ IM posting completed └──────────────┘
Step 1: Sales Order → Outbound Delivery (销售订单→对外交货)
Outbound Delivery Creation
Property
Detail
Created with reference to
Sales order
T-code
VL01N
Inherits from order
Key data including scheduled dates for follow-on processes
Selection date
Should match material availability date from order
Picking Storage Location Determination
1 2 3 4 5 6 7 8 9
Outbound Delivery Processing ┌───────────────────────────────────────┐ │ For each delivery item: │ │ ├── Determine picking SLoc │ │ ├── Check: SLoc assigned to WH#? │ │ │ └── YES → display warehouse # │ │ ├── Assign overall picking status │ │ └── Assign stock removal status │ └───────────────────────────────────────┘
💡The system automatically checks whether the picking storage location is assigned to a warehouse number. If so, it displays the warehouse number in the outbound delivery and sets the appropriate picking/removal statuses.
Movement Type (3-digit key) │ ├──► Quantity Update (数量更新) │ └── Controlled by "Quantity String" (fixed, cannot change) │ ├──► Value Update & Account Determination (值更新/科目确定) │ └── Controlled by "Value String" (fixed) │ └── Account Modifier (科目修改码) can differentiate │ e.g., 201 (cost center) vs 551 (scrapping) │ → Different consumption accounts │ ├──► Field Selection (字段选择) │ └── Which fields appear on MIGO screen │ └──► Other Settings ├── Shelf Life Expiration Date Check ├── Automatic PO generation at GR ├── Auto creation of storage location data ├── Stock determination └── Dynamic availability check
Quantity String vs Value String
Concept
Description
Can Change?
Quantity String (数量字符串)
Controls quantity update logic per movement type
No – fixed in SAP system
Value String (值字符串)
Controls value update & triggers auto account determination
No – fixed in SAP system
Account Modifier (科目修改码)
Second key within value string for differentiated G/L posting
Yes – configurable
📌The account modifier enables different consumption accounts for different movement types sharing the same value string. Example: movement type 201 (cost center GI) vs 551 (scrapping GI) post to different consumption accounts.
Key Movement Type Settings (关键设置)
Views in Movement Type Configuration
Settings are split into different views, each containing relevant control indicators:
View
Content
Field selection
Which fields are optional/required/hidden
Update control
Quantity & value string assignments
Allowed transactions
Which MIGO transactions are permitted
Reversal movement type
Which movement type to use for reversal
💡Some control indicators depend on additional parameters (debit/credit indicator, special stock indicator, quantity/value update indicator), so a single movement type may have multiple entries in some views.
Defining a New Movement Type (创建新移动类型)
Step-by-Step Process
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Step 1: Copy existing movement type │ (Select a template matching your needs) │ Step 2: Save the new movement type │ Key must start with: 9, X, Y, or Z │ Step 3: Modify control parameters │ (Field selection, allowed transactions, etc.) │ Step 4: Copy reversal + reference movement types │ And assign them to the new movement type │ Step 5: Copy ALL dependent entries (Important: do not miss sub-entries!)
Rule
Detail
New key must start with
9, X, Y, or Z
Template selection criterion
Match quantity & value update requirements
Must copy
All dependent entries of reference movement type
Must also copy
Reversal movement type and reference movement type
IMG Path
1 2
Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types
⚠️You cannot change the quantity string or value string – these are hard-coded in the SAP system. Choose your template movement type carefully.
Movement Type Grouping (移动类型分组)
Movement types can be grouped for various purposes:
Number range grouping: Group movement types sharing the same number range interval
Account determination grouping: Use account modifiers to differentiate posting within a value string
考试高频考点 (考试高频考点)
Scenario/Keyword
Answer
“Three-digit key for goods movement?”
Movement type
“What controls quantity update?”
Quantity string (fixed, cannot change)
“What controls value update?”
Value string (fixed)
“How to differentiate accounts for same value string?”
Account modifier (科目修改码)
“New movement type key prefix?”
Must start with 9, X, Y, or Z
“Can you change quantity/value strings?”
No, they are fixed in SAP
“Why copy all dependent entries?”
Missing entries cause incomplete control settings
“Name 4+ functions controlled by movement type”
Quantity update, account determination, field selection, shelf life check, auto PO, auto storage location data
“Example: 201 vs 551 different accounts?”
Different account modifiers route to different consumption accounts
