topic Re: Why "SO_DEQUEUE_UPDATE_LOCKS" ? in Application Development and Automation Discussions

Why "SO_DEQUEUE_UPDATE_LOCKS" ?

Former Member — Tue, 10 Jun 2008 16:32:18 GMT

Hi friends... I ve come here to understand why the use of function SO_DEQUEUE_UPDATE_LOCKS in the code below.

CALL FUNCTION 'SO_DOCUMENT_SEND_API1'

EXPORTING

document_data = doc_chng

put_in_outbox = cc_x

commit_work = cc_x

TABLES

packing_list = objpack

contents_txt = ti_mensagem

receivers = ti_usuarios

EXCEPTIONS

too_many_receivers = 1

document_not_sent = 2

operation_no_authorization = 4

OTHERS = 8.

IF sy-subrc = 0.

SUBMIT rsconn01 USING SELECTION-SET 'INT' AND RETURN.

CALL FUNCTION 'SO_DEQUEUE_UPDATE_LOCKS'.

ENDIF.

Ok.... I know that the bold code is to send a mail instantly.

But why call that function(SO_DEQUEUE_UPDATE_LOCKS) after the rsconn01 submition?

Re: Why "SO_DEQUEUE_UPDATE_LOCKS" ?

Former Member — Tue, 10 Jun 2008 18:11:29 GMT

The problem is.... basis called saying that the use "SUBMIT rsconn01" is making the original Job works unproperly, not sending others mails, marking them as errors.

But at those codes, I don´t see the function "SO_DEQUEUE_UPDATE_LOCKS" after the submit rsconn01. So.... this function is really important? SO_DEQUEUE_UPDATE_LOCKS is used to make the rsconn01 work properly after forcing sending?

Re: Why "SO_DEQUEUE_UPDATE_LOCKS" ?

Former Member — Wed, 11 Jun 2008 11:04:29 GMT

Someone know the transaction to monitor the e-mails at the sap spool? (So I can see, if they get some error status while not using the SO_DEQUEUE_UPDATE_LOCKS) Or gonna need see SM37 Job stats for rsconn01 situation?

Re: Why "SO_DEQUEUE_UPDATE_LOCKS" ?

Former Member — Thu, 12 Jun 2008 17:16:28 GMT

Got another hint here at Sdn.... maybe I can find the status of the mail at SOOS or SOST tables.

Does anyone knows the diference between these tables? Wich one I can find info about mail at spool? It can provide me about mails marked as error?