SAP MDG · DATA MODEL UI
How do MDG custom FPM feeder classes work, and which methods do I redefine?
MDG custom FPM feeder classes are usually subclasses of the standard feeder. Redefine GET_DEFINITION for static UI definition, GET_DATA for round-trip data and usage control, PROCESS_EVENT for user actions, and IF_FPM_GUIBB_OVS for value help.
MDG custom FPM feeder classes are usually subclasses of the standard feeder. Redefine GET_DEFINITION for static UI definition, GET_DATA for round-trip data and usage control, PROCESS_EVENT for user actions, and IF_FPM_GUIBB_OVS for value help.
MDG single-object and multi-record maintenance screens are FPM applications built from GUIBBs, and each GUIBB gets data and behavior from a feeder class. In MDG, the usual pattern is to subclass the SAP standard feeder, redefine only the required methods, and keep the standard logic via `super->`.
`GET_DEFINITION` is used to define the static UI content such as field catalog, field descriptions, actions, and OVS wiring. `GET_DATA` runs on every round-trip to fill the UI data and adjust field or action usage, while `PROCESS_EVENT` handles user-triggered events such as custom buttons or validation logic.
Process flow
- Subclass the relevant SAP standard feeder class for your GUIBB type.
- Redefine only the needed methods and keep `super->` behavior.
- In `GET_DEFINITION`, define fields, actions, and OVS linkage.
- In `GET_DATA`, fill data and control field or action usage.
- In `PROCESS_EVENT`, handle custom events, validation, or dialog logic.
- For OVS, implement phase 0 configuration, phase 1 query handling, phase 2 result selection, and phase 3 value transfer.
- Assign the feeder class in the FPM component configuration used by the MDG UI model.
FPM component configuration for the UIBB (for example `FPM_FORM_UIBB` / `FPM_LIST_UIBB`)
Assign the feeder class to the UIBB configuration.
MDG UI model / application configuration for the CR or single-object screen
Expose the copied UIBB configuration in the MDG application.
SE24
Subclass the standard feeder, redefine methods, and syntax-check the interface signatures.
Referenced tables
| Object | Purpose |
|---|---|
fpmgb_s_actiondef | Row type used when adding a custom UI action in `et_action_definition`. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- Which feeder class methods are used in MDG FPM UIBBs?
- How do GET_DEFINITION, GET_DATA, and PROCESS_EVENT work in an MDG feeder class?
- How is OVS implemented in an MDG FPM feeder class?
Possible questions
- Which feeder class should I subclass for a Form or List GUIBB?
- When should I use GET_DEFINITION versus GET_DATA in an MDG feeder?
- How do I attach custom OVS value help to a field?
- How do I wire a feeder class to an FPM UIBB configuration?
- How do I trigger a UI refresh after changing field or action usage?