RM-IRON-01 · ROH (exists)
→
HALB-BILLET-01 · semi-finished
→
FERT-REBAR-01 · finished
MM01
🎯 Why produced materials are set up differently
PakSteel's chain: buy iron → melt & cast into billets → roll billets into rebar. The raw material is bought; the billet and rebar are made. That single difference flips three master-data settings — learn these three and material types stop being confusing:
| Setting (Accounting 1 / MRP 2) | RM-IRON-01 (bought) | HALB-BILLET-01 (made) | FERT-REBAR-01 (made) |
|---|---|---|---|
| Material type | ROH | HALB | FERT |
| Valuation class (→ OBYC G/L) | 3000 | 7900 | 7920 |
| Price control | V — moving avg | S — standard | S — standard |
| Procurement type | F — external | E — in-house | E — in-house |
Why S, not V, for made goods? A bought material's cost is whatever the vendor charged (it varies → V, moving average). A made material's cost is a planned standard you set once (S); when actual production costs differ, the gap posts as a variance — that's how SAP measures factory efficiency. So produced materials almost always use price control S.
🗺️ The MM01 screen — 3 moves, then tabs with sections
MM01 always runs in the same 3 moves: ① the Initial screen (which material, which type) → ② two popups — "Select View(s)" (which chapters of the material book you will fill) and "Organizational Levels" (which plant / storage location this copy belongs to) → ③ the view tabs (MRP 1, Accounting 1, …). On every tab, directly under the tab strip sits a header line with the Material number and the Description field — you type the name there once and every tab shows it. Inside each tab, fields are grouped into titled boxes ("sections") — our tables below name the exact section for every field, so you always know where to look.
🗺️ Want the bigger picture — which tables these views write to, and how the valuation class turns a goods movement into money? See the MM ↔ FI Map (one page).
⚠️ Before you start — three one-time config keys these views demand
Produced materials need a few plant-level config keys on the MRP / Work-Scheduling views. Like "person responsible" on the work center, your plant PK01 may not have them yet — create each once (any value), then reuse forever. If a field rejects your entry, that's why.
When prompted for a Customizing Request while creating any of these, click Create Request → describe it → continue. (That records config locally; it is never transported — same as before.)
| Key — and where MM01 asks for it | Value | Create it here (verified) | On its New Entries screen, fill |
|---|---|---|---|
| MRP Controller MRP 1 tab → "MRP Procedure" section |
PK1 | OMD0 — or SPRO → Production → MRP → Master Data → Define MRP Controllers | Only Plant PK01 + MRP Controller PK1 are required. Add a name (e.g. "PK Planner 1") so lists read well. Leave Telephone, Recipient, Business Area, Profit Center blank → Save. |
| Schedule Margin Key MRP 2 tab → "Scheduling" section (label: SchedMargin key) |
000 | SPRO → Production → MRP → Planning → Scheduling and Capacity Parameters → Define Floats (Scheduling Margin Key) — or OPPQ → plant → Floats button. No direct T-code: OPPF opens an unrelated "Order Report" screen, and OMDC is not valid on S/4HANA → registry | Plant PK01 · Margin key 000 · Opening period 0 · Float after production 0 · Float before production 0 · Release period 0. All are workdays; zeros = no scheduling buffer (fine for practice) → Save. |
| Production Scheduler Work Scheduling tab → "General Data" section (label: Production Supervisor — SAP renamed it; older screens abbreviate "Prodn Supervisor") |
PK1 | OPJ9 — or SPRO → Production → Shop Floor Control → Master Data → Define Production Scheduler | Plant PK01 + ProdScheduler PK1 + a description. Leave Prod.Sched.Profile blank — if filled, that profile must already exist (OPKP) → Save. |
| Valuation class allowed for the type Accounting 1 tab → "General Valuation Data" section |
7900 / 7920 | OMSK — usually already allowed in IDES; only touch if MM01 rejects it | Account category reference of HALB must allow 7900, of FERT 7920 (standard SAP already does). |
| Profit Center Costing 1 tab → "General data" section |
PSPK-PC | KE51 — you created this in the Controlling setup | Nothing new — just make sure it exists and is active for PSPK. |
🟡 Material 1 — HALB-BILLET-01 (semi-finished steel billet)
Select views: Basic Data 1 · Basic Data 2 · MRP 1 · MRP 2 · MRP 3 · MRP 4 · Work Scheduling · General Plant Data / Storage 1 · Accounting 1 · Costing 1 · Costing 2.
(Skip Sales views — a billet is consumed internally, not sold. Skip Quality views unless you run QM.)
Organizational Levels popup: Plant
(Skip Sales views — a billet is consumed internally, not sold. Skip Quality views unless you run QM.)
Organizational Levels popup: Plant
PK01 · Storage Location WIPS (work-in-progress).
How to read the tables. Column 1 = the exact section box on the tab (📍 rows) and the field's on-screen label. Fill column: ✅ mandatory (can't save without) · ➕ set this · — leave blank/default · 🔧 needs a one-time config key (see prerequisites). Anything not listed on a view: leave at default.
Move 1+2 — Initial screen & the two popups
| Where · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Initial screen | |||
| Material | ✅ HALB-BILLET-01 | The unique code this material will live under — like a person's ID number. | You type it yourself because our material type allows external numbering. Impact: a typo here creates a differently-named material — there is no rename, only delete-and-recreate. |
| Industry Sector | ✅ M | Which industry's field set SAP should show — a filter over the screens. | M (Mechanical Engineering) shows the manufacturing fields we need. Impact: cannot be changed later; a wrong sector can hide fields you need forever. |
| Material type | ✅ HALB | What KIND of thing this is — bought? made? sellable? The type decides allowed views, numbering, and the default valuation class. | HALB = semi-finished, made in-house and consumed in-house. Impact: wrong type = wrong G/L determination and wrong views; also effectively unchangeable once stock exists. |
| 📍 Popup "Select View(s)" — appears after Enter | |||
| View list | ✅ pick the 11 views above | Which chapters of this material's book you will maintain now. Unpicked views can be added later with MM01 again (called "extending"). | A produced material needs planning (MRP), shop-floor (Work Scheduling) and money (Accounting/Costing) chapters. Impact: a missing view = missing fields at transaction time (e.g. no Accounting 1 → no goods movement possible). |
| 📍 Popup "Organizational Levels" — appears next | |||
| Plant | ✅ PK01 | Which factory this copy of the data belongs to. Plant-level views (MRP, Work Scheduling, Accounting) are stored PER plant. | Our only plant. Impact: data lands under the wrong plant → the material "does not exist" where you need it. |
| Storage Location | ➕ WIPS | Which room inside the factory to prepare storage data for. | WIPS = work-in-progress store, where billets wait to be rolled. Impact: without it, the storage view isn't created — first goods receipt can still create it, but reports stay empty until then. |
| 📍 Header line — under the tab strip, on every tab | |||
| Descr. (Description) | ➕ Steel Billet 100×100mm | The human name shown on orders, stock lists and reports. Typed once here, visible on every tab. | Clear names save everyone time. Impact: a vague name ("Material 1") makes every future F4 search painful. |
Basic Data 1 — identity & unit
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "General Data" | |||
| Base Unit of Measure | ✅ TO | The unit ALL stock and value are counted in — the material's mother tongue. Other units are translated into this one. | Steel is traded in tonnes. Impact: very hard to change once any stock or document exists; a wrong base unit poisons every quantity forever. |
| Material Group | ✅ 001 (F4) | A family label for reporting and purchasing ("all steel products"), like a supermarket aisle name. | Any existing group works for practice — F4 and pick. Impact: must already exist; a wrong group only skews reports, it doesn't block postings. |
| Old material number | — blank | A cross-reference to the code this material had in an older/legacy system. | We have no legacy system. Impact: none — purely informational. |
| Division | — blank | A sales-side grouping (SD uses it to route sales). | The billet is never sold. Impact: none without SD views. |
| X-Plant Mat.Status | — blank | A company-wide "traffic light" that can block this material everywhere (e.g. "being phased out — no new orders"). | A new material should be fully usable. Impact: setting a blocking status here stops purchasing/production in ALL plants. |
| GenItemCatGroup | — blank | Tells SD how an item of this material behaves on a sales order. | No sales here. Impact: none without SD. |
| 📍 Section "Dimensions/EANs" | |||
| Gross Weight · Net Weight · Volume (+ units) | — blank | Physical shipping data — how heavy and how big one unit is. | Only needed for transport/packing planning. Impact: none for our scenarios. |
| 📍 Tab "Basic data 2" | |||
| All fields | — blank | Design documents, environment/safety data, extra descriptions. | Not needed for a practice billet. Impact: none. |
MRP 1 — how it's planned
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "MRP Procedure" | |||
| MRP Type | ✅ PD | Which planning brain runs this material: full look-ahead planning, simple refill-when-low, or none at all? | PD = classic MRP: the system looks at demand and creates supply proposals. (VB = reorder point, ND = no planning.) Impact: ND means MRP runs ignore the material completely; VB needs a reorder point filled. |
| MRP Controller | ✅ 🔧 PK1 | WHO is responsible for planning this material — the planner's 3-character badge. Reports and worklists are grouped by it. | PK1 is our plant planner key (create once via OMD0 — see prerequisites). Impact: MM01 refuses to save the view without a valid controller. |
| Reorder Point | — blank | The stock level that triggers a refill — the fuel-warning lamp. | Only used by reorder-point MRP types (VB). Impact: ignored with PD. |
| Planning time fence | — blank | A "do not touch" window (in days) where MRP may not change existing plans automatically. | Refinement we don't need. Impact: none when blank. |
| 📍 Section "Lot-Size Data" | |||
| Lot Sizing Procedure (this is the S/4HANA label — older materials call it "Lot size") | ✅ EX | When demand exists, HOW BIG should each production order be? Exactly as needed? Fixed batches? Weekly buckets? | EX = lot-for-lot: make exactly what is needed, when needed — simplest to follow when learning. Impact: a fixed/periodic procedure changes order quantities and dates in ways that confuse a first MRP run. |
| 📍 Section "General Data" | |||
| Purchasing Group · MRP Group · ABC Indicator | — blank | Buyer team (for bought parts), plant-level planning parameter bundle, and importance ranking. | Optional refinements — not needed for a made-in-house part. Impact: none when blank. |
MRP 2 — procurement & timing
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "Procurement" | |||
| Procurement type | ✅ E | Where supply comes from: E = we make it, F = we buy it, X = either. | The key "made not bought" flag — it makes MRP propose planned/production orders instead of purchase requisitions. Impact: F here would send billet demand to the purchasing department. |
| Special procurement | — blank | An exception rule on top: phantom assembly, subcontracting, stock transfer from another plant… | Plain in-house production needs no exception. Impact: a wrong key silently reroutes supply (e.g. to another plant). |
| Prod. stor. location | ➕ WIPS | Which room the finished billets land in when the production order receives them (and where components are pulled for backflush). | WIPS is our work-in-progress store. Same field also appears on the Work Scheduling tab ("Prod.stor.loc.") — one field, two windows; fill it once. Impact: blank = you must type the location by hand on every goods receipt. |
| Backflush | — blank | Should component consumption post automatically at confirmation instead of by hand? | Manual first — learn the goods movements before automating them. Impact: none when blank. |
| 📍 Section "Scheduling" | |||
| In-house production | ➕ 2 (days) | How many workdays it takes to produce one lot, independent of lot size — the kitchen's cooking time. | 2 days is a sensible practice value; MRP uses it to schedule order start dates backwards from the need date. Impact: 0 days = orders start the day they must finish; unrealistic dates. |
| SchedMargin key (exact on-screen label) | ✅ 🔧 000 | Which "buffer-days package" to wrap around production — safety margins before/after the cooking time. | 000 = our zero-buffer key (create once via the SPRO "Define Floats" path — see prerequisites; note: no direct T-code, OPPF is a trap → registry). Impact: MM01 refuses the view if the key doesn't exist for PK01. |
| GR processing time | — blank | Extra workdays to inspect/put away goods after receipt. | No inspection delay in our practice flow. Impact: none when blank. |
| Planned Deliv. Time | — blank | Vendor lead time in days — how long a PURCHASE takes to arrive. | Only meaningful for bought (F) materials. Impact: ignored with E. |
| 📍 Section "Net requirements calculation" | |||
| Safety stock · Min safety stock · Coverage profile | — blank | Untouchable emergency stock and dynamic buffer rules. | Buffers are a later lesson. Impact: none when blank. |
MRP 3 — forecast & availability
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "Availability check" | |||
| Availability check | ✅ 02 | Which rulebook ATP uses when promising stock: what counts as "available" and how far ahead to look. | 02 = individual requirements — each demand is checked on its own; the standard choice. Impact: blank blocks the view; a wrong group can make sales/production promises against stock that isn't really free. |
| Tot. repl. lead time | — blank | Total days to fully replenish the material from zero, used by the check as the outer horizon. | Optional refinement. Impact: none when blank. |
| 📍 Section "Forecast Requirements" | |||
| Period Indicator | ➕ M | The bucket size for forecast/consumption history: monthly, weekly, daily. | M (monthly) is the default and fine. Impact: only matters if forecasting is used. |
| 📍 Section "Planning" | |||
| Strategy Group | — blank | The make-to-stock / make-to-order playbook that tells MRP how sales and production demand meet. | Set 10 (make-to-stock) only if you want MRP to auto-plan; not needed for a manual CO01 order. Impact: none when blank for our flow. |
| Consumption mode · Fwd/Bwd consumption per. · Mixed MRP · Planning material | — blank | Rules for netting forecast against real orders. | Only used with planning strategies. Impact: none when blank. |
MRP 4 — BOM explosion / dependent requirements
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "BOM explosion/dependent requirements" | |||
| Individual/coll. | ➕ 1 | When a parent order needs this material, should each need stay separate (1) or be pooled together (2)? | 1 = individual — easiest to trace while learning: one requirement, one supply. Impact: pooling hides which parent caused which need. |
| ProdVersions (button) | later | Opens the material's production versions — each version links one BOM + one routing into a valid "recipe card". In S/4HANA a production version is mandatory for production. | Don't click yet — BOM and routing don't exist. Create the version after CS01/CA01, via C223 (Step 17D). Impact: without a version, S/4HANA cannot source production. The old ECC field "Selection method" is deprecated in S/4HANA — if your screen still shows it, leave it blank; production versions are the real mechanism now. |
| Component Scrap (%) · Requirements group · MRP dep.requirements | — blank | Scrap allowance and requirement grouping refinements. | Optional. Impact: none when blank. |
| 📍 Section "Discontinued parts" | |||
| Discontin. ind. · Eff.-out · Follow-up matl | — blank | Phase-out plan: stop this part on a date and switch to a successor. | Nothing is being phased out. Impact: none when blank. |
| 📍 Section "Repetitive manufacturing / assembly / deployment strategy" | |||
| Repet. Manufacturing · REM Profile | — unticked / blank | Is this made on a continuous line (repetitive) instead of discrete orders? | We use discrete production orders (CO01). Impact: ticking it demands a REM profile and changes the whole execution flow. |
Work Scheduling — the shop-floor view
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "General Data" | |||
| Production Supervisor (may render abbreviated as "Prodn Supervisor" — SAP's renamed term for the production scheduler) | ✅ 🔧 PK1 | WHO runs the shop floor for this material — the shop-floor counterpart of the MRP controller. Production orders and worklists group by it. | PK1, our scheduler key (create once via OPJ9 — see prerequisites). Impact: MM01 refuses the view without a valid key. |
| Prod.stor.loc. | display / same | The same "Prod. stor. location" field you filled on MRP 2 — one field shown in two windows. | Should already show WIPS. Impact: changing it here changes it everywhere (it is the same stored value). |
| Prod.Sched.Profile | — blank | A bundle of automation rules for production orders (auto-release, auto-print…). | No profile exists in our fresh plant, and none is needed. Impact: filling a non-existent profile blocks the view. |
| Insp.stock · Critical Part · BatchManagement | — unticked | Post receipts to quality-inspection stock? Flag as critical? Manage in batches? | None apply to a plain billet. Impact: Batch management especially — once stock exists it is very hard to switch on/off. |
| 📍 Section "Tolerance data" | |||
| Underdely tol. · Overdely tol. · Unlimited | — blank | How much over- or under-production the goods receipt may accept, in percent. | Defaults are fine for practice. Impact: none when blank. |
| 📍 Section "In-house production time in days" | |||
| InhseProdTime (column "Lot size independent") | ➕ 2 | The same cooking-time value as MRP 2's "In-house production" — SAP shows the one field in both views. | Keep it 2, matching MRP 2. Impact: same field — changing it here changes MRP scheduling. |
| Setup time · Processing time · Interoperation · Base quantity (column "Lot size dependent") | — blank | Precise per-lot scheduling pieces (machine setup, run time per base quantity…). | The routing will carry real times later; the lot-size-independent value above is enough for now. Impact: none when blank. |
General Plant Data / Storage 1 — warehousing
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "General data" | |||
| Storage conditions · Temp. conditions · Container reqmts | — blank | Physical handling rules — must it stay cool, dry, in special containers? | Steel billets need no special handling. Impact: none for learning. |
| Batch management (checkbox) | — unticked | Same batch flag as on Work Scheduling — split stock into tracked batches? | No batches for the billet. Impact: hard to reverse once stock exists. |
| 📍 Section "Shelf life data" | |||
| Min. Rem. Shelf Life · Total shelf life · SLED fields | — blank | Expiry-date management — for food, chemicals, medicine. | Steel doesn't expire. Impact: filling these forces expiry dates on every goods receipt. |
Accounting 1 — the bridge to Finance (the important one)
S/4HANA note: this view was redesigned versus older SAP. Its two sections are "General Valuation Data" (top) and "Prices and Values" (bottom — a small grid with one column per currency; you work in the first column, your company-code currency PKR).
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Section "General Valuation Data" | |||
| Valuation Class | ✅ 7900 | Which G/L "drawer" every stock posting of this material lands in — the address label Finance reads (via OBYC). | 7900 = semi-finished products. Press F4 — only classes allowed for HALB show. Impact: the single most dangerous field on the page — a wrong class silently books every movement to the wrong G/L account. |
| VC: Sale Ord. Stk · Valuation Cat. | — blank | Special stocks valuation and split valuation (different values per batch/origin). | Not used here. Impact: none when blank. |
| ML Act. (checkbox) | display — ticked, greyed | Shows the Material Ledger is on. In S/4HANA it is always on — the value diary is mandatory. | Nothing to do. Impact: none — informational. |
| Price Determ. | display 2 | HOW the material's price is calculated: 2 = transaction-based (normal), 3 = single-/multilevel (only for Actual Costing). | Your system proposes 2 — that is what we set in OMX1 during Material Ledger startup, and 2 is SAP's standard when Actual Costing is off. Leave it. Impact: 3 would force actual-costing mechanics you haven't configured; changing it after creation needs a special transaction (CKMM). |
| 📍 Section "Prices and Values" — fill the first (PKR) column of the grid | |||
| Price Control | ✅ S | Is the book value a fixed plan (S) or a floating average of what you paid (V)? | S — made goods use a planned standard; production differences post as variances, which is how the factory's efficiency is measured. Impact: V on a produced material lets actual costs silently swallow inefficiencies. |
| Standard Price | ✅ 300000 | The planned cost of 1 base unit (1 TO), in PKR — the number stock will be valued at. | ₨300,000 per tonne of billet (iron ₨250k + conversion). Required because Price Control = S. Impact: 0 or missing → MM01 refuses to save; a nonsense price mis-values all stock. |
| Price Unit | ➕ 1 | The price above is per HOW MANY units? (Per 1? Per 100?) | Per 1 TO — keeps mental math simple. Impact: a price unit of 100 silently divides your effective price by 100. |
| Per. Unit Price / Moving price | — blank | The moving-average companion figure. | Informational when Price Control = S. Impact: none. |
| Inventory Value · Total Stock | display | Current value and quantity — SAP calculates these. | Both 0 for a new material. Impact: not enterable. |
Costing 1 / 2 — for the standard-cost estimate
| Section · Field | Fill | What the field asks (plain words) | Why this value — and impact if wrong |
|---|---|---|---|
| 📍 Costing 1 · Section "General data" | |||
| With Qty Structure | ➕ ✔ tick | May SAP cost this material automatically from its BOM + routing (the recipe), instead of you typing costs by hand? | Yes — that is the whole point of standard costing. Impact: unticked = costing runs (CK11N) skip the BOM and expect manual prices. |
| Do Not Cost | — unticked | Exclude this material from costing entirely? | We WANT it costed. Impact: ticked = no cost estimate possible, ever. |
| Profit Center | ✅ PSPK-PC | Which internal "mini-company" owns this material's stock value for management reporting. | Our one profit center. S/4HANA expects it on the material; this Costing 1 field is the standard place to set it for materials that are never sold. Impact: missing → postings error or land on the dummy profit center. |
| Material origin · Origin group · Overhead Group · Variance Key | — blank | Cost-controlling refinements (trace by material, overhead surcharge groups, variance calculation key). | Optional for practice. Impact: none when blank. |
| 📍 Costing 1 · Section "Quantity structure data" | |||
| All fields (BOM Usage, Costing Lot Size, …) | — default | WHICH BOM/routing the cost estimate should pick, and the lot size it costs with. | Defaults work once the production version exists. Impact: none now. |
| 📍 Costing 2 · Sections "Standard Cost Estimate" / "Planned prices" / "Valuation Data" | |||
| All fields | — leave empty | The Future/Current/Previous cost-estimate grid, optional planned prices, and a mirror of Accounting 1. | The grid is filled by the costing process, never typed: CK11N creates the estimate → CK24 marks it (Future) → CK24 releases it (Current, and it updates the Standard Price). Impact: nothing to do at creation. |
When all ✅ fields are filled, Save → "Material HALB-BILLET-01 created". (🔧 fields need a one-time config key — create it, attach to a request, return.)
🟢 Material 2 — FERT-REBAR-01 (finished TMT rebar)
Same flow, two differences: material type FERT, valuation class 7920, finished-goods storage location FNGD.
📌 Every field works the same as the billet — use the per-view tables above. Only the rows below differ (one field per row, with its exact home).
Select views: Basic Data 1/2 · MRP 1–4 · Work Scheduling · General Plant Data / Storage 1 · Accounting 1 · Costing 1/2.
Sales views (Sales Org 1/2, Sales: General/Plant) — only if you'll sell rebar through SD. Skip for now; you can extend later.
Organizational Levels popup: Plant
Sales views (Sales Org 1/2, Sales: General/Plant) — only if you'll sell rebar through SD. Skip for now; you can extend later.
Organizational Levels popup: Plant
PK01 · Storage Location FNGD (finished goods).
| Where (view → section) · Field | Fill | Why / difference vs billet |
|---|---|---|
| Initial screen · Material | FERT-REBAR-01 | The finished product's own code |
| Initial screen · Material type | FERT | Finished good — sellable, made in-house |
| Header line · Descr. | TMT Rebar 12mm | The sellable product's name |
| Basic Data 1 → General Data · Base Unit of Measure * | TO | Same unit as the chain |
| Basic Data 1 → General Data · Material Group * | 001 (F4) | Must exist — same as billet |
| MRP 1 → MRP Procedure · MRP Type * | PD | Same planning brain |
| MRP 1 → MRP Procedure · MRP Controller * | PK1 | Same planner key |
| MRP 1 → Lot-Size Data · Lot Sizing Procedure * | EX | Lot-for-lot, same as billet |
| MRP 2 → Procurement · Procurement type * | E | In-house (you make rebar too) |
| MRP 2 → Procurement · Prod. stor. location | FNGD | Finished goods store (billet was WIPS) |
| MRP 2 → Scheduling · SchedMargin key * | 000 | Same zero-buffer key |
| MRP 2 → Scheduling · In-house production | 2 | Same practice value |
| MRP 3 → Availability check · Availability check * | 02 | Same rulebook |
| MRP 4 → BOM explosion · ProdVersions | later (C223) | Production version comes after BOM + routing exist — the old ECC "Selection method = 2" advice is obsolete in S/4HANA; versions are the mechanism |
| Work Scheduling → General Data · Production Supervisor * | PK1 | Same scheduler key |
| Accounting 1 → General Valuation Data · Valuation Class * | 7920 | Finished products (billet was 7900) |
| Accounting 1 → Prices and Values · Price Control * | S | Standard (made good) |
| Accounting 1 → Prices and Values · Standard Price * | 350000 | Planned cost per TO (₨) — rebar > billet > iron |
| Costing 1 → General data · With Qty Structure | ✔ tick | Cost from BOM + routing, same as billet |
| Costing 1 → General data · Profit Center * | PSPK-PC | Same owner |
Save → "Material FERT-REBAR-01 created". Your value chain now reads RM-IRON-01 ₨250,000 → HALB-BILLET-01 ₨300,000 → FERT-REBAR-01 ₨350,000 per TO.
🚨 Common errors & fixes
| Message / symptom | Cause | Fix |
|---|---|---|
| "Valuation class 7900/7920 not allowed…" | Type↔class link missing | OMSK → allow 7900 for HALB / 7920 for FERT (rare in IDES) |
| "Enter MRP controller / production scheduler / schedule margin key" | That config key doesn't exist for PK01 | Create it once (see the prerequisites table, with the exact New Entries fields) → return to MM01 |
| Typed OPPF for the margin key → strange "Profile / Order Report" screen | OPPF is a mislabeled T-code — it customizes an unrelated report | Back out without saving → registry #err-oppf (use the SPRO "Define Floats" path or OPPQ → Floats) |
| "Standard price must be greater than 0" / costing error | Price control S needs a value | Type a standard price (300000 / 350000) on Accounting 1 → Prices and Values |
| "Profit center … does not exist" | PSPK-PC not created/assigned | Create in KE51, or use the dummy profit center |
✅ Verify
- MM03 → open each material → the selected views are filled (Accounting 1 shows 7900/S and 7920/S).
- SE16N →
MARA(1 row per material),MARC(plant PK01),MBEW(valuation: class + price control S + standard price),MARD(storage WIPS / FNGD).
▶ What's next
With the materials in place you can build the recipe and run a production order: Setup Step 17 — PP Setup for Production (work center → BOM → routing → production version → order), then post the goods issue in Scenario 3.2 (mvt 261).