SAP MDG · REPLICATION OUTBOUND
How do I implement the MDG BP bulk replication outbound BAdI to enrich the proxy payload?
Implement IF_MDG_SE_BP_BULK_REPLRQ_OUT as an outbound payload enrichment step: read the current BP data from the MDG model, map standard and custom fields into the proxy output structure, append extension rows where needed, and apply target- or country-specific adjustments before returning the message.
Implement IF_MDG_SE_BP_BULK_REPLRQ_OUT as an outbound payload enrichment step: read the current BP data from the MDG model, map standard and custom fields into the proxy output structure, append extension rows where needed, and apply target- or country-specific adjustments before returning the message.
`IF_MDG_SE_BP_BULK_REPLRQ_OUT` is the outbound proxy BAdI for Business Partner bulk replication request generation. The documented implementation pattern reads the outbound proxy structure, loads active BP data from the MDG model, maps standard and custom fields, and then applies country- or target-specific rules before the payload is returned to the framework.
Process flow
- Identify whether the outbound scenario is customer-facing or supplier-facing.
- Read the outbound proxy structure supplied by the framework.
- Load the active BP data from the MDG model.
- Map standard fields and custom append fields into the proxy structure.
- Read dependent data such as sales area, company code, procurement, address, or extension data if required.
- Apply country-specific or target-system-specific rules.
- Return the enriched proxy structure to the framework.
ILLUSTRATIVE ABAP SAMPLE
Source ABAP example: MAP_CUSTOMER_CUSTOM_FIELDS.abap
Exact relevant implementation excerpt from the knowledge document set.
1"Generic skill: map customer extension fields into the outbound BP bulk proxy.
2"Use this pattern when copying central customer data, sales-area data, and customer append structures.
3
4out-business_partner-customer-zzmdgproxy_apprlevel = in-customer-central_data-central-data-zzapprlevel.
5out-business_partner-customer-zzmdgproxy_bpmappstat = in-customer-central_data-central-data-zzbpmappstat.
6out-business_partner-customer-zzmdgproxy_ind_bus_code = in-customer-central_data-central-data-zzwwibc.
7
8IF in-customer-header-object_instance-kunnr IS NOT INITIAL.
9 SELECT *
10 INTO TABLE @DATA(lt_knvv)
11 FROM knvv
12 FOR ALL ENTRIES IN @out-business_partner-customer-sales_arrangement
13 WHERE kunnr EQ @in-customer-header-object_instance-kunnr.
14ENDIF.The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How does IF_MDG_SE_BP_BULK_REPLRQ_OUT work?
- What is the implementation pattern for MDG_SE_BP_BULK_REPLRQ_OUT?
- How do I map custom BP fields in the outbound bulk replication request?
Possible questions
- How do I add custom customer fields to the MDG BP outbound payload?
- How do I enrich the supplier outbound proxy in MDG?
- Which data do I read before filling the outbound BP proxy structure?
- How do I handle country-specific logic in outbound BP replication?
- How do I suppress or rewrite outbound values before sending?