SAP MDG: UI Modelling - Part 01

---

Introduction

Each of these applications can be enhanced to meet custom requirements.

The enhancement options are made using the Floorplan Manager framework. Floorplan Manager leverages the active SAP MDG data model to get the field properties for the Floorplan Manager UI field catalog.

This is enabled using application specific abstraction layers such as the Business Object Layer (BOL) & Generic Interaction Layer (GenIL) frameworks.

The GenIL framework helps abstract the complex data management logic and provides a structure based on the defined data model and the assigned classes.

The standard domains have standard classes for search, dynamic query, hierarchy list, and so on. These are created after the data model is activated and data structures are generated.

---

Transactions

GENIL_MODEL_BROWSER - dynamic GenIL objects
GENIL_BOL_BROWSER - test queries

---

Data Models - As Part of Genil Model

The material UI leverages a different integration framework and is discussed in detail in This Blog (Click Here).

The BOL and GenIL contents are generated, nevertheless. The BOL/GenIL contents contain entity names, attributes, and relations mapped to root objects, structures, dependent objects, and associated object classes and methods. These provide a uniform interface for the integration between the application layer and presentation layer.

Data objects based on the BP data model, finance data model (0G) and custom objects leverage the GenIL framework. The GenIL data models are dynamically generated by its implementation class on the activation of the data model. Discussed more detail about BP, Customer & Supplier - Blog (Click Here).

---

Mapping to Data Model Structure

• Type 1 entity is generated as a root object.

• Type 4 entity is generated as a dependent object.

• Relationships are generated as GenIL relations.

• Additional queries and query result objects are generated to search on the type 1 entity.

• A dependent object is generated to support the text processing capabilities if the type 1 entity supports multilingual descriptions.

• Two dependent objects are generated to support the type 1 attachments: one for attachment processing, and another for handling popups.

• The entity attributes and related structures are transferred to the GenIL key and attribute structures.

---

UIBB | FPM | Feeder Class | SAP MDG APIs

Each FPM application has the field layout and the associated ABAP class to contain the processing logic. The main ABAP class associated with the UIBB is called the feeder class. The feeder class logic helps in dynamically modifying or enhancing the field layout and field properties.

With the help of SAP MDG (APIs), you can retrieve the metadata information of the CR as well as the data model to make complex enhancements.

Each UIBB can have its feeder class and the main entity. The feeder class inherits from the main class provided as part of SAP delivery.

---

Credits: SAP Press.

Thanks,
Suggu Sandeep.