Hierarchy
⤷ BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷ SO (Package) SAPoffice
Basic Data
Data Element | SOST_STATUS_INCONS |
Short Description | Send Status: Status Flag Inconsistent |
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 | Status |
Medium | 19 | Status Inconsistent |
Long | 38 | Still no entry in queue |
Heading | 38 | Still no entry in queue |
Documentation
Definition
A message was sent from the application. The current status of the message is 'Waiting'. However, no entry exist (yet) in the queue.
Use
This can be a normal interim status of a sent message. Preparations for entering the message in the queue for the SAPconnect send process are complete. As soon as the Persistence Service has put the message into the corresponding database table for the queue, the status changes to 'Waiting'.
If this status stays the same for too long, an inconsistent state exists. In many cases, the cause of this lies with the sending application. The Persistence Service first writes the data to the database when the application has set an explicit Commit Work. If this is missing, then the message is not put into the queue and is not recorded by the SAPconnect send process. On the send request overview, you can put the message in the queue again using retry, but you must look for the cause of the problem in the sending application itself.
Another cause of the problem may be that the corresponding entry in the queue was deleted manually before the send process recorded the message.
Dependencies
Example
History
Last changed by/on | SAP | 20050204 |
SAP Release Created in | 700 |