Valuation
MM / P2Pintermediate

MM Valuation Part 3: Special Stocks, Negative Stock and Valuation Edge Cases

Key takeaway

Valuation beyond standard stock: supplier consignment (not valuated until withdrawal), sales order and project stock (valuated or non-valuated), stock in transit, negative stocks and their valuation risks, returns to supplier, and revaluation effects of price changes.

Explanation

📌 KEY POINTS
✅ Supplier consignment stock is not valuated in your books until withdrawal (then liability to supplier).

✅ Sales order and project stock can be valuated or non-valuated depending on settings.

✅ Stock in transit (e.g. two-step STO) stays valuated at the issuing side until receipt.

✅ Negative stock can distort moving average prices and creates later valuation corrections.

⚠️ Allowing negative stock without strict controls hides process errors.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 2 configured valuation. Now edge cases.

━━━━━━━━━━━━━━━━━━━━
▶ 1. SUPPLIER CONSIGNMENT

  • Withdrawal creates stock value and payable (KON).

━━━━━━━━━━━━━━━━━━━━
▶ 2. SALES ORDER / PROJECT STOCK

  • Valuated vs non-valuated (requirements class/settings).

━━━━━━━━━━━━━━━━━━━━
▶ 3. STOCK IN TRANSIT

  • Value remains until receiving plant posts GR.

━━━━━━━━━━━━━━━━━━━━
▶ 4. NEGATIVE STOCK

  • Allowed per plant/storage location/material; risks for V materials.

━━━━━━━━━━━━━━━━━━━━
▶ 5. RETURNS AND PRICE CHANGES

  • Return to supplier (122) at original value; price changes revalue stock.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Withdraw consignment stock and check postings.
  2. Post an STO in two steps; check stock in transit.
  3. Review negative stock settings.

✅ CHECKPOINT: you can explain valuation for each special stock type used.

Code example

ABAP Code
===== STEP 1: consignment =====201 K withdrawal: Dr consumption | Cr consignment payable (KON) ===== STEP 2: special stocks =====E sales order stock | Q project stock → valuated/non-valuated per settingsTwo-step STO: 643/641 → stock in transit (valuated) → 101 at receiving plant ===== STEP 3: negative stock =====Allowed per valuation area and storage location + material plant data | monitor and clear quickly

Real project scenario

A steel fabrication company allowed negative stock to avoid production stoppages. Moving average prices swung wildly when late GRs arrived at different prices, and month-end values required manual corrections. Restricting negative stock to a few storage locations with daily clearing stabilized valuation.

Common mistakes

  • Allowing negative stock broadly.
  • Misunderstanding consignment liability.
  • Ignoring stock in transit value.
  • Wrong special stock valuation setting.
  • Untracked price changes.

Best practices

  • Limit negative stock.
  • Settle consignment regularly.
  • Monitor stock in transit.
  • Decide valuated special stocks with finance.
  • Control price changes.

Interview angle

Questions: "How is consignment stock valued?", "Valuated vs non-valuated sales order stock?", "What are negative stock risks?"
Strong answer: consignment on withdrawal, special stock settings, stock in transit, negative stock risks, returns and revaluation.

Practice this lesson

Quick check

1. Where is the stock value held during a two-step stock transport between plants?

2. When does supplier consignment stock create a value and liability in your books?

3. A company allows negative stock broadly and sees moving average prices swing. Why?

Interview questions

1. How does SAP value special stocks such as vendor consignment or subcontracting stock during period-end close, and how does account determination differ from standard own stock?

Answer it in your own words first, then compare.

2. What is split valuation in the material master, and what business scenario would justify enabling it for a material?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics