ctu_params

[Former Member]

Hi all,

Please anyone let me know whether ctu_params used in BDC is a structure or a table. And tell me if we want to change the screen resolution we will be marking nothing in defaultsize but how to set the screen size after thaqt.

regards

Karthi.

[varma_narayana]

Hi..

<b>BDC Table control handling and CTUPARAMS usage</b>

In BDC.........while Recording the screen resolution for line items differs from system to system. .......how to make the coding fit for all the resolutions in case of BATCH INPUT METHOD :

While using CALL TRANSACTION ...we can declare a structure with type CTUPARAMS....and set the DEF SIZE to ‘X’....By doing so...the screen resolution becomes standard.no matter where u r executing the program.

And so we can write as....

CALL TRANSACTION 'VK11' OPTIONS FROM S_CTUPARAMS.

We can handle this in Session method also.

If you check the FM BDC_INSERT there is a parameter

CTUPARAMS LIKE CTU_PARAMS which can be used to fill the Default size.

This structure contains the follwing.

DISMODE : Display mode (like the MODE addition)

UPDMODE: Update mode (like the UPDATE addition)

CATTMODE: CATT mode (controls a CATT)

CATT mode can have the following values:

' ' No CATT active

'N' CATT without single-screen control

'A' CATT with single-screen control

DEFSIZE : Use default window size (Here we are handling those transaction by giving default window size) DEFSIZE = ‘X’.

RACOMMIT: Do not end transaction at COMMIT WORK

NOBINPT : No batch input mode (that is, SY-BINPT = SPACE)

NOBIEND : No batch input mode after the end of BDC data.

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

'X' Yes.

<b>Reward if Helpful.</b>