SAP ABAP Data Element FIELDNAME (Field Name)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
     SDIC (Package) ABAP Dictionary
Basic Data
Data Element FIELDNAME
Short Description Field Name  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FDNAME    
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 DFD  
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

Name of a field within an Intermediate Document record.

Example

Field SDATA in the data record

Supplementary Documentation - FIELDNAME 0001

Use

Name of a table field.

Procedure

The name of a field can have up to 10 characters and must begin with a letter. The following characters can be letters, digits, or underscores.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0002

Use

Name of the table field you selected for single field maintenance.

Procedure

You can use edit the table fields individually with Goto -> Previous field or Next field.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0003

Use

Key field of the check table to which the foreign key field of the foreign key table is assigned.

Procedure

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0004

Use

Name of a table field relevant for the index.

Procedure

Enter the table fields relevant for the index, or choose Edit -> Select fields to go to the list of table fields where you can select the fields that you need.

When you return to the screen Maintain table (Index) , the fields are taken over into the index field list in the sequence in which you have selected them.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0005

Use

Names of the base fields from the tables on which they are based.

The key fields automatically taken over into the view are listed. These fields are marked accordingly in the column Key.

Procedure

To select additional fields, place the cursor on the name of the table and choose Edit -> Select fields. From the list choose the table fields to be taken over into the view. These fields are taken over when you return to the maintenance screen.

When two fields from different tables have the same name, a new name must be entered for at least one of the fields in the column View field.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0006

Use

Names of the view fields.

The system enters the names of the selected table fields as the names of the view fields.

Procedure

You can change the names of the view fields.

If two fields from different tables have the same name, you have to specify a new name for at least one of the fields.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0007

Use

Names of the table fields included in view selection conditions.

The field conditions do not necessarily refer only to the fields that belong to the view but can be specified for any field from the base tables.

Procedure

To see a list of all fields, choose Edit -> Select fields. You can choose fields from this list and take them over to specify the field conditions.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0008

Use

Names of the fields to be adopted from the tables belonging to the matchcode object.

The key fields of all tables relevant to the matchcode object are displayed automatically. These fields are marked accordingly in the column Key.

Procedure

All fields that are to be used in any of the matchcode IDs for this object must be adopted in the matchcode object. In addition, the matchcode object must contain at least the primary key fields of the associated tables that are not defined as foreign-key fields.

The order of the fields in the matchcode object is not important. To choose fields, position the cursor on the name of the desired table and choose Choose fields or Edit -> Choose fields. The fields of the table are displayed and can be adopted in the matchcode object.

If two fields from different tables have the same name, you must enter a new name for at least one field in the column MC field.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0009

Use

Names of the matchcode fields.

The system enters the names of the selected table fields as the names of the matchcode fields.

These names must then be specified in the definition of the matchcode IDs that belong to the matchcode object.

Procedure

You can change the names of these matchcode fields.

If two fields from different tables have the same name, you have to enter a new name for at least one of the two fields.

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0010

Use

Names of the table fields included in the lock arguments.

Procedure

Since the system determines the log arguments automatically, you cannot make any changes here.

If this column contains fields with the same names from different tables, you must enter different names for these fields in the column Lock arg..

Examples

Dependencies

Supplementary Documentation - FIELDNAME 0011

Use

Names of the table fields to be locked.

The system enters all the fields of the tables included in the lock object with (* ).

Procedure

If you want to change this setting, i.e., lock only specific table fields, enter these fields here or copy the required fields from a field list.

Proceed as follows:

  1. Delete the line that contains the entry * .
  2. Place the cursor on the table from which you want to copy the fields.
  3. Choose Edit -> Select fields or Select fields.
  4. In the next screen enter the mode in the first column in front of the fields that you want to copy.
  5. Return to the initial screen. You see the selected fields.

Examples

Dependencies

At the moment all table fields are locked even if you select specific fields as described above.

Supplementary Documentation - FIELDNAME 0012

Use

Name of the lock parameter.

The system enters the names of the table fields as names of the lock parameters as default.

Procedure

You can also assign new names for the lock parameters, but the names of the lock parameters must be unique.

Examples

Dependencies

You must assign new names for lock parameters if fields from different tables have the same name. This ensures that the names of the lock parameters are unique.

Supplementary Documentation - FIELDNAME 0013

Use

The creation of an event can depend on certain field restrictions that result from the old and/or new value of a database field.

Procedure

If you maintain a field restriction yourself, enter the field that should influence the creation of the event here.

Examples

Dependencies

You must make an entry in the field "Field name", but if you want the creation of the event to be dependent on the creation or deletion of entries in the specified table, you should enter KEY as the field name.

You can find further information and an example in the following system messages:

Supplementary Documentation - FIELDNAME 0080

Use

Procedure

Enter the name of the text field in which the text for the F1 help for the object type is stored. This is necessary to ensure that the correct text is displayed for the F1 help on the application.

Dependencies

History
Last changed by/on SAP  20010130 
SAP Release Created in