Atlas Diagnostic

SAP business partner replication diagnostics

A first-pass structure for finding why a business partner was not replicated, arrived incomplete, or created duplicates in a target system.

Reviewed

Core idea

Business partner replication moves BP master data from a source system to target systems. Most tickets resolve to one of three handoffs: the source did not select the BP, the target did not accept it, or the accepted BP was mapped to the wrong key. The diagnostic job is to find which handoff failed and why.

The fastest way to narrow the issue is to prove the message left the source, then prove the target received it. Everything in between is noise until those two facts are established.

Common symptoms

  • BP created in source system but does not appear in target system after expected replication time.
  • BP appears in target but with missing roles, addresses, or bank details.
  • Target system creates a duplicate BP instead of updating the existing one.
  • Replication shows success in the source but the target BP has different data.
  • Specific BP role (customer, vendor, contact) is missing after replication.

Likely causes

  • Replication model filter: the BP type, role, or organizational unit is excluded from the replication model.
  • Key mapping missing: the source BP GUID or number is not mapped to the target system key, causing a new BP to be created.
  • Data quality block: the BP data fails validation in the target system (missing required field, invalid format, duplicate tax number).
  • Role-specific filter: the replication model sends the BP header but filters out specific roles or relationships.
  • Target system configuration: the target system has different BP grouping, number ranges, or role assignment rules that conflict with the replicated data.

Where to check in SAP

  • MDG Data Replication log (if MDG is the source) — check replication status and error messages.
  • BDCP / BDCPS — change pointers for the BP object.
  • WE02 — IDoc status if ALE is used for replication.
  • Key mapping tables (if custom mapping is used) — check source-to-target key mapping.
  • Target system BP display (FLBP1 / FLBP2) — verify roles, addresses, and assignments.

Key tables / transactions / objects

  • BUT000 / BUT001 — BP header and general data.
  • BUT100 / BUT100 — BP roles.
  • BUT020 / ADRC — BP addresses.
  • BKDF / BNKA — BP bank details.
  • BDCP / BDCPS — change pointers.

Diagnostic workflow

  1. Identify the BP number, source system, target system, and the expected versus actual result.
  2. Check the replication log or change pointer status to confirm the BP was selected for replication.
  3. Check WE02 or the replication middleware for IDoc or message status.
  4. Verify key mapping: does the target system recognize the source BP key or create a new one?
  5. Check the target BP in FLBP1/FLBP2 for missing roles, addresses, or data.
  6. Compare the source BP data with the target BP data to identify which fields were filtered or failed validation.

Typical fixes or next actions

  • Update the replication model to include the missing BP type, role, or organizational unit.
  • Create or correct key mapping between source and target systems.
  • Fix data quality issues in the source BP before replicating.
  • Adjust target system BP grouping or role assignment rules if they conflict with replicated data.
  • If duplicates exist, evaluate merge or deactivation options with master data governance.

What to capture first

Before routing the issue, capture: BP number, source and target systems, expected versus actual result, replication model name, and any error from the replication log or IDoc status. A vague "BP missing" report wastes a round of basic questions; these six items let a support engineer start the real diagnosis.

Escalation signals

  • Replication failures affect many business partners or all target systems.
  • A duplicate BP was created in a target system and needs data steward or business approval to merge.
  • The issue involves key mapping, number ranges, or BP grouping changes that require MDG/ BASIS involvement.
  • Missing bank, tax, or address data has compliance, payment, or reporting impact.

Boundaries and non-goals

This page is a diagnostic frame, not a BP replication configuration guide. It does not cover MDG replication model design, key mapping setup, or BP grouping configuration. It does not replace SAP's master data governance documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.

Related Atlas Pages