Lesson 3 of 6
The product master: views and organizational levels
7 min
The product master (still called the material master in many screens and documents) is the record that describes what Contoso buys, makes, stores and sells. One product number, such as CMC-ALT-100, is used by sales, purchasing, planning, production, warehousing, quality and finance. Each of those teams needs different data, so the record is divided into views.
Views and the level they live at
A view is a group of fields for one department. The important idea is that each view is maintained at a particular organizational level. Basic data is the same everywhere. Sales data can differ by sales organization and distribution channel. MRP data can differ by plant. Accounting data can differ by valuation area, which in most systems is the plant.
The product type (material type) decides which views make sense and how the product is valuated. Finished goods (type FERT), raw materials (ROH), semifinished products (HALB) and trading goods (HAWA) are common standard types. Contoso's alternator is a FERT; the rotor it buys is a ROH.
Where you maintain it
In SAP GUI, the classic transactions are MM01 (create), MM02 (change) and MM03 (display). You choose the views, then enter the organizational levels on a pop-up. In Fiori, the Manage Product Master Data app lets you search, display, create, copy and edit products on one object page. SAP's own Best Practices test scripts offer both routes. The Fiori app does not expose every field the classic transactions do, so some specialist fields still need MM02.
How a missing view stops a process
Because views are org-specific, a product can be perfectly usable in one place and invisible in another. Typical symptoms:
| What the user tries | Missing view | What happens |
|---|---|---|
| Sell CMC-ALT-100 through sales org 1710, channel 10 | Sales views for 1710 / 10 | The sales order rejects the item: product not defined for the sales area |
| Order rotors for plant 1720 | Purchasing or plant view for 1720 | The purchase order rejects the item: product not maintained in the plant |
| Run MRP for plant 1720 | MRP views for 1720 | MRP does not plan the product in that plant |
| Post a goods receipt into plant 1720 | Accounting view for valuation area 1720 | The posting fails because the product cannot be valuated there |
Missing views fail loudly or, worse, quietly.
The loud failures are easy. The quiet ones are dangerous: a product with an MRP view but the wrong MRP type will not be planned, and nothing errors. A product with the wrong valuation class posts inventory to the wrong G/L account, and the goods receipt saves happily.
What would you do?
Contoso is rolling out sales from the Chicago plant. A tester creates a sales order for CMC-ALT-100 with delivering plant 1720. The order saves, but the delivery cannot be created and the availability check shows no stock even though the warehouse says 40 units are on the shelf. What is the best first step?
- The product master is divided into views, each for one department.
- Views are maintained at organizational levels: client, sales org and channel, plant, valuation area, storage location.
- The product type (FERT, ROH, HALB, HAWA) controls which views apply and how stock is valuated.
- Missing views stop processes in that org unit; wrong values in existing views can fail silently.
- Use MM01/MM02/MM03 or the Manage Product Master Data app; not every field appears in both.
Check your understanding · not graded
Lesson check
1. At which organizational level is MRP data maintained?
2. Why might CMC-ALT-100 be sellable in one sales area and not another?
3. Which Fiori app is used to create and edit products?
4. A product posts goods receipts to the wrong inventory account. Which view is most likely wrong?