SAP MDG · COMMUNITY
How do I develop a node extension for Business Partner in SAP MDG Cloud-Ready RAP objects?
Start by extending the CMP data model and generating the needed DDIC artifacts, then extend the delivered RAP Business Partner BOs using CDS view entity extensions, BDEF extensions, behavior implementation, service definition extensions, and metadata extensions. For the process node, build the inactive base CDS on the process table such as `zzzfinorgdata_pr`, then add `_BPFinOrgData` into the `I_BusinessPartnerProcessTP` / `C_BusinessPartnerProcessTP` composition tree and complete the BP governance and MDG application-class extensions.
Start by extending the CMP data model and generating the needed DDIC artifacts, then extend the delivered RAP Business Partner BOs using CDS view entity extensions, BDEF extensions, behavior implementation, service definition extensions, and metadata extensions. For the process node, build the inactive base CDS on the process table such as `zzzfinorgdata_pr`, then add `_BPFinOrgData` into the `I_BusinessPartnerProcessTP` / `C_BusinessPartnerProcessTP` composition tree and complete the BP governance and MDG application-class extensions.
Extend the CMP data model first and generate the required DDIC artifacts. Then extend the delivered RAP BOs for Business Partner using CDS view entity extensions, BDEF extensions, a behavior pool, service definition extensions, and metadata extensions. For the process node, the guide models inactive staging data on `zzzfinorgdata_pr`, builds the node view `ZI_BusinessPartnerFinOrgProcTP`, and attaches it to the process composition tree through `_BPFinOrgData`.
Process flow
- Extend the CMP data model first.
- Generate the required DDIC artifacts after the data model extension.
- Confirm the target BO is implemented as `Managed`.
- Confirm the BDEF header contains `extensible`.
- Confirm the original service definition has `AbapCatalog.extensibility.extensible:true`.
- Create the inactive base CDS view over the process table such as `zzzfinorgdata_pr`.
- Create the inactive process node view `ZI_BusinessPartnerFinOrgProcTP`.
- Add the to-parent association and the associations to `I_BPProcessKPIRecordType` and `I_MDChgProcRecordMessages`.
ABAP Development Tools (ADT) → CDS View Entity Extension
Extend `I_BusinessPartnerProcessTP`, `I_BusinessPartnerGovTP`, `C_BusinessPartnerProcessTP`, and `C_BusinessPartnerGovTP` with the extension-node associations such as `_BPFinOrgData`.
ABAP Development Tools (ADT) → Behavior Definition Extension
Extend the interface and projection BDEFs for the process and governance BOs, including `SaveMassEdit`, draft, lock, authorization, and unmanaged-save settings where required.
ABAP Development Tools (ADT) → Service Definition Extension
Expose the extension-node projection entities in the delivered process and governance services without changing the SAP-delivered originals.
Referenced tables
| Object | Purpose |
|---|---|
zzzfinorgdata_pr | Example process table used for the inactive base CDS view of the Business Partner process 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?