Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-PCF-CUS (Application Component) People-Centric UI Framework Customizing⤷
CRM_BSP_FRAME_SC_BLUEPRINT (Package) Controller Implementation: Blueprint
Basic Data
| Data Element | CRMT_BSP_TOOLTIPFIELDNAME |
| Short Description | Field Name for Tool Tips Field |
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 | Quick Info |
| Medium | 15 | Tool Tips Field |
| Long | 20 | Tool Tips Field |
| Heading | 30 | Tool Tips Field |
Documentation
Definition
Field name of table, structure or view.
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0001
Use
Name of a table field.
Procedure
The name of a field may only be 10 characters long, and must begin with a letter. The following characters may be letters, numbers, or underscores.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0002
Use
Name of table field that you have selected for individual field maintenance.
Procedure
You can maintain fields in the table individually by selecting Goto, Previous Field and Next Field.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0003
Use
Key field of Check Table, to which the foreign key field of the foreign key table is assigned.
Procedure
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0004
Use
Name of table field that is relevant for the index.
Procedure
Specify table fields that are relevant for the index, or navigate to the respective list of table fields from where you can select the required fields by choosing Edit -> Select Fields.
By returning to the Maintain Table (Index) screen, the fields are copied to the index field list in the sequence in which they were selected.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0005
Use
Name of basic fields from basis tables.
Key fields that are automatically copied by the system to the view are listed here. These fields are flagged in the Key column accordingly.
Procedure
In order to select further fields, place your cursor on the name of the required table and choose Edit -> Select Fields. Select those table fields from the list that should be copied into the views. These fields are copied when switching back to the maintenance screen.
If two fields from different tables have the same name, you must enter a new name for at least one of the fields in the View Field column.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0006
Use
Name of view fields.
The names of selected table fields are also entered as the names of view fields by default by the system.
Procedure
View field names can be changed.
If two fields from different tables have the same name, at least one of the fields has to be renamed.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0007
Use
Names of table fields that are a part of the view selection requirements.
Field requirements do not necessarily have to refer to fields belonging to the view, but can be specified for user-defined fields from basic basis tables.
Procedure
To display a list of all fields, choose Edit -> Select Fields. You can select fields from this list and also copy field requirements.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0008
Use
Names of table fields that should be copied from tables that correspond to the matchcode object.
Key fields of all tables that are relevant for the matchcode object are displayed automatically. They are flagged accordingly in the Key column.
Procedure
All fields have to be copied to the matchcode object that should be used in any matchcode ID for this object. In addition to this, the matchcode object must also contain at least all primary key fields of the tables concerned that are not also simultaneously foreign key fields.
The sequence of fields in the matchcode object is irrelevant.
In order to select fields, place your cursor on the name of the required table and select Select Fields or Edit -> Select Fields. The fields of the table concerned are displayed, and can be copied into the matchcode object.
If two fields from different tables have the same name, then a new name has to be entered for at least one field in the MC Field column.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0009
Definition
Names of matchcode fields.
Use
In the standard, the system enters the names of selected table fields as names of matchcode fields.
These names are then specified in the definition of corresponding matchcode IDs for the matchcode object.
Procedure
You can change the names of the matchcode fields.
It two fields from different tables have the same name, then you must specify a new name for at least one of the two fields.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0010
Use
Names of table fields that enter lock arguments.
Procedure
As lock arguments are automatically determined by the system, you cannot make changes here.
If fields from different tables have the same name in this column, you have to enter different names in the Lock Argument column for these fields.
Examples
Dependencies
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0011
Use
Names of table fields that should be locked.
In the standard, all fields are flagged with * that are entered in the lock object table.
Procedure
If you wish to change this presetting, that is, if you wish to only lock specific tables, then enter these fields here or copy the respective fields from a field list.
To do so, carry out the following steps:
- Delete the row that contains the * .
- Place your cursor on the table from which you wish to copy fields.
- Select Edit -> Select Fields or Select Fields.
- In the following screen, enter the mode in the first column before the fields that you wish to copy.
- Return to the initial screen. The selected fields are now displayed.
Examples
Dependencies
Note that during a lock all fields in the table are locked, even if only specific fields are selected here.
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0012
Use
Names of lock parameters.
In the default, the system enters the names of table fields as names of Lock Parameters.
Procedure
You have the option here to specify new names for the lock parameters.
However, names of the lock parameters have to be unique.
Examples
Dependencies
You have to specifiy new names for lock parameters if the fields from different tables have the same name in order to maintain uniqueness.
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0013
Use
The creation of events can depend on specific field restrictions that arise from old and/ir new value of a database field.
Procedure
If you maintain a field restriction yourself, enter the field here that should influence the creation of an event.
Examples
Dependencies
In the "Field Name" input field, you have to make an entry. However, if you wish to make the creation of the event dependent on the creation or deletion of entries in the entered table, enter KEY as the field name.
You can find more information and an example in the following system messages:
Supplementary Documentation - CRMT_BSP_TOOLTIPFIELDNAME0080
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 in order that the correct text is displayed in the application when the F1 Help is called.
Dependencies
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 400 |
