SAP ABAP Data Element BS_CT_LOCAL (Local Context ID)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷ CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷ BS_COMMON_OBJECTS (Package) Common Tools and Interfaces
⤷ CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷ BS_COMMON_OBJECTS (Package) Common Tools and Interfaces
Basic Data
Data Element | BS_CT_LOCAL |
Short Description | Local Context ID |
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 | Local |
Medium | 15 | Local |
Long | 20 | Local |
Heading | 20 | Local |
Documentation
Definition
Specifies that a context ID is available only locally within its origin context accord.
Use
A context ID that is specified as local is only available within its specified environment. Within any other context accord local context IDs are neither accessible nor mutable. Actually an application instance is vested to exactly one context accord, so that only applications that use its origin context accord are allowed to access a local context ID.
Context IDs that are not specified as local are accessible in all context accord they are assigned to.
Dependencies
Even if a context ID is not marked as mutable an application that uses its origin context accord is allowed to change the contextual information of that context ID.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 731 |