SAP MDG · CONSOLIDATION
How do I add a custom table/node to Business Partner consolidation and mass processing in SAP MDG?
Use this guide to add a customer-namespace table to the Business Partner model in MDG Consolidation or Mass Processing. For the supplier-rating example, the custom table is ZSUPPLIER_RATING, the applicable releases are SAP MDG 8.0 or higher and SAP S/4HANA 1610 or higher, and the solution extends consolidation classes, the process model, and Change Request integration.
Use this guide to add a customer-namespace table to the Business Partner model in MDG Consolidation or Mass Processing. For the supplier-rating example, the custom table is ZSUPPLIER_RATING, the applicable releases are SAP MDG 8.0 or higher and SAP S/4HANA 1610 or higher, and the solution extends consolidation classes, the process model, and Change Request integration.
Use this guide to extend the Business Partner data model for MDG Consolidation or MDG Mass Processing with a customer-namespace table. In the supplier-rating example, the new table is ZSUPPLIER_RATING, and the implementation also covers the required model-class changes, process-model setup, and the integration path needed to write activated data into a Change Request...
Process flow
- Use the guide to extend the Business Partner data model for MDG Consolidation or MDG Mass Processing.
- Treat `ZSUPPLIER_RATING` as the supplier-rating example custom table.
- Confirm release scope: SAP MDG 8.0+ or SAP S/4HANA 1610+.
- Extend the consolidation classes, process model, and Change Request integration flow.
- If needed, extend Central Governance before using the Change Request flow.
MDCIMGImplementation Guide for Consolidation and Mass Processing -> Specify Process Model
Open the process-model customizing where Business Object Type `147` and table `ZSUPPLIER_RATING` are maintained.
SE19Create implementation for BAdI Definition `MDG_BS_CUST_SUPP_CR_SI`
Create the Change Request staging integration implementation used for supplier-rating data.
Referenced tables
| Object | Purpose |
|---|---|
ZSUPPLIER_RATING | Custom active table used by the supplier-rating example; activated data is stored here. |
ZSUPPLIER_RA_SRC | Generated source database table for the supplier-rating process model artifacts. |
ZSUPPLIER_RA_PRC | Generated process database table for the supplier-rating process model artifacts. |
LFA1 | Source table used to create the join to `ZSUPPLIER_RATING` in the process model. |
ZSUPP_RAC | MDG entity used in the Change Request staging example. |
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 table/node to Business Partner consolidation?
- Which releases support this extension?
Possible questions
- What is the supplier-rating business scenario?
- Where is custom supplier-rating data stored after activation?
- What must be extended before MDG can process a new table?
- What are the three main extension areas?
- Do I need to extend the Central Governance supplier model?
- Is the MDG-S/MDG-C model extension covered by this guide?
- Which data access class should I create?
- What superclass does ZCL_MDC_DATA_BP inherit from?
- When must TABLE_NAME_BY_TYPE be redefined?