Related transactions:

• AC01 — Create
• AC02 — Change
• AC03 — Display

Information contained in a service master record:

• Service number — Unique identifier for the service
• Short text / Long text — Description of the service
• Base unit of measure — How the service is quantified (e.g., hours, days, pieces)
• Material group — Categorization for the service
• Valuation — Service category and valuation class for accounting determination
• Service category — Grouping for reporting and selection

The service master serves as a centralized catalog that can be referenced across multiple purchase orders, ensuring consistency and efficiency in service procurement.

Key characteristics of item category D:

• The item does not have a material number (it references service master records instead)
• A service specification (outline) is maintained at the item level
• The specification contains individual service lines with quantities and prices
• No traditional goods receipt — services are confirmed via service entry sheets instead
• Account assignment is mandatory (services are always consumed directly)
• Supports both planned services (listed in the specification) and unplanned services (added during entry)
• The value of the item is the sum of all service lines

1. In the PO item (Item Category D):

   • Create the service specification with the planned service lines
   • Enter the planned services with their quantities and prices

2. Set the limit for unplanned services:

   • In the PO item detail, specify the limit value of $2,000 for unplanned services
   • This is entered in the “Limits” section of the service item
   • The system uses this as the maximum allowable amount for services NOT listed in the original specification

3. When creating the service entry sheet:

   • The service provider can enter unplanned services (services not in the original PO specification)
   • The total value of unplanned services cannot exceed the configured $2,000 limit
   • The system validates against this limit and issues warnings/errors if exceeded

4. Total PO value = Planned services value + Unplanned services limit

This approach provides flexibility while maintaining cost control over service procurement.

The service entry sheet replaces the traditional goods receipt for services, since services are intangible and cannot be physically received into a warehouse.

Process steps:

1. Creation — The service provider or internal person creates a service entry sheet referencing the PO
2. Service entry — Actual services performed are recorded with quantities and values
   • Planned services from the PO specification are listed
   • Unplanned services can be added (up to the configured limit)
3. Review — The entry sheet is reviewed for accuracy
4. Approval/Acceptance — An authorized person accepts (approves) the service entry sheet
   • This triggers the material document posting (and accounting document if applicable)
   • Acceptance can be a single-step or multi-step process depending on configuration
5. Invoice verification — The vendor invoice is verified against the accepted service entry sheet

Purpose:

• Confirms that services were actually performed
• Provides the basis for vendor payment
• Creates the equivalent of a goods receipt for financial posting
• Enables tracking and approval of service costs before payment

Summary: The fundamental difference is that material procurement deals with tangible goods tracked in inventory, while service procurement manages intangible deliverables confirmed through service entry sheets. The PO structure for services is more complex (multi-line specification) to accommodate the detailed breakdown of service activities.

Related transactions:

• ML81N — Integrated service entry sheet (create, change, display, accept)
• ML81 — Create service entry sheet (older version)

Key functions in ML81N:

• Create new service entry sheets referencing a PO
• Enter actual service quantities performed
• Add unplanned services (if allowed by the PO)
• Submit for approval
• Accept (approve) service entry sheets
• Display and review existing entry sheets
• The transaction supports the full lifecycle from creation through acceptance

Step 1: Create Service Entry Sheet (ML81N)

• Enter the PO number as reference
• The system automatically loads the 3 planned service lines from the PO specification

Step 2: Enter Actual Quantities for Planned Services

• For each of the 3 planned service lines, enter the actual quantity performed
• The system calculates the value based on the agreed prices in the PO
• Example:
  • Service 1: Planned 100 hours → Actual 95 hours
  • Service 2: Planned 50 units → Actual 50 units
  • Service 3: Planned 10 days → Actual 12 days

Step 3: Add Unplanned Services (if needed)

• Navigate to the unplanned services section
• Enter additional services not in the original specification
• Provide description, quantity, unit, and price for each unplanned service
• The system checks the total against the configured limit

Step 4: Review and Save

• Review all entries for accuracy
• Save the service entry sheet (status: “In Preparation” or “Submitted”)

Step 5: Accept (Approve)

• An authorized approver opens the entry sheet
• Reviews the services and values
• Clicks “Accept” to approve
• System automatically posts the material document upon acceptance
• If account assignment is valuated, an accounting document is also posted

Step 6: Invoice Verification

• The vendor submits an invoice
• Reference the PO and/or service entry sheet number
• The system matches invoice against the accepted service entry sheet

Why this differs from material GR:

1. No physical goods to receive:

   • In material procurement, goods physically arrive and the GR is recorded immediately (MIGO)
   • Services are intangible — there is no physical delivery event to trigger receipt

2. Service confirmation requires validation:

   • The service entry sheet first needs to be created (describing what was performed)
   • Then it must be reviewed and formally accepted by an authorized person
   • Only upon acceptance is the posting triggered — this ensures proper authorization before financial commitment

3. Approval workflow:

   • Material GR can often be posted by warehouse staff upon delivery
   • Service entry sheets require explicit acceptance, which may involve multiple approval levels
   • This additional step provides financial control over service costs

4. Posting logic:

   • At SES acceptance: Material document is posted (recording the service “receipt”)
   • If valuated: Accounting document also posted (charging the cost object, crediting GR/IR)
   • At invoice: GR/IR clearing is debited, vendor is credited

In summary: The posting occurs at SES acceptance rather than at a traditional GR because services require formal confirmation and approval of performance before financial recognition, unlike physical goods which are immediately verifiable upon delivery.

Consumable material (non-stock material) may or may not have a material master record. It is procured for direct consumption and charged to a cost object (cost center, project, order, etc.) via an account assignment category. It does NOT increase warehouse stock — the cost is posted directly to the consuming department.

Since there is no material master record, the short text or material group is used to describe the item. The account assignment category K charges the cost directly to the specified cost center.

Goods Receipt Type: Non-valuated GR

For consumables without a material master (or with account assignment K and no valuated stock), a non-valuated goods receipt is typically posted. This creates only a material document (for tracking purposes) but does NOT create an accounting document. The actual cost posting occurs at invoice verification. However, if the material has a material master and the account assignment category is configured for valuated GR, a valuated GR with accounting document can also be posted.

Key characteristics:

• The account assignment remains open/unknown during the ordering phase
• The actual account assignment must be specified before or at the time of goods receipt or invoice verification
• This provides flexibility when the consuming department or project is not yet confirmed
• The system will require the user to specify a valid account assignment before the financial posting can be completed
• Commonly used in scenarios where procurement initiates purchasing before final budget allocation is decided

• When used: When the consumable material has a material master with a valuation price, and the account assignment category allows valuated GR (configured in customizing)
• Postings at GR:
  • Material document is created (movement type 101)
  • Accounting document is created: Debit to consumption account (e.g., cost center), Credit to GR/IR clearing account
  • Stock value is updated (if material is valuated)
• Postings at Invoice:
  • Any price difference between GR and invoice is posted to the account assignment object
  • GR/IR clearing account is cleared

Non-valuated GR:

• When used: When no material master exists, or the material is purely consumable with no inventory valuation requirement
• Postings at GR:
  • Only a material document is created (for quantity tracking)
  • NO accounting document is posted at this stage
• Postings at Invoice:
  • Accounting document created: Debit to consumption account, Credit to vendor
  • The full cost is only recognized at invoice verification

Key difference: The timing of financial recognition — valuated GR recognizes cost at goods receipt, while non-valuated GR defers cost recognition until invoice verification.

Configuration steps:

1. Select account assignment category P (Project/WBS Element)
2. Enable multiple account assignment (the system allows distribution across multiple WBS elements)
3. Enter the three WBS elements as follows:

4. The total must equal 100% (or the full quantity/amount)
5. At goods receipt, the system posts the consumption costs to each WBS element proportionally
6. The distribution can be by percentage, quantity, or amount depending on configuration

Key characteristics:

• Used for recurring, low-value procurement of materials or services
• Defined with a spending limit (maximum value) instead of a specific quantity
• No delivery schedule — the vendor delivers as needed during the validity period
• No goods receipt is required in the traditional sense (no quantity-based GR)
• Invoice is referenced directly to the blanket PO
• Validity period is specified (start and end dates)
• Simplifies procurement by avoiding creation of multiple POs for small, repetitive purchases
• Commonly used for office supplies, maintenance materials, or other frequently needed low-value items

1. System warning/error message is issued depending on the configuration (tolerance limits)

• If within tolerance: warning message, processing continues
• If outside tolerance: error message, blocking the invoice from being posted

2. Tolerance configuration determines the behavior:

• Tolerance limits can be set as absolute amounts or percentages
• Configured in customizing for Invoice Verification

3. Resolution options:

• Increase the blanket PO limit (if authorized)
• Split the invoice across multiple blanket POs
• Override the warning (if configured as a warning, not an error)

4. No automatic blocking occurs if the limit is set as informational only (depends on system configuration)

Step 1: Purchase Requisition (PR)

• Document: Purchase Requisition created (e.g., ME51N)
• Account assignment K with cost center specified
• No financial postings yet
• Document type: Purchase Requisition

Step 2: Purchase Order (PO)

• Document: Purchase Order created from PR (e.g., ME21N)
• Account assignment K inherited from PR
• No financial postings yet (commitment may be created if active)
• Document type: Purchase Order

Step 3: Goods Receipt (GR) — Valuated

• Material Document: Created (movement type 101)
  • Records quantity received
• Accounting Document: Created
  • Debit: Consumption account (charged to cost center)
  • Credit: GR/IR Clearing account
  • The cost center is charged at this point

Step 4: Invoice Verification

• Accounting Document: Created
  • If invoice price = GR price:
    • Debit: GR/IR Clearing account
    • Credit: Vendor account
  • If invoice price differs from GR price:
    • Debit: GR/IR Clearing account
    • Debit: Price difference posted to cost center
    • Credit: Vendor account
• Tax document may also be posted separately

Summary of Documents:

1. Purchase Requisition
2. Purchase Order
3. Material Document (at GR)
4. Accounting Document (at GR)
5. Accounting Document (at Invoice)
6. Tax Document (if applicable)

• Blanket PO limit: $5,000
• First invoice: $3,000 (remaining limit: $2,000)
• Second invoice: $2,500 → Exceeds remaining limit by $500

What happens:

1. The system checks the cumulative invoice value against the blanket PO limit
2. Total invoiced would be $5,500 ($3,000 + $2,500), exceeding the $5,000 limit
3. Depending on tolerance configuration:
   • Within tolerance: Warning message displayed, invoice can be posted
   • Outside tolerance: Error message, invoice is blocked

Resolution options:

1. Increase the blanket PO limit — The purchaser can change the PO limit from $5,000 to $5,500+ (transaction ME22N), then reprocess the invoice
2. Partial invoice — Process only $2,000 of the $2,500 invoice against this blanket PO, and process the remaining $500 against a new PO
3. Create a new PO — Process the full $2,500 against a newly created purchase order or blanket PO
4. Check tolerance settings — If configured with a 10% tolerance ($500), the system may allow it as a warning

Key characteristics:

• The reorder point is manually entered in the material master (MRP 1 view)
• When stock falls below the reorder point, MRP generates a procurement proposal
• The system does NOT automatically calculate the reorder point (unlike automatic reorder point planning, MRP type VR)
• The lot size determines the procurement quantity when triggered
• Suitable for materials with relatively stable, predictable consumption patterns
• The reorder point should cover expected demand during the procurement lead time plus safety stock

• Displays a dynamic, real-time view of the current stock and requirements situation
• Updated continuously as changes occur (goods movements, new orders, etc.)
• Shows the current actual stock and requirements at any point in time
• Used for day-to-day monitoring and interactive planning
• Changes are reflected immediately

MD05 — MRP List:

• Displays a static snapshot of the stock/requirements situation from the last MRP run
• Only updated when MRP is executed again
• Shows the planning situation at the time of the last MRP run
• Useful for comparing planning results over time
• Used to review what MRP planned and verify the results

Key difference: MD04 is live/dynamic; MD05 is a frozen snapshot from the last planning run.

Reasoning:

1. Reorder point check: Current stock (80) < Reorder point (100) → Material is below reorder point
2. MRP triggers a procurement proposal because stock has fallen below the reorder point
3. Lot size FX (Fixed Order Quantity) = 200 units
4. The system generates a PR for exactly 200 units (the fixed lot size), regardless of the shortfall amount

Note: With fixed lot size, the PR quantity is always the defined fixed quantity (200). The system does NOT calculate the exact shortage (100 - 80 = 20 units). The lot size procedure determines the order quantity, not the reorder point logic.

When to use MD04 (Stock/Requirements List):

• Daily operations: Monitor current stock levels and open requirements
• Interactive planning: Convert planned orders to purchase requisitions manually
• Exception handling: Respond to urgent requirements or sudden changes
• Real-time decisions: When you need the most current information
• Post-MRP adjustments: After MRP has run, to see the impact of manual changes

When to use MD05 (MRP List):

• Audit trail: Document what MRP planned at a specific point in time
• Planning review: Compare MRP results across multiple runs to identify trends
• Validation: Verify that MRP produced expected results
• Reporting: Generate consistent reports based on a fixed data snapshot
• Troubleshooting: Investigate why MRP generated certain proposals

Key insight: MD05 provides traceability and auditability of the planning process, while MD04 provides operational agility for real-time decision-making.

Important combinations:

• 1 + M: Fixed vendor AND MRP-relevant — MRP automatically assigns this vendor
• Blank + M: MRP-relevant but not fixed — MRP selects from available sources
• 2: Blocked — excluded from source determination
• Source list entries have validity periods (start and end dates)

1. MRP detects a requirement for material X (e.g., stock below reorder point or dependent requirement from BOM)

2. MRP generates a purchase requisition with the required quantity

3. Source determination occurs automatically because:

   • The source list has vendor A with indicator M (MRP-relevant)
   • A valid contract exists for material X with vendor A
   • The system assigns vendor A and the contract to the PR as the source of supply

4. PR details:

   • Vendor: A (from source determination)
   • Contract: Referenced in the PR
   • Source of supply: Contract with vendor A
   • The PR is a schedule line against the contract (not a standalone PR)

5. Next step: The PR can be converted to a PO or, if configured for automatic PO creation (ME59N), the system can create the PO automatically referencing the contract

Key point: The combination of a contract and an MRP-relevant source list entry enables fully automated source assignment during MRP, streamlining the procurement process.

Material master settings:

• The material must have a valid source of supply (vendor or contract)
• The purchasing view must be maintained
• Source list must be maintained with MRP-relevant indicator (M)

Purchase requisition settings:

• PR must be released/approved (status must allow conversion)
• PR must have a valid source of supply assigned (vendor or outline agreement)
• PR must have proper account assignment (if consumable)

Vendor master settings:

• Valid vendor master record must exist
• Purchasing organization data must be maintained

Customizing settings:

• Document types must be configured for automatic PO creation
• The PR document type must be allowed for automatic conversion
• Tolerance limits must be configured (if applicable)

Additional conditions:

• Delivery dates must be in the future (or current)
• No blocking indicators on the PR
• The quota arrangement (if used) must be properly maintained

How ERS works:

1. Goods Receipt is posted (MIGO) — material document and accounting document are created
2. ERS is executed (transaction MRRL) — the system automatically generates an invoice document based on:
   • The GR quantity
   • The agreed prices from the PO (or contract)
   • The terms of payment from the PO
3. Invoice document is created automatically — debiting the vendor and clearing the GR/IR account
4. Payment is processed based on the automatically created invoice

Prerequisites for ERS:

• The ERS indicator must be set in the vendor master record (purchasing view)
• The PO must be flagged for ERS
• Valid prices must exist in the PO (no estimated prices)
• Tax information must be properly maintained

Benefits:

• Eliminates physical invoice processing
• Reduces invoice verification workload
• Faster payment processing
• Reduces errors from manual invoice entry

When to use ERS:

• High-volume, repetitive procurement with trusted vendors
• Fixed-price contracts where invoice amounts are predictable
• When reducing AP processing costs is a priority

When to use normal invoice verification:

• Variable pricing or complex pricing arrangements
• New vendor relationships where verification is important
• Situations where vendor invoices may differ from PO prices
• When tax or charge handling requires manual review

Step 1: MRP generates Purchase Requisition

• Material master: MRP type, lot size, reorder point (or BOM for dependent requirements)
• Material master: Purchasing view maintained with purchasing group
• Source list: Valid entries with indicator M (MRP-relevant) for automatic source determination
• Contract or quota arrangement: Must exist for automatic source assignment
• MRP must be configured to generate PRs (not planned orders) or planned orders set to auto-convert
• Planning file entry must exist for the material

Step 2: Automatic PO Creation (ME59N)

• PR must have a valid source of supply (vendor or outline agreement assigned by MRP)
• PR must be automatically releasable (no manual approval required, or auto-release configured)
• Vendor master: Complete purchasing data maintained
• Customizing: PR document type must allow automatic PO conversion
• Source determination must have assigned a specific vendor
• Proper pricing conditions maintained (info record or contract prices)

Step 3: Goods Receipt (can be simplified but typically manual)

• PO must be valid and approved
• Delivery must be expected (PO output sent to vendor)
• Material master: Storage location and warehouse management data (if applicable)
• For automatic GR: Can use BAPI or scheduled job for expected deliveries

Step 4: ERS (Evaluated Receipt Settlement)

• Vendor master: ERS indicator checked in the purchasing view
• Purchase Order: ERS indicator must be set
• PO prices: Must be definitive (no estimated or temporary prices)
• Tax data: Must be maintained in the PO or vendor master
• Terms of payment: Must be defined in the PO
• GR must be posted before ERS can run
• MRRL transaction scheduled as a background job

Cross-cutting prerequisites:

• Consistent master data across all objects
• Proper organizational structure (plant, purchasing org, company code)
• Background jobs configured for ME59N and MRRL
• Monitoring and exception handling processes in place
• Vendor agreement to participate in ERS (no physical invoices)

条件技术是SAP中用于自动确定价格、折扣、附加费和税费的核心方法。它通过结构化的层次搜索来找到最精确匹配的条件记录。

采购定价中的组件（按层次顺序）：

1. 条件表（Condition Table） — 定义条件记录的搜索关键字组合（如供应商+物料、供应商+物料组+工厂等）。是条件技术最底层的组件。

2. 存取顺序（Access Sequence） — 定义搜索条件记录的策略和顺序。包含多个条件表，按优先级从最具体到最一般排列。系统按顺序查找，找到第一个有效记录即停止。

3. 条件类型（Condition Type） — 代表价格或折扣的具体含义（如PB00= gross price，RA01=折扣，FRA1=运费）。每个条件类型可分配一个存取顺序。

4. 定价过程（Pricing Procedure） — 定义在定价过程中使用哪些条件类型、它们的顺序、是否可手动更改、是否为统计性条件等。

5. 定价公式（Pricing Formula） — 可选，用于复杂计算逻辑的例程。

搜索流程示意：
定价过程 → 条件类型(PB00) → 存取顺序 → 条件表1(工厂+供应商+物料) → 条件表2(供应商+物料) → … → 找到价格

PB00的详细说明：

• 代表物料的基本采购单价
• 分配了存取顺序（如0002），依次搜索不同粒度的条件表
• 在PO中可以手动覆盖（如果定价过程配置允许）

RA01的详细说明：

• 代表折扣或附加费（通过正负号区分）
• 通常基于PB00金额的百分比计算
• 也可以是绝对金额
• 常见场景：数量折扣、现金折扣、物料组折扣

在定价过程中的顺序：
PB00 → RA01（折扣）→ 其他条件类型 → 有效价格（NETPR）

NETPR = PB00 + RA01 + 其他折扣/附加费

Step 1 — 确定收货前数据：

• 当前库存数量 = 100件
• 当前移动平均价 = $10
• 当前库存总价值 = 100 × $10 = $1,000

Step 2 — 计算收货价值：

• 收货数量 = 50件
• PO单价（收货评估价格）= $12
• 收货价值 = 50 × $12 = $600

Step 3 — 计算新的移动平均价：

• 新总库存 = 100 + 50 = 150件
• 新总价值 = $1,000 + $600 = $1,600
• 新MAP = $1,600 / 150 = $10.6667（系统保留4位小数）

FI过账：

注意： 移动平均价在每次涉及价值变化的收货时都会重新计算。如果收货价格高于当前MAP，MAP上升；反之下降。

场景设定： PO价格$12，当前库存价不同

情况A — 移动平均价物料（V）：

• 假设当前MAP = $10，库存100件
• GR 50件，PO价$12

• MAP变化： 重新计算为新的加权平均价
• 无价格差异过账 — 全部金额进入存货
• 结论：V价物料GR始终按PO价格更新库存价值并重算MAP

情况B — 标准价物料（S）：

• 假设标准价 = $10
• GR 50件，PO价$12

• 标准价不变 — 仍为$10
• 价格差异$100 过账到价格差异科目（PRD）
• 结论：S价物料GR始终按标准价计入库存，差异单独过账

核心区别总结：

库存类型间的转换：

其他特殊库存类型：

• K — 供应商寄售库存
• E — 销售订单库存
• Q — 项目库存
• O — 订单库存（Subcontracting）

注意： 在MMBE事务中可以看到每种库存类型下各库存地点的数量。

Step 1 — 收货到质检库存：

两种方式：

• 推荐方式：如果QM模块激活，使用101 + 质检设置自动触发
• 如果QM未激活但需要质检，使用103手动收到质检

Step 2 — 质检合格后释放到非限制使用库存：

Step 3 — 如果质检不合格：

MMBE中的显示：

• 质检阶段 → 该数量显示在”Quality Inspection”行
• 释放后 → 数量转移到”Unrestricted-use”行

PIR是连接供应商和物料的信息源，存储了特定供应商供应特定物料的采购条件。它是采购定价的重要数据来源。

组织层级 — PIR存在于两个层级：

PIR包含的关键数据：

PIR的4种类型：

创建事务码： ME11（创建）、ME12（修改）、ME13（显示）、ME1M（按物料查询）

在定价中的作用： PB00的存取顺序会搜索PIR中的价格条件记录。

基本数据：

• 物料单价 = $100 × 10件 = $1,000
• 计划交货成本（FRA1）= $50
• PO总值 = $1,050

一、GR时的过账（移动类型101）：

V价物料（移动平均价）：

• MAP重新计算，运费包含在库存价值中
• 新MAP = (原价值 + $1,050) / (原数量 + 10)

S价物料（标准价）：

• 假设标准价 = $100

• 运费单独过账到运费科目，不影响存货标准价
• 如果标准价≠PO价，额外产生价格差异

二、IR时的过账（MIRO）：

发票金额：物料$1,000 + 运费$50 = $1,050

• V价和S价在IR阶段的基础过账相同
• 差异仅在发票价格与PO/GR价格不同时产生

核心区别总结：

• GR/IR清算是FI中的一个过渡科目（Bridging Account）
• 用于暂时记录已收货但尚未收到发票（或反之）的金额
• 属于资产负债表科目，通常归类在”未清项”下

在采购流程中的变化：

会计分录示例（PO价$1,000）：

GR时：

1
2

借：存货科目        $1,000
    贷：GR/IR清算            $1,000

IR时：

1
2

借：GR/IR清算        $1,000
    贷：供应商应付           $1,000

特殊情况：

• GR未IR → GR/IR有贷方余额（已收货未收发票）
• IR未GR → GR/IR有借方余额（已收发票未收货）
• 期末需要运行 MR11（GR/IR清算维护） 来处理长期未清的项目
• 期末重分类：通过 MR11SHOW 查看未清项

基本数据：

• PO价格 = $10，GR数量 = 100件，GR价值 = $1,000
• 发票价格 = $12，发票数量 = 100件
• 价格差异 = $12 - $10 = $2/件
• 总差异 = 100件 × $2 = $200
• 当前库存 = 80件（已消耗20件）

处理规则 — V价物料：

系统首先尝试将差异全部调整到MAP。但只有当前库存足够时，差异才能全部进入库存价值。

判断库存是否足够：

• 差异总额 = $200
• 当前库存价值中可承受的最大调整 = 80件 × 当前MAP
• 由于差异金额为正（$200），库存80件 > 0，所以差异可以部分进入库存

具体过账：

MAP重新计算：

• 差异中与现有库存相关的部分（$160）调整MAP
• 已消耗物料的差异（$40）进入价格差异科目

如果库存为0（已全部消耗）：

• 全部$200差异进入价格差异科目，不影响MAP

如果库存 ≥ 100件：

• 全部$200差异进入存货科目，MAP上调

核心规则： V价物料发票差异按照（当前库存 / 发票数量）的比例分配到存货，剩余部分进入价格差异。

RFQ流程：

1. ME41 — 创建RFQ，指定物料、数量、报价截止日期
2. 发送给多个供应商
3. ME47 — 收到报价后，为每个供应商录入报价（价格、条件等）
4. ME49 — 比较所有供应商的报价

ME49报价比较功能：

• 显示所有供应商对同一物料的价格对比
• 可以按价格排序，标识最低价
• 显示每个报价的有效期
• 可以直接从比较画面选择最优报价并创建PO

RFQ类型：

与采购申请的关系： RFQ可以参考采购申请创建，ME41中可以自动从PR提取物料需求。

计划外交货成本是在MIRO中手动录入的、PO中未预估的运输、保险等成本。

V价物料（移动平均价）的计划外交货成本：

系统默认将计划外交货成本分配到物料（如果库存充足）：

• MAP会上升 — 因为库存价值增加了$100
• 如果当前库存不足（如已消耗完），则进入价格差异科目
• 分配逻辑与发票价格差异相同：按库存比例分配

MIRO中的配置选项：

• 可以选择将计划外成本分配到物料（默认V价行为）或单独过账到指定科目

S价物料（标准价）的计划外交货成本：

系统将计划外交货成本过账到价格差异科目或指定的运费科目：

• 标准价不变 — 不影响存货估值
• 计划外成本不会进入存货科目
• 对P&L的影响：通过CO-PA影响成本分析

核心区别总结：

配置路径： SPRO → Materials Management → Logistics Invoice Verification → Incoming Invoice → Configure How Unplanned Delivery Costs are Posted