SAP ABAP Data Element SMT_CONTEXT (Context)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷ CA-SOA-SMT (Application Component) Service Mapping Tool
⤷ GMT_GENERAL (Package) Objects for All Packages Within GMT
⤷ CA-SOA-SMT (Application Component) Service Mapping Tool
⤷ GMT_GENERAL (Package) Objects for All Packages Within GMT
Basic Data
Data Element | SMT_CONTEXT |
Short Description | Context |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SMT_CONTEXT | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | CONTEXT | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Context |
Medium | 15 | Context |
Long | 20 | Context |
Heading | 10 | Context |
Documentation
Definition
Specifies the business environment in which the transformation application is implemented.
Use
If the application supports multiple contexts, you can carry out mapping extensions depending on the context. The context has been integrated in the Customizing of the application. In the case of service implementations, multiple contexts are normally not supported. Then only the predefined context "DEFAULT" is available.
Dependencies
The prerequisite for use of multiple contexts is that the application has explicitly released this function. If this has not happened, only a single context with the predefined key "DEFAULT" is supported. In that case, you get an error message if you attempt to create extensions with other contexts.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 700 |