The actual interface between the infotypeand the user.
This screen provides the user with the following functions:
Create Data Records
Display Data Records
Edit data records
Screen 2000 is usually used for the single screen. However, you can choose to use a different screen as a single screen. Screen
2000
of module pool
MPMMMM00
is used as a model for the single screen.
You can create your own single screens for infotypes included in the standard system. Customer-specific single screens are assigned to the name range 2900 to 2999 .
The values of the
Organizational Assignment
infotype (0001) that are valid at the beginning of the record’s validity period, as well as the entries in the tables listed below that are valid in structure PSYST, enable you to carry out infotype-specific entry checks.
Personnel area / subarea (T001P)
Currency of the public sector (T500C)
Personnel area (T500P)
Employee Group/Subgroup(T503)
This means that the system does not need to read the tables cited above. It is sufficient to include the tables in the TABLES statement.
Caution
Do not use the values in structures
P0001
or
P0002
. These structures are used internally and are not always initialized.
The system displays possible entries for all of the fields whose entry is checked against a table.
If you assign a check table that can be checked automatically to a field within the ABAP Dictionary, the system displays possible entries automatically.
The first six lines of the initial screen are the same for all infotypes:
Line number |
Use |
---|---|
1 to 3 |
Include screen for header lines with data such as the personnel number |
4 |
Empty line |
5 |
FROM date, TO date, lock field, text field, the last person to make a change, and the date on which the last change was made |
6 |
Empty line |
Infotype-specific fields are included in lines 7 to 21.
The infotypes in the standard system then contain an include screen for customer enhancements.
All of the screen fields must be included in one frame. The screen field that contains the subtype assigned to the infotype, however, may appear above the first frame.
You can include a tabstrip controlon the single screen. Note the following dependencies:
You must include three modules in the flow logic of the tab strip control subscreen. The modules are in the include MPPERS00.
The
modify_subscreen
module must be included as the first module of the PBO.
The
hidden_data_subscreen
module must be the last module included in the PBO.
The
input_status_subscreen
must be included as the first module of the PAI. The module is called up in the same way as the
input_status
module on the single screen: all fields that may be maintained must be included in a CHAIN statement.
Example
process before output.
MODULE modify_subscreen.
* ... Subscreen specific PBO Module ...
MODULE hidden_data_subscreen.
process after input.
chain.
field: ... all maintainable fields ...
module input_status_subscreen on chain-request.
endchain.
* ... Subscreen specific PAI Module ...
The function codes for the buttons on the tabstrip control must be the same type as the function codes of a P button (local GUI function, function code is processed directly from GUI). That way a PAI is not triggered when scrolling. If this is not possible because validations are to take place when scrolling between the different screens, a new PBO must be triggered on the single screen before the last module,
post_input_checks
is executed.
Otherwise the
fcode
function code field is deleted in the
post_input_checks
module.