topic Controlling Screen Resolution in BDCs in Application Development and Automation Discussions

Controlling Screen Resolution in BDCs

Former Member — Thu, 22 Mar 2007 08:09:41 GMT

Hi,

Can any one explain about the process for Controlling Screen Resolution in BDCs.

Thanks & Regards,

Rajesh.

Re: Controlling Screen Resolution in BDCs

Simha_ — Thu, 22 Mar 2007 08:13:27 GMT

Hi,

Do something like this.

data x_ctuparams type ctu_params.

x_ctuparams-defsize = 'X'. " This would freeze the resolution in any system

x_ctuparams-dismode = 'N'.

x_ctuparams-updmode = 'S'.

call transaction <TCODE> using it_bdcdata options from x_ctuparams.

Hope this resolves your query.

Cheers,

Simha.

Reward all the helpful answers.

Re: Controlling Screen Resolution in BDCs

Former Member — Thu, 22 Mar 2007 09:09:50 GMT

Hi Amruta,

Check this coding.

WA_CTU_PARAMS type ctu_params.

WA_CTU_PARAMS-DISMODE = 'N'. "no screen mode

WA_CTU_PARAMS-UPDMODE = 'S'. "synchronus update

WA_CTU_PARAMS-NOBINPT = 'X'.

WA_CTU_PARAMS-NOBIEND = 'X'.

WA_CTU_PARAMS-DEFSIZE = 'X'. "Default size

CALL TRANSACTION 'VA01' USING it_bdcdata

OPTIONS FROM WA_CTU_PARAMS

MESSAGES INTO it_mesg.

Default size will play good role in terms of resoultion. in one system in table control you can see 10rows, but in others system it will show 20 records. it depends on resoultion. but when you set the default size then it will take same (default screen size) in all the systems when you run BDC.

Hope this resolves your query.

Reward all the helpful answers.

Regards

Re: Controlling Screen Resolution in BDCs

Former Member — Fri, 30 May 2008 07:01:28 GMT

Hi,

If u write table control bdc program in 14'' monitor screen, then if the same program u run at different monitor size, then the screen resolution problem comes in to the picture,

like, u get 5 records in table control in one screen, and some other records in other screen, to avoid this screen resolution problem we use CTU-PARAMS Structure.

In ur program u have to set

defsize type ctu_params-defsize value 'X',

Then u will be free of screen resolution problem.

Fill the str CTU_PARAMS-defsize = 'X' and pass in CTU stmnt as

call transaction 'XXX' options using t_bdcdata ctu_params.

Analysing :

1. If nothing works, then we have to

some ifs & buts.

2. There shall be normally

2-4 different kinds of resolution

on various users comptuers.

3. Based on this,

we have to know beforehand,

what will be the number of rows

in the table control.

4. The user can be given

a selection/paraemter

for resolution

eg. 800x600

1024x100

axb

etc.

5. Based on this, we will hardcode

in the program (based upon our knowledge/recording

which we have seen and done)

we will hardcode

the number of lines

in the VARIBLE.

6. Then we can simply use this variable

for our LOOP and logic purpose.

7. It will be the responsibiltiy of the

use to CHOOSE THE CORRECT resolution,

on the selection-screen.

For screen resolution use ctu_params, with default size

Data : f_option type ctu_params,

f_option-updmode = 'S'.

f_option-defsize = 'X'.

f_option-dismode = 'N'.

call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.

CALL TRANSACTION tcode... OPTIONS FROM opt

... OPTIONS FROM opt

Effect

Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:

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

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

' ' No

If you do not use the OPTIONS FROM addition, the following control parameter settings apply:

DISMODE

From addition MODE

UPDMODE

From addition UPDATE

CATTMODE

No CATT active

DEFSIZE

Do not use default window size

RACOMMIT

Successful end on COMMIT WORK

NOBINPT

Batch input mode active ( SY-BINPT = X

NOBIEND

Batch input mode remains active after the BDC data

Hope it makes u understand...

Reagrds,