Help required in getting the header details.

Question

Hi All ,
In my first WDA , I am showing the header details of Purchase Order for a input parameter  in table
and now I want to show the items details for that particular PO on lead selection of the the PO details
in my second application . How can I achieve the desired functionality .
Please help , any pointers regarding this ..
Thanks in Advance.

Answer 1

Hi ,
U need tto get the URL of the called application through method
construct_wd_url and generate the popup window for the second application with the above URL .
in ur first app , crate an event on lead selection of the table and write the following piece of code :
   DATA:
      w_url   type string,
      w_value type string.
         call method cl_wd_utilities=>construct_wd_url
        exporting
        application_name              = u2018 u2018 // here specify the name of the called application
      importing
        out_absolute_url              = w_url.
   * make the Value type compatible that has to be passed with the URL
  w_value = lv_ebeln.
* Attach the parameters and its value with the URL that
* have to be passed to the 2nd application
  call method cl_http_server=>append_field_url
    exporting
      name  = ' '   // input parameter here
      value = w_value
    changing
      url   = w_url.
* generate a popup window for the 2nd application with the above URL
  DATA lo_window_manager TYPE REF TO if_wd_window_manager.
  DATA lo_api_component  TYPE REF TO if_wd_component.
  DATA lo_window         TYPE REF TO if_wd_window.
  lo_api_component  = wd_comp_controller->wd_get_api( ).
  lo_window_manager = lo_api_component->get_window_manager( ).
  lo_window         = lo_window_manager->create_external_window(
                   url = w_url ).
  lo_window->open( ).
Now in the doinit of ur called application , u can get the value for that particular input parameter
[code}
DATA:
  lv_param type string.  
lv_param = wdr_task=>client_window->get_parameter( ' u2018  ).  // paramtr name
Now select the appropriate values in internal table for this and bind it to ur context node ..
I hope this helps..