Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PLM-RM (Application Component) Recipe Management⤷
RMSTLSXCL (Package) RMS-TLS: Excel Output Functions
Basic Data
| Data Element | RMSTE_FIELDNAME |
| Short Description | Field Name |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RMSTD_FIELDNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | DD03L |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Field |
| Medium | 15 | Field Name |
| Long | 18 | Field Name |
| Heading | 10 | Field Name |
Documentation
Definition
Field name of a table, structure, or view.
Supplementary Documentation - RMSTE_FIELDNAME0001
Use
Name of a table field.
Procedure
The field name can comprise a maximum of 10 characters and must begin with a letter. The subsequent characters can be letters, digits, or underscores.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0002
Use
Name of the table field that you have chosen to maintain.
Procedure
You can work through the individual fields in the table by choosing Goto -> Previous Field and Next Field.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0003
Use
Key field in the CHECK TABLE, to which the foreign key field in the foreign key table is assigned.
Procedure
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0004
Use
Name of a table field that is relevant for the index.
Procedure
Specify the table fields that are relevant for the index, or choose Edit -> Choose Fields to choose the fields from a list of the table fields.
When you go back to the Maintain Table (Index) screen, the fields are copied to the index field list in the order in which you selected them.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0005
Use
Names of the Basis fields from the underlying tables.
The key fields that were automatically copied to the view by the system are listed here. These fields are identified accordingly in the Key column.
Procedure
To choose other fields, position your cursor on the name of the table and choose Edit -> Choose Fields. Choose the table fields from the list that are to be copied to the view. These fields are copied as soon as you go back to the maintenance screen.
If two fields from different tables have the same name, you have to enter a new name for at least one field in the View Field column.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0006
Use
Names of the view fields.
The system enters the names of the selected table fields and the names of the view fields here by default.
Procedure
You can change the names of the view fields.
If two fields from different tables have the same name, you have to enter a new name here for at least one field.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0007
Use
Names of the table fields that are used in view selection conditions.
The field conditions do not necessarily have to refer to just the fields that belong to the view. They can also be specified for any of the fields in the underlying Basis tables.
Procedure
To display a list of all the fields, choose Edit -> Choose Fields. You can choose fields from this list and copy them to specify the field conditions.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0008
Use
Names of the table fields that are to be copied from the tables that belong to the matchcode object.
The key fields of all the tables that are relevant for the matchcode object are displayed automatically. These fields are identified accordingly in the Key column.
Procedure
All the fields that are to be used in any matchcode ID for this object have to be copied to the matchcode object. The matchcode object must also contain at least all the primary key fields of the relevant tables that are not foreign key fields at the same time.
The order of the fields in the matchcode object is not important.
To choose the fields, position your cursor on the name of the table and choose Choose Fields or Edit -> Choose Fields. The fields in the relevant table are then displayed and can be copied to the matchcode object.
If two fields from different tables have the same name, you have to enter a new name for at least one field in the MC Field column.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0009
Definition
Names of the matchcode fields.
Use
The system enters the names of the selected table fields and matchcode fields by default.
These names are then specified in the definition of the matchcode IDs for the matchcode object.
Procedure
You can change the names of the matchcode fields if necessary.
If two fields from different tables have the same name, you have to enter a new name for at least one of the fields here.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0010
Use
Names of the table fields that are used in the lock arguments.
Procedure
Since the system determines the lock arguments automatically, you cannot make any changes here.
If this column contains fields with the same name from different tables, you have to enter different names for these fields in the Lock arg. column.
Examples
Dependencies
Supplementary Documentation - RMSTE_FIELDNAME0011
Use
Names of the table fields that are to be locked.
By default, all the fields in the tables that are relevant for the lock object are entered here (*).
Procedure
If you want to change this setting (so that only some of the fields in a table are locked), enter the relevant fields here, or copy them from a field list.
Carry out the following steps:
- Delete the row that contains the entry *.
- Position your cursor on the table whose fields you want to copy.
- Choose Edit -> Choose Fields or Choose Fields.
- In the screen displayed, enter the mode in the column in front of the fields you want to copy.
- Go back to the initial screen. You can now see the fields you selected.
Examples
Dependencies
Note that locks currently apply to all the fields in a table, even if you only selected certain ones here.
Supplementary Documentation - RMSTE_FIELDNAME0012
Use
Names of the lock (enqueue) parameters.
The system automatically enters the names of the table fields as the names of the lock parameters.
Procedure
You can enter new names for the lock parameters here.
The names of the lock parameters, however, must be unique.
Examples
Dependencies
You have to enter new names for lock parameters if the fields are from different tables but have the same name. By doing so, you can ensure that the names are unique.
Supplementary Documentation - RMSTE_FIELDNAME0013
Use
Event creation can depend on certain field restrictions that arise from the old and/or new value of a database field.
Procedure
If you want to create a field restriction, enter the field that is to control the creation of the event here.
Examples
Dependencies
You have to make an entry in the "Field Name" field. If you want to make event creation dependent on the creation or deletion of entries in the specified table, however, enter KEY as the field name.
Further information and an example are provided in the following system messages:
Supplementary Documentation - RMSTE_FIELDNAME0080
Use
Procedure
Enter the name of the text field that contains the F1 Help text for the object type. This is required to ensure that the correct text is displayed for the F1 Help in the application.
Dependencies
History
| Last changed by/on | SAP | 20031212 |
| SAP Release Created in | 210 |
