topic Re: ctu_params in Application Development and Automation Discussions

ctu_params

Former Member — Wed, 23 Aug 2006 16:09:45 GMT

hi!

wat does the field <b>defsize</b> in the structure ctu_params mean actually?

i mean wat is default screen size?

where do we set it?

Wat is the use of it?

(we use this structure in call transaction tc1 using...options..)

Re: ctu_params

RichHeilman — Wed, 23 Aug 2006 16:14:00 GMT

You use this in BDC programming to make the screen size as one default size regardless of frontend size. This is so that the processing of table controls does not get messed up when the programming is set for 1 screen size and the actual runtime is seeing another size. If the resolution is bigger, then there will be more lines of a table control, which means that the program will need to handle it. I think I may have confused myself here, sorry.

Regards,

Rich Heilman

Re: ctu_params

Former Member — Wed, 23 Aug 2006 16:14:09 GMT

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.

Regards,

Ravi

Re: ctu_params

Former Member — Wed, 23 Aug 2006 16:14:38 GMT

This is for Default screen size for CALL TRANSACTION. It signifies the screen size will be constant irrespective of the screen resolution(which can vary for different user). The importance of this lies in programs(module pool) that contain table controls. With default screen size we can control the no of rows in the table control which otherwise may vary depending on the screen resolution.

DEFSIZE is the Selection as to whether the screens of the called transaction are displayed in the standard screen size. Values "X" (standard size), " " (current size).

sample.

data : x_ctu_params type ctu_params.

* To have default screen size, mode and update

  x_ctu_params-defsize = 'X'.
  x_ctu_params-dismode = 'X'.
  x_ctu_params-updmode = 'X'.

call transaction tscode using  bdcdata
                          options from x_ctu_params

Regards,

Richa

Re: ctu_params

venkata_ramisetti — Wed, 23 Aug 2006 16:17:26 GMT

Hi,

Please check this from SAP help.

Effect

This addition gives you control using the values of the components of the structure opt, which must be of the Dictionary type CTU_PARAMS. The components have the following meaning:

DISMODE

Processing mode (comparable with the MODE addition)

UPDMODE

Update mode (comparable with the UPDATE addition)

CATTMODE

CATT mode (controlling a CATT procedure)

The CATT mode can have the following values:

' ' No CATT procedure active

'N' CATT procedure without single screen control

'A' CATT procedure with single screen control

DEFSIZE

Use standard window size

RACOMMIT

COMMIT WORK does not end CATT procedure

NOBINPT

No batch input mode, that s SY-BINPT = SPACE.

NOBIEND

No batch input mode after BDC data has been read

The components DEFSIZE , RACOMMIT, NOBINPT, NOBIEND always take the following values:

'X' Yes

' ' No

Thanks,

ramakrishna

Re: ctu_params

Former Member — Wed, 23 Aug 2006 17:35:20 GMT

hi ravi kanth!

first of all thanq for ur valuable reply.

so when i'm doing bdc,if i set DEFSIZE = X,example for PO(PO has table control in items,isn't it), will this BDC program work for all screen resolutiobs?