Screen sequences

The screen sequence defines the order in which screens appear. You can go through the sequence with the Next screen function. Tab strips take you to screens directly.

Up until now, you could only configure screen sequence with the BDT starting with the initial screen. Now you can use menu options to branch into other screen sequences.

Menu path: Control <Object > → < Screen sequence >

Defining Screen Sequences

You can define any number of screen sequences to be distributed later over various screen sequence categories.

Naming convention: <Application><n>The ID for a view should always have 6 places. It should start with the application ID followed by a set of numbers.

Assigning Screen Sequences à Screens

The sequence of screens is defined by the position number. Screen sequences in the main screen sequence category (see Screen Sequence Categories) include the data screens and the initial screen, which always has to be at the beginning of a screen sequence. All other screen sequences consist exclusively of data screens. Naming convention: The naming convention for the position number corresponds to that for the position number in Assign Section → View (see Sections).

Note: Screens on which fields are hidden (by the object part → view assignment or because of a customer field grouping) are automatically skipped over by the BDT in dialog maintenance.

Screen sequence categories

A screen sequence category is a logical place within a dialog flow in which a screen sequence can be processed. The main screen sequence category, whose identification is always SPACE (six blanks), plays a special role. The BDT always starts the dialog flow with the first screen of a screen sequence which is assigned to this category. This is usually the initial screen.

Navigation to other screen sequence categories usually takes place with a GUI function (see Menus ). When defining this function, the screen sequence category is also defined. After the function is selected, the event FCODE is processed and the BDT calls the screen sequence of the defined screen sequence category. If the screen sequence category is not unambiguously assigned to a menu option and for that reason cannot be stored in the definition of this function (for instance if the screen sequence category is decided at run time based on the cursor position), call function module BUS_SCREEN_CALL in event FCODE. The screen sequence category is to be transferred with parameter I_VARTP.

Assigning Screen Sequence Category à Screen Sequences

All valid screen sequences are defined for each screen sequence category, of which one must be indicated as standard.

Screen Sequences for Main Screen Sequence Category: You can assign an unlimited number of screen sequences. The BDT uses the following rules to decide which of the assigned screen sequences will be put into effect:

Standard Screen Sequence for Main Screen Sequence Category: Make sure that this sequence includes all views relevant to the main screen sequence. The reason for this is that the BDT sequence is always used in those cases when no sequence variant has been unambiguously assigned (functions as a catch-all).

Number of Screen Sequences for Main Screen Sequence Category: In many cases, one sequence is enough even for application objects that use divisibility. The BDT automatically skips over screens that contain no input fields for the current dialog. You only need to create more sequences for special object parts if:

Screen Sequences for Other Categories At the moment, only one sequence is to be assigned, which is then marked as standard. The BDT always uses the standard screen sequence for a screen sequence category. In a future Release, it will be possible for the application to determine the screen sequences based on object parts for all screen sequence types.