Ansicht
Dokumentation

Transaction Management: Field Selection Control for the User Interface ( RELNTRTRM_46A_TR_FIELDS )

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Short text

Transaction Management: Field Selection Control for the User Interface

Scope of Functions

You use the field selection control function to determine how to access a large number of visible fields. In this way, you can adjust the external appearance of transaction management in Treasury Management to suit the business conditions.

The visible fields are grouped together in field groups according to different business criteria. To each of the field groups available, you can assign one attribute, which determines the appearance of the screen for the user. This enables you to specify whether you want to hide or display field groups, or whether you want them to be required entries.

The function for defining differentiated field selection strings is supported. You choose a name for the field selection string. It is possible, though not absolutely necessary, to assign the string to a specific product category.

Once you have defined a field selection string, you can start assigning it to the following levels:

1. Product type and company code
2. Transaction types
3. Activity categories
4. Functions

The valid field selection string is determined at the start of a transaction in the transaction management function. The system first searches for a field selection string for the function. If this is not found, the system continues searching for the activity category. If the search is also unsuccessful, the search moves up to the next level. The last search level represents the assignment at product type and company code level.

It is not always possible to make the required settings. This is the case when the field selection control you require does not match the attribute predefined in the application. For example, a field group is set to hidden in the field selection control, yet for business or technical reasons, the application urgently requires the entry for the same field group. In this conflict situation, the field group is assigned the attribute from the application. The field selection attribute is ignored.

The pushbuttons are an exception to this. You can partly control them, but you cannot determine whether they appear as required or display fields. A pushbutton is either available and visible, or vice versa.

Effects on Customizing

Go to the field selection control function in Customizing for Basic functions, by choosing Transaction Management →Define Field Selection.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2745 Date: 20240604 Time: 054442     sap01-206 ( 65 ms )