topic Re: CALL TRANSACTION - not returning error message in Application Development and Automation Discussions

CALL TRANSACTION - not returning error message

Former Member — Tue, 15 May 2012 11:55:02 GMT

Hi experts,

I try to: 'CALL TRANSACTION 'CJ88' USING gt_bdc MODE 'E' UPDATE 'S' MESSAGES INTO l_mes'. But l_mes not returning an error message. In fact error message is shown in popup window in CJ88 but in code I have no information that something went wrong. How can I get this message from this popup window? Thank you in advance.

Best regards

Pawel Smuda

Re: CALL TRANSACTION - not returning error message

laurent_fournier2 — Tue, 15 May 2012 12:10:38 GMT

Hello,

Change the mode from 'E' to 'N'.

Regards.

Re: CALL TRANSACTION - not returning error message

former_member186055 — Tue, 15 May 2012 12:11:29 GMT

Hello Smuda,

MODE 'E' means it'll stop the transaction when the error massage occured while calling transaction. I think, message which occured is type may be E(error) and it is displayed like I(Information), then it may happen.

MESSAGE E001(AA) with lv_msgv1 lv_msgv2 lv_msgv3 DISPLAY LIKE 'I'.

Regards,

Surya...SuryaPraveen

Re: CALL TRANSACTION - not returning error message

Former Member — Tue, 15 May 2012 12:22:39 GMT

Hi Pawel,

In the table i_mes you will have the MESSAGE TYPE, MESSADE Id and not the Message text. For the text you have to use the FM: MESSAGE_GET_TEXT.

Regards,

Raj..

Re: CALL TRANSACTION - not returning error message

former_member186055 — Tue, 15 May 2012 12:39:07 GMT

Smuda,

If you call the transaction in ERROR mode (E), then transaction is processed only when you corrected value(lead to error values). then there is no error message is raised after complete execution of the transaction. then there is no use adding of MESSAGES INTO l_mes to the call transaction. MESSAGES INTO l_mes is only works in mode N, display all screens. Message internal table is not filled in both E & A MODEs.

Regards,

Surya...SuryaPraveen

Re: CALL TRANSACTION - not returning error message

Former Member — Tue, 15 May 2012 13:54:52 GMT

This is a pretty difficult situation that is hard to overcome. If the messages are shown in a popup rather than being returned in the message table, the only solution I know of is to simulate the logic of the program that creates the popup before calling the transaction and creating your own message.

Rob

Re: CALL TRANSACTION - not returning error message

Former Member — Tue, 15 May 2012 14:08:07 GMT

Hi Rob,

you are right, and 'CJ88' dosen't work in the background. I will try to use a BAPI instead of CALL TRANSACTION.

Regards

Pawel

Re: CALL TRANSACTION - not returning error message

Former Member — Tue, 15 May 2012 14:23:03 GMT

See note 123726.

Rob

Re: CALL TRANSACTION - not returning error message

Former Member — Wed, 16 May 2012 09:37:35 GMT

Thanks Rob.

Re: CALL TRANSACTION - not returning error message

Former Member — Wed, 04 Sep 2019 05:27:29 GMT

I am also struck in same scenario. Can you elaborate in detail?