Hierarchy
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation⤷
SLL (Application Component) Global Trade Services⤷
/SAPSLL/CORE (Package) Legal & Logistics Services: Global Basis
Basic Data
| Data Element | /SAPSLL/BCOVL |
| Short Description | Sequence Number of Request Message for Serialization |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /SAPSLL/INOVL | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | Seq. No. |
| Medium | 15 | Sequence No. |
| Long | 20 | Sequence Number |
| Heading | 10 | Seq. No. |
Documentation
Definition
Sequence number of the request message processed last in a communication scenario based on the request/confirmation template.
The serialization concept at the application level is designed to have the two applications that are involved manage sequential numbers: one sequence number for outbound messages and one for the processed inbound messages.
Each time a request message is sent, the system of the service consumer increments the number for outbound messages and places this number in the message attribute changeOrdinalNumberValue. Each time an inbound message is successfully processed, the system of the service provider persists the value that is found in the inbound message in attribute changeOrdinalNumberValue and, in turn, places that value in subsequent configuration messages of the other application in the element baseChangeOrdinalNumberValue. This way, both applications, in a sense, map each other's sequence numbers to their own respective change status.
Request messages carry the attribute changeOrdinalNumberValue, but not the element baseChangeOrdinalNumberValue. Each time the system of the service consumer sends a new change status via request message for the same document, the system increments the value for changeOrdinalNumberValue. The system of the service provider persists the value of the attribute changeOrdinalNumberValue of the request message processed last in a separate persistence X. The same system simultaneously keeps a sequence number for its own change status in a persistence Y.
The confirmation message requires both values: baseChangeOrdinalNumberValue and changeOrdinalNumberValue. The provider system places the value X in element baseChangeOrdinalNumberValue; this is the value of the attribute changeOrdinalNumberValue from a request message that was received or processed last. In contrast, the value of field Y is placed in the attribute changeOrdinalNumberValue of the confirmation message.
This way, the system of the service consumer detects (a) whether the confirmation matches its own most recent change status, or (b) whether the replies to the same change status contained "overtakers".
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20141106 |
| SAP Release Created in | 901 |
