topic Re: Enqueue - Dequeue in Application Development and Automation Discussions

Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 07:29:10 GMT

Hello!

We want enqueue the execution of a FM. So, we do:

CALL FUNCTION 'ENQUEUE...'.

CALL FUNCTION 'DO_SOMETHING'.

CALL FUNCTION 'DEQUEUE'....

If an error message occurs on FM 'DO_SOMETHING', the function dequeue is not executed. Do you know how we can resolve this problem?

Thanks a lot!

Edited by: LM on Oct 6, 2008 9:29 AM

Re: Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 07:31:30 GMT

Hi,

you must be checking the sy-subrc before call the FM 'Dequeue'...

Re: Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 07:35:01 GMT

When the type of message is E, the program abort its execution and we can not do noting (we can't consult the sy-subrc).

Re: Enqueue - Dequeue

matt — Mon, 06 Oct 2008 07:39:49 GMT

When a transaction finishes, locks are automatically released (usually!).

What is the nature of the function module? SAP Standard? Which one? If not, then change the function module so that it DOES set the sy-subrc.

matt

Re: Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 07:42:32 GMT

CALL FUNCTION 'ENQUEUE...'.

CALL FUNCTION 'DO_SOMETHING'.

MOVE SY-SUBRC TO W_SUBRC.

CALL FUNCTION 'DEQUEUE'....

IF W_SUBRC NE 0.

*ERROR MESSAGE

ENDIF.

Re: Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 08:17:03 GMT

The Function Module is standard is "FMFR_CREATE_FROM_DATA". This function module show an error message and do not return. So, we can't do the dequeue.

Re: Enqueue - Dequeue

Former Member — Mon, 06 Oct 2008 08:20:44 GMT

I think we do not have any programable solution, we should contact basis team to remove the lock

Regards

Re: Enqueue - Dequeue

Former Member — Tue, 21 Jul 2009 16:13:34 GMT

Hello LM,

Have you solved you problem with FMFR_CREATE_FROM_DATA showing message without return? Could you please share the solution?

Thank you in advance!

Kirill

Re: Enqueue - Dequeue

Former Member — Thu, 18 Nov 2010 10:00:09 GMT

Allthough this is a rather old question, I still would like to post a possible answer (maybe helpful for people facing the same problem):

Just disable all exceptions in the function module in the source code and add the generic statement "error_message = 1".

Ofcourse you now need to handle messages after execution of the function module - messages will not be shown on screen anymore,

So the code should look like this:

CALL FUNCTION 'FMFR_CREATE_FROM_DATA'

EXPORTING

i_flg_checkonly = space

i_flg_commit = 'X'

TABLES

t_posdata = pr_posdata

CHANGING

c_f_headdata = pr_head_data

EXCEPTIONS

doctype_not_allowed = 1
error_occured = 2
OTHERS = 3.

error_message = 1.