SAP MDG · DATA MODEL UI
How do I develop node extensions for Business Partner in SAP MDG cloud-ready RAP?
Develop the node extension in this order: extend the CMP data model first, then create the process and governance CDS views, extend the standard RAP BOs, implement the required MDG classes/behavior, and finally expose the node through service definition and metadata extensions.
Develop the node extension in this order: extend the CMP data model first, then create the process and governance CDS views, extend the standard RAP BOs, implement the required MDG classes/behavior, and finally expose the node through service definition and metadata extensions.
Developing a Business Partner node extension in SAP MDG cloud-ready mode follows the standard RAP extension flow: extend the CMP data model first, generate DDIC artifacts, and then build the inactive process and governance CDS views that will be inserted into the existing Business Partner composition tree. After that, extend `I_BusinessPartnerProcessTP`, `I_BusinessPartnerGovTP`, `C_BusinessPartnerProcessTP`, and `C_BusinessPartnerGovTP`, implement the needed behavior and MDG application classes, and expose the node through service and metadata extensions.
Process flow
- Extend the CMP data model first and generate the required DDIC artifacts.
- Confirm the target RAP BO is managed and the original BO is extensible.
- Create the inactive process base CDS over the process table (`zzzfinorgdata_pr`).
- Create the inactive process node view and add to-parent, KPI, and message associations.
- Create the process record-change views and the inactive projection view.
- Create the governance base CDS as a union of active and inactive data.
- Create the governance interface and projection views and attach them to the composition tree.
- Extend `C_MDChgProcBusPartDetailsTP` for the node section in the mass-edit UI and add the needed metadata extension annotations to `I_BusinessPartnerProcessTP`, `I_BusinessPartnerGovTP`, `C_BusinessPartnerProcessTP`, and `C_BusinessPartnerГ
MDCIMGMaster Data Governance, Consolidation and Mass Processing -> Configure Process Models and Field Properties -> Specify Table and Field Properties
Configure process and governance feature control for the extension node and related field properties.
Referenced tables
| Object | Purpose |
|---|---|
I_BPProcessKPIRecordType | Interface association used to identify new, updated, or deleted records in the process UI. |
I_MDChgProcRecordMessages | Interface association used to identify record-level messages in the process UI. |
zzzfinorgdata_pr | Example inactive process table used as the base CDS for the extension node. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What are the prerequisites for BP node extension?
- Can node extensibility be used with unmanaged BOs?
- What must be extensible before creating a BDEF extension?
Possible questions
- What is node extensibility?
- What are the high-level steps to add a node to an SAP-delivered RAP BO?
- Which areas must be extended for an MDG BP node?
- How do I create the base CDS for the process node?
- Which table should the inactive base view use?
- What does inactive mean in this guide?
- How do I add the extension node to the process composition hierarchy?
- Which associations are needed for process UI filtering?
- What is ZI_BusinessPartnerFinOrgProcTP?