Atlas Diagnostic

SAP ALE distribution model diagnostics

A first-pass structure for finding why master data is not distributed, arrives at the wrong target, or creates duplicate objects.

Reviewed

Core idea

ALE distribution models decide which master data changes go to which target systems. A missing object usually means the model did not select it, the change pointer was not processed, or the target did not accept it. Duplicates usually mean key mapping is missing or wrong. The diagnostic job is to follow the selection chain: model → change pointer → IDoc → target.

Common symptoms

  • Master data change in source system is not reflected in target system.
  • Change pointer exists but no IDoc was generated.
  • IDoc was sent to wrong target system or multiple systems unexpectedly.
  • Target system creates duplicate master data objects instead of updating existing ones.
  • Distribution model shows active but no messages for the object type.

Likely causes

  • Missing distribution model entry: the object type or message type is not included in the active distribution model.
  • Change pointer not created: change documents were not written or the change pointer job (BD21) did not process them.
  • Filter object mismatch: the filter object excludes the specific plant, company code, or sales organization from distribution.
  • Partner profile issue: the receiver partner profile does not support the message type or the outbound parameter is missing.
  • Target system key mapping: the target system does not recognize the source key and creates a new object instead of updating.

Where to check in SAP

  • BD64 — distribution model display.
  • BD22 — change pointer overview.
  • BD21 — change pointer processing log.
  • WE20 — partner profile outbound parameters.
  • WE02 — generated IDocs for the message type.

Key tables / transactions / objects

  • BDCP / BDCPS — change pointers.
  • EDIDC / EDIDS — IDoc control and status.
  • TBD22 / TBD23 — distribution model tables.
  • TBDBE — filter objects.

Diagnostic workflow

  1. Identify the master data object, message type, source system, and expected target system.
  2. Check BD64 for the distribution model: is the object/message type included and active?
  3. Check BD22 for change pointers: was a change pointer created for the object change?
  4. Run or check BD21 to see if change pointers were processed into IDocs.
  5. Check WE20 for the receiver partner profile: does it have the outbound parameter for this message type?
  6. Check WE02 for generated IDocs and their status.
  7. On the target system, check if the IDoc was received and whether it created or updated the object.

Typical fixes or next actions

  • Add the missing object type or message type to the distribution model.
  • Process change pointers with BD21 if they were not automatically processed.
  • Adjust filter objects if the distribution scope is too narrow.
  • Update the partner profile to include the missing outbound parameter.
  • Fix key mapping on the target system if duplicates are being created.

What to capture first

Before routing the issue, capture: object type, message type, source and target systems, change document number, distribution model name, and whether the issue is new or recurring. This distinguishes a one-time filter miss from a model gap that will keep producing failures.

Boundaries and non-goals

This page is a diagnostic frame, not an ALE configuration guide. It does not cover distribution model design, filter object setup, or target system key mapping configuration. It does not replace SAP's ALE documentation.

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

Related Atlas Pages