CALL TRANSACTION - SKIP FIRST SCREEN

[Former Member]

Hi Experts,

I have a requirement where i should use call transaction method and skip the first screen .

but the Syntax "Call transaction tcode and skip first screen" is not solving my issue.

is there any other way to achive this.

send me the sample code if possible.

[Former Member]

Hi Krithika

For using CALL TRANSACTION <tcode> AND SKIP FIRST SCREEN, we have to make sure all required values exist in the first screen to proceed to the next screen.

Letting us know the transaction code you are using might help in better advices from friends here.

Regards

Eswar

[Former Member]

Am using BDC - Call Transaction Method and the Tcode se37(For Function Modules) and i have to skip the First Screen.

[dru_marcellana]

Hi,

Before calling the command "CALL TRANSACTION..", add the code "SET PARAMETER ID 'LIB' field <variable>. Where the <variable> stores the FM name.

reward points if useful,

Dru

[Former Member]

u'll have to use SET PARAMETER command to set value of parameter-id of the values that exists on first screen and pass some value to those fields.

to know pameter id u can right click on any field and then view its tech. settings

reward if useful

keep rockin

vivek

[Former Member]

The screen contains fields for which an input has to be given.

so, check the parameter id of these fields ( in technical settings) and pass the respective values and the call the screen and skip the first screen.

without these input values the control does not go further to rhe next screen.

[Former Member]

Hi Krithika

Can the below code help you???

DATA: gt_bdcdata  TYPE STANDARD TABLE OF bdcdata,
      gw_bdcdata  TYPE bdcdata.

  SET PARAMETER ID 'LIB' FIELD 'TH_POPUP'.

  gw_bdcdata-program = 'SAPMS38L'.
  gw_bdcdata-dynpro = '1009'.
  gw_bdcdata-dynbegin = 'X'.
  APPEND gw_bdcdata TO gt_bdcdata.

  CLEAR: gw_bdcdata.
  gw_bdcdata-fnam = 'BDC_OKCODE'.
  gw_bdcdata-fval = '=TEST'.
  APPEND gw_bdcdata TO gt_bdcdata.

  CALL TRANSACTION 'SE37' USING gt_bdcdata
       mode 'E'.

Kind Regards

Eswar

[Former Member]

HI

Check this,It works as expected..

CLASS EVENTHANDLER IMPLEMENTATION.

METHOD HANDLE_HOTSPOT_CLICK.

READ TABLE g_t_final INTO g_r_final INDEX e_row_id-index.

CASE e_column_id.

WHEN 'VBELN'.

SET PARAMETER ID 'AUN' FIELD g_r_final-vbeln .

CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN .

WHEN 'VBELNPO'.

SET PARAMETER ID 'BES' FIELD g_r_final-vbelnpo.

CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.

WHEN 'VBELNOA'.

SET PARAMETER ID 'VLM' FIELD g_r_final-vbelnoa.

CALL TRANSACTION 'VL33N' AND SKIP FIRST SCREEN.

WHEN 'VBELNSH'.

SET PARAMETER ID 'VL' FIELD g_r_final-vbelnsh.

CALL TRANSACTION 'VL03N' AND SKIP FIRST SCREEN.

WHEN 'VBELNFO'.

SET PARAMETER ID 'VF' FIELD g_r_final-vbelnfo.

CALL TRANSACTION 'VF03' AND SKIP FIRST SCREEN .

WHEN 'BELNR'.

SET PARAMETER ID 'BLN' FIELD g_r_final-belnr.

SET PARAMETER ID 'BUK' FIELD g_r_final-bukrs.

SET PARAMETER ID 'GJR' FIELD g_r_final-gjahr.

CALL TRANSACTION 'FB03' AND SKIP FIRST SCREEN .

ENDCASE.

ENDMETHOD. "HANDLE_HOTSPOT_CLICK

ENDCLASS. "EVENTHANDLER IMPLEMENTATION

Praveen

Hope it helps.

[Former Member]

Hi Pravin,

Thanks for the reply.. can u please tell me frm the above code of yours how did u find on that VLM is the parameter ID to be set before calling VL33N transaction ?