The specific problems this training actually solves

Not generic SAP training. These are the exact field-level confusions that cost consultants hours — documented from a live ZRetail S/4HANA system, article Z300001 (ZRetail Classic Polo Shirt, 11 variants).

Why does MM46 open MASS instead of its own transaction?

MM46 is not a standalone mass-maintenance tool — it's a shortcut that opens the generic MASS transaction with object type BUS1001001 already preloaded. Once you know that, you stop hunting for an "MM46 field list" that doesn't exist and start working directly in MASS, where the real field selection lives.

SAP Change Material screen showing MRP Type by color and size variant for a generic material — Generic material Z300001 (ZRetail Classic Polo Shirt) — MRP Type maintained per Color/Size variant combination.

MASS vs WRFMASSMAT — which one do you actually need?

WRFMASSMAT is Integrated Mass Change: the retail-specific tool that lets you change article data across multiple views and multiple stores/DCs in one pass, with listing and assortment logic baked in. Plain MASS is the generic cross-module tool. If you're only touching basic data fields, MASS works. The moment listing, assortment, or store-specific pricing enters the picture, you need WRFMASSMAT — using MASS there will silently skip retail-specific validations.

MARA-ATTYP vs MARA-MTART: what actually distinguishes a generic article from a variant?

This is the single most common IS-Retail mistake for consultants coming from standard SAP MM. You'd expect MTART (material type) to tell you whether an article is generic or a variant — it doesn't, in retail. The field that actually matters is MARA-ATTYP (article category). Filter or debug on the wrong field and your generic-article logic will quietly miss records.

Why "Available to" and "For sale till" instead of standard discontinuation fields?

IS-Retail discontinuation doesn't use the field names you'd expect from an ECC materials background. The two fields that actually drive the process are labeled Available to and For sale till — get the mapping wrong in a data load and articles either discontinue too early or never trigger at all.

Why won't WQ01 or WQ11 open?

Both transactions are blocked per SAP Note 2476734 in current S/4HANA releases. If you're following an older tutorial or ECC-era documentation that references them, stop — they've been deprecated at the SAP level, not just disabled in your system. The course covers the current replacement path.

WAK1 or BPK1 for promotion creation? WSA3 or WSOA3?

Two more cases where the "obvious" transaction from general MM knowledge is wrong in retail: promotion creation is WAK1, not BPK1. And the correct transaction is WSOA3, not WSA3 — a one-character difference that sends you to the wrong screen entirely if you mistype or misremember it.

SAP Create Price Calculation screen showing markup percentage, gross sales price and final price for a retail article — Price calculation for Z300001: Basic PP, Markup%, Gross SP and Final price fields as they appear in a live pricing run.

KONH and KONP — are these really the right condition tables?

Yes — despite plenty of forum answers suggesting otherwise for retail-specific condition records, KONH (condition header) and KONP (condition item) are the correct tables to query. The course walks through pulling live pricing data from both during a real price calculation.

What actually happens during a Goods Receipt in ZRetail?

Beyond the transaction codes, the course walks a real stock movement end to end — movement type 561 (initial entry of stock balance), storage location, unrestricted-use stock — on the same article used throughout the course, so you see the article master data you built actually receiving inventory.

SAP Goods Receipt Other screen showing a stock movement for ZRetail Cotton Crew Neck T-Shirt Unisex — Goods Receipt Other: movement type 561 posting 87 EA of ZRetail Cotton Crew Neck T-Shirt Unisex into unrestricted-use stock.

What's actually inside Retail Master Data — General Control?

This customizing screen controls more than most consultants realize: default valuation class, assortment version logic, listing conditions, and — critically for data migration projects — the multiple-assignment and time-dependent assignment switches that determine whether your mass load will even be accepted.

SAP Retail Master Data General Control customizing screen — Retail Master Data — General Control: assortment, listing and mass-maintenance customizing switches.

Learn SAP IS-Retail the way it actually breaks in production — not the way the manual says it should work.

Pick your starting point

A Practical Guide to Article Master Data in SAP IS-Retail

MM41: Advanced Article Creation Guide

Free preview: the full ECC-era playlist