S/4HANA MM Transformation, Ariba, Migration, Public Cloud and Architecture

MM / P2Pintermediate

MM S/4HANA Part 1: Transformation — Business Partner, Data Model and Clean-Core Impacts

Key takeaway

What changes for MM in S/4HANA: business partner for suppliers, simplified inventory data model (MATDOC), material ledger for valuation, 40-character material numbers, Fiori apps, flexible workflow, output management and clean-core extensibility — and what this means for conversion projects.

Explanation

📌 KEY POINTS
✅ Suppliers are business partners (CVI mandatory before conversion).
✅ Inventory documents are stored in MATDOC; aggregates are calculated, so custom code on old tables needs checking.
✅ Material ledger is active for inventory valuation.
✅ Flexible workflow, output management and Fiori apps change procurement operations.
⚠️ Custom code and modifications must be adapted to simplification items — clean core reduces future effort.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Transformation impacts
Part 2: Architecture with Ariba, public cloud and APIs

━━━━━━━━━━━━━━━━━━━━
▶ 1. MASTER DATA

BP/CVI for suppliers; material number extension.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DATA MODEL

MATDOC for material documents; compatibility views for old tables.
Performance of stock reports.

━━━━━━━━━━━━━━━━━━━━
▶ 3. VALUATION

Material ledger mandatory; actual costing optional.

━━━━━━━━━━━━━━━━━━━━
▶ 4. PROCESSES AND UX

Fiori apps (e.g. Manage Purchase Orders), flexible workflow, output management.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CUSTOM CODE AND CLEAN CORE

Simplification items; ATC checks; move extensions to key-user and side-by-side where possible.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Review MM simplification items.
Analyse custom code touching MKPF/MSEG and aggregates.
Plan CVI, workflow and output changes.

✅ CHECKPOINT: every MM simplification item has an owner and a planned action.

Code example

ABAP Code

===== STEP 1: key changes =====Vendor → BP (CVI) | MKPF/MSEG → MATDOC (compatibility views) | material ledger activeRelease strategy → flexible workflow (optional) | NAST → output management (optional per object) ===== STEP 2: tools =====Readiness check | simplification item checks | ATC custom code checks ===== STEP 3: clean core =====Key-user extensibility | released APIs | side-by-side extensions (BTP)

Real project scenario

A global P2P program converted without analysing custom stock reports; several read aggregate tables directly and became slow or inaccurate. ATC analysis and replacing custom logic with standard Fiori apps and CDS-based reports fixed performance and reduced maintenance.

Common mistakes

Late CVI.
Ignoring custom code on inventory tables.
Keeping all modifications.
No plan for workflow/output.
Underestimating training.

Best practices

Start CVI early.
Run ATC and simplification checks.
Prefer standard apps.
Follow clean core principles.
Train users on Fiori.

Interview angle

Questions: "What changes in MM with S/4HANA?", "What is MATDOC?", "What is clean core?"
Strong answer: BP/CVI, MATDOC and aggregates, material ledger, workflow/output/Fiori, custom code and clean core.

Practice this lesson

Quick check

1. In S/4HANA, where are material document data stored?

2. During cutover, warehouse teams using EWM report that outbound delivery output (packing slips) for goods issue against purchase orders is not generating correctly, and users suspect an authorization gap. How do you architect the diagnosis across MM, output management, and EWM? Choose the response that best aligns with the expected SAP approach.

3. A multinational client is migrating from ECC to S/4HANA Public Cloud and needs to preserve country-specific localization requirements (e.g., withholding tax, e-invoicing) while integrating with an external logistics provider via BTP Integration Suite. What integration and configuration approach would you recommend? Choose the response that best aligns with the expected SAP approach.

Interview questions

1. You are using the SAP S/4HANA Migration Cockpit to load material master and open purchase order data, and the target system also has an EWM-managed warehouse. What special considerations apply to migration object sequencing and validation?

Answer it in your own words first, then compare.

2. During cutover and hypercare for an S/4HANA implementation integrated with Ariba, what authorization controls must be established around integration monitoring tools (e.g., error queues, message monitors) to prevent unauthorized access to or manipulation of in-flight procurement documents?