SAP MDG · REPLICATION INBOUND
How do I implement a source-system BP inbound interface utility for SAP MDG business partner replication?
Implement the utility as a static helper class called by the main MDG BP inbound BAdI: persist the source-system reference, resolve the internal BP with key matching, read the interface CR configuration, then enrich the outbound BP structure before governance processing.
Implement the utility as a static helper class called by the main MDG BP inbound BAdI: persist the source-system reference, resolve the internal BP with key matching, read the interface CR configuration, then enrich the outbound BP structure before governance processing.
The documented pattern is a static source-system utility class that the main MDG BP inbound BAdI delegates to. It first saves the source-system-to-BP reference, then checks whether the inbound message already maps to an internal BP number, derives the change request type from interface customizing, and finally enriches the outbound BP structure before handing it to governance.
Process flow
- Implement a static utility class for the source system, following the `*_INTF_UTIL` pattern.
- In `INBOUND_PROCESSING`, clear the exported CR and processed flags.
- Call `save_bp_source` to persist the source-system-to-BP reference in update task.
- Call `get_key_mapping` with the inbound internal ID and sender business system.
- Use the result to determine create vs change.
- Read `ZMDG_C_INTF_CREQ` for the matching `intf_id` and action.
- Call `find_cr` to return `usmd_crequest_type` and `abap_boolean` processed flag.
- Call `enrich_bp` to fill source-specific outbound fields and corresponding X flags.
SE24Class Builder -> open `ZCL_MDG_BP_SF_INTF_UTIL` or your custom `*_INTF_UTIL` class -> check method `INBOUND_PROCESSING`
Verify the exact inbound utility signature and reuse the documented static helper pattern.
Referenced tables
| Object | Purpose |
|---|---|
ZMDG_C_INTF_CREQ | Interface configuration table for deriving the CR type based on interface ID and action. |
ZMDG_C_MDC_SRC | Source-system to BP reference structure used when persisting the source mapping in update task. |
mdg_user_proxy_setting | MDG proxy routing settings table used in the broader inbound processing pattern for persistence and change request routing. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does the BP inbound utility determine create vs change and CR type?
- How do I map an external BP source ID to the internal BP number in MDG inbound processing?
- How do I enrich the outbound BP structure in a custom inbound utility class?
Possible questions
- How do I implement a custom BP inbound utility class in MDG?
- How does the MDG BP inbound service decide the change request type?
- Which tables and classes are used for BP source-system mapping?
- How do I enrich mdg_bs_bp_s_extern during inbound processing?
- What is the pattern for ZCL_MDG_BP_*_INTF_UTIL classes?