Hierarchy
⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷ SO (Package) SAPoffice
Basic Data
Data Element | SOST_STATUS_RETRY |
Short Description | Send Status: Status Flag Retry |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BCS_BOOL | |
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 | 10 | Retry |
Medium | 19 | Status Retry |
Long | 38 | Waiting for Retry |
Heading | 38 | Waiting for Retry |
Documentation
Definition
A message was sent by the application. The status of the message is 'Waiting for Retry'.
Use
The message has already been recorded by the SAPconnect send process and sent externally. An error occurred during the transmission, which may only be temporary. The corresponding node in the SAPconnect administration contains a specified maximum wait time for a send retry. During this wait time, SAPconnect keeps trying to send the message at fixed time intervals. If the wait time has passed, the message is given the status 'Errors'.
The wait time begins the moment when a message on the corresponding node first encounters a temporary error. This time is also the time used for messages sent later. If the wait time has passed, all messages encountering a temporary error on this node are set to status 'Errors' directly. Only when a message has been sent over this node successfully (thereby correcting a temporary error), does the retry process become active again for this node.
Dependencies
Example
History
Last changed by/on | SAP | 20050204 |
SAP Release Created in | 700 |