regarding bdc

[Former Member]

for what purpose we are using CTU_PARAM in BDC program

what are the parameters which can have

plz explain clearly with code and comments

[sreeramkumar_madisetty]

Hi

To handle the Table Controls in BDC we use CTU_PARAM structure.

Regards,

kumar

[Former Member]

"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".

check these links

;�

[Former Member]

thanks a lot

[Former Member]

Hi Rajesh,

This is used if you would like to do a commit work once call trnasaction is done. This has also got very important property, for example if your Screen resolution is different from others then the screen (Application) will be different that is you'll be having say 5 lines in your screen where as your friend will be having 8 or 10 so your program might fail in this case. If you set variable DEFSIZE as 'X' it will always use the default screen size and hence avoids error.

Hope this would have helped you.

Thanks,

Prashanth.

[Former Member]

Read below from sap help.

CALL TRANSACTION tcod OPTIONS FROM opt.

Addition OPTIONS FROM opt 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

If the OPTIONS addition is omitted, the following settings are valid for the control parameters:

DISMODE from the MODE addition

UPDMODE

from the UPDATE addition

CATTMODE

No CATT procedure active

DEFSIZE

Do not use standard window size

RACOMMIT

COMMIT WORK ends procedure successfully

NOBINPT

Batch input mode, that is SY-BINPT =X.

NOBIEND

Batch input mode also active after BDC data has been read

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers