SAP MDG · DATA MODEL UI
How do I implement an MDG FPM feeder class for a Form or List UIBB with custom GET_DEFINITION, GET_DATA, PROCESS_EVENT, and OVS behavior?
Extend the SAP standard MDG feeder class, redefine only the required GUIBB methods, keep `super->` calls, add static field/action metadata in `GET_DEFINITION`, runtime field/action usage in `GET_DATA`, user-triggered logic in `PROCESS_EVENT`, and configure OVS in the feeder and component configuration.
Extend the SAP standard MDG feeder class, redefine only the required GUIBB methods, keep `super->` calls, add static field/action metadata in `GET_DEFINITION`, runtime field/action usage in `GET_DATA`, user-triggered logic in `PROCESS_EVENT`, and configure OVS in the feeder and component configuration.
MDG single-object and multi-record UIs are FPM applications built from GUIBBs, and each GUIBB gets behavior from a feeder class. The standard pattern is to subclass the SAP feeder and redefine only the methods you need, while preserving the parent logic with `super->`.
Process flow
- 1. Identify the GUIBB type: Form, List, Search, QuickView, or OVS.
- 2. Copy or subclass the SAP standard feeder class for that UIBB.
- 3. Redefine only the required interface methods and keep `super->...` calls.
- 4. In `GET_DEFINITION`, add field catalog changes, field descriptions, actions, and OVS links.
- 5. In `GET_DATA`, fill data and update field or action usage; set the corresponding change flags.
- 6. In `PROCESS_EVENT`, handle custom event IDs, validations, messages, and roundtrip actions.
- 7. For OVS, implement phase 0 configuration and phases 1 to 3 for search and selection flow.
- 8. Assign the feeder class in the FPM component configuration for the UIBB and register it in the MDG UI model.
SE24Class Builder > Display/Change feeder class > redefine `IF_FPM_GUIBB_*` methods and syntax-check the exact method signatures
Create and adjust the feeder subclass and verify the interface method signatures in your release.
Web Dynpro component configuration > UIBB Configuration > assign the feeder class
Bind a Form GUIBB to the custom feeder class.
Web Dynpro component configuration > UIBB Configuration > assign the feeder class
Bind a List GUIBB to the custom feeder class.
Referenced tables
| Object | Purpose |
|---|---|
fpmgb_s_actiondef | Row type used when adding custom UI actions in `GET_DEFINITION`. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How do I extend the standard MDG feeder class instead of building a feeder from scratch?
- How do I add custom actions, field usage, and value help in an MDG FPM feeder?
- How do I wire a custom feeder class to an MDG UIBB and keep standard behavior with super calls?
Possible questions
- What is the difference between GET_DEFINITION, GET_DATA, and PROCESS_EVENT in an MDG feeder?
- How do I attach an OVS to a field in an MDG feeder?
- Which FPM GUIBB interface does a Form feeder implement?
- Where is a feeder class assigned in the FPM component configuration?
- How do I refresh field or action usage after changing data in GET_DATA?