Hierarchy

⤷

⤷

Basic Data
Data Element | SCPRTECHBZ |
Short Description | BC Sets: Show Technical Description |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | TechnDescr |
Medium | 15 | Techn. Descrip. |
Long | 39 | Show Technical Description |
Heading | 39 | Show Technical Description |
Documentation
Definition
Technical names for IMG activity, customizing object and table/view fields do not appear in the BC Set maintenance transaction. This can prevent the unique identification of a field.
Use
You can specify in the BC Set user settings, whether other technical values are to be displayed in the BC Set maintenance transaction. You can display the following other technical values in the BC Set maintenance transaction, as well as the already available technical settings, such as table/view name:
- IMG activity (after the activity name)
- Customizing object (after the object name)
- Field name (additional column in the list of field attributes, under "Field Selection, Attributes")
Dependencies
Example
Two fields in a table are called "Date". One is the purchase date, and the other is the sales date of an article. The name is not sufficient to distinguish which field stands for which date. If you show the technical settings, you would see the name "Date" followed by the (fictional) technical field name "BUYDATE" for the first field, and "SELLDATE" for the second field.
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 630 |