Hierarchy
⤷
⤷
Basic Data
| Data Element | SWE_CONT |
| Short Description | Event container contains individually entered elements |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 25 | Container exists |
| Heading | 0 |
Documentation
Definition
The event container contains certain elements as standard (for example, creation time, creator, etc.). This indicator specifies whether the event container contains additional elements at runtime (usually application-specific data).
Supplementary Documentation - SWE_CONTFB0001
Use
With this function module the event container can be modified and added to.
The function module will, if it is entered, be called up after the writing of a change document with the triggering of an event.
In the implementation of the function module you can access via the parameter CHANGEDOCUMENT_POSITION single items of the change document and place corresponding information about the change document in the event container.
Procedure
Examples
You can consult the function module SWE_MODIFY_EVENT_CNTN_TEMPLATE which can be used as a pattern and a reference.
Dependencies
So that you can also access the values that were created in the event parameter in a binding definition, you must create the corresponding element in the event container. You do this in the Business Object Builder.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |