screen resolutions

[former_member557020]

hi all,

could any one provide the code for how to handle screen resolutions while uploading the data

[former_member557020]

hi all,

could any one provide the code for how to handle screen resolutions while uploading the data

[Former Member]

data x_ctuparams type ctu_params.

x_ctuparams-updmode = 'S'.
x_ctuparams-dismode = 'N'.
x_ctuparams-defsize = 'X'.  "For default size resolution

call transaction '<TCODE>' using it_BDCDATA options from x_ctuparams.

Regards,

Ravi

[Former Member]

Re: screen resolutions

Posted: Apr 3, 2007 5:07 PM in response to: Sambasiva Divvela Reply E-mail this post

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.

Please close the Duplicate thread

Regards

Sudheer