topic Re: BDC TABLE CONTROL in Application Development and Automation Discussions

BDC TABLE CONTROL

Former Member — Tue, 09 Jan 2007 08:33:10 GMT

Hi,

Can anyone provide me the code on how to use CTU_PARAMS in bdc table control

Re: BDC TABLE CONTROL

Simha_ — Tue, 09 Jan 2007 08:48:30 GMT

Hi,

Use CALL TRANSACTION 'XXX' OPTIONS FROM w_ctu_params.( type CTU_PARAMS)

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)

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

This might help u in better understanding...

Cheers,

Simha.

Reward if helpful...

Re: BDC TABLE CONTROL

Former Member — Tue, 09 Jan 2007 09:15:12 GMT

Hi,

"CTU_PARMS will force the BDC to use the standard default screen size (rather than being dynamic based on the user's settings. I think I explained that right, but all I know is that it keeps the BDC from behaving differently between users and makes things more consistent for coding logic".

Here's an example (note that DEFSIZE is the key to the solution here):

data: begin of tran_opts,

dismode type ctu_params-dismode value 'N',

updmode type ctu_params-updmode value 'S',

cattmode type ctu_params-cattmode,

defsize type ctu_params-defsize value 'X',

racommit type ctu_params-racommit,

nobinpt type ctu_params-nobinpt,

nobiend type ctu_params-nobiend,

end of tran_opts.

call transaction 'F-02'

using bdcdata

options from tran_opts

messages into bdc_messages