SO672 Still no entry in queue

[Former Member]

We have a QM notification user-exit, where we need to send emails.

I used FM:SO_NEW_DOCUMENT_ATT_SEND_API1 to send the emails.

The issue we are having is that sometimes the emails do not go in the queue. I get a grey cross marks icon in the status in SOST. The error says "SO672 Still no entry in queue"

I realized that i did not have the commit_work ='X' in exporting parameter for FM:SO_NEW_DOCUMENT_ATT_SEND_API1

But i am afraid if i add the commit_work in the user-exit, it is going to cause some other problems, So i am not sure what to do. Is there any other way to handle this problem?

Will doing the below code helps? Did anybody do this in the user-exit and worked?

Call function 'SO_NEW_DOCUMENT_ATT_SEND_API1' in background task

exporting commit = 'X'

Thanks,

Gopi.

[Former Member]

We have a QM notification user-exit, where we need to send emails.

I used FM:SO_NEW_DOCUMENT_ATT_SEND_API1 to send the emails.

The issue we are having is that sometimes the emails do not go in the queue. I get a grey cross marks icon in the status in SOST. The error says "SO672 Still no entry in queue"

I realized that i did not have the commit_work ='X' in exporting parameter for FM:SO_NEW_DOCUMENT_ATT_SEND_API1

But i am afraid if i add the commit_work in the user-exit, it is going to cause some other problems, So i am not sure what to do. Is there any other way to handle this problem?

Will doing the below code helps? Did anybody do this in the user-exit and worked?

Call function 'SO_NEW_DOCUMENT_ATT_SEND_API1' in background task

exporting commit = 'X'

Thanks,

Gopi.

[mvoros]

Hi,

I do not think that IN BACKGROUND TASK will help in your case. This is from SAP documentation:

IN BACKGROUND TASK|UNIT (transactional RFC, tRFC, and qRFC) 
The IN BACKGROUND addition pre-marks the remotely called function for execution and starts it with the COMMIT WORK command.

Instead you should try STARTING NEW TASK

STARTING NEW TASK (asynchronous RFC, aRFC) 
The STARTING NEW TASK addition continues processing of the calling program as soon as the remotely-called function is started, without waiting for it to end. The results can be stored in callback routines.

But this way has one problem. This call will open new session for user and if user has already 6 sessions FM will fail.

Note that you cannot exceed the maximum number of six main modes in dialog processing. Otherwise, an error message is triggered. 

BTW: which user exit do you use?

Cheers

[Former Member]

Yes the Background Task did not work. I am using QQMA0014-QM/PM/SM: Checks before saving a notification.

I am planning to put the email code in another program and call that program using the SUBMIT statement and passing all the email data to the new program.

Thanks,

Gopi.