SAP MDG · DATA MODEL UI
How do I extend the Profit Center entity PCTR in SAP MDG-F data model 0G with additional fields?
To extend Profit Center in MDG-F data model 0G, first analyze the backend field definition and dependencies in SE11, then decide whether the field belongs as a simple attribute on existing entity PCTR or needs a separate model entity. The source shows that PCTR already supports company code assignment and several Joint Venture fields, with value help mappings and replication mappings available for S/4HANA 2025.
To extend Profit Center in MDG-F data model 0G, first analyze the backend field definition and dependencies in SE11, then decide whether the field belongs as a simple attribute on existing entity PCTR or needs a separate model entity. The source shows that PCTR already supports company code assignment and several Joint Venture fields, with value help mappings and replication mappings available for S/4HANA 2025.
Use data model 0G and extend entity PCTR for Profit Center master data. The retrieved source shows the supported PCTR fields and their technical mappings, including Company Code from CEPC_BUKRS and the Joint Venture-related fields VNAME, RECID, ETYPE, JV_OTYPE, JV_JIBCL, and JV_JIBSA. Before modeling any new field, first analyze the backend data element, check table, and dependency logic in SE11 so you can decide whether it can be added as a simple attribute or requires a separate entity.
Process flow
- Identify the backend field and business meaning.
- Check the field definition in SE11: data element, length, type, and check table.
- Decide whether it is a simple PCTR attribute or requires a separate entity.
- Enhance data model 0G for entity PCTR.
- Activate the data model and generate the model-specific structures.
- Extend the relevant PCTR UIBB.
- Add validation logic in
USMD_RULE_SERVICEif required. - Update replication and initial-load mappings if the field must be transferred outward.
MDG-F data model 0G -> entity PCTR
Extend the Profit Center entity with supported attributes or custom fields
Replication mapping for Profit CentreReplicationBulkRequest / PRCMAS
Ensure the new field is transferred to SOAP, IDoc, or replication consumers if required
Referenced tables
| Object | Purpose |
|---|---|
CEPC | Profit Center master data source table referenced by the source mapping |
CEPC_BUKRS | Profit Center to company-code assignment source for PCTR company code mapping |
CSKS | Referenced in the source guide for field-analysis examples on MDG-F extensions |
T001 | Check table for company code field BUKRS |
T8JV | Check table for Joint Venture field VNAME |
T8JJ | Check table for Recovery Indicator field RECID |
T8JG | Check table for Equity Type field ETYPE |
T8J6A | Check table for JIB/JIBE Class field JV_JIBCL |
T8J6C | Check table for JIB/JIBE Subclass A field JV_JIBSA |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I add custom attributes to the PCTR entity in MDG-F 0G?
- Which Profit Center fields are already available in MDG-F 0G?
- How do I analyze backend fields before extending PCTR in MDG?
Possible questions
- What is the process for adding new fields to an existing MDG-F entity?
- Which PCTR attributes are supported for Profit Center replication?
- How do I decide between a simple attribute and a new entity for MDG-F extensions?
- Which standard fields from CEPC / CEPC_BUKRS map to PCTR?
- How do I check check tables and value helps before modeling a new PCTR field?