SAP ABAP Data Element MEINDEX (Message Index (Sequential Number))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_CORE (Package) Mobile: Core Components
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_CORE (Package) Mobile: Core Components
Basic Data
Data Element | MEINDEX |
Short Description | Message Index (Sequential Number) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MEINDEX | |
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 | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Index |
Medium | 15 | Message Index |
Long | 20 | Message Index |
Heading | 13 | Message Index |
Documentation
Definition
Specifies the sequence number transferred with the container.
Use
Message indices exist for every conversation ID. This ensures the containers are processed in the right order. For each conversation ID, the client holds two message indices (also known as sequence numbers): one for inbound messages and the other for outbound messages.
Dependencies
Example
For example, when the framework or application creates an asynchronous container, the outbound message index is incremented and attached to the container.
History
Last changed by/on | SAP | 20070216 |
SAP Release Created in | 620 |