The screen layout of the business transaction processing is affected by the following parameters:

• Object type of the business transaction
• User interface method
• Business transaction type
• Object type of the business transaction item
• Item transaction type

The subscreens that can be used within the business transaction processing are divided among different function groups. For this reason when you access the screen sequence control, you must determine not only the numbers of the subscreens, but also the program name of the respective function group.

When the business transaction processing is started, the system first selects the object type of the business transaction from the business transaction type.

The user interface method distinguishes the various ways of processing a transaction, and is specified by the business transaction.

These two parameters (object type of the business transaction and user interface method) establish from which function group the screens and subscreens come that can be used within the transaction. From this it follows that business transactions of a business transaction type can be defined by means of various screens or screen sequences. For example you should also be able to process a transaction that has been entered in telesales in the general transaction processing

You can enter transactions for the object type of the business transaction. The significance of these transactions for business management varies (for example service order and service notification). In order to be able to influence the screen layout of these transactions, the transaction type is used as an essential selection parameter in the screen sequence control.

If, during the processing of a business transaction with several items, a function is triggered for one of the items (for example the display of the detailed data in the item overview), then the resulting screen layout is also affected by the item transaction type:

• In a transaction with sales and service items, there will be item detail subscreens that have the same business function (for example billing) but differ in terms of screen layout (for example resource-related billing only in the case of service items).
• However, there will also be position detail subscreens that occur only for items of certain applications (for example reference object/subject only in the case of service items).

It is only necessary the first time you call up a transaction to determine a complete record of screen control data from the screen sequence control. Many of the functions triggered during the transaction do not however change the entire screen layout, but only individual elements (subscreens, tabstrip assignments). For this reason the screen sequence control allows you to compare the previous screen control data with screen control data that has just been selected for a function code. This allows the number of data records to be reduced. If the same function is triggered at different points in the program flow, only one record of screen control data has to be created for the function code.

If several subscreens are collected in a tabstrip control , only one of these subscreens is visible, depending on the tabstrip selected. Using the screen sequence control you can set,

• which tabstrips on a tabstrip control are active
• which of the tabstrips is active when the tabstrip control is called up for the first time (default tabstrip)
• which function code is assigned to which tabstrip
• which subscreen is assigned to which tabstrip (and thus also to which function code)