SAP MDG · REPLICATION OUTBOUND
How do I map supplier custom fields into an MDG BP bulk outbound proxy in SAP?
Use the outbound proxy enhancement pattern: read the active supplier entity data from the MDG model, loop the returned data table, pick the custom field with ASSIGN COMPONENT, and move it into the outbound proxy structure before the request is sent.
Use the outbound proxy enhancement pattern: read the active supplier entity data from the MDG model, loop the returned data table, pick the custom field with ASSIGN COMPONENT, and move it into the outbound proxy structure before the request is sent.
Use the supplier outbound proxy enrichment pattern to read the active MDG supplier entity data, loop the data rows, and move custom append fields into the BP bulk request structure before the message is sent.
In the documented example, entity `BP_VENGEN` is read from the active data buffer, the returned internal table is assigned dynamically, and `ZZAPPRLEV` is copied into the outbound supplier proxy field `out-business_partner-supplier-zmdg_sup_zzapprlevel`. This is the core pattern to reuse for any additional supplier custom fields: identify the source component in the MDG structure, assign it safely, and write it into the outbound proxy output.
Process flow
- Read the active supplier entity data from the MDG model into an internal table such as `lt_active_data`.
- Find the supplier entity row by `usmd_entity_cont = 'BP_VENGEN'`.
- Assign `ls_active_data-r_t_data->*` to a field symbol for safe dynamic access.
- Loop through the assigned supplier rows.
- Use `ASSIGN COMPONENT 'ZZAPPRLEV' OF STRUCTURE <fs_data>` to read the custom append field.
- Move the value into `out-business_partner-supplier-zmdg_sup_zzapprlevel`.
- Repeat the same pattern for any additional supplier custom fields you need to expose in the outbound proxy.
- Return the updated outbound proxy structure to the framework.
Referenced tables
| Object | Purpose |
|---|---|
BP_VENGEN | MDG supplier entity container read from the active data set before mapping custom fields. |
ILLUSTRATIVE ABAP SAMPLE
Source ABAP example
Exact relevant implementation excerpt from the knowledge document.
1"Generic skill: map supplier extension fields into the outbound BP bulk proxy.
2"Use this pattern when copying vendor central data, accounting data, procurement data, and append structures.
3
4READ TABLE lt_active_data INTO DATA(ls_active_data) WITH KEY usmd_entity_cont = 'BP_VENGEN'.
5ASSIGN ls_active_data-r_t_data->* TO FIELD-SYMBOL(<ft_data>).
6IF <ft_data> IS ASSIGNED.
7 LOOP AT <ft_data> ASSIGNING FIELD-SYMBOL(<fs_data>).
8 ASSIGN COMPONENT 'ZZAPPRLEV' OF STRUCTURE <fs_data> TO FIELD-SYMBOL(<fs_zzapprlev>).
9 IF <fs_zzapprlev> IS ASSIGNED.
10 out-business_partner-supplier-zmdg_sup_zzapprlevel = <fs_zzapprlev>.
11 ENDIF.
12 ENDLOOP.
13ENDIF.The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I copy vendor extension fields into the outbound BP bulk proxy?
- How do I fill custom supplier fields in IF_MDG_SE_BP_BULK_REPLRQ_OUT?
- How do I pass supplier append fields to the BP bulk replication request?
Possible questions
- How do I map supplier custom fields into an MDG BP bulk outbound proxy in SAP?
- How do I copy vendor extension fields into the outbound BP bulk proxy?
- How do I fill custom supplier fields in IF_MDG_SE_BP_BULK_REPLRQ_OUT?
- How do I pass supplier append fields to the BP bulk replication request?
- Which source structure should I read for supplier extension fields?
- Which ABAP pattern is used to enrich the outbound proxy with supplier custom fields?