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_NAV_UNLOCK |
| Short Description | Unlock in Navigation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CRM_BSP_NAV_UNLOCK | |
| 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 | Unlock |
| Medium | 15 | Unlock Object |
| Long | 20 | Unlock Object |
| Heading | 10 | Unlock |
Documentation
Definition
Several values can be entered in this field.
1. No data loss popup: If the user wants to navigate, the source object data is neither saved nor unlocked.
2. Data loss popup and unlock: If the user wants to navigate, the source object is unlocked and displayed in the display mode. This is useful if the object to which the user wants to navigate is the same as the object from which the user is navigating (for example, in detailed processing. It is also useful when the object from which the user is navigating is locked by the target object (for example, in follow-up processing).
3. Data loss popup and no unlock: If the user wants to navigate, the source object is not unlocked. This selection is useful if the object to which the user wants to navigate refers to current data in the source object, but where it is not necessary to lock the source object.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 400 |
