SAP MDG · COMMUNITY
How do I extend Business Partner/Supplier/Customer fields in MDG Consolidation and Mass Processing?
Use the MDG Consolidation and Mass Processing field-extension guide to add a new Business Partner field. The example uses Supplier field LICENSE in LFA1, is applicable from MDG 8.0 and SAP S/4HANA 1610, and flows through source, process, and result tables before activation and, with the prerequisite MDG-S/MDG-C extension, into Change Requests.
Use the MDG Consolidation and Mass Processing field-extension guide to add a new Business Partner field. The example uses Supplier field LICENSE in LFA1, is applicable from MDG 8.0 and SAP S/4HANA 1610, and flows through source, process, and result tables before activation and, with the prerequisite MDG-S/MDG-C extension, into Change Requests.
Use this guide 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, and the field is carried through source, process, and result tables before being written to the active database table.
Process flow
- Complete the prerequisite How-To: Extend MDG-S / MDG-C data model by a new custom-defined field (reuse option).
- Create data element ZLICENSE with type CHAR10.
- Create structure ZLFA1_APPEND and add field ZLICENSE typed with ZLICENSE.
- Enhance table LFA1 with append structure ZLFA1_APPEND and activate the DDIC change.
- Start MDCIMG and open Specify Process Model.
- Select Business Object Type 147 — Business Partner.
- Choose Resultant Artifacts and select the package for the generated objects.
- Verify Source Append Name and Process Append Name are unique; if the customer append name is 30 characters, delete the last four characters and add _SRC / _PRC as needed for uniqueness. Select the LFA1 row and choose Apply Selected Templat
MDCIMGSpecify Process Model
Open the Business Partner process model and generate Consolidation resultant artifacts for the new field.
Referenced tables
| Object | Purpose |
|---|---|
LFA1 | ERP Supplier active table extended in the example. |
VMDS_EI_VMD_CENTRAL_DATA | Supplier API data structure that must carry the new field for the prerequisite Change Request integration steps. |
VMDS_EI_VMD_CENTRAL_DATA_XFLAG | Supplier API XFLAG structure that must carry the change indicator for the new field. |
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
- 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?
- What is the example custom field?
- Where is LICENSE added?
- Can Matching process the custom field?
- Where does the new field flow during consolidation?
- Which table is extended in the example?