1.4. Field Display Characteristics
1.4.1. Global Field Display Characteristics
1.4.2. Configure application transaction fields
Field Display Characteristics
Field Display Characteristics
Field display characteristics can be defined globally or for a transaction. This technique was developed to hide the complexity of the SAP System from the user when possible. The user is spared from entering data in fields that are always the same.
By defining global field characteristics (or "global fields") certain fields in screens can be influenced in all the transactions where they appear. Ready-for-input screen fields can be preset with a value. They can be set so as not to accept field entries, and they can be hidden.
Using transaction-related field characteristics ("transaction variants") you can preset fields occurring in a transaction, define characteristics of fields, or hide whole screens in a transaction if they are not required there.
Example of the use of a global field:
Your company only uses one company code, 0001, in its SAP System. You do not wish to hide the company code from the users, but they should not have to decide what to enter in this field. You can use a global field to preset the company code to 0001 in all screens in every transaction. You can also determine that the field should not be ready for input.
For extra differentiation, global fields can refer both to domains or data elements. For example, a distinction could be made between the "sender" and "receiver" company codes at data element level.
Example of the use of a transaction variant:
Your company uses just one order type on the purchase requisition, NP for normal purchase order. You want to preset the value in transaction ME21 so no employees use the wrong order type or need to decide which order type to enter. To do this you create a variant of transaction ME21 that has the order type preset to NP and the field set to not ready for input (or assigns the "hidden" characteristic to the field).\
Global Field Display Characteristics
To fill the global fields with values automatically, use global field display characteristics definition to definefield values and behavior characteristics.
Setting a field value and defining characteristics for a field are subject to the following conditions:
The value for the global field is set if
There are no conflicts
If a value is set internally in the transaction, or manually, and that value does not agree with the
global value, then the global value has precedence. In these circumstances the field is not blocked
for input.
the field is a mandatory field
A space is a valid entry, so for fields that are not mandatory it is impossible to tell if there is a value
conflict. For this reason, global values are set for mandatory fields only.
A global field's readiness for input is withdrawn if
If you set values and/or change display characteristics of global fields, this affects all fields in associated domains or associated data elements.
Global values have precedence over values set by parameter IDs.
Values (and display characteristics) set by transaction variants have precedence over global values.
In certain transactions no global values are set at all. These transactions include, for example, general table maintenance and IMG transactions.
Configure application transaction fields
Transaction-specific field display attributes are set by transaction variants which simplify transactions by:
A transaction variant is assigned to one transaction. A transaction can have several variants.
Notes:
A value can be set for each input field in a Step Loop. The output attributes (hidden, no input) can
only be set once per Step Loop (for the first field in the Step Loop); they apply to all fields in the
Step Loop.
All Step Loop fields in which a value was entered are displayed in the field list. The first field is
always displayed to determine the output attributes, even if no value was entered.
The same applies to Table Control fields as for Step Loop fields.
Table Controls should not be set to "hidden" as the Table Control columns remain and only the field
contents are hidden.
1. Specify the names of the transaction and the variant.
If you do not know the transaction code, you can find it in the "System -> Status" menu in the
transaction which you want to change.
If the changes in your transaction variant apply to all users, create a standard variant, which is
automatically found and run when the transaction is called (by menu or transaction code). Maintain
standard variants with "Goto -> Standard variant".
2. Create the variant and enter a short text.
3. Variant values can be entered with "Screen entries". The transaction for which the variant is to
be maintained is called and you can enter the field values. At each screen change, a dialog box
appears, in which the fields of the current screen are listed. You can choose whether the screen is
to be displayed, whether field values are to be copied, and enter field display attributes.
4. Leave the transaction and save the variant. If you have created a standard variant, you must
activate it.
5. Call the transaction variant with "Test".
If you have created the standard variant, you can simply call the transaction.
Further Notes
For additional information about maintaining, running and transporting transaction variants, see the online handbook (pushbutton "i") when you run the transaction.
1.4.1. Global Field Display Characteristics
1.4.2. Configure application transaction fields
Field Display Characteristics
Field Display Characteristics
Field display characteristics can be defined globally or for a transaction. This technique was developed to hide the complexity of the SAP System from the user when possible. The user is spared from entering data in fields that are always the same.
By defining global field characteristics (or "global fields") certain fields in screens can be influenced in all the transactions where they appear. Ready-for-input screen fields can be preset with a value. They can be set so as not to accept field entries, and they can be hidden.
Using transaction-related field characteristics ("transaction variants") you can preset fields occurring in a transaction, define characteristics of fields, or hide whole screens in a transaction if they are not required there.
Example of the use of a global field:
Your company only uses one company code, 0001, in its SAP System. You do not wish to hide the company code from the users, but they should not have to decide what to enter in this field. You can use a global field to preset the company code to 0001 in all screens in every transaction. You can also determine that the field should not be ready for input.
For extra differentiation, global fields can refer both to domains or data elements. For example, a distinction could be made between the "sender" and "receiver" company codes at data element level.
Example of the use of a transaction variant:
Your company uses just one order type on the purchase requisition, NP for normal purchase order. You want to preset the value in transaction ME21 so no employees use the wrong order type or need to decide which order type to enter. To do this you create a variant of transaction ME21 that has the order type preset to NP and the field set to not ready for input (or assigns the "hidden" characteristic to the field).\
Global Field Display Characteristics
To fill the global fields with values automatically, use global field display characteristics definition to definefield values and behavior characteristics.
Setting a field value and defining characteristics for a field are subject to the following conditions:
The value for the global field is set if
There are no conflicts
If a value is set internally in the transaction, or manually, and that value does not agree with the
global value, then the global value has precedence. In these circumstances the field is not blocked
for input.
the field is a mandatory field
A space is a valid entry, so for fields that are not mandatory it is impossible to tell if there is a value
conflict. For this reason, global values are set for mandatory fields only.
A global field's readiness for input is withdrawn if
- a good value is set (in mandatory fields)
- the value as set by the transaction, the parameter ID, or otherwise, agrees with the global value (in non-mandatory fields)
A global field is hidden if
- a field can have no other content than its initial value. Associated text fields are also hidden.
If you set values and/or change display characteristics of global fields, this affects all fields in associated domains or associated data elements.
Global values have precedence over values set by parameter IDs.
Values (and display characteristics) set by transaction variants have precedence over global values.
In certain transactions no global values are set at all. These transactions include, for example, general table maintenance and IMG transactions.
Configure application transaction fields
Transaction-specific field display attributes are set by transaction variants which simplify transactions by:
- setting field values
- hiding fields and specifying whether they are ready for input
- hiding screens
A transaction variant is assigned to one transaction. A transaction can have several variants.
Notes:
- You can copy transaction variant input field values and change their output attributes.
- Initial values are not copied into the variant. You can change the output attributes of fields with inital values.
- Function entries are not copied into the variant.Exception: If a screen is not to be displayed, the function entry for this screen is copied into the variant.
- Checkbox and radio button values cannot be copied. Checkbox output attributes can be changed.
- Two ABAP/4 programming language mechanisms are used to display and process table data:
A value can be set for each input field in a Step Loop. The output attributes (hidden, no input) can
only be set once per Step Loop (for the first field in the Step Loop); they apply to all fields in the
Step Loop.
All Step Loop fields in which a value was entered are displayed in the field list. The first field is
always displayed to determine the output attributes, even if no value was entered.
The same applies to Table Control fields as for Step Loop fields.
Table Controls should not be set to "hidden" as the Table Control columns remain and only the field
contents are hidden.
- A new field values dialog box appears for each sub screen. The "Cancel" function is not active in this dialog box, for technical reasons.
- Transaction variants are only possible for dialog transactions.
- Transaction variants are client-specific.
- Transaction variant values are not taken into account in Batch Input (incl. Batch Input recording)
1. Specify the names of the transaction and the variant.
If you do not know the transaction code, you can find it in the "System -> Status" menu in the
transaction which you want to change.
If the changes in your transaction variant apply to all users, create a standard variant, which is
automatically found and run when the transaction is called (by menu or transaction code). Maintain
standard variants with "Goto -> Standard variant".
2. Create the variant and enter a short text.
3. Variant values can be entered with "Screen entries". The transaction for which the variant is to
be maintained is called and you can enter the field values. At each screen change, a dialog box
appears, in which the fields of the current screen are listed. You can choose whether the screen is
to be displayed, whether field values are to be copied, and enter field display attributes.
4. Leave the transaction and save the variant. If you have created a standard variant, you must
activate it.
5. Call the transaction variant with "Test".
If you have created the standard variant, you can simply call the transaction.
Further Notes
For additional information about maintaining, running and transporting transaction variants, see the online handbook (pushbutton "i") when you run the transaction.
No comments:
Post a Comment