S/4HANA Inventory Management & Valuation: Split Valuation, S vs V Price Control, GR/IR, Consignment & Subcontracting – Deep Hands‑On Guide | Part 22 | FreeLearning365

 

Day 7 – Inventory Management & Valuation: Split Valuation, Price Control, GR/IR, Consignment & Subcontracting

Functional Consultant Track – Part 22

Welcome to Day 7, the day where we truly go beneath the surface of materials management. You already know how to structure your enterprise, wire OBYC, and control procurement. Now we tackle the financial soul of inventory: valuation. Misconfigure valuation, and your balance sheet is wrong – over- or under‑stated, hiding profit leaks, and confusing auditors. Get it right, and you have a real‑time, multi‑faceted inventory value that supports decision‑making, working‑capital optimisation, and flawless financial reporting.

Our client GlobalTech has outgrown simple valuation. They want to differentiate internally produced and externally purchased identical raw materials. They need batch‑based valuation for shelf‑life control. They use moving average for raw materials (to reflect market prices) but standard price for finished goods (to measure production efficiency). They have vendor‑owned consignment stock on‑site, and they send components out for subcontract painting. And every month, the AP accountant tears their hair out reconciling the GR/IR account. Your mission: configure and execute all of this in your sandbox, with full transaction postings and journal‑entry walkthroughs.

1. Split Valuation – One Material, Multiple Values

Split valuation allows a single material to be valued differently according to a valuation category. For example, the same raw plastic pellet might be sourced internally from another company code (valuation type ‘OWN’) or purchased externally (‘EXT’). Or it might be managed in batches with different shelf lives and therefore different values per batch. Split valuation splits the stock of a material in the same plant into different valuation types, each with its own quantity and value, price control, and possibly even G/L account.

1.1 Why Split Valuation?

• Different origins (internal vs. external) – for transfer pricing or cost accounting.
• Batch valuation – each batch can have a different cost (especially in chemical/pharma industries).
• Quality grades – material may have different grades with different values but same material number.
• Project stock – customer‑specific inventory may be valued differently.

1.2 Configuration Steps

Step 1: Activate Split Valuation.
SPRO path: Materials Management → Valuation and Account Assignment → Split Valuation → Activate Split Valuation (transaction OMW0).

Choose “Split material valuation active”. This is a global setting for the client. You must be extremely careful – once activated, you cannot easily deactivate it because it changes the database structure for material valuation. In our sandbox, we activate it safely.

Step 2: Define Valuation Categories.
SPRO: Materials Management → Valuation and Account Assignment → Split Valuation → Define Valuation Categories (transaction OMWC).

Categories are the reasons for splitting. Standard categories:

• B – Batch (valuation per batch)
• H – Origin (internal/external)
• S – Settlement (for project stock)

GlobalTech will use category H (Origin) for raw material RAW01 (plastic pellets) because they produce some internally (valuation type ‘OWN’) and buy some externally (valuation type ‘EXT’). We also use category B for a chemical material to show batch valuation.

In OMWC, create category H with description “Origin (internal/external)”. Then double‑click on “Valuation Types” and create:

• OWN – Own production (internal procurement)
• EXT – External procurement

For each valuation type, you can define different account determination? Actually, the G/L account for inventory can be the same or different per valuation type by using different valuation classes. But with split valuation, you can’t assign different valuation classes to the same material; the valuation class is at the material level. However, you can use account determination modifiers via the valuation grouping code and the valuation type. OBYC allows a further split by valuation type (field “Valuation Type” in OBYC). So you can set up OBYC to use different inventory accounts for OWN and EXT. We’ll come back to that.

Step 3: Assign Valuation Types to Plants.
SPRO: Materials Management → Valuation and Account Assignment → Split Valuation → Assign Valuation Types to Plants (transaction OMWD).

Assign valuation types OWN and EXT to plant GT01, GT02, GT03.

Step 4: Activate Split Valuation for Material Master.
In the material master (MM01/MM02) of RAW01, on the Accounting 1 view, you must set the valuation category. Before you can enter it, the material must have no existing stock (or you can convert stock using a special program). For RAW01, we set valuation category ‘H’ (Origin). Then the system allows entering valuation types; the valuation data (price, price control, etc.) is maintained per valuation type. Use transaction MM01 with additional data: after entering plant, the system asks for valuation type. For each valuation type, you can set a different price control and standard price or moving average price. Example: RAW01, valuation type OWN, price control V (moving average), price 9.50 USD. Valuation type EXT, price control V, price 10.00 USD.

Step 5: Account Determination for Split Valuation.
In OBYC, for transaction BSX, you can now further split by valuation type. In OBYC, when you enter the chart of accounts and transaction BSX, there is a column “Valuation type”. You can enter OWN and assign a separate inventory account (e.g., 20000011 for internal raw material) and EXT (20000012 for external raw material). This allows different G/L accounts per valuation type. GlobalTech wants that for reporting. So in OBYC:

• Valuation mod. 0001, Valuation class 3000 (raw material), Valuation type OWN → Account 20000011
• Valuation mod. 0001, Valuation class 3000, Valuation type EXT → Account 20000012

Now, when you receive goods with a purchase order for external procurement (EXT), the inventory debit goes to 20000012; when you receive from internal production (e.g., via movement type 101 for production order into own stock, valuation type OWN), it hits 20000011. Perfect segregation.

1.3 Hands‑On Split Valuation Scenario

External procurement: Create purchase order for RAW01, 100 KG, vendor USSUP01. In the PO, because the material has split valuation, you must specify the valuation type? Actually, the valuation type is determined by the movement type. For standard external procurement (101 from PO), the valuation type comes from the material master if it's split – you can’t choose; the system takes the valuation type from the master record? Wait, the process is: a material with split valuation has a valuation type maintained per procurement/usage? No, the split valuation is based on physical stock segregation. You receive goods into a specific valuation type stock. The movement type determines which valuation type is updated. For standard purchase order receipt (101), the system needs to know into which valuation type to post. This is controlled by the account assignment category or the movement type configuration. For external procurement, you typically define a separate movement type or use the standard 101 but with a valuation type derivation via the “automatic valuation type determination”. This is configured in OMWW (Define Default Values for Valuation Type). We set: for movement type 101, plant GT01, material RAW01, default valuation type EXT when the vendor is external. And for 101 from production order, default OWN. Then the goods receipt automatically posts to the correct valuation type.

In OMWW, create rule: Movement type 101, Plant GT01, Material RAW01, Valuation type EXT (this is used for purchase orders). Then create another rule: Movement type 101, reference order type (PP), valuation type OWN. This is advanced but essential for split valuation. In real life, you also set the batch determination to automatically create a batch number if batch management is active.

Now post goods receipt for the PO: MIGO, 101, reference PO. The material document shows quantity 100 KG posted to stock type “unrestricted”, valuation type EXT. The FI document debits 20000012 (External RM Inventory) and credits GR/IR 30000100. The moving average price for valuation type EXT is updated if price control V.

Internal production receipt: from a production order, use MIGO 101 with reference to production order. It posts to valuation type OWN and debits 20000011. The moving average price for OWN updates based on the production order actual cost.

In the material master, you can now see two separate stock quantities and values per valuation type in MM03 (Accounting view), split per valuation type.

Insight: Split valuation gives you a powerful way to track different inventory segments without creating separate material numbers. But it adds complexity: you must configure automatic valuation type determination for every relevant movement type, ensure OBYC accounts exist for each valuation type, and train users that the same material has multiple “stocks” that can only be moved within the same valuation type or via transfer postings (e.g., movement 309 with valuation type change).

2. Price Control: Standard Price (S) vs. Moving Average (V) – The Eternal Debate

Price control is the most critical setting in the material master’s accounting view. It dictates how the material’s inventory value is updated when you post goods movements and invoices. Choosing wrong can lead to serious misstatements.

2.1 Moving Average Price (V)

The moving average price is recalculated after every transaction that changes the inventory value and quantity, such as goods receipt, invoice receipt (if price differs from PO), or transfer posting. The formula: new MAP = (total value before + transaction value) / (total quantity before + transaction quantity). This keeps the inventory value per unit close to the actual average procurement cost. It is ideal for raw materials and trading goods that are frequently purchased at fluctuating prices.

Example: RAW01 (valuation type EXT) with MAP control. Initial stock: 0, price 0. Goods receipt PO for 100 KG at 10 USD/KG. MAP becomes (0+1000)/(0+100) = 10.00 USD. Next, another goods receipt of 100 KG at 11 USD. New MAP = (100*10 + 100*11) / 200 = (1000+1100)/200 = 10.50 USD. The inventory value is smoothly averaged.

Invoice difference: If later the invoice for the first PO comes in at 10.50 USD instead of 10, and the material still has stock, the MAP is adjusted. Post‑invoice, the system makes a posting: debit GR/IR 1000, credit vendor 1050, and then the difference (50) is posted to the inventory account if stock is available, adjusting the MAP. New MAP = (remaining stock value + 50) / stock quantity. This can cause MAP to drift. If stock is zero when invoice is posted, the difference goes to a price difference account instead, and a warning appears.

Danger: Moving average can fluctuate wildly if invoices are late and stock levels are low. For example, if you have only 1 unit left and a price variance of 1000 comes in, MAP becomes (current value + 1000)/1, making the unit cost unrealistic. Mitigation: set “price difference” posting tolerance in OBYC via transaction PRD, but MAP still adjusts. Use moving average only for items with high stock turnover.

2.2 Standard Price (S)

Standard price is a fixed value per unit, set manually (MR21) or by the system via costing run. All goods movements are posted at this standard price, regardless of actual purchase price. Variances are accumulated in price difference accounts. This provides stable inventory valuation and production cost control. Ideal for finished goods and semi‑finished goods in a manufacturing environment. Variance analysis is a core CO‑PC concept.

Example: FERT01 has standard price 50 USD. Goods receipt from production order for 100 units posts debit inventory 20000030 at 50 USD per unit = 5,000 USD, credit production order (settlement). If the actual production cost was 4,800 USD, a credit variance of 200 USD goes to price difference account (PRD). If actual cost was 5,200 USD, a debit variance. These variances are analysed to improve production efficiency.

Invoice variance (external procurement for a standard‑priced material): For a raw material that is standard‑priced (rare but possible), if you receive at standard price and invoice later at a different price, the difference goes directly to PRD, not to inventory. The MAP does not change. This protects inventory value from purchase price fluctuations but can hide real acquisition cost in P&L accounts.

Cons: Standard price must be regularly updated (at least yearly) to reflect reality; otherwise inventory may be over/understated. Changing standard price requires a careful revaluation (transaction MR21 or MR22) that can have a massive P&L impact.

2.3 When to Use Which – A Consultant’s Decision Matrix

• Raw materials, traded goods: moving average (V) – because purchase prices vary and inventory turns quickly.
• Finished goods, semi‑finished: standard price (S) – stable production costs, variance analysis.
• High‑value, low‑volume materials: consider standard price to avoid MAP distortion from a single invoice variance.
• Consignment stock: always MAP? Actually, consignment stock is valued at zero until transferred to own, then valued at the price in the info record. That price is typically a moving average? No, once transferred to own, the material’s own price control applies. If the material has MAP, the transfer posting will adjust MAP.

GlobalTech uses MAP for all raw materials and standard price for all semi‑finished and finished goods. This is a best‑practice baseline.

2.4 Price Change (MR21) and Its Impact

Changing a material’s standard price mid‑year triggers a revaluation of existing stock. Transaction MR21 (Price Change). Enter material, plant, new standard price. The system posts the difference between old and new total stock value to a revaluation account (configured in OBYC under transaction UMB). Example: FERT01 stock 100 units, old standard 50, new standard 55. Difference 5 * 100 = 500 USD. Debit inventory 500, credit revaluation surplus (or P&L) account 55000050. This revaluation affects the balance sheet and profit.

For moving average, you can also manually change the price via MR21, which adjusts the MAP and inventory value directly, posting the difference to a price difference account. This should be done rarely and with full documentation.

3. GR/IR Account Management – The Reconciliation Bridge

The Goods Receipt/Invoice Receipt (GR/IR) clearing account is a suspense account that sits between inventory and vendor payables. It is debited on goods receipt (credit side of inventory) and credited on invoice receipt. Ideally, for each PO, the GR/IR balance should be zero after full delivery and invoice. In reality, timing differences, partial deliveries, and invoice variances create open items that must be periodically cleared and reconciled.

3.1 Automatic Clearing – F.13 / FAGL_CL_REGRU

Transaction F.13 (Automatic Clearing of GR/IR Accounts) matches goods receipt and invoice line items for the same PO and purchase order item, and clears them if the quantities and amounts match within tolerance. It is typically run at period‑end. In S/4HANA, the recommended transaction is FAGL_CL_REGRU (Reclassify GR/IR), which not only clears but also reclassifies open items to a “GR/IR reclassification” G/L account for balance sheet presentation. The logic: remaining open items on the GR/IR account are reclassified as either “Goods receipt not invoiced” (liability) or “Invoice receipt not delivered” (asset). This ensures the balance sheet reflects true accrued liabilities and prepaid assets.

Configuration: In OBYC, define the GR/IR clearing account (WRX) as account 30000100. Then define reclassification accounts: in SPRO: Financial Accounting (New) → General Ledger Accounting (New) → Periodic Processing → Reclassify → GR/IR Reclassification → Define Reclassification Accounts. Specify account 30000100, and for “Goods delivered but not invoiced” (side 1) a liability account (e.g., 30000200), and for “Invoice received but not delivered” an asset account (e.g., 20000090). Assign these to company code GT01.

Now run FAGL_CL_REGRU. Enter company code, key date (month‑end). Execute test run. The program finds all PO items where GR and IR amounts differ, creates postings that reclassify the net difference. For example, GR 1000, IR 600 → net 400 liability (goods received but not invoiced). The posting: debit GR/IR 400, credit reclassification liability account 30000200. Next month, the posting is reversed automatically.

For classic clearing without reclassification, use F.13 (Automatic Clearing). It clears matched items and leaves a list of unmatched items for manual analysis.

3.2 Manual Reconciliation – MR11, MR11SHOW

Transaction MR11 (GR/IR Account Maintenance) allows you to manually clear a purchase order’s GR/IR items by posting the difference to a price difference account or initiating a follow‑up process. Use it when there are small, permanent differences that won’t be settled by further invoices or deliveries. For example, a PO for 100 units, GR 100, invoice for 98 units (2 scrapped). The GR/IR has a debit of 20 USD (2 * 10). In MR11, you enter the PO, the system proposes clearing the remaining GR/IR balance to price difference account (PRD). You confirm and post. The GR/IR is now clean.

MR11SHOW displays the GR/IR account items and their clearing status. Use it to review before month‑end.

3.3 GR/IR Best Practices

• Run FAGL_CL_REGRU every month‑end to reclassify, ensuring correct financial statements.
• Schedule F.13 weekly to automatically clear matched items and reduce manual effort.
• Set tolerance limits in vendor master (tolerance group) and in OMIR (Invoice Verification tolerance) so that small variances can be automatically posted to price difference without blocking the invoice.
• Monitor the GR/IR aging report (S_ALR_87012078) – old open items indicate missing invoices or deliveries. Follow up with purchasing and logistics.
• Do not use MR11 casually; it should be authorised and its postings reviewed because it can hide procurement issues.

4. Consignment Processing – Vendor‑Owned Stock on Your Premises

Consignment means the vendor delivers goods, but you only pay when you consume or sell them. The stock sits in your plant as special stock “K” (consignment), valued at zero in your books. Only when you transfer it to your own stock or issue it to a cost centre do you create a liability and inventory value. This is an excellent working‑capital tool.

4.1 Configuration and Master Data

Step 1: Configure consignment info record. In ME11 (Info Record), choose category “Consignment”. Enter vendor, material, purchasing org, plant. Maintain the consignment price (the price you will pay upon consumption). For example, 8.00 USD per KG. No tax, no discount, but you can add delivery costs.

Step 2: In the material master, there is no special setting for consignment. The material itself may be subject to MAP or S; the consignment stock does not affect its value until transferred. The material master must allow special stock K (standard).

Step 3: Create a purchase order with item category “K” (consignment). In ME21N, choose document type “Standard PO”, but at item level, change the item category to “K”. The PO references the consignment info record price. No account assignment.

4.2 Goods Receipt to Consignment (101 K)

Post goods receipt via MIGO, movement type 101, special stock indicator K. The material is received into unrestricted‑use consignment stock. No FI document is generated. The stock appears in the material master under “Consignment stock” (MMBE, display special stock K). The vendor’s consignment stock is tracked.

4.3 Consumption and Transfer to Own Stock

Transfer to own stock: When you decide to take ownership, use movement type 411 K (Transfer from consignment to own). The system moves quantity from consignment to own stock, and at the same time creates a goods receipt into own stock at the consignment price. This generates a material document and an FI document: debit inventory (own), credit GR/IR clearing (actually, a special consignment liability account). The vendor is now owed.

In OBYC, the account determination for this transfer uses transaction key KON (Consignment liability). So configure KON in OBYC for valuation class and consignment vendor? Actually, KON links to a liability account (e.g., 30000500 Consignment Payable). During 411 K, it credits that liability account. Then settlement (invoice or ERS) clears that liability and credits vendor.

Issue to cost centre directly from consignment: Movement type 201 K. This consumes consignment stock, debits expense (GBB VBR) and credits the consignment liability (KON). So the same liability arises without ever having own stock. This is common for maintenance items.

4.4 Settlement of Consignment Liabilities (MRKO)

Transaction MRKO (Automatic Consignment Settlement) selects all open consignment transfers and creates an invoice (or ERS) to pay the vendor. It generates a credit to vendor (AP) and a debit to the consignment liability account, clearing it. Run MRKO regularly, e.g., weekly, to ensure vendors are paid.

4.5 Hands‑On Consignment Scenario

GlobalTech stores packaging material PACK02 on consignment from vendor PACKVEN. Set up consignment info record (ME11), price 0.50 USD per piece. Create PO (item K). Goods receipt 5,000 pieces via MIGO 101 K. Stock shows in MMBE under consignment. When the production line needs packing, issue 1,000 pieces via 201 K to cost centre 2001. FI document: debit expense 40000100 500 USD, credit consignment liability 30000500 500 USD. End of month, run MRKO – vendor invoice generated, debits 30000500, credits vendor AP 30000010. The vendor gets paid. No inventory valuation impact until consumption – pure working‑capital efficiency.

5. Subcontracting – Send Components, Get Finished Assembly

Subcontracting is the process of sending your components to a vendor who performs a service (e.g., painting, assembly) and returns a finished or semi‑finished product. The special stock indicator is “O” (subcontracting stock). The components are stored at the subcontractor’s site but remain your inventory, albeit in a separate stock segment.

5.1 Configuration and Master Data

No major SPRO needed beyond standard. The subcontracting PO item category is “L”. A BOM (Bill of Material) for the material to be produced is typically required, or a component list can be entered manually in the PO.

GlobalTech subcontracts the painting of housings. Material “HOUSING_PAINT” (FERT or HALB) needs raw material “HOUSING_RAW” to be sent to the painter.

5.2 Process Walkthrough

Step 1: Create purchase order (ME21N) with item category “L” for material HOUSING_PAINT. In the PO, enter the target quantity, price per unit (subcontracting fee, e.g., 5 USD per unit). Then maintain the components to be provided: tab “Components” or “Material Data” → add component HOUSING_RAW, required quantity 1 per finished unit, plant GT01, storage location RM01. This tells the system which components to consume when the finished goods are received.

Step 2: Goods issue of components to subcontractor: movement type 541 (GI to subcontracting). In MIGO, enter movement type 541, reference the PO. Select the component, quantity. Post. Material document: reduces HOUSING_RAW unrestricted stock, increases subcontracting stock (special stock O) at the vendor’s location. FI document: debit subcontracting inventory (a special GBB account for 541, account grouping VBR? Actually, 541 uses GBB with account grouping ‘VBR’ but the offset account is the subcontracting material consumption account, typically a cost element that will be cleared later). Wait, the correct accounting: when you issue components to subcontractor, the components are still your asset, but they move to a different balance sheet account – “Inventory provided to subcontractor”. So configure GBB for movement 541 with a separate account (e.g., 20000095) distinct from normal raw material inventory. In OBYC, under GBB, account grouping for movement type 541 is ‘VBR’ (consumption). We assign for valuation class 3000, account 20000095 (Stock with Subcontractor). The posting: debit 20000095, credit 20000010 (raw material inventory). This is not a P&L impact; it’s an asset transfer. So you need to correctly map the account grouping for 541 to a balance sheet account, not a P&L account. This is a common mistake. You can define a new account grouping, e.g., “SUB”, and assign it to movement 541 via OMJJ (in the movement type’s value string) or simply use the standard that already maps 541 to the account grouping ‘VNG’? Actually, check: standard movement type 541 uses value string WA01 and transaction key GBB with account grouping ‘VBR’ for consumption. But many companies override this. The safest is to create a new account grouping for subcontracting (e.g., ZSC) and assign the balance sheet account. We’ll do that.

In OMJJ, select movement type 541, double‑click “Value String”. The account grouping for GBB is ‘VBR’. You can change it to a custom one, but better: in OBYC, for GBB account grouping VBR, you can assign different accounts depending on the special stock indicator? OBYC doesn’t directly key on special stock. So you must use the account modifier via the valuation grouping code? Actually, you can use the “Account grouping” field in the movement type to differentiate. In OMJJ, you can set the account grouping to a different value for subcontracting, e.g., ‘ZSC’. Then in OBYC, create GBB entry with account grouping ZSC and valuation class 3000 → account 20000095. That’s clean. GlobalTech will use that. So configure OMJJ: movement type 541, account grouping ‘ZSC’, and in OBYC GBB, ZSC -> 20000095.

Step 3: Goods receipt of finished material from subcontractor: movement type 101 for purchase order with item category L. In MIGO, reference the PO. The system automatically consumes the components (goods issue of subcontracting stock) via movement type 543 (GI from subcontracting). The user posts the receipt; behind the scenes, SAP posts the 101 receipt into own stock of HOUSING_PAINT, and also a 543 movement that reduces the subcontracting stock of HOUSING_RAW and debits the cost of the finished good (or rather, it credits the subcontracting inventory and debits the production/consumption account). The accounting for the finished good: The standard price of HOUSING_PAINT is 20 USD. The PO price is the subcontracting fee 5 USD, plus the value of components. SAP calculates the total value: subcontracting fee (5 USD) plus the component value (from the subcontracting stock valuation). The component value is determined by the material’s price control at the time of consumption. For HOUSING_RAW, if it’s MAP, the consumption value is at current MAP. For standard price, at standard. The total becomes the value credited to the vendor (fee) and the value debited to inventory. The posting: debit HOUSING_PAINT inventory (20 USD), credit vendor (5 USD), credit subcontracting stock (20000095) for the component value, and any residual to price difference.

Wait, precise journal entries: Upon receipt:

• Debit Finished Goods Inventory (BSX) 20.00 (standard)
• Credit Vendor (WRX? No, subcontracting fee liability) 5.00 (this uses a different transaction key, FRL – External service)
• Credit subcontracting inventory (GBB ZSC) for the component consumption value, say 15.00.

If the standard price doesn’t equal the sum of component value + fee, the difference goes to price difference (PRD). For moving average, the MAP is recalculated based on total receipt value.

OBYC needs configuration for FRL (Subcontracting Charges) which credits the vendor. In OBYC, transaction FRL, set account 30000100? Actually, FRL posts to GR/IR clearing or directly to a liability account depending on your config. Usually, it posts to GR/IR clearing (WRX) along with the goods receipt. So the total credit is to GR/IR: 5 + 15 = 20? No, component consumption doesn’t go through GR/IR; it’s internal. The vendor portion (fee) goes through GR/IR. So the actual posting: debit inventory 20, credit GR/IR 5 (via FRL), credit subcontracting stock consumption 15. Then the invoice clears the GR/IR 5.

We’ll configure FRL account similarly to WRX, or a specific subcontracting GR/IR. We’ll set FRL to account 30000100 (same GR/IR).

After posting, the subcontracting stock of components is reduced. The vendor delivery is complete.

This sub‑process highlights the importance of correct account determination for subcontracting. The value flow must be tested thoroughly.

5.3 Subcontracting Best Practices

• Ensure components are always correctly costed before consumption to avoid wild MAP swings.
• Use standard price for the finished product to isolate subcontracting cost variances.
• Regularly reconcile subcontracting stock (report MMBE special stock O) with physical vendor records.
• Set up tolerance for subcontracting fee invoice variance to avoid blocking payment for small differences.

6. Warehouse Management Basic vs. Extended (EWM) – A Decision Guide

When clients ask “Do we need a warehouse management system?”, the answer depends on complexity. SAP offers classic WM (LE‑WM) and the more modern SAP Extended Warehouse Management (EWM). In S/4HANA, embedded EWM is available, often replacing classic WM.

6.1 Basic Inventory Management (IM)

IM tracks stock at storage location level. It knows quantity and value but not exact bin location. Suitable for simple warehouses where pickers know where things are, or where storage is small. No complex put‑away or picking strategies.

6.2 Classic WM (LE‑WM)

Adds bins, transfer orders, and strategies for put‑away and picking. Integrates with IM. Still supported but SAP’s strategic focus is EWM. Suitable for medium complexity, single‑warehouse operations.

6.3 Embedded EWM in S/4HANA

Offers advanced features: labour management, yard management, wave picking, cross‑docking, slotting, integration with automated warehouse systems. It runs on the same S/4HANA instance (embedded) or separate. Embedded is recommended for new implementations if advanced warehouse processes are needed.

6.4 Decision Factors

• Number of warehouse movements: if you process thousands per day, EWM’s performance and wave picking help.
• Need for bin‑level tracking: if FIFO, shelf life, or serial number tracking at bin is required, EWM.
• Automation: conveyor systems, pick‑to‑light, voice picking – EWM is essential.
• Complex processes: cross‑docking, VAS, kitting – EWM.
• Cost: EWM requires additional licensing and implementation effort. Basic IM is free with S/4HANA. Classic WM may be cheaper if already in use.

For GlobalTech, plants GT01 and GT02 currently use IM with simple storage locations. As they grow, they plan to implement embedded EWM for their main distribution centre. Today’s configuration stays in IM, but we note the upgrade path.

7. Full End‑to‑End Scenario – Putting It All Together

GlobalTech’s US plant runs a typical month with split valuation, consignment, and subcontracting, ending with GR/IR clearing.

Day 1: Receive external RAW01 (valuation type EXT) 200 KG at 10 USD. Post 101 → debit 20000012, credit GR/IR 30000100. MAP updates.

Day 5: Receive internal RAW01 (OWN) 150 KG from production at 9.50 USD. Post 101 → debit 20000011. MAP for OWN adjusts.

Day 10: Transfer consignment PACK02 2000 pieces to own via 411 K. Debit packing material inventory, credit consignment liability 30000500. Run MRKO at week end to pay vendor.

Day 15: Send HOUSING_RAW 500 units to subcontractor via 541. Stock moves to subcontracting inventory 20000095. Later, receive HOUSING_PAINT 500 units via 101. Posting: debit finished goods 10,000 (20 x 500), credit GR/IR 2,500 (fee), credit subcontracting stock 20000095 7,500 (component value).

Day 25: Invoice for external RAW01 arrives with price difference. Invoice at 10.20 for the 200 KG. Post MIRO. Since MAP control, system checks stock. If stock > 200, MAP adjusts; difference 40 USD added to inventory value. If stock < 200, partial to price difference.

Day 31: Month‑end. Run FAGL_CL_REGRU to reclassify GR/IR. The net open item on 30000100 is reclassified. Clear any old GR/IR items via F.13. Check MR11 for discrepancies. Reconcile subcontracting stock with vendor statement. All accounts are balanced.

8. Best Practices, Pitfalls & Alternatives

Best Practices:

• Design split valuation and account determination carefully; document each valuation type and its usage.
• Use MAP for raw materials but set a maximum price difference tolerance in OBYC (transaction key PRD) to prevent wild MAP swings.
• For standard‑priced materials, run a costing run (CK11N/CK40N) at least once per quarter to keep standards close to actual.
• Automate GR/IR clearing with F.13 daily and FAGL_CL_REGRU monthly. Never leave GR/IR uncleared for more than 3 months.
• In consignment, always run MRKO before month‑end to ensure liability is properly stated; unprocessed consignment settlements distort the balance sheet.
• Test subcontracting thoroughly with small quantities; the automatic component consumption (543) can surprise you if BOM or component quantities are wrong.

Common Pitfalls:

• Forgetting to set the correct valuation type derivation in OMWW, leading to goods receipt errors “Valuation type not determined”.
• Using MAP for low‑turnover, high‑value items – a late invoice can revalue the last unit to an absurd amount.
• Not configuring the subcontracting account grouping (ZSC) correctly, causing component issue to post to P&L instead of asset transfer – distorts both P&L and inventory.
• Ignoring the GR/IR reclassification account setup, then the balance sheet shows gross GR and IR amounts instead of net, confusing stakeholders.

Alternatives:

• Instead of split valuation, use different material numbers for internal vs external – simpler but master data bloat.
• Actual costing (Material Ledger) can provide periodic actual price, which may eliminate the need for split valuation based on origin.
• For subcontracting, if you have an external manufacturer, you could use a separate plant and STO (stock transport order) instead of subcontracting, but that loses component tracking.
• EWM vs. WM: always lean towards embedded EWM for new implementations if any advanced feature is needed, to avoid legacy WM migration later.

9. Conclusion – You Are Now an Inventory Valuation and Special Stocks Expert

Day 7 has equipped you with the skills to configure and operate the most intricate parts of MM inventory management. You can split valuation, choose price controls intelligently, reconcile GR/IR with precision, manage consignment and subcontracting stock flows, and advise on warehouse system decisions. This is the deep expertise that senior MM consultants possess.

Tomorrow, on Day 8 (Part 23), we begin the Sales & Distribution (SD) track – enterprise structure, sales org, distribution channels, divisions, and customer master data. Prepare to configure the order‑to‑cash engine. The depth continues. Don’t miss it.

@FreeLearning365 – Tech Partner @techbook24