Calling Transactional Iview

[Former Member]

Hi ,

I am using the following code to call a trasaction iview , its not going to the iview thats been created. Any suggestion on this please.

method ONACTIONACTION_PROCESS .

data lr_componentcontroller type ref to ig_componentcontroller .

data l_api_componentcontroller type ref to if_wd_component.

data lr_port_manager type ref to if_wd_portal_integration.

lr_componentcontroller = wd_this->get_componentcontroller_ctr( ).

l_api_componentcontroller = lr_componentcontroller->wd_get_api( ).

lr_port_manager = l_api_componentcontroller->get_portal_manager( ).

Data: target type string.

Data: nmode type string.

target = 'pcd:portal_content/WORKBENCH'.

nmode = 'INPLACE'.

call method lr_port_manager->navigate_absolute

exporting

NAVIGATION_MODE = nmode

navigation_target = target .

endmethod.

Thanks,

Kumar

[vivekananthan_sellavel]

hi kumar,

Ur coding part is correct

CALL METHOD lo_portal_manager->navigate_absolute

EXPORTING

navigation_target = PCD Path

• navigation_mode = IF_WD_PORTAL_INTEGRATION=>CO_SHOW_INPLACE## This is optional

Please confim the PCD Path.

Regards

Vivekanantha.S

Edited by: vivekananthan sellavel on Apr 2, 2009 6:53 AM

[Former Member]

Hi,

The PCD path is correct , i took it as it is in portal PCD .Not sure why its not displaying

Thanks,

Kumar

[Former Member]

I have done a similar navigation. I had to call a dynpro in another system(svr2) other then where my wda application resides in Portal(svr1). I have done it by creating a transaction(SE93) and connecting the dynpro to the transaction. I had to pass also some business data to the dynpros.

Here are the two simple steps you might like taking.

1. Create SAP Transaction iView and set the destination to where the created Transaction resides(svr2). Set the other parameters correspondingly. For the Destination you have to make sure if that the destinations is created in Portal.

2. Call it from your WDA Application.

Example Code.

  data lo_api_component  type ref to if_wd_component.
  data lo_portal_manager type ref to if_wd_portal_integration.
  data  param_list type wdy_key_value_list.
  data  param like line of param_list.
  data: ln_lmtbl type ref to if_wd_context_node,
        le_lmtbl type ref to if_wd_context_element,
        ln_importing_f3 type ref to if_wd_context_node,
        le_importing_f3 type ref to if_wd_context_element,
        lv_limit_sector type zflm_dte_limit_sector,
        lv_limit_type type zflm_dte_limit_type,
        lv_limit_to type zflm_dte_limit_to,
        lv_limit_from type zflm_dte_limit_from,
        lv_limit_guid type zflm_r3_dte_lim_id_32,
        lv_lmguid_16 type sysuuid-x,
        lv_limit_date type dats.
  ln_lmtbl = wd_context->path_get_node( `LIMITTABLESEL.LIMITTABLESEL` ).
  le_lmtbl = ln_lmtbl->get_element( ).
  ln_importing_f3 = wd_context->path_get_node( `F3_GET.IMPORTING_F3` ).
  le_importing_f3 = ln_importing_f3->get_element( ).
  le_importing_f3->get_attribute( exporting name =  `I_KEYDATE` importing value = lv_limit_date ).
  le_lmtbl->get_attribute( exporting name = `LIMIT_TYPE` importing value = lv_limit_type ).
  le_lmtbl->get_attribute( exporting name = `LIMIT_SECTOR` importing value = lv_limit_sector ).
  le_lmtbl->get_attribute( exporting name = `LIMIT_FROM` importing value = lv_limit_from ).
  le_lmtbl->get_attribute( exporting name = `LIMIT_TO` importing value = lv_limit_to ).
  le_lmtbl->get_attribute( exporting name = `LIMIT_GUID` importing value = lv_limit_guid ).
  " Prepare Parameter List for the input into the SAP Transaction iView.
  lv_lmguid_16 = lv_limit_guid.
  param-key = 'p_lguid'. "Dynpro field names
  param-value = lv_limit_guid.
  insert param into table param_list.
  clear param.
  param-key = 'r_ltype-low'.
  param-value = lv_limit_type.
  insert param into table param_list.
  clear param.
  param-key = 'r_sector-low'.
  param-value = lv_limit_sector.
  insert param into table param_list.
  clear param.
  param-key = 'p_dateu'.
  param-value = lv_limit_date.
  insert param into table param_list.
  clear param.
  param-key = 'p_sing'.
  param-value = 'X'.
  insert param into table param_list.
  param-key = 'p_run'.
  param-value = lv_limit_date.
  insert param into table param_list.
  clear param.

  lo_api_component = wd_comp_controller->wd_get_api( ).
  lo_portal_manager = lo_api_component->get_portal_manager( ).

  call method lo_portal_manager->navigate_absolute
    exporting
      navigation_target   = 'pcd:portal_content/Limit_Manager/drill_thru_svr2'
      navigation_mode     = if_wd_portal_integration=>co_show_external
      window_name         = 'Drill Through in SVR2'
      target_title        = 'Drill Through'
      business_parameters = param_list
    .

In my case the SAP Transaction iView has id = drill_thru_svr2

Hope it could help.

Regards,

Farhan

[Former Member]

Hi Farhan,

Am doing similarly , Created a Transactional Iview for TC:PA20 in the Portal Content , In portal as well i was able to look into the preview of the transaction code PA20. I used the follwing code to navigate this Transactional IView in the ABAP WEBDYNP which is been linked to an action button .There is no view or dump comming up when i hit the button .

The code is as below for navigation :

data lr_componentcontroller type ref to ig_componentcontroller .

data l_api_componentcontroller type ref to if_wd_component.

data lr_port_manager type ref to if_wd_portal_integration.

lr_componentcontroller = wd_this->get_componentcontroller_ctr( ).

l_api_componentcontroller = lr_componentcontroller->wd_get_api( ).

lr_port_manager = l_api_componentcontroller->get_portal_manager( ).

Data: target type string.

Data: nmode type string.

target = 'pcd:portal_content/workbench/wkb_iview_p20'.

nmode = 'INPLACE'.

call method lr_port_manager->navigate_absolute

exporting

NAVIGATION_MODE = nmode

navigation_target = target .

Just wondering wht else i was missing ..any suggestion would be helpfull..

Thanks,

Kumar.

[raja_thangamani]

Please make sure you have mentioned the correct target..

target = 'pcd:portal_content/WORKBENCH'.

Raja