Hierarchy
⤷
⤷
Basic Data
| Data Element | RECACALLCONTEXT |
| Short Description | Context of Application |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RECACALLCONTEXT | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | Context |
| Medium | 15 | Applic. Context |
| Long | 20 | Application Context |
| Heading | 10 | Context |
Documentation
Definition
The context specifies from which application or environment a function (such as graphical integration) is called. The called function can be different on the basis of the context.
Use
Dependencies
The available values (domain fixed values) for the context are entered as the following constants in the type group RECA2:
Value Meaning Constant in Type Pool
' ' Without context reca2_callcontext-none
'APPL' Application (object processing) reca2_callcontext-application
'REPO' Reporting reca2_callcontext-reporting
'RESV' Reservation reca2_callcontext-reservation
'POMP' Move Planning reca2_callcontext-move_plan
Example
The graphical integration is called from two places:
- From the context of master data maintenance
- From the context of move planning
Depending on the context, different evaluations (queries) are available in the graphic.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |