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
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