SAP ABAP Data Element MEREP_LP (Last Sequence Number Processed)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
⤷ BC-MOB (Application Component) SAP NetWeaver Mobile - Use subcomponents
⤷ S_ME_DATA (Package) Mobile: data replication
Basic Data
Data Element | MEREP_LP |
Short Description | Last Sequence Number Processed |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT4 | |
Data Type | INT4 | 4-byte integer, integer number with sign |
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 | LP |
Medium | 15 | Last Processed |
Long | 32 | Last Sequence Number Processed |
Heading | 10 | LP |
Documentation
Definition
Sequence number of the last message processed for the mobile ID.
At runtime, this value defines the sequence number with which the system should start processing the request messages from the client of the mobile ID.
Procedure
The value is normally used for reference purposes only. However, the administrator can change this value when correcting errors.
Cases where this value could be used:
- A request message from the client is lost during synchronization and you are sure that it is no longer possible to retrieve the message.
=> Set the value to the sequence number of the lost message. - A request message from the client is processed on the server, but the server was not able to complete the processing of this message and the status remains I-Partial.
=> Set the value to the sequence number of the incompletely processed message.
The value can only be changed to a larger value than the current value. In this way the system avoids unintended double processing of request messages, which could be crucial for upload messages.
Examples
Dependencies
Definition
History
Last changed by/on | SAP | 20070216 |
SAP Release Created in | 620 |