Hierarchy
CPRXRPM (Software Component) SAP Portfolio and Project Management 6.0⤷
PPM-PRO-EXT-API (Application Component) BAPI Interface for cProjects⤷
DEVELOPMENT_PROJECTS_BAPI (Package) Project Management - BAPI
Basic Data
| Data Element | DPR_TV_BAPI_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 | FIELDNAME | |
| 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 - DPR_TV_BAPI_FIELDNAME0001
Use
Name of a table field.
Procedure
The name of a field may have a maximum of 10 characters and must start with a letter. The characters that follow can be letters, numbers, or underscores.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0002
Use
Name of the table field that you have selected for individual field maintenance.
Procedure
You can edit the fields in the table one by one by choosing Goto -> Previous Field or Next Field.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0003
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 - DPR_TV_BAPI_FIELDNAME0004
Use
Name of a table field that is relevant to the index.
Procedure
Specify the table fields that are relevant to the index or use Edit -> Select Fields to go to the appropriate list of table fields from which you can select the fields you need.
When you return to the Maintain Table (Index) screen, the system transfers the fields to the index field list in the order in which they were selected.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0005
Use
Names of the basis fields from the underlying tables.
The key fields that are automatically transferred to the view are listed here. These fields are identified accordingly in the Key column.
Procedure
To select more fields, place the cursor on the names of the required tables and choose Edit -> Select Fields. From the list of table fields, choose those that are to be transferred to the view. These fields are transferred when you return to the maintenance screen.
If two fields from different tables have the same name, the View Field column must contain a new name for at least one of the fields.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0006
Use
Name of the view fields.
The system also enters the names of the selected table fields as names of the view fields by default.
Procedure
The names of the view fields can be changed.
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 - DPR_TV_BAPI_FIELDNAME0007
Use
Names of the table fields that are part of the view selection criteria.
The field conditions do not necessarily only refer to the fields that belong to the view. They can be specified for any fields from the underlying basis tables.
Procedure
To obtain a list of all fields, choose Edit -> Select Fields. You can select fields from this list and transfer them for specifying field conditions.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0008
Use
Names of the table fields that are to be transferred from the tables that belong to the matchcode objects.
The key fields of all tables relevant to the matchcode objects are displayed automatically. These fields are identified accordingly in the Key column.
Procedure
In the matchcode object, all fields have to be transferred that are to be used in any matchcode ID for this object. Furthermore, the matchcode object must also contain at least all primary key fields of the appropriate table but not if they are also foreign key fields.
There is no meaning to the order of the matchcode objects in the table.
To select fields, place the cursor on the name of the required table and choose Select Fields or Edit -> Select Fields. The system then displays the fields from the appropriate table and they can then be transferred to the matchcode object.
If two fields from different tables have the same name, a new name must be entered in the MC Field column for at least one of the fields.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0009
Definition
Names of the matchcode fields.
Use
The system also enters the names of the selected table fields as names of matchcode fields by default.
These names are then specified in the definition of the matchcode IDs that belong to the matchcode object.
Procedure
You can change the names of the 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 fields.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0010
Use
Names of the table fields that are included in the lock argument.
Procedure
Since the lock argument is determined by the system automatically, you cannot make any changes here.
If this column contains any fields with the same names from different tables, you have to enter different names for these fields in the LockArg. column.
Examples
Dependencies
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0011
Use
Names of the table fields that are to be locked.
All fields that belong to the tables that are part of the lock object, are entered with * by default.
Procedure
If you want to change this default setting, that is, if you only want to lock certain fields in a table, enter these fields here or transfer the relevant fields from a field list.
Perform the following steps:
- Delete the row that contains the entry *.
- Place the cursor on the table from which you want to transfer fields.
- Choose Edit -> Select Fields or Select Fields.
- In the screen that follows, enter the mode in the first column in front of the fields you want to transfer.
- Go back to the initial screen. You can now see the selected fields here.
Examples
Dependencies
Note that the lock currently locks all fields in the table even if only certain fields were selected there.
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0012
Use
Names of the lock parameters.
The system enters the names of the table fields as names of the lock parameters by default.
Procedure
You have the option of assigning new names to the lock parameters.
However, the names of the lock parameters must be unique.
Examples
Dependencies
You have to assign new names to the lock parameters if fields from different tables have the same name, so that the names of the lock parameters remain unique.
Supplementary Documentation - DPR_TV_BAPI_FIELDNAME0013
Use
Creating an event may depend on certain field restrictions that arise from the old and/or new value of a database field.
Procedure
If you enter a field restriction yourself, enter the field here that is to influence the creation of the event.
Examples
Dependencies
You have to make an entry in the "Field Name" field. If you want to make the creation of an event depend on the creation or deletion of entries in the table that was entered, enter the field name KEY.
For more information and an example, see the following system messages:
History
| Last changed by/on | SAP | 20141109 |
| SAP Release Created in | 310 |
