topic Re: Call transaction in Application Development and Automation Discussions

Call transaction

Former Member — Mon, 01 Jan 2007 10:25:19 GMT

Hi,

I created a simple program that runs 3 transactions CC01, CC02 and CC03.

The program runs the transactions sequentially at the same order above.

When the program run transaction CC02 the field "Change number" is close for input the same for transaction CC03.

But in case I run transaction CC02 before running CC01 the field "Change number" is open for input.

Any clue why?

How to solve this problem?

The program looks like that

Call transaction 'CC01'.

Call transaction 'CC02'.

Call transaction 'CC03'.

Former Member — Mon, 01 Jan 2007 11:06:15 GMT

When you loop the screen for changing the screen attributes, you can check for transaction code by sy-tcode.

When you execute CC01, enable the field for input and when you execute CC02, disable it for input.

loop at screen.

....

if sy-tcode EQ 'CC01'.

screen-input = '1'.

...

elseif sy-tcode EQ 'CC02'.

screen-input = '0'.

endif.

Regards,

Navneet.

Former Member — Mon, 01 Jan 2007 12:33:15 GMT

Thanks for the answer but I think u miss the point.

These are SAP transactions that I'm calling and I do not handle any screen

Clemenss — Mon, 01 Jan 2007 15:17:25 GMT

I think this is because locks are set and checked. Check the locks during the run with transaction SM12 (ST12?)

Regards,

Clemens

Former Member — Mon, 01 Jan 2007 17:09:49 GMT

Hi,

How you are calling??Are you building BDCDATA to call the transaction..

Thanks,

Naren