Single Screen 

The single screen of an infotype is the interface between the system and the user. It enables you to

individual infotype 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 .

Entry checks

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 tables T001, T001P, T500P and T503 that are valid in structure PSYST, enable you to carry out infotype-specific entry checks.

This means that the system does not need to read infotype 0001 or the two tables cited above. It is sufficient to include the tables in the TABLES statement.

Do not use the values in structures P0001 or P0002. These structures are used internally and are not always initialized.

Possible entries for screen fields

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 Data Dictionary, the system displays possible entries automatically.

Screen setup

The first six lines of the initial screen are the same for all infotypes:

Line number

Use

1 to 3

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.

Tab Strips on the Single Screen

It is possible to include a tab strip control on the single screen. If you wish to do so, please note the following dependencies:

The flow logic of the tab strip control subscreen contains three modules. 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.

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 tab strip control must be the same type as the function codes of a P button (local GUI function, function code is processed directly from GUI). No PAI will then be triggered by scrolling. If this is not possible, as 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 in the post_input_checks module, the function code field, fcode is deleted.