topic Re: Screen resolution problem after call transaction BDC in Application Development and Automation Discussions

Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 06:25:04 GMT

Hi Experts,

My current screen resolution is 1280 by 1024.

I am doing a call transaction on VA01 using CTU_Params.

I did set defsize = 'X'.BDC is a success.

But the issue is once the control get back to the current session after executing BDC the screen size is reduced/resolution is similar what was for VA01 BDC.

Only after clicking on some thing the resolution is becomming back to normal that is 1280 by 1024.

But my client would not like to click on any thing.

Can any suggest me whats the issue.

Re: Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 06:40:54 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.

Re: Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 06:46:18 GMT

Hi,

This is for Default screen size for CALL TRANSACTION. It signifies the screen size will be constant irrespective of the screen resolution(which can vary for different user). The importance of this lies in programs(module pool) that contain table controls. With default screen size we can control the no of rows in the table control which otherwise may vary depending on the screen resolution.

DEFSIZE is the Selection as to whether the screens of the called transaction are displayed in the standard screen size. Values "X" (standard size), " " (current size).

sample.

data : x_ctu_params type ctu_params.

To have default screen size, mode and update

x_ctu_params-defsize = 'X'.

x_ctu_params-dismode = 'X'.

x_ctu_params-updmode = 'X'.

call transaction tscode using bdcdata

options from x_ctu_params

Re: Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 06:55:25 GMT

Hi Prince Thanks for the reply.

Please see the below code i wrote .

The BDC should be an Open BDC

*"----

""Local interface:

*" IMPORTING

*" VALUE(LV_MODE) TYPE APQI-PUTACTIVE DEFAULT 'A'

*" VALUE(LV_UPDATE) TYPE APQI-PUTACTIVE DEFAULT 'L'

*" TABLES

*" IT_BDCDATA STRUCTURE BDCDATA OPTIONAL

*" IT_BDCMSGCOLL STRUCTURE BDCMSGCOLL

*"----

DATA : LS_OPTIONS TYPE CTU_PARAMS.

LS_OPTIONS-DISMODE = LV_MODE. " 'A'

LS_OPTIONS-UPDMODE = LV_UPDATE. " 'L'

LS_OPTIONS-DEFSIZE = 'X'.

LS_OPTIONS-NOBINPT = 'X'.

LS_OPTIONS-NOBIEND = 'X'.

CALL TRANSACTION 'VA01' USING IT_BDCDATA

OPTIONS FROM LS_OPTIONS

MESSAGES INTO IT_BDCMSGCOLL.

COMMIT WORK.

There is no problem from with BDC but the issue is after returning from BDC the current screen resolution is set to the BDC one.

Re: Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 07:00:03 GMT

Hi,

Try to clear the fields NOBINPT, NOBIEND in the structure.

LS_OPTIONS-NOBINPT = SPACE.

LS_OPTIONS-NOBIEND = SPACE.

And also try to use Update mode as 'S' ( synchronous).

Rgds,

Bujji

Re: Screen resolution problem after call transaction BDC

Former Member — Fri, 30 May 2008 07:15:50 GMT

I bujji tried that as well but still the problem exist.

Re: Screen resolution problem after call transaction BDC

Former Member — Mon, 03 Nov 2008 13:50:21 GMT

Hi Venkat,

Please make the DEFSIZE = ' '. (Space)

this will solve your problem.

Best Regards,

Deepa Kulkarni