In order to add the Form GUIBB to your OVP configuration, proceed as follows:
In the Hierarchy on the left, in the element list, choose the ContentArea
MAIN_SCREEN
, then select .
The system adds a new Form UIBB.
Enter a new configuration name, for example ZYEC_CC_FORM_REPORTING
.
Choose the View type, General.
Enter 1 in the sequence index, so that the Document Display is located below the form GUIBB in this example).
Choose Save
.
Choose Configure UIBB
.
With forward navigation, you are now creating your own component configuration for the Form UIBB.
On the next screen, the system will point out the configuration does not yet exist, therefore choose Create
.
A dialog box is displayed.
In this dialog box, enter description and package.
A new dialog box is displayed.
In this new dialog box, choose Cancel
.
Note
This is because our feeder class has no parameters.
In the next dialog box that is displayed, enter your feeder class.
Note
If you cannot find your class, check that it is active and that it inherits the correct super class, for example the super class AC_HRGRT_REPORTING_FORM_FEEDER
in the case of a Form GUIBB.
Once you have entered the class, choose Edit parameters
(although you do not have parameters in this example).
A new dialog box is displayed.
In this dialog box, confirm with OK
.
Choose Save
.
Note
At this stage, you can see how your screen will finally look. In the following steps, see how to configure the Form GUIBB by arranging the fields on the screen (from the field catalogue provided by the feeder class).
Choose Add Group
.
Enter a name, for example General Data in the Text field, and choose Configure Group
.
A dialog box is displayed.
In this dialog box, choose the fields BRUTT
and DATUM
to go in this group, and then choose OK
.
Select the element (1)
in the hierarchy, enter an appropriate name for the field in Text
field, for example, Gross Remuneration for BRUTT
and Date for DATUM
.
Choose Save
.
Note
The fields you select come from the field catalogue you defined in Method GET_DEFINITION
. The texts you can enter here are override texts for the DDIC texts. Depending
on the status of texts in your back end system, and if you set the attributes of your field catalogue (in GET_DEFINITION
) to use DDIC labels, the system will give the DDIC default values. Try to use the DDIC default values as it makes for easier content recognition by the
user.