Execute a batch input in background as foreground mode

[Former Member]

Hello experts,

we are working on some call transaction developement.

During tests we saw that some 1 screen is not displayed when call transaction is executed in background.

When IDOC and  the call transaction is executed with WE19, it works fine.

When we process the IDoc with RBDAPP01, in background it is KO, because 1 screen is not called in the call transaction when executed in background.

Do you know if it is possible to execute a BDC/Call transaction in background, but simulated as if was executed on foreground ?

We tried to modify some CTU_PARAMS like DISMODE , NOPINBT but without success.

I know there is new DISMODES available in SAP as DISMODE = "Q".

Could this help in our situation ?

Thx for the help,

Newbie.

[Former Member]

Hello!

This is a trail guess!

Try to use CTU_PARAMS-DEFSIZE = 'X' , At times, if the screen size is not aligned with standard screen size, few fields may not be updated. This may lead to data inconsistence and leads in error.

Thank you,

Regards,

Kavi SAP

[Former Member]

Hello Kavi,

we tested defsize = 'X' already, but it does not fix the issue.

Thx for your suggestion.

Newbie

[Former Member]

what transaction you are calling?

[Former Member]

Hello Roy,

CEWB transaction.

Thx

Newbie

[Former Member]

While doing the recording via SHDB did you select "Simulate Background mode" checkbox?

R

[Former Member]

The SHDB was initially done without "simulate background mode" it seems.

Then, the issue has been identified during the tests when executing the program in background (via RBDAPP01).

After analyzing the SHDB we saw that a screen was not called in "simulate background mode".

And was displayed without selecting "simulate background mode".

As we will have to process these idocs/call transaction in background, we need to find a way to have this screen called even in background mode.

We tried to change some options of CTU_PARAMS uring the call transaction (DISMODE, DEFSIZE, NOBINPT,...) but we did not find a solution yet.

Thx for the help.

Newbie.

[Former Member]

Then I don't think the screen is meant to be called in background and that is the way the transaction is designed. Did you check for OSS notes?

R

[Former Member]

Hello,

yes and we found an OSS note (782607) which is indicating the same issue but even with this note installed, the call transaction is not working in background.

The note seems note corrcting the BTC in background.

This is why I was wondering a way to execute a BTC in background simulated like foreground exectution.

Is there some alterntative options to go through thi kind of issue ?

Newbie.

[former_member185414]

Hello,

Another suggestion would be to check the mismatch in functional configuration which is calling the screen in foreground mode and not in background mode.Then rectify the same so that even behavior is observed in foreground and background. Then it should work.This is based on the assumption that the checkbox  for 'Simulate Background Mode' in SHDB is not working.

Also if this does not work, then try this. Create another SE38 program and create a background job where you submit to the standard program of CEWB transaction just to see whether CEWB T-code as per system's current configuration can create entries in background mode.

BR.

[Former Member]

Hello,

Please try using racommit = 'X' and updmode = 'S' that might solve your problem.

Data: wa_ctuparams type CTU_PARAMS.

clear wa_ctuparams.

wa_ctuparams-racommit = 'X'.

wa_ctuparams-dismode  = 'N'.

wa_ctuparams-updmode  = 'S'.

Call Transaction 'CEWB' USING bdcdata

                        OPTIONS FROM wa_ctuparams

                        MESSAGES INTO messtab.