Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to Handle the Screen Resolution while doing BDC ? ----- Very Urgent plz

Former Member
0 Kudos

How to Handle the Screen Resolution while doing BDC ?

Very Urgent

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

You need to use the CTU_PARAM structure alon with the call transaction statment.


--------------------------------------------------------------------------------
**Sturcture of CTU_PARAM
**DISMODE : Display mode (like the MODE addition 'A' , 'E', 'N') 
**UPDMODE: Update mode (like the UPDATE addition 'S', 'A') 
**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
--------------------------------------------------------------------------------

DATA : L_OPTION TYPE CTU_PARAMS, "Parameter string for runtime of CALL TRANSACTION
L_SUBRC TYPE SYSUBRC.

L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.

CALL TRANSACTION 'FK01' "FK01-Vendor master creation
USING IT_BDCDATA
MESSAGES INTO IT_MESSTAB
OPTIONS FROM L_OPTION.

Regards

Vasanth

2 REPLIES 2

Former Member
0 Kudos

Hi,

You need to use the CTU_PARAM structure alon with the call transaction statment.


--------------------------------------------------------------------------------
**Sturcture of CTU_PARAM
**DISMODE : Display mode (like the MODE addition 'A' , 'E', 'N') 
**UPDMODE: Update mode (like the UPDATE addition 'S', 'A') 
**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
--------------------------------------------------------------------------------

DATA : L_OPTION TYPE CTU_PARAMS, "Parameter string for runtime of CALL TRANSACTION
L_SUBRC TYPE SYSUBRC.

L_OPTION-DEFSIZE = 'X'.
L_OPTION-DISMODE = P_MODE.
L_OPTION-UPDMODE = 'S'.

CALL TRANSACTION 'FK01' "FK01-Vendor master creation
USING IT_BDCDATA
MESSAGES INTO IT_MESSTAB
OPTIONS FROM L_OPTION.

Regards

Vasanth

Former Member
0 Kudos

Hi,

Use this Code.

DATA : opt TYPE ctu_params.

opt-dismode = 'N'.

opt-defsize = 'X'.

CALL TRANSACTION tcode USING bdcdata OPTIONS FROM opt MESSAGES INTO messtab.

Reward points if useful.

bye