Mark的技术博客

SAP顾问 | 咨询专家 | IT与AI技术探索者

吴让宇(Mark)

吴让宇(Mark)

SAP顾问 | 咨询专家 | IT与AI技术探索者

吴让宇(Mark)的个人技术博客,专注于SAP系统实施、行业方案咨询、IT技术与AI技术的研究与分享。

SAP Fiori ABAP CDS OData Dify Docker AI LLM

最新文章

盘点简化 (★★)

#physical-inventory #simplification

概览表 (一眼对比)

Item Key Point
Zero Count 库存为零时跳过盘点
Worklist 生成PI工作清单
Batch Input 批量创建PI凭证
Combine Steps 合并PI步骤提高效率

简化措施

Zero Count (零盘点)

  • 当库存为零时,盘点可以跳过
  • 系统自动将盘点数量设为0
  • 减少不必要的工作量

Worklist for PI

  • 生成盘点工作清单,分配给盘点人员
  • 可按不同标准筛选物料

Batch Input Session

  • 使用批输入会话批量创建PI凭证
  • 适用于大量物料的盘点场景
  • 路径: System → Services → Batch Input → Sessions

Combining Steps

  • 可以将多个PI步骤合并执行
  • 手动合并或通过批输入合并
  • 如:创建PI凭证 + 录入盘点数 → 一步完成

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“Zero count” 库存为零时跳过盘点
“Batch input session” 批量创建PI凭证
“Combine PI steps” 手动或批输入合并多个步骤

负库存 (★★★)

#negative-stock #goods-issue

概览表 (一眼对比)

Item Key Point
When GI数量 > 账面库存量
Why 收货未及时录入但物料已被消耗
Settings 三级设置:估值区域 → 工厂/Sloc → 物料主数据
Risk 不可在资产负债表日或盘点时有负库存

负库存场景

1
2
3
4
5
6
7
账面库存: 100 pc (实际已有 1000 pc,但GR未录入)
│
▼ 发货 300 pc
账面库存: -200 pc (负库存)
│
▼ 补录GR 900 pc
账面库存: 700 pc (恢复正常)

配置要求(三级设置)

Level Setting Transaction
1. 估值区域 允许负库存 OMJ1
2. 工厂/Sloc 指定哪些Sloc允许 OMJ1
3. 物料主数据 Neg. Stocks Plant 指示器 MM02
⚠️必须在三个级别都设置才能使用负库存。另外还需指定允许负库存的特殊库存类型。

允许负库存的特殊库存

Indicator Special Stock Type
K Vendor Consignment
O Material Provided to Vendor
W Consignment at Customer
E Sales Order Stock
Q Project Stock
V Returnable Packaging (Customer)
M Returnable Transport Packaging

移动平均价的影响

Price Control Negative Stock Effect
Standard Price 无特殊影响
Moving Average Price 补录GR时可能过账到价格差异科目

MAP负库存清算示例

1
2
3
4
5
1. 起始: 10 pc × €1 = €10 (MAP = €1)
2. GI 16 pc: 16 × €1 = €16 → 库存 = -6 pc, 价值 = -€6
3. GR 10 pc (PO价€3): 库存价值 = -6 + 6(清算) + 12(实物4pc×€3) = €12
→ 新MAP = €12 / 4 pc = €3
→ 价格差异 = PO总价€30 - 实际入账€18 = €12 (过账到价格差异科目)
📌MAP物料负库存清算后,新MAP可能与PO价格不同,且有价格差异科目过账。

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“Negative stock settings” 三级: 估值区域 → 工厂/Sloc → 物料主数据
“MAP + negative stock” 可能产生价格差异科目过账
“Balance sheet date” 不可在资产负债表日有负库存
“Standard price + negative” 无特殊影响

库存确定 (★★★)

#stock-determination #goods-issue

概览表 (一眼对比)

Item Key Point
Purpose 自动确定从哪个存储地点/库存发货
Configuration 组 → 规则 → 策略
Sorting 可按数量升/降序、优先级排序

配置层级

1
2
3
4
5
6
7
8
9
10
Material Master
├── Stock Determination Group (库存确定组)
│ │
│ ▼
│ Customizing
│ ├── Stock Determination Rule (规则) → 分配给移动类型
│ ├── Stock Determination Strategy (策略)
│ │ ├── Header: 组 + 规则 → 排序规则
│ │ └── Items: 存储地点列表 + 优先级
│ └── Sorting: Quantity ASC/DESC, Priority

关键配置步骤

Step Setting Path
1 分配规则给移动类型 MM → IM → Stock Determination → Assign Rule
2 创建库存确定组 Define Strategies
3 分配组给物料 Material Master → Gen Plant/Storage 2
4 定义策略 Header (排序规则) + Items (Sloc+优先级)

策略示例

Strategy Sorting Slocs Considered Result
成本中心发货 数量降序 0001, 0002, 0003 选库存最大的Sloc
项目发货 数量升序 0001, 0002, 0003 选库存最小的Sloc
📌库存确定按照配置的排序规则选择,不是按价格最优。

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“Stock determination group” 分配在Material Master中
“Sorting rule” 按数量升/降序或优先级
“Strategy definition” Header (组+规则+排序) + Items (Sloc+优先级)

定期处理 (★★)

#reporting #periodic-processing

概览表 (一眼对比)

Report Purpose
Conversion Differences 分析单位换算的舍入差异
Balance Display G/L余额 vs 库存价值对比
Stock Consistency Check 检查库存数据一致性

转换差异分析

  • 当物料使用不同计量单位时,换算可能产生舍入差异
  • 特别容易发生在:公制↔非公制单位换算
  • 可设置阈值排除微小差异
  • 可手工过账调整差异

余额显示 (Balance Display)

  • 对比 G/L科目余额 与 库存价值合计
  • 不一致的可能原因:
    1. 手工过账到库存科目
    2. 库存科目用于非库存过账
    3. 账户确定配置在运营期间被修改
📌G/L余额≠库存价值的原因包括:手工过账、账户确定被修改等。需检查账户确定确保库存科目仅用于BSX。

库存一致性检查

检查项目包括:

  • 物料主数据评估数据是否一致
  • 指定价格是否 = 价值/数量
  • 正数量是否有负价格
  • 不允许负库存的物料是否有负价值
  • 库存为零时价值是否非零
  • 总评估库存是否 = 各子段之和
💡由于报表运行时不锁定物料,可能存在临时不一致。建议多次运行比较结果。

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“Balance display discrepancy” 可能是手工过账、配置变更等导致
“Conversion difference” 单位换算的舍入差异
“Consistency check” 检查估值数据是否一致

报表分析练习 (8 questions)

#practice #reporting

📌核心模式(点击查看)
Keyword Answer
MMBE 库存概览
MB52 仓库库存(含价值)
MB51 物料凭证清单
Balance Display G/L余额 vs 库存价值
Posting date stock 历史时点库存

Question 1 - 库存概览 [recall]

查看物料在所有组织层级的库存情况,应使用哪个事务码?

📌查看答案
MMBE (Stock Overview)。可跨工厂、存储地点、特殊库存查看。

Question 2 - 仓库库存 [recall]

需要查看多个物料的数量和价值,应使用哪个报表?

📌查看答案
MB52 (Warehouse Stock)。显示多物料的数量和价值,可筛选负库存。

Question 3 - 物料凭证 [recall]

查看特定供应商的所有物料凭证,应使用哪个事务码?

📌查看答案
MB51 (Material Document List)。可按供应商、物料、工厂、移动类型等筛选。

Question 4 - 凭证日期库存 [application]

Stock on Posting Date报表显示的是什么?

📌查看答案
显示历史时点的库存。系统根据物料凭证从当前库存反算指定日期的库存数量和价值。

Question 5 - 余额不一致 [analysis]

Balance Display报表显示G/L科目余额与库存价值不一致,可能的原因有哪些?

📌查看答案
  1. 手工过账到库存科目
  2. 库存科目被用于非库存过账
  3. 账户确定配置在运营期间被修改(BSX配置变更)
  4. 报表运行期间有并发过账(临时不一致)

Question 6 - 转换差异 [recall]

什么情况下会产生转换差异(Conversion Differences)?

📌查看答案
当基本单位和替代单位之间换算时产生舍入差异,特别是公制↔非公制单位(如米↔码)。

Question 7 - 一致性检查 [recall]

Stock Consistency Check检查哪些内容?

📌查看答案
  • 评估数据是否一致
  • 价格 = 价值/数量?
  • 正数量是否有负价格?
  • 不允许负库存的物料是否有负价值?
  • 总评估库存 = 各子段之和?

Question 8 - Display Version [application]

在MMBE中,Display Version控制什么?

📌查看答案
Display Version控制显示哪些库存类型以及显示顺序。在Customizing (Define Stock List Display) 中定义。

📌模式总结(点击查看)
Keyword Answer
MMBE 库存概览(跨层级)
MB52 仓库库存(量+价)
MB51 物料凭证清单
Balance差异 手工过账/配置变更/并发
Posting date 历史反算

库存与凭证报表 (★★★)

#reporting #stock-list

概览表 (一眼对比)

Report T-Code Description
Stock Overview MMBE 多层级库存概览
Warehouse Stock MB52 按工厂/Sloc的数量和价值
Material Documents MB51 物料凭证清单
Stock/Requirements MD04 MRP要素一览
Stock in Transit MBBE 在途库存
Plant Availability MB53 工厂可用库存

凭证报表

Report T-Code Description
Material Documents MB51 按物料/工厂/移动类型筛选
Accounting Documents — 物料相关会计凭证
Canceled Documents MBSM 冲销凭证清单
Doc with Reason — 含移动原因的凭证

库存报表

Report Key Features
Stock Overview (MMBE) 跨组织层级的库存概览;可查看特殊库存;支持Display Version
Warehouse Stock (MB52) 多物料数量+价值;可筛选负库存;层级/非层级显示
Stock on Posting Date 历史时点库存(从当前库存反算)
Stock/Requirements (MD04) 当前可用性状态;包含MRP要素

配置

Setting Path
Display Version MM → IM → Reporting → Define Stock List Display
Field Selection MM → IM → Reporting → Define Field Selection for Material Document List
Movement Type Group MM → IM → Reporting → Group Movement Types for Stock Lists
💡凭证日期库存(Stock on Posting Date)是历史时点库存,系统根据物料凭证从当前库存反算。

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“MMBE” Stock Overview(库存概览)
“MB52” Warehouse Stock(仓库库存)
“MB51” Material Document List
“Stock on posting date” 历史时点库存,从当前反算
“Display Version” Customizing中定义,控制显示的库存类型

计划外发货 (★★★★)

#goods-issue #unplanned

概览表 (一眼对比)

Item Key Point
Reference Others (无参考)
Transaction MIGO → Goods Issue → Others
BOM Explosion 可参考BOM展开组件发货
Account Assignment 必须指定(成本中心/订单/项目)

常见GI类型

MvT Description Account Assignment
201 GI for Cost Center 成本中心
221 GI for Project WBS元素
261 GI for Order (production) 生产订单
331 GI for Sampling 取样
551 GI for Scrapping 报废
📌样品抽取(MvT 331)和报废(MvT 551)在标准系统中不是消耗过账,它们过账到不同科目。

BOM展开发货 (GI with Reference to BOM)

1
2
3
4
5
6
7
8
9
MIGO → Goods Issue → Others
│
├── Reference: BOM (物料清单)
├── 输入父物料号
├── 系统自动展开BOM → 显示组件列表
└── 选择需要发货的组件
│
▼
各组件按BOM数量发货
  • 使用BOM作为模板,一次性输入多个组件
  • 父物料本身不发货,仅其组件发货

取样 vs 报废 vs 消耗

Type MvT FI Effect Special Note
Consumption 201/221/261 过账到消耗科目 有账户分配
Sampling 331 过账到取样科目 非消耗过账
Scrapping 551 过账到报废科目 非消耗过账

考试高频考点 (考试高频考点)

Scenario/Keyword Answer
“MvT 201” GI for Cost Center
“Sampling = consumption?” 否,MvT 331不是消耗过账
“BOM GI” BOM作为模板,组件发货,父物料不发
“Unplanned GI account assignment” 必须指定账户分配

凭证配置 (★★★)

#customizing #document-settings

概览表 (一眼对比)

Document Type Number Assignment Key T-code / Path
Accounting Document (会计凭证) By document type + company code + fiscal year OBA7 / FB00
Material Document (物料凭证) By transaction type group OMBA
Physical Inventory Document (盘点凭证) 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
“Reservation number range scope?” Client-level, internal only
“External reservation number?” Only via BAPI_RESERVATION_CREATE1 with NR RB
“Number range for material doc GR?” 5000000000-5999999999
“Number range for physical inventory docs?” 0100000000-0199999999

其他配置设置 (★★★)

#customizing #plant-settings

概览表 (一眼对比)

Topic Purpose Key Path
Plant Parameters (工厂参数) Central plant-level IM & PI settings OMNH / SPRO
Field Selection for MIGO Hide/require header fields in MIGO SPRO → Enjoy Transactions
Field Selection per Movement Type Per-movement-type field control SPRO → Movement Types
Transaction & Reference Doc Settings Restrict allowed transactions & references SPRO → Settings for Transactions
Restricted MIGO Transactions Predefined transaction variants MIGO_GR, MIGO_GI, etc.

Plant Parameters for IM (库存管理工厂参数)

Plant parameters provide a central overview of all plant-dependent settings for Inventory Management and Physical Inventory.

1
2
3
4
5
6
7
8
9
Plant Parameters (OMNH)
┌─────────────────────────────────────────┐
│ Grouped by: │
│ ├── Goods movement settings │
│ ├── Physical inventory settings │
│ ├── Reservation settings │
│ └── Negative stock settings │
│ (Activation NOT possible here!) │
└─────────────────────────────────────────┘
Feature Detail
Scope All settings for one plant in one view
Also available In individual IMG activities
Copy behavior 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).

Transaction MIGO Default Values Configuration (MIGO默认值配置)

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)
MIGO_TR Create all transfer postings
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Settings for Transactions & Reference Documents
┌─────────────────────────────────────┐
│ Transaction: MIGO_GR │
│ ┌─────────────────────────────┐ │
│ │ Allowed: │ │
│ │ ✓ Goods Receipt │ │
│ │ ✗ Goods Issue │ │
│ │ ✗ Transfer Posting │ │
│ │ │ │
│ │ Reference Documents: │ │
│ │ ✓ Purchase Order │ │
│ │ ✗ Material Document │ │
│ └─────────────────────────────┘ │
└─────────────────────────────────────┘
💡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?” No, use specific IMG activity
“Standard MIGO field status?” All fields optional; GR/Issue Slip hidden
“Required entry fields with HiLi?” Only for GOHEAD… and GOITEM… field names
“Transaction for GR only?” MIGO_GR
“Transaction for GI only?” MIGO_GI
“How to hide a field per movement type?” Delete the entry from the field selection table
“How to show a hidden field?” Choose New Entry → enter movement type + field
“Copy plant → plant parameters?” Parameters are also copied from reference plant
“Special stock fields in field selection?” Always shown automatically – no config needed

LE收货流程 (★★★★)

#logistics-execution #goods-receipt

概览表 (一眼对比)

Step Document Description
1 Material Document Post GR in IM (MIGO)
2 Transfer Requirement (TR) Auto-generated; planning basis for putaway
3 Transfer Order (TO) Handling instruction for storeperson
4 Confirmation Report completion of putaway

Process Flow (流程图)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
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
“TO created with reference to?” Transfer Requirement
“Can TO be auto-created?” Yes, directly after GR posting (background)
“Stock status before TO confirm?” In transit – shown as both removal + putaway
“Can you use stock during putaway?” No, must confirm TO first
“Putaway strategy determines?” Final storage bin within storage type
“WM movement types linked to?” IM movement types via Customizing tables
0%