Show TOC

Field Selection for Multi-Level List Displays of Orders

In this step you maintain the default settings for the multi-level list display of orders.

Here you can configure

Procedure

If you proceed, you will see the standard selection screen with all the fields defined by SAP.

You can preselect values for these fields.

Press 'Continue' to come to another mask in which you can assign particular attributes for the selection fields.

The attributes have the following meaning:

For example, the selection should always be executed over a certain planning interval, for example, the current month. You would enter the variable 'Current month' in this case. This way, the current month would be proposed automatically as a selection criterion.

Note and Recommendation

Every user can create his own selection screen this way. The selection screen you have defined here is proposed by the system only if no individual selection screen was defined for the user under his user ID.

If you want to define an individual selection screen for each user and the user-specific selection screen should be automatically proposed every time the report is called, the report variant name must start with 'U_USERNAME'.

Maintaining selection variants

If you call up this function, this will take you to a start screen containing all the selection fields. Here you can define the standard selection screen. This selection screen will then be proposed whenever no individual selection screen was defined for the user under the name 'U_USERNAME'. The name of the selection variant is always 'SAP_TCODE_XXXX'. XXXX stands for the corresponding application transaction.

Maintaining user-specific selection screens

This function is not set using Customizing.
The individual user maintains the user-specific variants by calling and executing individual transactions.
The user can call the 'Settings' function from the list and create his or her own selection screen there.
The systems automatically generates the variant 'U_USERNAME', which is always called up for the user in subsequent transaction calls after saving.