Screen variants are called:
The field values and attributes stored for a screen are technically saved in the screen variant. When a transaction variant is processed (see
This technique allows you to set different field values and attributes for a screen according to the current context.
When is it helpful to call screen variants using a program?
Transaction A and transaction B have the same initial screen. However, the subsequent screens of these two transactions differ from one another. Screen variant A or B can be set for the initial screen depending on whether transaction A or B is being processed. By calling the appropriate screen variant with a program, you avoid having to create two different transaction variants.
Screen variants can also be created for subscreens. This allows you to send the same subscreen with different values and attributes.
You can adopt table control layout guidelines in screen variants (see
Function module RS_HDSYS_GET_SC_VARIANT checks if a screen variant is active for the current screen and returns with the variant's name and current values.