Quartz 4

Business_Partner

2 min read

Business Partner

What is this?

A Business Partner (BP) is the central master entity in SAP S/4HANA that represents any party the company does business with.

This includes:

  • Suppliers (Vendors)
  • Customers
  • Organizations
  • Individuals

In S/4HANA, this is the single master record used across all processes.

Why it exists?

SAP replaced separate Customer and Vendor records with Business Partner to:

  • Eliminate duplicate data
  • Centralize master data
  • Enable cross-process consistency

In older systems:

  • Same company could exist as Vendor + Customer (duplicate)

In S/4HANA:

  • One BP → multiple roles

This reduces redundancy and improves data integrity. :contentReference[oaicite:0]{index=0}

Structure

A Business Partner has three key components:

1. Category (What type of entity?)

  • Person
  • Organization
  • Group

This determines what fields exist (e.g., first name vs company name). :contentReference[oaicite:1]{index=1}

2. Roles (What does it do?)

A BP can take multiple roles depending on business context:

Examples:

  • Supplier (Procurement)
  • Customer (Sales)
  • FI Vendor (Finance)

Important:

BP ≠ Supplier
BP + Role = Supplier

Roles define which data is active in a given process. :contentReference[oaicite:2]{index=2}

3. General vs Role-Specific Data

General Data (shared)

  • Name
  • Address
  • Contact details
  • Bank info

Role-Specific Data

  • Payment terms (FI)
  • Purchasing data (MM)
  • Sales data (SD)

General data is created once and reused across roles. :contentReference[oaicite:3]{index=3}

In Oracle

Typical representation:

  • Supplier tables (e.g., AP_SUPPLIERS)
  • Customer tables (AR_CUSTOMERS)
  • Separate master records
  • Duplicate entities across modules

Key characteristic: → Same real-world entity stored multiple times

In S/4HANA

  • Single BP record
  • Extended via roles
  • Used across:
    • Finance (FI)
    • Procurement (MM)
    • Sales (SD)

BP is the mandatory entry point for customer/vendor data in S/4HANA. :contentReference[oaicite:4]{index=4}

Mapping Logic

→ BP_Mapping

Core idea:

  • Multiple Oracle entities → One BP
  • Then assign roles

Example:

  • Oracle Supplier → BP (Supplier Role)
  • Oracle Customer → BP (Customer Role)
  • Same entity → single BP with both roles

Process Impact

Used in:

  • Procure-to-Pay (Supplier role)
  • Order-to-Cash (Customer role)
  • Record-to-Report (FI integration)

Without correct BP: → No transactions can run

Validation

→ BP_Validation

Key checks:

  • Duplicate detection
  • Role assignment correctness
  • Mandatory fields per role
  • Number consistency

Common Issues

→ BP_Issues

Typical failures:

  1. Duplicate BP creation
  2. Missing role assignment
  3. Incorrect grouping / number range
  4. Vendor ≠ BP confusion
  5. Data split across multiple BPs

Key Takeaway

You are NOT migrating:

  • Vendor → Vendor
  • Customer → Customer

You are transforming:

→ Multiple fragmented identities
→ One unified Business Partner

If this is wrong: Everything downstream breaks.

Backlinks