topic Re: Screen Resolution in Application Development and Automation Discussions

Screen Resolution

Former Member — Thu, 10 Apr 2008 13:58:04 GMT

hi experts,

i had a interview question,

-> i am developing my bdc with 10 line items in my development server and in Onsite, it is showing only 5 line items. how come v adjust to get the same no, of line items in both the servers?

plz answer me...

Re: Screen Resolution

Former Member — Thu, 10 Apr 2008 21:30:36 GMT

Hi,

do this way ...

CALL TRANSACTION 'VA01' USING it_bdcdata

OPTIONS FROM OPT

MESSAGES INTO it_mesg.

opt of type ctu_params.

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

OPT-UPDMODE = 'S'. "synchronus update

OPT-NOBINPT = 'X'.

OPT-NOBIEND = 'X'.

OPT-DEFSIZE = 'X'. "Default size

Regards,

Re: Screen Resolution

venkat_o — Fri, 11 Apr 2008 02:32:43 GMT

Hi Sakthi Sri, Have a look at this . Use additon OPTIONS FROM <ctu_params> to Call Transction statement by specifying defsize = 'X'. Then problem will be solved.

DATA:
        w_params TYPE ctu_params,
        i_msgcoll  TYPE STANDARD TABLE OF bdcmsgcoll,
        i_bdcdata  TYPE STANDARD TABLE OF bdcdata.

  "structure of ctu_params.
  "----------------------
  "dismode   processing mode for call transaction using...
  "updmode   update mode for call transaction using...
  "cattmode  catt mode for call transaction using...
  "defsize   default screen size for call transaction using...
  "racommit  call transaction using... is not completed by commit
  "nobinpt   sy-binpt=space for call transaction using...
  "nobiend   sy-binpt=space after data end for call transaction using...

  w_params-dismode = 'A'. "All screen mode
  w_params-updmode = 'A'. "Asynchronous update
  w_params-defsize = 'X'. "standard size

  CALL TRANSACTION 'PA30' USING i_bdcdata MESSAGES INTO i_msgcoll OPTIONS FROM  w_params .

I hope that it helps you . Regards, Venkat.O