SOST : email not going - still no entry in queue

[ashish_vikas]

Dear friends,

i have a problem where emails always stays in status - still no entry in queue (Message S0672).

these emails are always triggered by running a newly developed report.

this happens for few of these emails only, all other emails are working file, Send job is of 10 min frequency. So i hope, i have everythink working fine with SAPConnect configuration.. but need to find a problem reason/hint to ask ABAP person to loon into it.

If i do repeat send for this email, it goes well.

Can you please suggest.

**********************************************************Long text for Status text**************************************************************

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.

***********************************************************************************************************************************************************

thanks

ashish

[Former Member]

perhaps there is a situation in which the program sometimes completes without sending a COMMIT WORK? I'd be sure I had a COMMIT WORK as the last statement in my END-OF-SELECTION event.

[ashish_vikas]

solved, SAP Note 717265

[Former Member]

Explicit commit work does not work in update task and mostly this is seen and faced in transactions like PA30 PA40 etc...

Try with following,

CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1' IN BACKGROUND TASK

Hope it will work

[bharatbajaj]

Hi,

Add the below line along with the Call function :

DESTINATION 'NONE'

the FM call should look like.

CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'

       DESTINATION 'NONE'

       EXPORTING

         document_data              = l_wa_doc_data

         commit_work                = 'X'

       IMPORTING

         sent_to_all                = l_var_sent

       TABLES

         object_content             = l_tab_objcont

         receivers                  = l_tab_receiver

       EXCEPTIONS

         too_many_receivers         = 1

         document_not_sent          = 2

         document_type_not_exist    = 3

         operation_no_authorization = 4

         parameter_error            = 5

         x_error                    = 6

         enqueue_error              = 7

         OTHERS                     = 8.

[krishnakumar_karthickeyan]

Best answer