CTU_PARAMS

[Former Member]

hello all

can anybody tell me what is the role of CTU_PARAMS In Call Transaction Method

Edited by: swamy katta on May 13, 2008 10:56 AM

[Former Member]

Refer to this related thread

[Former Member]

Hi,

DEFSIZE = 'X' means the screen size will be constant irrespective of the screen resolution.

Say you are doing a bdc for some transaction which has X number of lines in a table control when resolution is some A.

If you change the resolution to some other value say B, the number of visible line wil change to Y.

You cannot know how many lines are visible to handle your BDC logic at run time. If the defsize is not set to 'X', then it may lead to errors in BDC.

so in your call transaction statement, we use this defsize.

x_ctu_params-mode = 'N'.

x_ctu_params-update = 'S'.

x_ctu_params-defsize = 'X'.

call transaction 'VA01' using t_bdcdata options from x_ctu_params.

Check sample code

code

data: begin of i_options occurs 0.

include structure ctu_params.

data: end of i_options.

refresh : i_bdc, i_message, i_options.

move : 'N' to i_options-dismode,

'L' to i_options-updmode,

c_x to i_options-defsize.

append i_options.

call transaction v_tcode using i_bdc options from i_options

messages into i_message.

[/code]

Regards

Kiran Sure

[Former Member]

Hi Swamy,

Call transaction <tcode> using BDCDATA mode A/E/N/P

update S/A options from Messages into messtab

Instead of giving mode and update options we use this structure CTU_PARAMS

The CTU_PARAMS structure has the components

1.DISMODE --->Specified by Mode addition

2.UPMODE -

---

>Specified by update addition

3.CATTMODE -

---

>Enables CATT for complex transactions.

Normally batch input is data transfer where as Computer aided test tool is for complex trasactions

4.DEFSIZE -

---

>Default size of window

5.RACOMMIT

6.NOBIEND

I don't know abt 5 & 6.

I hope this is useful for you.Award points if useful

thanks,

Ravee..

Edited by: ravee on May 13, 2008 10:29 PM

Edited by: ravee on May 13, 2008 10:30 PM