Hi, I provide training in SAP UI5. Also feel free to checkout my new web page https://saptechblog.com
Webdynpro ABAP

Feeder Class

A feeder class isn’t any special type of class. It is a class that implements any one of the following interface.

·         IF_FPM_GUIBB_FORM(for form components)

·         IF_FPM_GUIBB_FORM_REPEATER(for form repeater components)

·         IF_FPM_GUIBB_LIST(for list components)

·         IF_FPM_GUIBB_SEARCH(for search components)

·         IF_FPM_GUIBB_TREE(for hierarchical list components)

·         IF_FPM_GUIBB_LAUNCHPAD(for Launchpad components)


SAP Help: http://help.sap.com/saphelp_nw70ehp3/helpdata/en/6c/5632d4e79b4003b97c93946ad3aa29/content.htm


A feeder class is required to provide the necessary configuration to build the layout and fill the data in it at runtime.

Feeder classes are usually used in addition with the generic UIBB’s.  There are several generic components created by the SAP for a particular mode of display of data according to UI guidelines. For example to generate a form SAP has created a generic component FPM_FORM_UIBB and to display data in the form of table we have FPM_LIST_UIBB.

Now these are generic components are created with the purpose of reusability and can be used in n no of applications. Taking a Form GUIBB component as an example, this component is designed with the purpose of creating a form according to UI Guidelines. When used in an Employee details applications this form component can be used to generate the form to display employee details where are when used with travel application it can be used to generate the form for travel details. Now from where does the detail to create the form for the FPM_FORM_UIBB component comes from.  The generic component FPM_FORM_GUIBB is designed in a way that it gets the configuration (layout and data) from one place (Feeder class) and using that information the components generate the layout and actions. Thus feeder class is a class which is used to provide the generic components with the information what is the layout to be generated and processing logic for displaying the data.




Irrespective of any type of interface the feeder class implements, say form or list or tree, the implemented interface will contain two important methods.

1.      Get definition: This is the method which is called by the generic components (at design time) to get the information of what is the layout to be generated and what are the actions to be embedded. This method has an Exporting parameter called eo_fieldcatalog which refers to a structure (form) or table type (Table) depending on interface implemented.

We need to provide the object reference of the layout to be created using RTTI services.

2.      Get data: This is another important method of the feeder class which is called at the runtime to get the data to be displayed in the UIBB.


Let’s build and application that makes use of the some of the GUIBBS.


About Arun


Post a Comment

Powered by Blogger.