· System ® User profile ® Hold data
Hold data allows users to retain values that they have entered on a screen so that they appear the next time they start the same transaction. Only values actually entered by the user are retained. These values are again set as default values in the corresponding input fields every time the screen is reprocessed. In this process, the values transported from the ABAP program at PBO are overwritten.
· System ® User profile ® Set data
This has the same effect as Hold data. Additionally, when the held data is placed in the screen fields, these fields are no longer ready for input.
· System ® User profile ® Delete data
This deletes the held data, and makes the relevant fields on the screen ready for input again.
If Hold data is not activated in the screen attributes, the above menu entries have no effect.
In the PBO event of a screen, you can overwrite the Hold data attribute dynamically using the statement:
SET HOLD DATA ON|OFF.
. The ON addition activates the attribute, OFFdeactivates it.
DATA field(10) TYPE c.
CALL SCREEN 100.
field = 'XXXXXXXXXX'.
CALL SCREEN 100.
MODULE hold_data OUTPUT.
SET HOLD DATA ON.
The statically-defined next screen for screen 100 is 0, and it contains a single input/output field called field.
The flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
In the PBO event, the Hold data attribute is activated dynamically. If the user enters a value and then chooses System ® User profile ® Hold data or Set data, the same value is displayed in the field when the screen is next displayed. This value is displayed each time the screen is called until the user chooses Delete data. This overwrites any value assigned to the field field in the ABAP program.