SAP MM ECC vs S/4HANA: Key Changes and Simplifications

 ECC vs S/4 HANA in SAP MM — What You Really Need to Understand

To help every consultant, whether they are Functional, Technical, or a Project Manager, understand the shift from ECC to S/4HANA MM, we need to focus on the "Big Six" changes.

Think of this as moving from an old, fragmented system to a streamlined, high-speed engine.

 

1. The "Unified ID": Business Partner (BP)

In ECC, you had separate screens for Vendors (XK01) and Customers (XD01).

• S/4HANA Reality: Everything is a Business Partner (BP).
• Easy understanding: Imagine you have one "Profile" (the BP) and you simply assign different "hats" to it. One hat is the Supplier role (for MM), and another is the Customer role (for SD).
• Why it matters: It eliminates duplicate data. You no longer have to create the same company twice if you both buy from and sell to them.

2. The "Single File": MATDOC Table

In ECC, inventory data was messy. A single Goods Receipt was saved in many different tables (like MKPF for the header and MSEG for the items).

• S/4HANA Reality: All logistics movements now live in one single table: MATDOC.
• Easy understanding: Instead of keeping your receipts in five different folders, you now have one master digital ledger.
• Why it matters: It makes reporting 100x faster. When you search for stock history, the system only has to look in one place.

3. The "Supercar" Engine: MRP Live

In ECC, Material Requirements Planning (MRP) was a heavy process. You usually ran it overnight because it slowed down the system.

• S/4HANA Reality: MRP Live (MD01N) runs directly on the HANA database, not the application layer.
• Easy understanding: MRP moved from a slow "tractor" to a "Formula 1" car. It calculates what you need to buy in seconds.
• Why it matters: You can run MRP many times a day. If a L'Oréal warehouse in Paris suddenly runs out of shampoo, MRP Live can detect it and suggest a purchase order almost instantly.

4. The "Name Tag": 40-Character Material Number

In ECC, the Material Number (MATNR) was limited to 18 characters.

• S/4HANA Reality: You can now have up to 40 characters.
• Easy understanding: You have more space to name your products.
• Why it matters: This is a "Technical Warning." If you have custom ABAP code (Z-programs) written for 18 characters, they might break. Technical consultants must check this during the migration.

5. The "Smartphone" Interface: Fiori

In ECC, we used the SAP GUI with Transaction Codes like ME21N. It looked like software from the 1990s.

• S/4HANA Reality: We use Fiori Apps.
• Easy understanding: It’s like moving from an old flip phone to an iPhone. Instead of typing T-codes, you click on "Tiles."
• Why it matters: You can approve Purchase Orders on your phone or tablet while traveling. It also gives you "Alerts"—the system tells you when a vendor is late, instead of you having to run a report to find out.

6. The "Smart Rules": Output Management (BRF+)

In ECC, if you wanted to print a PO or send an email to a vendor, you used "NAST" (Output Types). It was rigid and hard to configure.

• S/4HANA Reality: The new standard is BRF+ (Business Rule Framework plus).
• Easy understanding: It’s a "Decision Tree" for your documents.
• Why it matters: It is much more powerful. You can set complex rules like: "If the PO is for a Luxury Brand and the amount is > €50k, send an encrypted PDF; otherwise, send a standard EDI."

 

⚖️ Summary for the Team

Point	ECC MM (The Old Way)	S/4HANA MM (The New Way)
Vendor	Separate "Vendor" master data.	Unified Business Partner (BP).
Data	Data scattered in MSEG, MKPF, etc.	Data centralized in MATDOC.
Speed	Overnight MRP runs.	Real-time MRP Live.
Length	18 chars for Material ID.	40 chars for Material ID.
Look	Grey screens and T-codes.	Modern Fiori Apps and Tiles.
Prints	Old NAST configuration.	Intelligent BRF+ rules.