Success messages not displayed when ~singletransaction=1?

[Former Member]

Dear Experts,

We are using the CAT2 transaction for entering the timesheets.

when we save the timesheet we are immediately logged off and we get the message "Logged off successfully". The problem is we are unable to see the success message 'Your data has been saved".

We have set the following parameters.

~webgui 1

~webgui_simple_toolbar 1

~singletransaction 1

~transaction CAT2

With reference to note 959417 we came to know that we have to write a wrapper transaction using the "Call transaction" and call the actual transaction from there.

So we wrote a report program and called the transaction CAT2 from within the program and defined a new transaction for that with ZCAT2 and we changed the

sicf ~transaction parameters to ZCAT2 .

REPORT Z_TEST.

CALL TRANSACTION 'CAT2'.

is the report.

But still we are getting the same message "logged off successfully".

We are currently using Integrated ITS 7.00 and SAPKB70012 is the support package level.

Is there any way in which we can display the message without resetting ~singletransaction to 0

Waiting for your reply.

Thanks & Regards,

Subramanya

[Former Member]

Hallo,

indeed, success messages are sometimes not displayed when ~singletransaction is set. Success messages are often send when the transaction/the job is done. These success messages are displayed on the first screen of the next transaction. Since ~singletransaction does not display the first screen of the next transaction the message is invisible. As workaround you can implement a "wrapper" transaction to display the success message. The wrapper has to call the origin transaction using CALL TRANSACTION to stay onto the stack while the origin transaction is executed. When the origin transaction terminates the success message can be displayed in the wrapper transaction. Since we use CALL TRANSACTION in the wrapper, ~singletransaction will terminate the session when the wrapper transaction terminates.

[Former Member]

Hi all,

I am also facing similar issue in vl02n transaction. Appreciate if someone can provide solution to this issue. Thanks.

Regards

Vasu