SAP ABAP Data Element SOST_STATUS_ACTIVE (Send Status: Status Flag In Processing by Send Process)
Hierarchy
SAP_BASIS (Software Component) SAP Basis Component
   BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
     SO (Package) SAPoffice
Basic Data
Data Element SOST_STATUS_ACTIVE
Short Description Send Status: Status Flag In Processing by Send Process  
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 Active 
Medium 19 Status 
Long 38 In Processing by Send Process 
Heading 38 In Processing by Send Process 
Documentation

Definition

A message was sent by the application. The status of the message is 'Being processed by send process'.

Use

Send process has read this message from the queue and is about to send it externally.

This status can be a normal interim status. After the send process has run, the message is given the status 'Sent', 'Transmitted' or 'Errors'.

If this status stays the same for a long time, or if no send process is currently running in the system, then an error has occurred during the send process (such as canceled externally). Unlike in previous releases, such messages are not automatically kept in the queue, as in some cases it is the message itself that causes the cancelation (for example, timeout for extremely large documents) and can therefore bring the entire send activity to a standstill, if it is processed again every time the send process runs.

In a case like this, check whether the error reoccurs when trying to send the message again by looking in the send request overview. If it does, then the message is most probably causing the error itself. Check the document contents and also the application sending the document.

Dependencies

Example

History
Last changed by/on SAP  20050204 
SAP Release Created in 700