Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with call transaction.

Former Member
0 Kudos

Hi guys,

Im recording a transaction with the following options:

Update mode: Asynchronous

CATT mode: No CATT

X Default size

X Cont. After Commit.

Blank, Not a Batch Input Session

Blank, Simulate Background Mode

I access one options of the menu and the recording is workin ok,

my problem is that when i use that BDC DATA, with call transaction, stops after the first Commit,

and i need to continue after the commit, is there any way to do that will CALL TRANSACTION?

Im using as follow:

CALL TRANSACTION 'PC00_M32_CEDT'

USING bdcdata

MODE 'A'

UPDATE 'S'.

tks in advance

1 ACCEPTED SOLUTION

Former Member
0 Kudos

U need to pass CTU_PARAMS parameters as ..

data : param like CTU_PARAMS.

params-DISMODE = 'A'.

params-UPDMODE = 'S'.

params-DEFSIZE ='X'.

params-RACOMMIT = 'X'.

CALL TRANSACTION 'PC00_M32_CEDT'

USING bdcdata options params.

6 REPLIES 6

Former Member
0 Kudos

please check mode

mode 'A': display all screen

mode 'N': background processing - does not stop

0 Kudos

Tks Ralf,

but with N, stops after the first commit =( too, and does not continue with rest of the bdcdata.

0 Kudos

Then there screen field issue,you have to record properly then try it.

Thanks

Seshu

Former Member
0 Kudos

Hi Javier,

CALL TRANSACTION tcod ... MODE mode

The specified processing mode can accept the following values:

'A' Display screen

'E' Display screen only if an error occurs

'N' No display

If the addition MODE is not specified, the processing mode is set to 'A' .

The MODE Parameter

You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:

A Display all. All screens and the data that goes in them appear when you run your program.

N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.

E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.

Have a look at below link for details:

Using CALL TRANSACTION USING for Data Transfer

I hope it helps.

Former Member
0 Kudos

U need to pass CTU_PARAMS parameters as ..

data : param like CTU_PARAMS.

params-DISMODE = 'A'.

params-UPDMODE = 'S'.

params-DEFSIZE ='X'.

params-RACOMMIT = 'X'.

CALL TRANSACTION 'PC00_M32_CEDT'

USING bdcdata options params.

0 Kudos

tks A LOT!!

now its working fine!