Launch transaction without launchpad

[Former Member]

Hi All,

I have to launch an transaction in FPM without using launchpad for which I'm using the LAUNCH_TRANSACTION method of IF_FPM_NAVIGATE_TO. Below pasted is the code that I'm executing

DATA: lo_fpm        TYPE REF TO if_fpm,
        lo_fpm_nav    TYPE REF TO if_fpm_navigation,
        lo_fpm_nav_to TYPE REF TO if_fpm_navigate_to,
        ls_tcode      TYPE fpm_s_launch_transaction,
        lt_messages   TYPE fpm_t_t100_messages,
        lt_param      TYPE apb_lpd_t_params,
        ls_param      TYPE apb_lpd_s_params,
        ld_error      TYPE boole_d,
        lv_tcode      TYPE sytcode.

  lv_tcode = 'MM42'.

  lo_fpm = cl_fpm_factory=>get_instance( ).

  lo_fpm_nav_to = lo_fpm->get_navigate_to( iv_instance_sharing = abap_true ).

  ls_tcode-header_text = wd_comp_controller->go_channel->gs_act_det-link_text.
  ls_tcode-tcode = lv_tcode.
  ls_tcode-system_alias = 'ZRE_SDW'.
  ls_tcode-gui_type = 'WIN_GUI'.
  ls_tcode-pers_dialog = 'DIA_BUA_CCMONITOR'.
  ls_param-key = 'MATNR'.
  ls_param-value = 'B02'.
  APPEND ls_param TO lt_param.
  ls_tcode-parameter = lt_param.

  CALL METHOD lo_fpm_nav_to->launch_transaction
    EXPORTING
      is_transaction_fields = ls_tcode
    IMPORTING
      et_messages           = lt_messages
      ev_error              = ld_error.

But the transaction is not coming up.

I've also checked with the standard examples FPM_TEST_NAVIGATION_2 which doesn't use the launch pad and also FPM_TEST_NAVIGATION that uses a launch pad, however even the standard examples are not bringing up and result.

I'm using the Net Weaver release 710 version 7100.4.14.3136

SAP_BASIS 701 0003 SAPKB70103

SAP_ABA 701 0003 SAPKA70103

SAP_APPL 604 0003 SAPKH60403

Is there any patch that needs to be applied or any changes to the code?

Thank you.

Regards,

Indu.

[Former Member]

Hi Indu,

Where did you test this application ? Did you try creating an iview and add that to a role and test it in portal ? Or are you trying to test it from ECC(from SE80 or SICF) ?

Your code looks absolutely fine and I am sure it would work if it's tested from portal. If it's not working from portal, then I would suggest you should request your BASIS team to check the appropiate System definition at System Administration - System Landscape. Please make sure that the System alias maintained over there is used in your coding.

Let us know if it still gives you a problem.

Regards

Raja Sekhar

[yesrajkumar]

Hello,

It is interesting for me, after going through your issue. I tried launching the Abap Webdynpro application without using the transaction LPD_CUST.

I got a similar response as you. On debugging I came to know that they are using BADI implementations to actually make it work. I made my own ZBADI implementation and that Worked!!!.

For launching the transaction, have a glance at the enhancement spot APB_LAUNCHPAD. There are around 9 BADI definitions and each definition has many implementations. Try to make use of these BADI definitions and implement your logic accordingly.

For launching the Abap Webdynpro application I used the following code and the BADI implementation(ZLAUNCHPAD_IMPLEMENT) for the definition BADI_APB_LPD_BROWSER_ONLY_URL.

Even the launch url method worked for me(doesnu2019t require any implementations)

data: lo_fpm type ref to if_fpm,

lo_fpm_nav type ref to if_fpm_navigation,

lo_fpm_nav_to type ref to if_fpm_navigate_to,

is_webdynpro_fields type fpm_s_launch_webdynpro,

et_message type fpm_t_t100_messages,

ev_error type boole_d.

lo_fpm = cl_fpm_factory=>get_instance( ).

lo_fpm_nav_to = lo_fpm->get_navigate_to( iv_instance_sharing = abap_false ).

is_webdynpro_fields-header_text = 'Raj testing the application'.

is_webdynpro_fields-wd_namespace = 'sap'.

is_webdynpro_fields-wd_application = 'yraj_fpm_navigate_fpm'.

is_webdynpro_fields-wd_configuration = 'YRAJ_FPM_NAVIGATE_APP'.

is_webdynpro_fields-system_alias = 'SAP_ECC_ERECRUITING'.

• DATA: IS_URL_FIELDS TYPE FPM_S_LAUNCH_URL.

*

• IS_URL_FIELDS-HEADER_TEXT = 'Raj testing the application'.

• IS_URL_FIELDS-URL = 'https://********* /sap/bc/webdynpro/sap/yraj_fpm_navigate_fpm?sap-wd-configid=YRAJ_FPM_NAVIGATE_APP&sap-system-login-basic_auth=X&sap-client=095&sap-language=EN'.

*

• call method lo_fpm_nav_to->LAUNCH_URL"WEBDYNPRO_ABAP

• EXPORTING IS_URL_FIELDS = IS_URL_FIELDS

• IMPORTING ET_MESSAGES = ET_MESSAGE

• EV_ERROR = EV_ERROR.

call method lo_fpm_nav_to->launch_webdynpro_abap

exporting is_webdynpro_fields = is_webdynpro_fields

importing et_messages = et_message

ev_error = ev_error.

Regards,

S Rajkumar

[ashish_shah]

Hi Rajkumar,

I have referred the code provided by you to call my WebDynpro Application using URL.

However when the called webDynpro Application is being called in new Window , it asks for log in details again.

Is there any way to avoid this logon ?

I know it is somebody else's thread and i should not be asking my question here , but i need you to answer this.

so posting in this thread.

My apologies for the same.

Regards,

Ashish Shah

[Former Member]

Hi Ashish,

I would suggest, you should refer the User Management property category in the system defined in portal. Ensure that appropriate settings are maintained to ensure SSO.

Regards

Raja Sekhar

[Former Member]

Hi Indu,

I am right now looking for the same information (launch transaction without launchpad).

Have you by now discovered the solution or was there any other update?

Thanks & Kind Regards,

Robert

[Former Member]

Any updates ?