吴让宇(Mark)

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

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

SAP Fiori ABAP CDS OData Dify Docker AI LLM

后勤执行练习 (Unit 11 Practice)

发表于 2026-05-13 更新于 2026-08-08 分类于 SAP_MM ， SCM510_库存管理， 11-后勤执行本文字数： 1.1k 阅读时长 ≈ 4 分钟

后勤执行 Practice (10 questions)

#practice #logistics-execution

Keyword	Answer
LE 3 components	WM (from MM), Shipping (from SD), Transportation (from SD)
Warehouse # assignment	Plant + Storage Location
Interim storage prefix	9 (e.g., 902 GR, 916 shipping)
GR process form	IM-posting-driven
GI process form	Delivery-driven
TO =	Handling instruction for physical movement
Picking status A → C	Not picked → Fully picked

Question 1 - LE Components [recall]

Name the three components of Logistics Execution and state which SAP modules they were originally part of.

Warehouse Management – originally from MM (Materials Management)
Shipping – originally from SD (Sales and Distribution)
Transportation – originally from SD (Sales and Distribution)

LE bundled these existing functions together and developed them further.

Question 2 - Organizational Unit Assignments [recall]

Match each LE organizational unit to its assignment: warehouse number, shipping point, transportation planning point.

Organizational Unit	Assigned to
Warehouse Number	Plant + Storage Location (1:N)
Shipping Point	Plants (N:N possible)
Transportation Planning Point	Company Code (1:1)

Key rule: A plant-SLoc combination can only be assigned to one warehouse number.

Question 3 - Interim Storage Areas [recall]

What is special about interim storage areas in the warehouse number substructure? Name two examples and their storage type keys.

Interim storage areas are recognized by their key starting with 9. They form the link between IM and WM – every goods movement affecting both IM and WM is processed through an interim storage area. Examples:

902: Goods receiving zone (for external receipts)
916: Shipping zone (for outbound deliveries)

Stock in these areas is represented as quants.

Question 4 - Two Process Forms [application]

A colleague asks: “For a goods receipt from a vendor, should we create the delivery first or post the IM goods receipt first?” What is the correct answer?

For a goods receipt from a vendor (external procurement), the process is IM-posting-driven: the IM goods receipt is posted first (via MIGO). This automatically generates a transfer requirement. The putaway is then completed via a transfer order.

The delivery-driven form applies to outbound processes (sales orders) where the outbound delivery is created first.

Question 5 - GR Process: Transfer Requirement [recall]

What conditions must be met for the system to automatically generate a transfer requirement during a goods receipt?

The system checks for each PO item whether the plant-storage location combination is assigned to a warehouse number in Customizing. If yes:

A WM tab page appears at item level in MIGO
When GR is posted to that SLoc, the system generates a transfer requirement (in addition to material and accounting documents)
The incoming quantity is booked into interim storage area 902 as a quant

Question 6 - Transfer Order and Stock Status [application]

During a GR putaway process, the transfer order has been created but not yet confirmed. Can the warehouse manager access this stock for another order?

No. After the TO is created but before confirmation, the stock is in transit. In the WM stock overview (LS26), it is shown as:

Stock to be removed from the goods receiving area (902)
Stock to be placed (putaway) at the destination storage type

The stock is not accessible until the TO is confirmed.

Question 7 - Outbound Delivery Creation [recall]

When creating an outbound delivery (VL01N) with reference to a sales order, what information does the system determine for each delivery item?

The system determines:

Picking storage location for each item
Whether that SLoc is assigned to a warehouse number (if yes, displayed in delivery)
Overall picking status (e.g., A = not yet picked)
Stock removal status (whether TO is required)
Shipping dates from the order (GI date, loading date, material availability date)

Question 8 - Picking Status Flow [application]

An outbound delivery shows picking status “A”. After what actions does it change to “C”?

The status changes from A → C through these steps:

Create transfer order (LT03) with reference to the outbound delivery for stock removal
Confirm the transfer order (via VL06O → Confirm Picking, or LT12)

After confirmation, both statuses show C:

Picking status: C = Fully picked
WM transfer order status: C = Confirmed

Only then can you post GI (VL02N).

Question 9 - Post GI Prerequisites [application]

A user tries to post goods issue for an outbound delivery but the system does not allow it. What should they check?

Check the Picking tab in the outbound delivery (VL02N):

Both statuses must be C (Fully picked AND WM TO confirmed)
The transfer order must have been confirmed before GI posting
If status is still A, the TO has not been created or confirmed yet

The system validates that picking is complete before allowing the IM goods issue posting.

Question 10 - GR vs GI Process Comparison [recall]

Compare the GR and GI processes with LE: which form are they, what is the interim storage area, and when does the IM posting occur?

Aspect	GR with LE	GI with LE
Process form	IM-posting-driven	Delivery-driven
IM posting timing	First (at beginning)	Last (after picking)
Interim storage	902 (GR zone)	916 (shipping zone)
First LE document	Transfer Requirement (auto)	Outbound Delivery (manual)
TO purpose	Putaway (into warehouse)	Picking (out of warehouse)
Stock destination	Rack storage (final bin)	Shipping zone → customer

Keyword	Answer
LE source modules	WM from MM, Shipping + Transportation from SD
Warehouse # ↔ assignment	1 warehouse # : N plant-SLoc combos
Storage section minimum	At least 1 per storage type (mandatory)
Picking area	Optional (unlike storage section)
Interim storage keys	Start with 9
GR zone type	902
Shipping zone type	916
GR process	IM posting → TR → TO → Confirm
GI process	Sales order → Delivery → TO → Confirm → GI
TO = physical movement doc	Handling instruction for storeperson
Picking status A	Not yet picked
Picking status C	Fully picked
Stock during putaway (TO not confirmed)	In transit, not accessible
VL06O	Outbound delivery monitor
Post GI T-code	VL02N

后台配置练习 (Unit 10 Practice)

发表于 2026-05-13 更新于 2026-08-08 分类于 SAP_MM ， SCM510_库存管理， 10-后台配置本文字数： 954 阅读时长 ≈ 3 分钟

后台配置 Practice (10 questions)

#practice #customizing

Keyword	Answer
Document type WE	Goods receipt for PO
New movement type prefix	9, X, Y, Z
Quantity string	Fixed, cannot change
Account modifier	Differentiates G/L accounts within same value string
Plant parameters OMNH	Central overview, not for activation of negative stock

Question 1 - Accounting Document Types [recall]

Which accounting document type is used for goods receipts with reference to purchase orders?

WE (Goods Receipts for Purchase Orders). The document type determines the number range and is assigned per company code and fiscal year. Other key types: WA (GI/transfer), WI (inventory differences), WL (GI for deliveries).

Question 2 - Number Assignment for Material Documents [recall]

Can you change the transaction types (WA, WE, WI, etc.) for material document number assignment?

No. Transaction types are fixed in the SAP system. However, you can change the number range intervals and assign transaction types to different number range groups.

Question 3 - Reservation Number Assignment [recall]

A consultant asks whether reservations can use external number assignment. What is the answer?

For reservations created directly in SAP ERP: only internal number assignment is possible. External number assignment is available only when using BAPI BAPI_RESERVATION_CREATE1 with number range RB. The standard number range is 01 and is valid for all plants in the client.

Question 4 - Movement Type Control Functions [recall]

Name at least four functions controlled by the movement type in Inventory Management.

Key control functions include:

Quantity update (via quantity string)
Value update & account determination (via value string)
Field selection (screen structure)
Shelf life expiration date check
Automatic PO generation at GR
Automatic creation of storage location data
Stock determination
Dynamic availability check

Question 5 - Quantity String vs Value String [application]

A colleague wants to change the quantity string for movement type 101 to modify how quantities are updated. Is this possible?

No. Both quantity strings and value strings are fixed amounts in the SAP system and cannot be changed. The assignment of a quantity string to a movement type is also fixed. The colleague should select a different template movement type that already has the desired quantity/value update behavior.

Question 6 - Account Modifier [application]

Movement type 201 (GI to cost center) and movement type 551 (GI for scrapping) both issue goods from unrestricted stock. How does the system post to different consumption accounts?

Through the account modifier (科目修改码). The value string is the same, but the account modifier serves as a second key within the value string. For different account determination transactions, the account modifier routes postings to different G/L accounts. This ensures that cost center withdrawals and scrapping hit different consumption accounts.

Question 7 - Creating a New Movement Type [application]

You need to create a new movement type Z01 based on movement type 201. List the steps and any key rules.

Steps:

Copy movement type 201 with all subentries (do not create from scratch)
Key must start with 9, X, Y, or Z → use Z01
Save the new movement type first
Then modify control parameters (field selection, allowed transactions, etc.)
Also copy and assign the reversal movement type and reference movement type
Ensure all dependent entries are copied (critical!)

Question 8 - Plant Parameters [recall]

Your team lead wants to activate negative stock management using the plant parameters transaction (OMNH). Is this possible?

No. The activation of negative stocks is not possible through plant parameters (OMNH). OMNH provides only a central overview of plant-level settings. The actual activation of negative stock must be done in the specific IMG activity for negative stock settings. General rule: make settings in the relevant IMG activities, not in the central plant parameters view.

Question 9 - MIGO Field Selection [application]

In your company, the delivery note field must always be filled during goods receipt. How do you configure this?

Use the Field Selection for Transaction MIGO in Customizing (SPRO → Materials Management → Inventory Management → Settings for Enjoy Transactions → Settings for Goods Movements (MIGO) → Field Selection). Set the Delivery Note field (GOHEAD-based field) to Required Entry. When users post without filling it, the system will highlight the field with the “HiLi” attribute and prevent posting.

Question 10 - MIGO Transaction Variants [recall]

A user should only be able to post goods receipts from external procurement. Which transaction do you assign?

Assign transaction MIGO_GR. This restricted transaction only allows entering goods receipts from external procurement. Other variants:

MIGO_GO: GR for production orders only
MIGO_GI: GI and other GR only
MIGO_GS: Subcontracting subsequent adjustment only
MIGO_TR: Transfer postings only
MIGO: All goods movements (unrestricted)

Keyword	Answer
Doc type for GR with PO	WE
Doc type for inventory diff	WI
Can change transaction types?	No, only number range intervals/groups
Reservation NR scope	Client-level, internal only
External reservation NR	RB via BAPI only
Quantity/Value string	Fixed, cannot modify
Account modifier	Differentiates G/L accounts in same value string
New movement type prefix	9, X, Y, Z
Negative stock in plant params?	Cannot activate there
MIGO_GR purpose	GR from external procurement only
Hidden field in standard MIGO	Goods Receipt/Issue Slip
Copy plant → plant params?	Also copied from reference

后勤执行概述 (Logistics Execution Overview)

发表于 2026-05-13 更新于 2026-08-08 分类于 SAP_MM ， SCM510_库存管理， 11-后勤执行本文字数： 704 阅读时长 ≈ 3 分钟

后勤执行概述 (★★★★)

#logistics-execution #warehouse-management

概览表 (一眼对比)

Component	Source Module	Function
Warehouse Management (WM)	Copied from MM	Storage bin management, putaway, stock removal
Shipping (装运)	Copied from SD	Outbound delivery processing
Transportation (运输)	Copied from SD	Transportation planning & execution

Logistics Execution Components (后勤执行组件)

Logistics Execution (LE) bundles existing logistics functions and connects to PP, MM, and SD. It can also run as a stand-alone system.

Logistics Execution (LE)
┌─────────────────────────────────────────────────┐
│                                                 │
│  ┌──────────────────┐  ┌─────────────────────┐  │
│  │ Warehouse Mgmt   │  │ Shipping            │  │
│  │ (from MM)        │  │ (from SD)           │  │
│  └──────────────────┘  └─────────────────────┘  │
│                                                 │
│  ┌──────────────────────────────────────────┐   │
│  │ Transportation (from SD)                 │   │
│  └──────────────────────────────────────────┘   │
│                                                 │
│  Links: Procurement ◄──── LE ────► Distribution │
└─────────────────────────────────────────────────┘

Organizational Units (组织单位)

Organizational Unit	Description	Assignment
Warehouse Number (仓库号)	Top-level WM unit; represents a warehouse complex	Assigned to plant + storage location
Shipping Point (装运点)	Place or group handling shipping processing	Assigned to plants (many-to-many)
Transportation Planning Point (运输计划点)	Required for transportation processing	Assigned to company code (1:1)

Assignment Rules

Warehouse Number ←──── 1:N ────► Plant + Storage Location
   │                                        │
   │   One plant-SLoc can be assigned to    │
   │   only ONE warehouse number            │
   │   BUT one warehouse number can cover   │
   │   multiple plant-SLoc combinations     │
   └────────────────────────────────────────┘

Shipping Point ←──── N:N ────► Plant
   (One plant can have multiple shipping points)

Transportation Planning Point ──1:1──► Company Code
   (Required for shipment cost settlement)

Warehouse Number Substructure (仓库号子结构)

Warehouse Number (仓库号)
├── Storage Type (存储类型)
│   ├── e.g., High rack, Fixed bin, Bulk storage
│   ├── Interim Storage Area (过渡存储区, key starts with 9)
│   │   ├── 902: Goods receiving zone
│   │   ├── 916: Shipping zone (deliveries)
│   │   └── Links IM ↔ WM
│   │
│   ├── Storage Section (存储区域) [MANDATORY, at least 1]
│   │   ├── Fast-moving items → front section
│   │   ├── Perishable goods → refrigerated section
│   │   └── Material → Section assignment via indicator
│   │
│   ├── Picking Area (拣货区) [OPTIONAL]
│   │   └── For technical stock removal purposes
│   │
│   └── Storage Bin (存储仓位) [Master Data]
│       └── Created within a storage section

Storage Type Comparison

Storage Type	Key Feature	Example
Regular types	Physical/org separation	High rack, bulk storage, fixed bin
Interim storage areas (key starts with 9)	Link between IM and WM	GR zone (902), GI zone (916)

Interim Storage Areas (过渡存储区)

Interim storage areas are the link between IM and WM:

Area	Key	Purpose
Goods receiving zone	902	GR from external procurement
Shipping zone (deliveries)	916	Outbound delivery staging
Goods issue area	910	GI staging

Basic Process Forms (基本流程形式)

Two fundamental process forms for GR/GI in LE:

Form	Trigger	Sequence
Delivery-driven (交货驱动)	Delivery created first	Delivery → TO → Confirm → IM posting
IM-posting-driven (IM过账驱动)	IM posting first	IM posting → Transfer Requirement → TO → Confirm

Form 1: Delivery-Driven (e.g., outbound from vendor)
┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
│ Delivery │───►│ Transfer │───►│ Confirm  │───►│ IM       │
│ created  │    │ Order    │    │ TO       │    │ Posting  │
└──────────┘    └──────────┘    └──────────┘    └──────────┘

Form 2: IM-Posting-Driven (e.g., GR against PO)
┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
│ IM       │───►│ Transfer │───►│ Transfer │───►│ Confirm  │
│ Posting  │    │Requirem't│    │ Order    │    │ TO       │
└──────────┘    └──────────┘    └──────────┘    └──────────┘

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

Scenario/Keyword	Answer
“LE components?”	WM (from MM), Shipping (from SD), Transportation (from SD)
“Warehouse number assignment?”	Assigned to plant + storage location (1:N)
“Can one SLoc have 2 warehouse numbers?”	No, only one warehouse number per plant-SLoc
“Interim storage area key prefix?”	Starts with 9
“GR zone storage type?”	902
“Shipping zone storage type?”	916
“Minimum storage sections per storage type?”	At least one (mandatory)
“Delivery-driven vs IM-posting-driven?”	Delivery → TO → Confirm → IM vs IM → TR → TO → Confirm
“Transfer order is…?”	The document for all physical material movements in the warehouse
“Can LE run standalone?”	Yes, separate from SAP context

SCM500 - 快速参考

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 00-仪表盘本文字数： 1.3k 阅读时长 ≈ 5 分钟

SCM500 Quick Reference

#dashboard #procurement #mm

Key Transaction Codes → 采购订单基础 / 收货基础 / 发票基础

T-Code	Description	Usage
ME21N	Create Purchase Order	Central PO creation transaction
ME22N	Change Purchase Order	Modify existing PO
ME23N	Display Purchase Order	View PO details
ME51N	Create Purchase Requisition	PR creation
ME52N	Change Purchase Requisition	Modify PR
ME53N	Display Purchase Requisition	View PR details
ME41	Create Request for Quotation	RFQ creation
ME47	Maintain Quotation	Enter vendor quotations
ME49	Price Comparison	Compare quotations
ME31K	Create Contract	Outline agreement — contract
ME33K	Display Contract	View contract details
ME21	Create PO (old)	Legacy PO transaction
MIGO	Goods Movement	GR and all goods movements
MB52	Warehouse Stock Report	Current stock by material/plant
MMBE	Stock Overview	Stock overview by storage location/batch
MB51	Material Document List	Display material movements
MIRO	Post Invoice	Invoice verification entry
MR8M	Cancel Invoice	Reverse posted invoice
MRRL	Evaluated Receipt Settlement (ERS)	Automatic invoice settlement
MK01	Create Vendor (Purchasing)	Vendor master — purchasing view
XK01	Create Vendor (Central)	Vendor master — all views
MK03	Display Vendor (Purchasing)	View vendor purchasing data
MM01	Create Material	Material master creation
MM02	Change Material	Modify material master
MM03	Display Material	View material master
ME11	Create Purchasing Info Record	Info record creation
ME13	Display Purchasing Info Record	View info record
ME59N	Auto-Create PO from PR	Automated PO generation
ML81N	Service Entry Sheet	Create/maintain service entry sheets
AC03	Display Service Master	Service master record display
MD04	Stock/Requirements List	MRP current situation
MD06	MRP Evaluation	MRP result overview
ME2M	POs by Material	PO reporting by material
ME2N	POs by PO Number	PO reporting by number
ME2W	POs by Supplying Plant	PO reporting by vendor

Organizational Levels → 采购流程与组织层级

Level	Description	Assignment
Client	Highest level, central repository	—
Company Code	Legal entity for external reporting	Assigned to client
Plant	Physical/logical location for production/stock	Assigned to company code
Storage Location	Subdivision of plant for inventory	Assigned to plant
Purchasing Organization	Negotiates conditions with vendors	Assigned to company code(s)
Purchasing Group	Buyer or group of buyers	Assigned to purchasing org

Document Types → 采购订单基础 / 收货基础 / 发票基础

Document	Purpose	Key Fields
Purchase Requisition	Internal request for materials/services	PR number, material, quantity, delivery date
Request for Quotation	Solicit vendor bids	RFQ number, vendor, deadline
Quotation	Vendor’s bid response	Quotation number, price, validity
Purchase Order	Formal order to vendor	PO number, vendor, items, prices, delivery date
Contract	Long-term outline agreement	Contract number, target quantity/value, validity
Scheduling Agreement	Delivery schedule with vendor	SA number, schedule lines
Goods Receipt	Confirmation of material receipt	Material document, movement type, posting date
Invoice	Vendor bill for goods/services	Invoice number, amount, tax, PO reference

Key Movement Types → 库存类型与收货

Movement Type	Description	Key Usage
101	Goods receipt for purchase order/production order	Standard GR against PO
102	Goods receipt for PO — reversal	Cancel GR
103	Goods receipt into GR blocked stock	Quality inspection upon receipt
105	Release from GR blocked stock	Move from blocked to unrestricted
122	Return delivery to vendor	Return goods to vendor
321	Transfer from QI to unrestricted	Release from quality inspection
322	Transfer from unrestricted to QI	Reverse 321
343	Transfer from blocked to unrestricted	Release from blocked stock
344	Transfer from unrestricted to blocked	Reverse 343
261	Goods issue for production order	Consumable issue to production

Price Control Comparison → 物料评估基础

Aspect	Standard Price (S)	Moving Average Price (V)
Price changes	Only by manual revaluation	Automatic on each GR/Invoice
GR price ≠ current price	Difference posted to price difference account	MAP recalculated automatically
Invoice price ≠ PO price	Difference posted to price difference account	MAP recalculated; if coverage insufficient, difference to price difference account
Debit/credit from price changes	Posted to separate account	Adjusted in stock account directly
Recommended for	Semi-finished/finished goods	Raw materials and trading goods
Valuation stability	High — constant price per period	Fluctuates with each receipt

Moving Average Price Formula → 物料评估基础:

1	New MAP = (Total Stock Value + New Receipt Value) / (Total Stock Qty + New Receipt Qty)

Stock Value Calculation → 物料评估基础:

1	Stock Value = Stock Quantity × Price (MAP or Standard)

Account Assignment Categories → 消耗品采购订单 / 消耗品概述

Category	Description	Account Assignment	Stock Posting
(blank)	Standard — stock item	No account assignment — material is valuated	Yes, to valuated stock
K	Cost center	Cost center (KOSTL)	No — consumed directly
A	Asset	Asset number (ANLN1)	No — capitalized directly
F	Production order	Order number (AUFNR)	No — consumed by order
P	Project (WBS element)	WBS element (PS_PSP_PNR)	No — charged to project
U	Unknown (at PR level)	Determined later	Determined later

Item Categories → 采购订单基础 / 消耗品采购订单

Category	Description	Account Assignment Required	Typical Use
(blank)	Standard	No (stock material)	Stock materials
B	Limit	Yes	Services without known quantity — lump sum
D	Service	Yes	External services with service entry sheet
K	Consignment	No	Vendor consignment stock
L	Subcontracting	No	Subcontracting orders
U	Stock transfer	No	Stock transfer between plants

Condition Technique → 条件与定价

Component	Description	Example
Condition Type	Individual pricing element	PB00 (gross price), RA01 (discount), MWST (tax)
Access Sequence	Search strategy for condition records	Ordered list of condition tables
Condition Table	Combination of key fields	Vendor + Material, Vendor + Material Group
Condition Record	Actual stored price/discount value	PB00: Vendor 1000 + Material M-01 = $10.00
Pricing Procedure	Ordered list of condition types	RM0000 series for purchasing
Procedure Determination	Which procedure for which document	Purchasing org + document type → procedure

Access Sequence Flow → 条件与定价:

Condition Type → Access Sequence → Condition Tables (ordered by priority)
  → Table 1: Vendor + Material + Plant
  → Table 2: Vendor + Material
  → Table 3: Vendor + Material Group
  → (first match wins)

Vendor Master Data Views → 供应商主数据

View	Level	Key Data
General Data	Client-level	Name, address, communication, bank details
Company Code Data	Company code-level	Reconciliation account, payment terms, dunning
Purchasing Data	Purchasing org-level	Currency, Incoterms, ordering address, partner functions

Material Master Data Views → 物料主数据

View	Level	Key Data
Basic Data	Client-level	Description, base UoM, material group, weight
Sales	Sales org + distribution channel	Sales price, delivery plant, tax indicators
Purchasing	Plant-level	Purchasing group, MRPr controller, lot size
MRP	Plant-level	MRP type, lot size, reorder point, planned delivery time
Accounting	Plant-level	Valuation class, price control, standard/moving avg price
Storage	Plant + storage location	Storage conditions, shelf life

Source Determination Priority → 合同与货源确定

Priority	Source	Description
1	Fixed vendor in source list	Explicitly fixed source of supply
2	Quota arrangement	Automatic allocation based on quota percentages
3	Outline agreement (contract)	Long-term contract with released quantities
4	Purchasing info record	Standard info record with valid price
5	Last PO	Most recent purchase order price

MRP Lot-Sizing Procedures → 物料需求计划

Procedure	Description	Behavior
MB	Monthly lot size	Consolidate requirements per month
FX	Fixed lot size	Order a fixed quantity each time
EX	Exact lot size	Order exactly the requirement quantity
WB	Weekly lot size	Consolidate requirements per week

Invoice Verification Types → 发票校验与交货成本

Type	Transaction	Description
Standard (MIRO)	MIRO	Manual invoice entry with PO reference
ERS (Evaluated Receipt Settlement)	MRRL	Automatic invoice creation based on GR
Subsequent Debit/Credit	MIRO	Additional charge or credit after initial invoice

ERS Prerequisites → 发票校验与交货成本:

GR-based Invoice Verification flag set on vendor/material
ERS indicator set in vendor master (purchasing view)
Valid info record or contract price must exist
Goods receipt must be posted

发票基础

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 01-采购基础本文字数： 810 阅读时长 ≈ 3 分钟

发票基础 (★★★)

#invoice #procurement

Overview Table — Invoice Verification

Item	Key Point
Transaction	MIRO（Logistics Invoice Verification）
Prerequisite	需要有 PO 和（通常）GR 作为参考
Purpose	校验供应商发票与 PO/GR 是否一致
Result	更新供应商余额、清结 GR/IR、过账税金

Transaction MIRO — Screen Areas

┌─────────────────────────────────────────────────┐
│              MIRO — Logistics Invoice Verification│
├─────────────────────────────────────────────────┤
│ Transaction Data                                 │
│  [Invoice ▼]  [PO Reference]  [Amount]  [Tax]   │
├─────────────────────────────────────────────────┤
│ Header Data                                      │
│  (Invoice Date, Posting Date, Reference...)      │
├─────────────────────────────────────────────────┤
│ Assignment                                       │
│  (Company Code, Currency...)                     │
├─────────────────────────────────────────────────┤
│ Invoice Items                                    │
│  ┌─────────────────────────────────────────┐     │
│  │PO │Material│Qty │Amount │Tax │GL Account│     │
│  ├───┼────────┼────┼───────┼────┼──────────┤     │
│  │450│100-100 │100 │1000.00│190│ 891000   │     │
│  └─────────────────────────────────────────┘     │
├─────────────────────────────────────────────────┤
│ Vendor Data                                      │
│  (Vendor No., Name, Terms of Payment...)         │
├─────────────────────────────────────────────────┤
│ Balance                                          │
│  ┌─────────────────────────────────────────┐     │
│  │ Balance: 0.00  ← 必须为零才能过账        │     │
│  └─────────────────────────────────────────┘     │
└─────────────────────────────────────────────────┘

Screen Area	Purpose
Transaction Data	选择业务类型（Invoice/Credit Memo）、输入金额和税码
Header Data	发票日期、过账日期、参考号
Assignment	公司代码、货币等分配信息
Invoice Items	发票行项目（来自 PO 的 GR 数据）
Vendor Data	供应商信息、付款条件
Balance	显示借贷方余额，必须为零才能过账

Invoice Against PO Process Flow

┌───────────────┐
│  Enter MIRO    │
│  Select        │
│  "Invoice"     │
└───────┬───────┘
        │
        ▼
┌───────────────┐
│  Enter PO No.  │
│  & Invoice     │
│  Details       │
└───────┬───────┘
        │
        ▼
┌───────────────┐
│  System        │
│  Retrieves     │
│  PO + GR Data  │
└───────┬───────┘
        │
        ▼
┌───────────────┐
│  Verify        │
│  Amounts / Qty │
│  vs Invoice    │
└───────┬───────┘
        │
        ▼
┌───────────────┐         ┌───────────────┐
│  Check Balance │         │ Tolerance     │
│  = 0?          │──No───→ │ Check         │
└───────┬───────┘         └───────┬───────┘
        │ Yes                     │
        │                         │ Within tolerance?
        ▼                         ▼
┌───────────────┐         ┌───────────────┐
│  Post Invoice │         │ Adjust/Block  │
│               │         │ Payment       │
└───────────────┘         └───────────────┘

Tolerances and Payment Blocks

Tolerance Groups

Tolerance Check	Description
Price Variance	发票价格 vs PO 价格的差异容忍度
Quantity Variance	发票数量 vs GR 数量的差异容忍度
Amount Variance	金额差异的绝对值限制
Moving Average Price	移动平均价变化的百分比限制

发出警告或错误消息
自动设置 payment block（付款冻结）
需要手动处理后才能过账

Payment Block

Block Type	Description
Automatic Block	系统因超容忍度自动设置
Manual Block	用户手动设置付款冻结
No Block	差异在容忍范围内，不冻结

Documents Generated by Invoice

Document	Always Generated?	Description
Invoice Document	是	记录发票校验的凭证
Accounting Document	是	记录财务过账（供应商贷记、税金等）

Effect of Invoice Verification

Effect	Description
Update Vendor Balance	供应商应付余额增加（贷记供应商账户）
Clear GR/IR	清结 GR/IR 清算科目（GR 时已贷记，Invoice 时借记）
Post Tax	计算并过账进项税金
Update PO History	PO 历史记录更新发票信息

Accounting Entries at Invoice Verification

Invoice Verification 时的会计分录：

  借 (Debit)          贷 (Credit)
  ──────────          ──────────
  GR/IR Clearing      Vendor (AP)
  Tax Account
  Price Difference
   (if variance)

Invoice Verification in the Procurement Cycle

PO (ME21N) → GR (MIGO) → Invoice (MIRO) → Payment (F-53)

              GR 时:          Invoice 时:
              存货 ↑          供应商(AP) ↑
              GR/IR ↑         GR/IR ↓
                              Tax ↑

Exam/Test Patterns

Scenario/Keyword	Answer
“发票校验的事务码？”	MIRO
“MIRO 中 Balance 必须为多少才能过账？”	必须为零
“超出容忍度会怎样？”	系统设置 Payment Block（付款冻结）
“发票校验更新哪个清算科目？”	GR/IR Clearing Account
“发票校验对供应商的影响？”	供应商应付余额增加（贷记）
“GR/IR 科目的作用？”	过渡科目，GR 贷记、Invoice 借记
“发票过账生成什么凭证？”	Invoice Document + Accounting Document
“Payment Block 可以自动设置吗？”	可以，超容忍度时自动设置
“发票校验必须先有 GR 吗？”	不一定，但通常需要 GR 作为参考（取决于配置）
“发票日期在哪个区域输入？”	Header Data

SCM500 - 采购流程学习地图

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 00-仪表盘本文字数： 756 阅读时长 ≈ 3 分钟

SCM500 — Processes in Procurement Study Map

#dashboard #procurement #mm

Overview

SAP SCM500 Certification Course: Processes in Procurement
Covers external procurement processes in SAP ERP (Materials Management)
Duration: 5 days, SAP ERP ECC 6.0 platform
Core exam areas: organizational structures, master data, procurement cycle (PO → GR → Invoice), automation, and reporting

Topic Map

Unit	Source	Notes	Status
Unit 1: Procurement Basics	Unit 1	采购流程与组织层级, 采购订单基础, 收货基础, 发票基础	[ ]
Unit 2: Master Data	Unit 2	供应商主数据, 物料主数据, 输入辅助, 批量维护	[ ]
Unit 3: Stock Material Procurement	Unit 3	条件与定价, 报价请求与处理, 参考创建采购订单, 采购信息记录, 物料评估基础, 库存类型与收货, 发票校验与交货成本	[ ]
Unit 4: Consumable Procurement	Unit 4	消耗品概述, 采购申请, 消耗品采购订单, 估价与非估价收货, 一揽子采购订单	[ ]
Unit 5: External Services Procurement	Unit 5	服务主记录与条件, 服务订购, 服务确认与发票	[ ]
Unit 6: Automated Procurement	Unit 6	物料需求计划, 合同与货源确定, 自动化采购流程	[ ]
Unit 7: Reporting & Analysis	Unit 7	标准报表, 后勤信息系统	[ ]

Practice Notes

Question Set	Link
Procurement Basics	采购基础练习
Master Data	主数据练习
Stock Material Procurement	库存物料采购练习
Consumable Procurement	消耗品采购练习
External Services Procurement	外部服务采购练习
Automated Procurement	自动化采购练习
Reporting & Analysis	报表与分析练习

Study Tools

Tool	Description	Link
Exam Traps	Common mistakes and pitfalls in SCM500 exams	[[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
Quick Reference	Complete cheat sheet with T-codes, movement types, and formulas	[[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/快速参考]]

Tag Index

Tag	Topics	Hierarchy
`#procurement`	Top-level domain	Domain
`#mm`	Materials Management module	Domain
`#master-data`	Vendor, material, info records	Domain
`#po`	Purchase Orders (creation, change, display)	Domain
`#gr`	Goods Receipt processing	Domain
`#invoice`	Invoice Verification (standard, ERS)	Domain
`#valuation`	Material Valuation (MAP, standard price)	Domain
`#conditions`	Pricing, condition technique, discounts/surcharges	Domain
`#mrp`	Material Requirements Planning, lot sizing	Domain
`#source-determination`	Source of supply, quotas, outlines	Domain
`#practice`	Practice questions	Note type
`#dashboard`	Dashboard notes	Note type
`#exam-traps`	Exam traps	Note type

Tag Rules: All tags are in English kebab-case. The domain tags #procurement and #mm are always applied together. Specific tags always include their parent domain tag. Concept notes carry one domain-level tag + relevant specific tags.

Weak Areas

Moving average price vs Standard price behavior during GR/Invoice → 物料评估基础 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
Account assignment categories and their effect on stock posting → 消耗品采购订单 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
Condition technique access sequence and pricing procedure → 条件与定价 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
Source determination priority rules → 合同与货源确定 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
Valuated vs non-valuated goods receipt → 估价与非估价收货 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]
MRP lot-sizing procedures and their implications → 物料需求计划 → [[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/考试陷阱]]

Non-core Topic Policy

Source	Content	Handling
Unit 8: Portal	SAP Enterprise Portal procurement scenarios	Skip — legacy UI, not core exam material
Unit 9: Self-Service	Self-Service Procurement (MSS/SAP SRM)	Skip — covers SRM integration, outside SCM500 scope
Unit 10: Navigation	SAP GUI navigation basics	Skip — prerequisite knowledge, not exam-tested
Exercises	Step-by-step exercise instructions	Exclude — hands-on lab content, not exam theory

考试陷阱

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 00-仪表盘本文字数： 1.8k 阅读时长 ≈ 7 分钟

SCM500 Exam Traps

#dashboard #exam-traps #procurement #mm

Collection of frequently tested pitfalls and common misconceptions in the SCM500 Processes in Procurement exam.

Material Valuation

Wrong: Moving average price only changes when you manually revalue the material.
Correct: Moving average price (V) is automatically recalculated on every goods receipt and every invoice receipt that has a price different from the PO price. The formula is: New MAP = (Current Stock Value + New Value) / (Current Stock Qty + New Qty).
物料评估基础

Wrong: With standard price control, all postings use the fixed price — no differences arise.
Correct: With standard price (S), if the GR price or invoice price differs from the standard price, the difference is posted to a price difference account. The standard price itself does NOT change (unless manually revalued).
物料评估基础

Wrong: All invoice price differences are always absorbed into the moving average price.
Correct: If the invoice price differs from the PO price and the invoice value exceeds the total stock value (i.e., stock coverage is insufficient), the system posts the uncovered portion to a price difference account instead of adjusting MAP.
物料评估基础

Account Assignment & Item Categories

Wrong: Every PO item must have an account assignment category.
Correct: Stock materials (item category blank) do not require an account assignment — the material is posted to valuated stock and valuated via the material master. Only consumable items (account assignment K, A, F, P) need direct account assignments.
消耗品采购订单 / 消耗品概述

Wrong: Category K stands for “Stock” because it starts with K.
Correct: Category K means Cost Center (Kostenstelle in German). Materials with this category are consumed directly to a cost center — they are not posted to valuated stock.
消耗品采购订单

Wrong: They are interchangeable terms.
Correct: Item category determines the type of procurement (standard, limit, service, subcontracting). Account assignment category determines where costs are allocated (cost center, asset, order). They serve different purposes but can interact — e.g., item category D (service) always requires an account assignment.
采购订单基础 / 消耗品采购订单

Goods Receipt & Stock Types

Wrong: GR always puts material into unrestricted stock.
Correct: GR can post to unrestricted-use, quality inspection, or blocked stock depending on the movement type and material master settings (e.g., post to inspection stock indicator). Movement type 103 posts to GR blocked stock; 101 with inspection setup posts to QI stock.
库存类型与收货

Wrong: All goods receipts create the same financial postings.
Correct: A valuated GR updates both quantity and value in the material master (stock account debited, GR/IR account credited). A non-valuated GR updates quantity only — no financial posting occurs until the invoice is posted. Non-valuated GR is used for account-assigned consumable materials.
估价与非估价收货

Wrong: Reversal with 102 always fully reverses the original posting.
Correct: For moving average price materials, if stock has been consumed since the original GR, the value reversal may differ because the current MAP has changed. For standard price materials, the price difference portion posts to a price difference account if the reversal price differs.
库存类型与收货 / 物料评估基础

Condition Technique & Pricing

Wrong: The system searches all condition tables and uses the cheapest price.
Correct: The access sequence searches condition tables in a defined priority order. The first valid condition record found is used — the system does NOT compare prices across tables. Order matters, not price comparison.
条件与定价

Wrong: Conditions are stored directly in PO document tables only.
Correct: Condition records are stored in condition tables (separate master data). When a PO is created, the system copies the condition values from the condition records. Changes to condition records after PO creation do not retroactively affect existing POs.
条件与定价

Wrong: Condition types only represent prices and discounts.
Correct: Condition types also cover freight, insurance, customs duties, taxes, surcharges, and delivery costs. Each has its own configuration in the pricing procedure with specific account keys for posting to different G/L accounts.
条件与定价 / 发票校验与交货成本

Source Determination & Info Records

Wrong: You cannot create a PO without a valid info record.
Correct: Info records are not mandatory. They serve as a default source of supply and price reference. A PO can be created by entering the vendor and price manually. However, for automated procurement (MRP-generated POs), a valid source of supply is required.
采购信息记录 / 合同与货源确定

Wrong: Once a source is marked as “fixed” in the source list, it is permanently locked.
Correct: A fixed source is a default preference used in automated source determination. During manual PO creation, the user can override the fixed source. The “fixed” flag primarily affects MRP-generated purchase requisitions.
合同与货源确定

Wrong: Checking “Info Update” on a PO always creates a new purchasing info record.
Correct: The Info Update indicator updates an existing info record with the current PO conditions. If no info record exists, then it creates one. It does not duplicate existing records.
采购信息记录

MRP & Automated Procurement

Wrong: MRP generates purchase orders automatically.
Correct: MRP typically creates purchase requisitions, not purchase orders directly. Purchase orders are then created from requisitions — either manually (ME21N with reference to PR) or automatically (ME59N). Only in specific configuration (with source list and automatic PO indicator) does the system create POs directly.
物料需求计划 / 自动化采购流程

Wrong: Lot size procedure doesn’t matter — you get the same quantity.
Correct: Different lot-sizing procedures produce different order quantities and timing. Fixed lot size (FX) always orders the same quantity regardless of requirement. Exact lot size (EX) orders exactly what is needed. Monthly/weekly lot sizes (MB/WB) consolidate requirements into fewer but larger orders. Each has different cost and inventory implications.
物料需求计划

Wrong: Once a contract is created, POs are automatically issued.
Correct: Contracts are outline agreements that define terms but do not trigger orders. You must create release orders (call-off orders) against the contract — either manually (ME21N referencing the contract) or via MRP with quota arrangement/source list. The contract itself does not generate POs.
合同与货源确定

Blanket Purchase Orders (Consumables)

Wrong: The limit on a blanket PO is the exact amount you must spend.
Correct: The limit is a maximum ceiling, not a target. You can spend up to but not exceed this amount across all service entry sheets/invoices against the blanket PO. There is no obligation to spend the full amount.
一揽子采购订单

Wrong: Blanket POs follow the same GR-based process as standard POs.
Correct: Blanket POs with item category B (limit) typically do not require a goods receipt. Invoicing is done directly against the PO. Service entry sheets (if applicable) serve as the equivalent of GR.
一揽子采购订单

External Services

Wrong: Service entry sheets are just another name for goods receipt.
Correct: Service entry sheets (ML81N) are the services equivalent of a goods receipt. They record the quantity of services performed. Unlike material GR, they must be explicitly accepted/released before the vendor can be paid. The acceptance step is unique to services.
服务确认与发票

Wrong: ERS can be used for any PO, any material, any vendor.
Correct: ERS has strict prerequisites: the vendor master must have the ERS indicator set, the material/vendor must allow GR-based invoice verification, and a valid price must exist in the info record or contract. ERS does not work for service POs or blanket POs without proper price conditions.
发票校验与交货成本

Organizational Levels

Wrong: Purchasing org has a 1:1 relationship with company code.
Correct: A purchasing organization can be assigned to one company code (standard), multiple company codes (cross-company), or no company code (cross-client reference). The assignment flexibility is a key exam point.
采购流程与组织层级

Wrong: Storage locations are assigned directly to company codes.
Correct: Storage locations are assigned to plants, and plants are assigned to company codes. The hierarchy is: Client → Company Code → Plant → Storage Location. You cannot assign a storage location to a company code directly.
采购流程与组织层级

Vendor Master Data

Wrong: Vendors are maintained at the plant level, like materials.
Correct: Vendor master data has three levels: General data (client-level, shared across all orgs), Company Code data (financial info per company code), and Purchasing data (per purchasing organization). Vendors are not plant-specific.
供应商主数据

[[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/学习地图]] → Weak Areas section
[[_posts/SAP_MM/SCM500_采购流程/00-仪表盘/快速参考]]

收货基础

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 01-采购基础本文字数： 710 阅读时长 ≈ 3 分钟

收货基础 (★★★)

#gr #procurement

Overview Table — Goods Receipt

Item	Key Point
Transaction	MIGO（统一收发货事务）
Movement Type	3 位数字键，决定业务类型（如 101 = 针对 PO 的 GR）
Generated Documents	Material Document + Accounting Document
Stock Effect	非限制使用库存增加
PO History Update	PO 历史记录更新收货信息

Transaction MIGO — Key Actions

Action	Description
A01 – Goods Receipt	收货（针对 PO、生产订单等）
A02 – Return Delivery	退货给供应商
A03 – Transfer Posting	转储过账
A04 – Cancellation	取消（冲销）之前的物料凭证

Movement Types — Common GR Types

Movement Type	Description	Key Usage
101	针对 PO 收货	最常用的 GR 类型
101	针对生产订单收货	同一 mvt type，不同参考
103	收货到 GR 阻塞库存	质检前暂存
105	从 GR 阻塞库存释放到非限制库存	质检通过后
122	退货给供应商	从非限制库存退回
161	退货给供应商（针对 PO）	创建退货 PO 时使用

Screen Areas in MIGO

┌────────────────────────────────────────────────┐
│              Menu Bar / Action Selection        │
│  [Goods Receipt ▼]  [For Purchase Order ▼]     │
├────────┬───────────────────────────────────────┤
│        │                                       │
│  Item  │         Header Data                   │
│  List  │  (Posting Date, Doc Date...)           │
│        │                                       │
│ (Left  ├───────────────────────────────────────┤
│  Panel)│                                       │
│        │     Material / Item Detail             │
│ Shows  │  (Material, Qty, Plant, SLoc,          │
│ PO     │   Batch, Movement Type...)             │
│ items  │                                       │
│        ├───────────────────────────────────────┤
│        │                                       │
│        │     Detail Tab Pages                   │
│        │  (Quantity, Where tab, Account          │
│        │   Assignment, Material...)             │
│        │                                       │
└────────┴───────────────────────────────────────┘

Goods Receipt Process Flow

┌──────────────┐
│  Enter MIGO   │
│  PO Number    │
└──────┬───────┘
       │
       ▼
┌──────────────┐
│  System       │
│  Retrieves    │
│  PO Items     │
└──────┬───────┘
       │
       ▼
┌──────────────┐
│  Select Items │
│  Enter Qty    │
│  & SLoc       │
└──────┬───────┘
       │
       ▼
┌──────────────┐
│  Post GR      │
│  (Check/Post) │
└──────┬───────┘
       │
       ├──────────────────────┐
       │                      │
       ▼                      ▼
┌──────────────┐    ┌──────────────┐
│  Material    │    │  Accounting  │
│  Document    │    │  Document    │
│  (Always)    │    │  (Usually)   │
└──────────────┘    └──────────────┘

Effect of Goods Receipt

Effect	Description
Increase Stock	非限制使用库存（或 GR 阻塞库存）增加
Update PO History	PO 的 “History” 标签页记录收货详情
Create Material Document	记录库存变动，始终生成
Create Accounting Document	记录财务过账（存货借记、GR/IR 贷记），通常生成

Material Document vs Accounting Document

Document	Always Generated?	Purpose
Material Document	是	记录所有库存变动
Accounting Document	通常（非寄售/评估物料时除外）	记录财务影响

PO History After GR

PO History Tab:
┌─────────────────────────────────────────┐
│ │Doc.Type│Doc. No │Qty    │Value        │
│ ├────────┼────────┼───────┼─────────────┤
│ │  WE    │50000001│ 100   │  1,000.00   │  ← GR entry
│ │  RE    │50000002│ -10   │  -100.00    │  ← Return entry
└─────────────────────────────────────────┘

Exam/Test Patterns

Scenario/Keyword	Answer
“收货的事务码？”	MIGO
“针对 PO 收货的移动类型？”	101
“GR 一定生成什么凭证？”	Material Document（物料凭证）
“寄售收货生成会计凭证吗？”	不生成，只有物料凭证
“移动类型是几位？”	3 位数字
“如何查看 PO 的收货历史？”	ME23N → History 标签页
“退货给供应商用什么移动类型？”	122 或 161
“收货到质检库存用什么移动类型？”	103（收货到 GR 阻塞库存）
“GR 对库存的影响？”	非限制使用库存增加

采购流程与组织层级

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 01-采购基础本文字数： 933 阅读时长 ≈ 3 分钟

采购流程与组织层级 (★★★★)

#procurement #mm

Overview Table — Procurement Cycle Phases

Phase	Description	Key Transaction
Determination of Requirements	识别物料/服务需求，创建采购申请	ME51N
Source Determination	确定供应来源（报价单、合同、信息记录）	ME41 / ME33K
Vendor Selection	比较报价，选择最优供应商	ME49
PO Handling	创建采购订单	ME21N
PO Monitoring	跟踪订单状态和交货进度	ME2N / ME23N
Goods Receipt	收货入库	MIGO
Invoice Verification	发票校验	MIRO
Payment	付款处理（FI 模块）	F-53

External Procurement Process Flow

┌───────────────────────┐
│ Determination of       │
│ Requirements (PR)      │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Source Determination   │
│ (Quota / Info Record)  │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Vendor Selection       │
│ (Comparison / Auto)    │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Purchase Order (PO)    │
│ ME21N                  │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ PO Monitoring          │
│ (Reminders / Status)   │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Goods Receipt (GR)     │
│ MIGO (mvt 101)         │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Invoice Verification   │
│ MIRO                   │
└──────────┬────────────┘
           │
           ▼
┌───────────────────────┐
│ Payment (FI)           │
│ F-53                   │
└───────────────────────┘

Special Procurement Types — Comparison

Type	Description	Key Feature
Stock Transport Order (STO)	工厂间库存调拨	属于内部采购，使用采购订单形式
Subcontracting (外协加工)	提供组件给供应商加工后收回	需维护 BOM，组件发到供应商库存
Vendor Consignment (寄售)	物料存放在本企业但归供应商所有	消耗时才产生应付，无发票校验
Pipeline (管道)	管道供应物料（如水、电）	按消耗量结算
Third-party Order (第三方订单)	供应商直接发货给客户	SD 销售订单触发，MM 创建 PO

Organizational Levels Hierarchy

                ┌──────────┐
                │  Client  │  (集团 — 最高层级)
                │  3-digit │
                └────┬─────┘
                     │
       ┌─────────────┼─────────────┐
       │                           │
┌──────▼──────┐             ┌──────▼──────┐
│ Company Code│             │  Purchasing  │
│   4-char    │             │ Organization │
└──────┬──────┘             └──────┬──────┘
       │                           │
┌──────▼──────┐             ┌──────▼──────┐
│    Plant    │◄────────────│  Purchasing  │
│   4-char    │   分配关系   │    Group     │
└──────┬──────┘             └─────────────┘
       │
┌──────▼──────────┐
│ Storage Location │
│    4-char        │
└─────────────────┘

Organizational Levels — Key Facts

Level	Key Length	Description	Key Relationship
Client	3-digit	集团最高层级，数据在此层共享	一个 Client 可包含多个 Company Code
Company Code	4-char	独立会计核算的最小单位	一个 CC 可包含多个 Plant
Plant	4-char	生产经营单位（工厂/仓库/分支机构）	可分配给多个 Purchasing Org
Storage Location	4-char	库存管理地点，隶属于 Plant	一个 Plant 下可有多个 SLoc
Purchasing Organization	4-char	负责采购活动的组织单位	可分配给 Company Code / Plant
Purchasing Group	3-char	采购员/采购组	独立于组织层级，代表采购员

Purchasing Organization Types

Type	Description	Example
Plant-specific	采购组织分配给一个工厂	工厂A有自己的采购部门
Cross-plant	采购组织为多个工厂服务（同公司代码内）	集中采购为多个工厂统一采购
Cross-company-code	采购组织跨公司代码服务	集团集中采购，服务多个子公司

Key Relationships Summary

Purchasing Org ──1:N──→ Plant
Purchasing Org ──1:1──→ Company Code  (cross-plant 时)
Plant          ──1:N──→ Storage Location
Company Code   ──1:N──→ Plant
Client         ──1:N──→ Company Code
Purchasing Group ──独立── 不分配给任何组织层级

Exam/Test Patterns

Scenario/Keyword	Answer
“寄售物料何时产生应付？”	消耗时（不是收货时）
“Client 的编号长度？”	3 位数字
“Plant 的编号长度？”	4 位字符
“采购组织可以跨公司代码吗？”	可以，cross-company-code 类型
“采购组分配给哪个组织？”	不分配给任何组织层级，独立存在
“Stock Transport Order 属于？”	内部采购，工厂间调拨
“外协加工需要维护什么？”	BOM（物料清单），组件发给供应商
“采购流程的第一步？”	Determination of Requirements（确定需求）
“发票校验后下一步？”	Payment（付款，FI 模块）
“Storage Location 隶属于？”	Plant

采购基础练习

发表于 2026-05-12 更新于 2026-08-08 分类于 SAP_MM ， SCM500_采购流程， 01-采购基础本文字数： 2.7k 阅读时长 ≈ 10 分钟

采购基础 Practice (10 questions)

#practice #采购基础

Keyword	Answer
采购流程阶段	确定需求 → 确定供应源 → 选择供应商 → 采购订单 → 监督 → 收货 → 发票校验 → 付款
组织层级	集团 → 公司代码 → 工厂 → 库存地点 → 采购组织 → 采购组
移动类型	3位数字，决定货物移动的类型、方向和字段屏幕
MIRO	Logistics Invoice Verification，发票校验事务
GR/IR	收货/发票收据清算科目，GR时贷记，IR时借记

Question 1 - 外部采购流程阶段 [recall]

描述外部采购（External Procurement）流程中的主要阶段，按正确顺序列出。

外部采购流程包含以下阶段（按顺序）：

确定需求（Determination of Requirements） — 创建采购申请
确定供应源（Source Determination） — 查找合适的供应来源
选择供应商（Vendor Selection） — 比较报价，选择最优供应商
采购订单（Purchase Order Processing） — 创建并发送PO给供应商
订单监督（PO Monitoring） — 跟踪订单状态和交货进度
收货（Goods Receipt） — 接收货物并入库
发票校验（Invoice Verification） — 校验发票与PO和GR是否匹配
付款处理（Payment Processing） — 向供应商付款（FI模块处理）

前面5步属于MM-PUR（采购）组件，GR属于MM-INV（库存管理），Invoice Verification属于MM-IVR。

Question 2 - 采购相关组织层级 [recall]

列出与采购流程相关的所有组织层级（Organizational Levels），并说明其层级关系。

采购相关的组织层级从上到下为：

集团（Client） — 最高层级，代表整个企业
公司代码（Company Code） — 独立的财务核算单位
工厂（Plant） — 物料管理、生产计划、物料需求的组织单元（如生产厂、仓库）
库存地点（Storage Location） — 工厂下区分不同库存的物理或逻辑位置
采购组织（Purchasing Organization） — 负责与供应商谈判采购条件的组织单元
采购组（Purchasing Group） — 负责日常采购活动的最小组织单元

关键要点：采购组织可以分配给一个公司代码（专用），多个公司代码（跨公司），或不分配（全局）。采购组不分配给任何组织层级，是一个独立的概念。

Question 3 - 创建采购订单的事务码 [recall]

在SAP中，哪个事务码用于创建采购订单（Purchase Order）？还列出相关的显示和修改事务码。

采购订单相关的主要事务码：

ME21N — 创建采购订单（EnjoySAP事务）
ME22N — 修改采购订单
ME23N — 显示采购订单
ME21/ME22/ME23 — 旧版事务码（仍可用）
ME29N — 释放采购订单（审批）
ME2N — 采购订单清单（按PO号）

创建PO时可以参考采购申请（ME51N创建）、报价（ME47）、信息记录或其他PO来创建。

Question 4 - 移动类型的定义 [recall]

什么是移动类型（Movement Type）？它控制了哪些内容？

移动类型是SAP MM中用于区分不同货物移动的3位数字代码。

主要功能：

决定货物移动的类型（收货、发货、转储等）
决定移动方向（入库、出库、库间转移）
控制字段屏幕布局（哪些字段必填、可选或隐藏）
触发自动过账到FI（通过自动科目确定）

常用移动类型：

101 — 针对采购订单的收货
102 — 针对采购订单的收货取消
103 — 收货到冻结状态
105 — 从冻结释放到非限制使用库存
311 — 工厂内库存地点间的转储 Posting
301 — 工厂到工厂的库存转移
261 — 针对生产订单的发货

移动类型 + 特殊库存标识 + 移动标识组合，可产生超过200种不同的货物移动场景。

Question 5 - 库存转储的采购类型 [application]

场景：公司代码1000下的工厂A需要从工厂B获取物料。两个工厂属于同一个公司代码。这种情况下应使用哪种采购类型？涉及哪些步骤和移动类型？

这是**工厂间库存转储（Stock Transfer between Plants）**场景。

采购类型分析：

同公司代码内工厂间转移 → 使用 库存转储采购订单（Stock Transport Order, STO）
不需要外部采购流程，但可以通过PO形式管理

可能的实现方式：

方式	转储类型	说明
MB1B + 301	一步法	直接从工厂B转储到工厂A，一次过账完成
STO + 2步	两步法	创建STO → 工厂B发货（351）→ 工厂A收货（101）

关键要点：

同公司代码内转储不产生FI凭证（库存只在公司代码内移动）
跨公司代码的转储会产生FI凭证
STO可以纳入MRP计划中自动生成

Question 6 - 收货时创建的凭证 [recall]

对采购订单执行收货（Goods Receipt）时，SAP系统会创建哪些凭证？

执行GR时会创建以下凭证：

物料凭证（Material Document） — MM模块，记录物料的数量变化和库存地点变化。物料凭证号 + 年份唯一标识一次货物移动。
会计凭证（Accounting Document） — FI模块，记录财务过账（如果该移动涉及价值变化）。包括：
- 借记：存货科目（库存增加）
- 贷记：GR/IR清算科目（Goods Received/Invoice Received）
可能创建的其他凭证：
- 如果物料有批次管理 → 自动创建批次
- 如果启用了质检 → 创建质检批（Inspection Lot）
- 如果有已计划的交货成本 → 额外的FI过账行项目

注意： 无价值物料（如非计价库存）的收货可能只创建物料凭证，不创建会计凭证。

Question 7 - 采购订单收货的库存变化和凭证 [application]

用户对采购订单4500000001执行了收货（MIGO，移动类型101）。该物料使用移动平均价（V价），PO单价为$15，收货数量100件。请说明此操作对库存和财务的影响。

库存变化：

该物料的非限制使用库存（Unrestricted-use Stock）增加 100件
如果物料有库存管理，库存地点的相关记录更新

财务过账（FI凭证）：

科目	借/贷	金额
存货科目（Stock Account）	借记（Debit）	$1,500
GR/IR清算科目（GR/IR Clearing）	贷记（Credit）	$1,500

移动平均价影响：

假设原来库存200件，MAP = $12
原库存价值 = 200 × $12 = $2,400
新收货价值 = 100 × $15 = $1,500
新MAP = ($2,400 + $1,500) / (200 + 100) = $13.00

创建的凭证：

物料凭证 — 记录100件入库
会计凭证 — 记录$1,500的财务过账
采购订单历史更新 — 记录本次GR

Question 8 - MIRO的用途 [recall]

MIRO事务码的用途是什么？它与MIGO有什么区别？

MIRO（Logistics Invoice Verification） 用于执行后勤发票校验。

MIRO的主要功能：

录入供应商发票并与采购订单、收货进行三单匹配
校验发票价格、数量与PO和GR是否一致
过账发票到FI（更新供应商应付余额）
处理计划内和计划外交货成本

MIRO vs MIGO的区别：

特征	MIGO	MIRO
模块	MM-INV 库存管理	MM-IVR 发票校验
操作	货物移动（收货/发货/转储）	发票过账
影响	更新库存数量和GR/IR	更新供应商余额，清结GR/IR
凭证	物料凭证 + 会计凭证	会计凭证

发票校验的三单匹配原则：

PO数量 ≥ GR数量 ≥ 发票数量
PO价格 ≥ 发票价格（通常）

Question 9 - 收货与发票对库存价值和供应商余额的影响对比 [analysis]

比较执行收货（GR）和录入发票（Invoice Entry）时，对库存价值和供应商余额的不同影响。请分别从FI科目的角度分析。

收货（GR）时的影响：

操作	FI科目	方向	金额	对库存价值	对供应商余额
GR	存货科目	借记	PO价格×数量	增加	无影响
GR	GR/IR清算	贷记	PO价格×数量	—	无影响

发票录入（IR）时的影响：

操作	FI科目	方向	金额	对库存价值	对供应商余额
IR	GR/IR清算	借记	GR金额	—	无影响
IR	供应商应付	贷记	发票金额	—	增加应付（credit balance）
IR	差额→存货/价格差异	借/贷	差额	可能变化	无影响

核心区别：

GR阶段 — 库存价值增加（借记存货），但供应商余额不变。GR/IR清算科目作为过渡。
IR阶段 — 供应商应付余额增加（贷记供应商），库存价值是否再变化取决于价格差异和价格控制方式。
GR/IR清算科目 — GR时贷记，IR时借记，完成整个过程的清算。两个操作使GR/IR科目归零。
对于移动平均价（V）物料，发票价格与PO价格的差异可能调整MAP（如果有足够库存）。
对于标准价（S）物料，发票价格差异全部过账到价格差异科目，不影响库存价值。

Question 10 - 供应商寄售场景的责任时点 [application]

场景：公司使用供应商寄售（Consignment）采购。供应商将物料存放在我方仓库，但所有权仍属于供应商。请分析：在什么时间点上，公司对供应商产生付款责任？这个时间点与普通采购有什么区别？

供应商寄售（Consignment）采购分析：

责任产生时点：

寄售场景中，物料从寄售库存消耗（withdrawn from consignment stock）时才产生对供应商的付款责任
具体操作：使用移动类型 201K（消耗到成本中心）或其他K结尾的移动类型

与普通采购的对比：

时间点	普通采购	寄售采购
收货时	产生负债（GR/IR），库存归我方	无负债，库存类型为K（供应商特殊库存）
发票校验	三单匹配，确认负债	不适用（无PO价格）
消耗时	不适用（已是我的库存）	此时产生负债，需要结算
结算方式	MIRO发票校验	MRKO — 寄售结算（Consignment Settlement）

寄售库存的特点：

物料存放在我方仓库，但在系统中显示为供应商特殊库存（Special Stock K）
收货时使用移动类型 101K
供应商仍持有物料所有权
只有在物料被消耗时才触发财务过账
物料计价使用信息记录中的价格，而非PO价格

吴让宇(Mark)

最新文章

后勤执行 Practice (10 questions)

Related Concepts

Question 1 - LE Components [recall]

Question 2 - Organizational Unit Assignments [recall]

Question 3 - Interim Storage Areas [recall]

Question 4 - Two Process Forms [application]

Question 5 - GR Process: Transfer Requirement [recall]

Question 6 - Transfer Order and Stock Status [application]

Question 7 - Outbound Delivery Creation [recall]

Question 8 - Picking Status Flow [application]

Question 9 - Post GI Prerequisites [application]

Question 10 - GR vs GI Process Comparison [recall]

后台配置 Practice (10 questions)

Related Concepts

Question 1 - Accounting Document Types [recall]

Question 2 - Number Assignment for Material Documents [recall]

Question 3 - Reservation Number Assignment [recall]

Question 4 - Movement Type Control Functions [recall]

Question 5 - Quantity String vs Value String [application]

Question 6 - Account Modifier [application]

Question 7 - Creating a New Movement Type [application]

Question 8 - Plant Parameters [recall]

Question 9 - MIGO Field Selection [application]

Question 10 - MIGO Transaction Variants [recall]

后勤执行概述 (★★★★)

概览表 (一眼对比)

Logistics Execution Components (后勤执行组件)

Organizational Units (组织单位)

Assignment Rules

Warehouse Number Substructure (仓库号子结构)

Storage Type Comparison

Interim Storage Areas (过渡存储区)

Basic Process Forms (基本流程形式)

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

Related Notes

SCM500 Quick Reference

Key Transaction Codes → 采购订单基础 / 收货基础 / 发票基础

Organizational Levels → 采购流程与组织层级

Document Types → 采购订单基础 / 收货基础 / 发票基础

Key Movement Types → 库存类型与收货

Price Control Comparison → 物料评估基础

Account Assignment Categories → 消耗品采购订单 / 消耗品概述

Item Categories → 采购订单基础 / 消耗品采购订单

Condition Technique → 条件与定价

Vendor Master Data Views → 供应商主数据

Material Master Data Views → 物料主数据

Source Determination Priority → 合同与货源确定

MRP Lot-Sizing Procedures → 物料需求计划

Invoice Verification Types → 发票校验与交货成本

发票基础 (★★★)

Overview Table — Invoice Verification

Transaction MIRO — Screen Areas

Invoice Against PO Process Flow

Tolerances and Payment Blocks

Tolerance Groups

Payment Block

Documents Generated by Invoice

Effect of Invoice Verification

Accounting Entries at Invoice Verification

Invoice Verification in the Procurement Cycle

Exam/Test Patterns

Related Notes

SCM500 — Processes in Procurement Study Map

Overview

Topic Map

Practice Notes

Study Tools

Tag Index

Weak Areas

Non-core Topic Policy

SCM500 Exam Traps

Material Valuation

Account Assignment & Item Categories

Goods Receipt & Stock Types

Condition Technique & Pricing

Source Determination & Info Records

MRP & Automated Procurement

Blanket Purchase Orders (Consumables)