Quartz 4

Master_Data_Load

3 min read

Master Data Load

What is this?

Master Data Load defines how foundational data is loaded into SAP S/4HANA.

This includes:

  • Business Partner (BP)
  • Material
  • Organizational data

This step MUST complete successfully before any transactional data.

Why it exists?

Master data defines:

  • Who (Business Partner)
  • What (Material)
  • Where (Org structure)

Without this: → Transactions cannot exist

SAP migration cockpit uses predefined objects (BP, Material, etc.) to load master data first. :contentReference[oaicite:0]{index=0}

Core Principle

No master data
→ No system

You cannot:

  • Create PO without BP
  • Post GR without Material
  • Process Invoice without both

Load Sequence (MANDATORY)

1. Organizational Data

  • Company Code
  • Plant
  • Purchasing Organization

2. Business Partner (BP)

  • Create BP (general data)
  • Assign roles (Supplier, Customer)

3. Material

  • Create Material
  • Extend to:
    • Plant
    • Storage location
    • Accounting view

Step-by-Step Process

Step 1: Prepare Data

From transformation layer:

  • Cleaned
  • Deduplicated
  • Enriched

Data must already be: → SAP-ready

Step 2: Select Migration Object

In Migration Cockpit:

  • Business Partner
  • Material

Migration objects define how each type of data is loaded. :contentReference[oaicite:1]{index=1}

Step 3: Download Template

  • SAP provides object-specific templates (Excel/CSV)

These templates:

  • Define required fields
  • Enforce structure

Step 4: Populate Template

From: → Mapping Excel

Apply:

  • Field mapping
  • Default values
  • Derivations

Step 5: Upload Data

  • Upload file into Migration Cockpit
  • System reads and prepares data

Step 6: Field Mapping

  • Map source → target fields
  • Map value translations

Example:

  • Oracle payment term → SAP payment term

Step 7: Validation

System checks:

  • Mandatory fields
  • Data consistency
  • Role completeness

If error: → Fix source data

NOT SAP

Step 8: Simulation

  • Dry run
  • No actual data creation

Used to: → Identify issues early

Simulation step is standard before execution in migration cockpit workflows. :contentReference[oaicite:2]{index=2}

Step 9: Execute Load

  • Data is created in SAP:
    • BP created
    • Material created

Step 10: Post-Load Validation

Check:

  • BP exists with correct roles
  • Material extended correctly
  • No duplicates
  • No missing data

Dependency Mapping

→ BP_Mapping
→ Material_Mapping
→ BP_Validation
→ Material_Validation

Master load executes all of the above logic.

Common Failures

1. Duplicate BP

→ Bad deduplication

2. Missing Roles

→ BP unusable

3. Material Without Plant

→ Cannot transact

4. Missing Valuation

→ FI errors later

5. Partial Load

→ Inconsistent system

Anti-Patterns

❌ Load transactional data first
❌ Fix errors manually in SAP
❌ Skip simulation
❌ Ignore validation warnings

Critical Rule

If master data is wrong:

→ EVERYTHING downstream fails

Not “maybe”
Not “sometimes”

Always

Key Takeaway

Master Data Load is NOT:

→ Initial step

It is:

→ Foundation of the entire system

If this layer is unstable:

  • Transactions break
  • Reporting breaks
  • System becomes unreliable

Backlinks