Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DST (Application Component) Data Staging⤷
RSPC (Package) Process Chains
Basic Data
| Data Element | RSPC_DECISION_PRED_FNAM |
| 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 | RSPC_DECISION_PRED_FNAM | |
| Search Help: Parameters | FNAM | |
| 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
Field name of a table, structure or a view.
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0001
Use
Name of a table field.
Procedure
The name of a field may have 10 characters maximum and must start with a letter. The other characters may be letters, numbers, or underscores.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0002
Use
Name of a table field that you have selected for individual maintenance.
Procedure
You can edit the fields in the table individually by choosing Goto -> Previous field or Next field.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0003
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 - RSPC_DECISION_PRED_FNAM0004
Use
Name of a table field that is relevant for the index.
Procedure
Enter the table fields that are relevant for the index or choose Edit -> Select Fields to access the list of table fields from which you want to select fields.
When you return to the Maintain Table (Index) screen, you will see the fields listed in the index field list in the order in which you selected them.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0005
Use
Names of the Basis fields in the underlying tables.
The system automatically lists the key fields transferred to the view. These fields are marked accordingly in the Key column.
Procedure
If you want to select more fields, position the cursor on the name of the required table and choose Edit -> Select Fields. From the list of table fields, select those you want transferred to the view. The fields you select will be displayed on the maintenance screen when you go back.
If two fields from different tables have the same name, you must enter a new name for one of them at least in the View field column.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0006
Use
Names of View fields.
The system assigns the names of the table fields you selected to the view fields by default.
Procedure
You can change the names of the view fields.
If two fields from different tables have the same name, you must enter a new name for at least one of them.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0007
Use
Names of the table fields included in the view selection conditions.
The field conditions do not necessarily have to refer only to the fields belonging to the view. They can include any fields contained in the underlying Basis tables.
Procedure
To obtain a list of all fields, choose Edit -> Select Fields. You can then select fields from the complete list for transfer to the field conditions.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0008
Use
Names of table fields to be transferred 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 flagged accordingly in the Key column.
Procedure
All fields that are to be used in a matchcode ID of this object must be transferred to the matchcode object. Furthermore, the matchcode object must contain at least all of the primary key fields of the tables concerned, which are not foreign key fields.
The sequence of the fields in the matchcode object is of no importance.
To select fields, position the cursor on the name of the required table and choose Select Fields or Edit -> Select Fields. The fields of the table are displayed and can be transferred to the matchcode object.
If two fields from different tables have the same name, you must enter a new name for at least one of them in the MC field column.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0009
Definition
Names of the matchcode fields.
Use
By default the system enters the names of the selected table fields as the names of the matchcode fields.
These names are then specified in the definition of the matchcode IDs belonging 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 must enter a new name for at least one of them.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0010
Use
Names of the tables fields included in the lock arguments.
Procedure
Since the system determines lock arguments automatically, you cannot make any changes to them.
If fields from different tables have the same names, you must enter new names for them in the Lock Arg. column.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0011
Use
Names of the table fields that are to be locked.
In the standard system, all fields of tables involved in the lock argument are entered here with a * .
Procedure
If you want to change this setting, so that only certain fields of a table are locked, enter the required fields here or transfer the fields from a field list.
Perform the following steps:
- Delete the row containing the entry * .
- Position the cursor on the table from which you want to transfer fields.
- Choose Edit -> Select Fields or Select Fields .
- On the next screen, enter a mode in the first column in front of the fields you want to transfer.
- Return to the initial screen. The fields you selected are now listed there.
Examples
Dependencies
Note that currently all table fields are locked by a lock even if you only select certain fields here.
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0012
Use
Names of the lock parameters.
The system enters the names of the table fields as the lock parameter names by default.
Procedure
You can change the lock parameter names here if you want.
The lock parameter names must be unique.
Examples
Dependencies
You must assign new names to lock parameters if some fields from different tables have the same names so as to ensure that the lock parameter names are unique.
Supplementary Documentation - RSPC_DECISION_PRED_FNAM0013
Use
Event generation may depend upon certain field restrictions that derive from the old and/or new value of a database field.
Procedure
If you yourself maintain a field restriction, enter the field here that should influence event generation.
Examples
Dependencies
You must make an entry in the "Field name" field. However, if you want event generation to be dependent on the creation or deletion of entries in the tables specified, you must enter KEY as the field name.
For more information and an example of this, see the following system messages:
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 400 |
