In this step you create your own feeder class, based on one of the following super classes provided by FPM:
AC_HRGRT_REPORTING_FORM_FEEDER
Use this super class if your reporting scenario requires the end user to make entries in a set of fields.
AC_HRGRT_REPORTING_LIST_FEEDER
Use this super class if your scenario requires the end user to choose an entry from a list or table (e.g. payroll results, tax form).
These super classes already contain the FPM interfaces and implement the generic international code, so you do not need to implement each method provided by the interfaces. You must only redefine those interface methods that you need to implement. You do this in the following step, Step 3: Complete the Methods of Your Feeder Class.
Note
For some country-specific reports, you may find the international implementation of an FPM interface method is entirely sufficient, so that you need do nothing. In many reporting scenarios, you will need only to redefine the bare minimum GET_DEFINITON
and GET_DATA
methods.
In this example implementation of a simple reporting service to be able to configure the UI, you need only to redefine the method GET_DEFINITION
and ensure the two exporting parameters ET_FIELD_CATALOG
and ET_FIELD_DESCRIPTION
are
filled (see also the description under Create the Field Catalogue (Method GET_DEFINITION). This is the essential part, because it provides the fields that you need when you arrange them on the screen. You can
come back and do the other parts of this method and any other methods later.
Proceed as follows:
Create your feeder class in your appropriate package.
Inherit from one of the following super classes:
AC_HRGRT_REPORTING_FORM_FEEDER
or AC_HRGRT_REPORTING_LIST_FEEDER
Save and activate your new class.