The field catalogue is the structure of fields that are to be visible to the end user, either as entry fields in your form, or as the fields in the table in the case of a list.
Note
When you try to implement a former Web Dynpro for Java application, take a note of the input fields that were there. You should find something you can re-use, or at least append to a new structure you can create especially for your new application. In the following code examples for a FORM and a LIST, existing DDIC structures have been used.
In this method you not only determine DDIC fields (in your structure), but you can also override the fields’ properties, such as length
, mandatory
or not, read only
, etc.
Also here, you can give fixed value lists for each field’s input help.
You must carry out following basic steps in your code. This is principally the same, regardless if it is a LIST or FORM implementation:
Call super method GET_DEFINITION
.
Declare application specific events (so that they are visible in your configuration).
Convert your structure to field catalogue format
Read data for fixed values.
In the following code example for forms, some global tables for the value helps are filled and to aid this, some text variables will be created, for example:
a) V01
Compulsory/Voluntarily Insured
b) V02
Privately Insured
Field by field, adjust properties, set fixed values etc., if necessary.
Also see the following examples for creating the field catalogue: