SAP MDG · REPLICATION OUTBOUND
How do I map custom customer fields into the MDG BP bulk replication outbound proxy?
Use the outbound proxy BAdI `IF_MDG_SE_BP_BULK_REPLRQ_OUT` to enrich the BP/customer bulk replication request: read the inbound proxy structure, map custom customer fields from central data and sales-area data, and then return the updated outbound payload.
Use the outbound proxy BAdI `IF_MDG_SE_BP_BULK_REPLRQ_OUT` to enrich the BP/customer bulk replication request: read the inbound proxy structure, map custom customer fields from central data and sales-area data, and then return the updated outbound payload.
Use the outbound proxy BAdI `IF_MDG_SE_BP_BULK_REPLRQ_OUT` to enrich the BP/customer bulk replication request. The documented pattern is to read the inbound proxy structure, map custom customer central fields into the outbound customer node, optionally read dependent sales-area data such as `KNVV`, and then return the updated proxy payload.
Process flow
- Identify the customer custom fields that must be sent in the outbound BP proxy.
- Map central customer fields from `in-customer-central_data-central-data` into the outbound customer node.
- Read dependent sales-area data from `KNVV` when `in-customer-header-object_instance-kunnr` is filled.
- Use the dependent data to enrich sales-arrangement or related outbound extension structures.
- Return the updated outbound proxy structure to the framework.
Referenced tables
| Object | Purpose |
|---|---|
KNVV | Sales area data read during outbound customer payload enrichment. |
ILLUSTRATIVE ABAP SAMPLE
Source ABAP example
Exact relevant implementation excerpt from the knowledge document.
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 do I extend customer outbound payload mapping in IF_MDG_SE_BP_BULK_REPLRQ_OUT?
- How do I copy customer append fields into the BP bulk replication request?
- How do I map KNVV and customer central custom fields in outbound BP replication?
Possible questions
- How do I map custom customer fields into the MDG BP bulk replication outbound proxy?
- Which fields are copied from customer central data and sales-area data in outbound BP bulk replication?
- How do I add a new customer append field to the outbound BP proxy structure?
- How should I read KNVV data when enriching the outbound BP customer payload?
- Which outbound BAdI is used for BP bulk replication request enrichment?