SAP MDG · CONSOLIDATION
How do I add a custom field to Business Partner/Supplier/Customer in MDG Consolidation and Mass Processing?
Use this guide to extend the Business Partner data model for MDG Consolidation and Mass Processing with a new field such as Supplier `LICENSE`. The example is for Process Model `147` and applies from MDG 8.0 / SAP S/4HANA 1610.
Use this guide to extend the Business Partner data model for MDG Consolidation and Mass Processing with a new field such as Supplier `LICENSE`. The example is for Process Model `147` and applies from MDG 8.0 / SAP S/4HANA 1610.
This guide shows how to add a new field to the Business Partner data model for MDG Consolidation and Mass Processing. The documented example is Supplier field `LICENSE` in `LFA1`, applicable from MDG 8.0 and SAP S/4HANA 1610. The field is carried through source, process, and result tables and can be written back to active data and MDG Change Requests.
If the BP model was extended with customizing includes such as `INCL_EEW_BUT000`, those fields are already included in MDG Consolidation tables and do not need a separate consolidation model extension. For the supplier/customer scenario, SAP recommends completing the prerequisite guide `How-To: Extend MDG-S / MDG-C data model by a new custom-defined field (reuse option)` first.
Process flow
- Complete the prerequisite guide `How-To: Extend MDG-S / MDG-C data model by a new custom-defined field (reuse option)`.
- Extend table `LFA1` with append structure `ZLFA1_APPEND` containing `LICENSE` typed with data element `ZLICENSE` (`CHAR10`).
- In `MDCIMG`, open `Specify Process Model` and choose Business Object Type `147` — Business Partner.
- Open `Resultant Artifacts`, assign the package, and verify unique Source Append Name and Process Append Name.
- If the Customer Append Name is 30 characters, shorten it by four characters and add `_SRC` / `_PRC` as described.
- Select the `LFA1` append row and choose `Apply Selected Templates & Appends`.
- If the field uses a LOB-related type, create/redefine `ZCL_MDC_DATA_BP` inheriting from `CL_MDC_DATA_BP` and redefine `IF_MDC_DATA~CONTAINS_LOB_DATA` to return `abap_true` for the affected table(s).
- Extend `VMDS_EI_VMD_CENTRAL_DATA` and `VMDS_EI_VMD_CENTRAL_DATA_XFLAG` with `ZLFA1_APPEND`. Use the prerequisite guide for staging and SMT details (`SUPPL_BP_VENGEN_2API` and `SUPPL_BP_VENGEN_2STA`).
MDCIMGConsolidation > Specify Process Model
Open the Process Model maintenance for Business Object Type `147` — Business Partner and generate Resultant Artifacts.
Referenced tables
| Object | Purpose |
|---|---|
LFA1 | Active supplier database table extended in the example with the custom field `LICENSE` via append structure `ZLFA1_APPEND`. |
VMDS_EI_VMD_CENTRAL_DATA | Supplier API structure that must be extended with `ZLFA1_APPEND` for the field to flow into the API layer. |
VMDS_EI_VMD_CENTRAL_DATA_XFLAG | Change-flag structure that must be extended with `ZLFA1_APPEND`. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is this guide about?
- How do I add a custom field to Business Partner/Supplier/Customer in MDG Consolidation?
- Which releases are applicable?
Possible questions
- Which table is extended in the example?
- Which append structure is used?
- What type is LICENSE?
- Do Customizing includes require a separate Consolidation model extension?
- What happens to INCL_EEW_BUT000 fields?
- Which guide should I complete first?
- What is the prerequisite for Supplier/Customer field extension?
- Can Matching process the custom field?
- Where does the new field flow during consolidation?