topic Re: Call Transaction behaviour in Application Development and Automation Discussions

Call Transaction behaviour

Former Member — Mon, 01 Jul 2013 20:12:00 GMT

In my program I am passing on some values to Call Transaction 'CJ9C' using bdc_data. The objective is the called transaction should show result to the user and then the control should be returned to the calling program once user presses back button. However its not happeneing and the called transaction does NOT show anything to user but the control immediately returns to the calling program.

I tried sevaral options from ctu_param but its not happeneing.

Any clues would be helpful.

Thanks in advance

Re: Call Transaction behaviour

Former Member — Mon, 01 Jul 2013 20:17:15 GMT

Hi Sam,

Post the code that calls the transaction. Make sure you used the mode 'A' to call BDC in foreground and check in debugging whether the control is transferred to the called transaction.

Regards,

Karthik

Re: Call Transaction behaviour

Arun_Prabhu_K — Tue, 02 Jul 2013 03:17:47 GMT

Hi Sam,

I am posting sample code for your reference which calls CO02 with user values and returns to calling program on pressing back. Check if it is useful.

bdcdata-program = 'SAPLCOKO1'.

bdcdata-dynpro = '110'.

bdcdata-dynbegin = 'X'.

bdcdata-fnam = 'CAUFVD-AUFNR'.

bdcdata-fval = production_order.

APPEND bdcdata.

bdcdata-fnam = 'BDC_OKCODE'.

bdcdata-fval = '=ENTE'. "Enter command

APPEND bdcdata.

opt-dismode = 'E'.

CALL TRANSACTION 'CO02' USING bdcdata OPTIONS FROM opt.

Regards.

Re: Call Transaction behaviour

Former Member — Tue, 02 Jul 2013 05:21:20 GMT

Hi Sam,

Are you using call transaction in side loop?? and when you loop start are you refreshing BDCDATA structure???

Please post your code once.

Thanks & Regards,

buz_sap

Re: Call Transaction behaviour

Former Member — Wed, 03 Jul 2013 13:45:56 GMT

Hello All,

Thanks for the response and sorry for not responding.

@Arun,

yes the code is similar to what you have given.

One important thing that I fogto to add in earliar posting is that the same code works FINE in background and NOT in foreground.

In foregreaound if I use 'A' mode it at least shows me it is going inside the code of CJ9C but if I use anyother mode , it is not even showing me its going insde.

Re: Call Transaction behaviour

former_member188827 — Wed, 03 Jul 2013 14:00:55 GMT

Please use addition MESSAGES INTO msg_tab and see if you get any message after call transaction.

CALL TRANSACTION 'CO02' USING bdcdata OPTIONS FROM opt MESSAGES INTO msg_tab.

Regards

Re: Call Transaction behaviour

Former Member — Wed, 03 Jul 2013 18:30:50 GMT

I observed its not even going into code of CJ9C, the messages table is empty.

Re: Call Transaction behaviour

venkateswaran_k — Wed, 03 Jul 2013 18:38:45 GMT

Is it working in Foreground ? - End to End ? OR

it is working in background only...

Also, kindly update your sample code...

Secondly, how you are supplying data to BDC... How are you reading the file?

Please note that, any GUI functions like upload/download does not work in Background....

Regards,

Venkat

Re: Call Transaction behaviour

Former Member — Wed, 03 Jul 2013 18:42:55 GMT

If there is an explicit commit in the transaction, BDC is terminated immediately. If this is true of your process, there is nothing (for practical purposes) that you can do to make your proposed solution work.

Neal