SAP MDG · COMMUNITY
How do I add Requesting Business Area as an additional Change Request parameter in SAP MDG?
Add Requesting Business Area as a customer-specific Change Request parameter outside the MDG data model, persist it in ZUSMD_CR_BUSAREA with the Change Request ID, expose it via a dependent GenIL object and a Form UIBB, and use GSBER with value help from TGSB/TGSBT.
Add Requesting Business Area as a customer-specific Change Request parameter outside the MDG data model, persist it in ZUSMD_CR_BUSAREA with the Change Request ID, expose it via a dependent GenIL object and a Form UIBB, and use GSBER with value help from TGSB/TGSBT.
Use a separate Z-table and a dependent GenIL object rather than the MDG master-data model when the field is only controlling the request process. In the source pattern, Requesting Business Area is stored in ZUSMD_CR_BUSAREA, displayed on the Change Request General Data tab, and offered with value help from GSBER/TGSB/TGSBT.
Process flow
- Define Requesting Business Area as a process-control parameter.
- Keep it outside the MDG business data model when it is not master-data context.
- Create DDIC artifacts: structure and table.
- Create transparent table ZUSMD_CR_BUSAREA to store Change Request ID and Business Area.
- Enhance GenIL component CR with dependent object ZCR_REQ_BUSINESS_AREA.
- Implement ZCL_USMD_CR_GIL_ROOT_ENHANCED and register transactional handlers.
- Implement ZCL_CR_GIL_REQ_BUS_AREA for read/write/property logic.
- Create the Form feeder class ZCL_USMD_CR_GUIBB_REQ_BUS_AREA with value help logic for GSBER from TGSB and TGSBT.
Add the Form UIBB to the Change Request General Data tab.
Wire the UIBB to
USMD_CR_MASTERusing CL_FPM_CONNECTOR_BOL_RELATION.
SE11Create structure Z_CR_BUSINESS_AREA / ZCR_BUSINESS_AREA and transparent table ZUSMD_CR_BUSAREA
Define the DDIC field and persistence for the additional Change Request parameter.
SE80Create and activate classes ZCL_USMD_CR_GIL_ROOT_ENHANCED, ZCL_CR_GIL_REQ_BUS_AREA, and ZCL_USMD_CR_GUIBB_REQ_BUS_AREA
Implement the GenIL handlers and the FPM feeder class.
Enhance GenIL component CR with dependent object ZCR_REQ_BUSINESS_AREA and relation ZCR_ReqBusAreaRel
Expose the parameter as a dependent GenIL object in the Change Request model.
Copy FPM_FORM_UIBB_GL2_TEMPLATE to ZUSMD_CR_REQ_BUS_AREA
Create the Form UIBB configuration for Requesting Business Area.
Add the Form Component UIBB to the Change Request General Data tab and wire it to USMD_CR_MASTER using CL_FPM_CONNECTOR_BOL_RELATION
Place the new field in the Change Request UI and connect it to the GenIL model.
Referenced tables
| Object | Purpose |
|---|---|
ZUSMD_CR_BUSAREA | Custom persistence table for Change Request ID and Requesting Business Area. |
TGSB | Business Area customizing table used for value help source values. |
TGSBT | Language-dependent Business Area text table used for value help display text. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I add Requesting Business Area to the MDG Change Request UI?
- How can I add a workflow-control parameter to a change request?
- How do I enhance the CR UIBB with customer-specific data?
Possible questions
- Why isn't Requesting Business Area added to the MDG data model?
- Where does Requesting Business Area get its values?
- Which table contains Business Areas?
- What objects are required for the CR UIBB enhancement?
- Where is Requesting Business Area displayed?