Quartz 4

BP_Mapping

3 min read

Business Partner Mapping

What is being mapped?

Business entities from Oracle (Suppliers, Customers) are mapped into a single unified structure in SAP S/4HANA called Business Partner (BP).

This involves:

  • Consolidation
  • Transformation
  • Role assignment

Core Transformation

Oracle → SAP

  • Oracle Supplier → BP + Supplier Role
  • Oracle Customer → BP + Customer Role

If same entity exists in both:

→ ONE BP with multiple roles

Key Principle

You are NOT mapping records
You are merging identities

SAP enforces a single master record for all business interactions. :contentReference[oaicite:0]{index=0}

Mapping Strategy

Step 1: Identify Unique Entities

From Oracle:

  • Suppliers
  • Customers

Problem:

  • Same company may exist in both

Solution: → Deduplicate based on:

  • Name
  • Tax ID
  • Address
  • External identifiers

Step 2: Create BP (Base Identity)

For each unique entity:

  • Create ONE Business Partner
  • Assign:
    • Category (Organization / Person)
    • General Data (name, address, contact)

General data is shared across all roles and stored once. :contentReference[oaicite:1]{index=1}

Step 3: Assign Roles

Based on source data:

Oracle SourceSAP Role
SupplierSupplier Role
CustomerCustomer Role

Important:

  • Roles activate process-specific data
  • Without role → no transaction possible

Step 4: Extend Role-Specific Data

Each role requires additional data:

Supplier Role

  • Purchasing data
  • Payment terms
  • Company code data

Customer Role

  • Sales data
  • Billing data
  • Credit data

Role determines which fields are available and required. :contentReference[oaicite:2]{index=2}

Step 5: Number Mapping

Two approaches:

Option 1: Same Number

  • BP ID = Vendor/Customer ID

Option 2: Different Numbers

  • Separate numbering systems

Decision depends on:

  • Legacy dependencies
  • Integration constraints

Number assignment must be defined during BP setup. :contentReference[oaicite:3]{index=3}

Mapping Logic

→ [Google Sheet: Master Data Mapping.xlsx]

This document defines:

  • Field-level transformations
  • Source → target mapping
  • Default values
  • Derivations

Markdown only explains logic.
Excel contains execution.

Process Impact

→ P2P_Procure_to_Pay

Incorrect BP mapping leads to:

  • PO creation failure
  • Invoice mismatch
  • Payment errors

BP is the entry point for all transactions

Validation

→ BP_Validation

Critical checks:

  1. Duplicate BPs
  2. Missing roles
  3. Incorrect role assignment
  4. Invalid number mapping
  5. Missing mandatory fields

Common Issues

→ BP_Issues

Typical failures:

1. Duplicate Business Partners

Cause:

  • Poor deduplication logic

Impact:

  • Split transactions
  • Reporting inconsistency

2. Missing Roles

Cause:

  • Incomplete mapping

Impact:

  • Transactions fail (e.g., cannot create PO)

3. Incorrect Entity Merging

Cause:

  • Aggressive deduplication

Impact:

  • Different companies merged incorrectly

4. Number Mapping Issues

Cause:

  • Inconsistent number ranges

Impact:

  • Integration failures

5. Data Loss During Transformation

Cause:

  • Fields not mapped

Impact:

  • Missing business-critical data

Anti-Patterns (Do NOT do this)

❌ Map Vendor → Vendor
❌ Map Customer → Customer
❌ Create separate BPs for each

This recreates ECC inside S/4.
Which defeats the entire purpose.

Key Takeaway

Business Partner mapping is NOT:

→ Data migration

It is:

→ Identity resolution + role assignment

If this is wrong:

  • Every module breaks
  • Every report lies
  • Every reconciliation fails

Backlinks