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_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 | RSPC_DECISION_FIELDNAME | |
| 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 view.
Supplementary Documentation - RSPC_DECISION_FIELDNAME0001
Use
Name of a table field
Procedure
The name of a field may be a maximum of 10 characters long and must start with a letter. With the following characters, these can be letters, numbers or underscores.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0002
Use
Name of the table field that you have selected for single field maintenance.
Procedure
You can edit the fields of the table individually using
Goto -> Previous field or Next field .
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0003
Use
Key field of PRÜFTABELLE, to which the foreign key relationship field of the foreign key relationship table is assigned.
Procedure
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0004
Use
Name of a table field that is relevant for the index.
Procedure
Specify the table fields relevant for the index or go to the corresponding list of table fields from which you can select your desired fields using Edit -> Select fields .
When you return to the screen Maintain table (index) , the fields are added to the index field list in the order in which they were selected.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0005
Use
Name of the basic fields from the source tables.
Here, the key fields transferred automatically to the view by the system. These fields are designated as such in the column Key .
Procedure
To select further fields, put the cursor on the name of the desired table and choose Edit -> Select Fields. From the list of table fields, choose those that should be transferred to the view. These fields will be transferred upon return to the maintenance screen.
If two fields from different tables have the same name, a new name must be entered into the View field column for at least one of them.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0006
Use
Names of the view fields.
By default, the system enters the name of the selected table fields as the names of the view fields as well.
Procedure
The names of the view fields can be changed.
If two fields from different tables have the same name, a new name must be entered for at least one field here.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0007
Use
Name of the table fields that are part of view selection conditions.
The field conditions do not necessarily have to refer to the fields belonging to the view. Instead, they can be specificed for any fields from the underlying basic tables.
Procedure
To get a list of all fields, choose Edit -> Select Fields. You can select fields from this list and transfer them for specification of field conditions.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0008
Use
Names of the table fields that are to be transferred from the tables belonging to the matchcode object.
The key fields for all tables relevant for the matchcode object are displayed automatically. These fields are indicated with Key in the column.
Procedure
All fields need to be transferred to the matchcode object that are to be used in any matchcode ID for this object. In addition, the matchcode object must contain at least all of the primary key fields of the participating table that are not also foreign key fields.
The sequence of fields in the matchcode object is irrelevant.
To select fields, position the cursor on the name of the desired table and choose Select Fields or Edit -> Select Fields. The fields for the affected table are displayed and can be transferred to the matchcode object
If two fields from different tables have the same name, a new name has to be entered for at least one field in the column MC field .
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0009
Definition
Name of the matchcode error.
Use
By default, the system also enters the names of the selected table fields as names of the matchcode fields
These names are 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 have to enter a new name for at least one of the fields here.
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0010
Use
Name of table fields included in the lock arguments.
Procedure
Since the system determines lock arguments automatically, you cannot make any changes here.
If this column contains fields with the same name from different tables,you must enter different names for the fields in the column Lock Arg..
Examples
Dependencies
Supplementary Documentation - RSPC_DECISION_FIELDNAME0011
Use
Names of the table fields that should be locked.
In the standard system, all fields of tables included in the lock object are flagged with * .
Procedure
If you want to change this setting, in other words, only lock certain fields in a table, enter the fields here or transfer the fields in question from a field list.
To do this:
- Delete the row containing the entry * .
- Position the cursor on the table whose fields you want to transfer.
- Choose Edit -> Select Fields or Select Fields.
- On the next screen, enter the mode in the first column in front of the fields that you want to transfer.
- Return to the initial screen, where you will now see the fields you selected.
Examples
Dependencies
Please note that a lock currently locks all fields in a table even if you selected only some fields here.
Supplementary Documentation - RSPC_DECISION_FIELDNAME0012
Use
Names of lock parameters.
The system enters the names of the table fields as the lock parameter names by default.
Procedure
You can assign new names to the lock parameters if required.
The lock parameter names must be unique.
Examples
Dependencies
You must assign new names to lock parameters if there are fields with the same name from different tables, so that all lock parameter names are unique.
Supplementary Documentation - RSPC_DECISION_FIELDNAME0013
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 maintain a field restriction yourself, enter here the field that should have an influence on the event generation.
Examples
Dependencies
You must make an entry in the "Field name" field. However, if you want event generation to depend on the creation or deletion of entries in the table concerned, 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 |
