Skip to Content
author's profile photo Former Member
Former Member

Call url for BEX Query result


I am developping an application which needs to call several BEX Queries with parameters (filter values) and receive the result of each report

as a csv file. All these results will then be analysed by the calling application. I am not a bw expert and wondering if there is a way to build the url of a bex query in order to tell bex to run the query with the passed parameters and return the result as a csv file ...

Thank you


Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jan 08, 2014 at 08:14 PM


    If you execute your bex in web and pass the parameters intended then execute your screen then I think next screen URL will all the parameters init.. Just give a try as I don't have system in front of me to try.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 08, 2014 at 09:13 PM

    Hi Thierry,

    You can call Bex Web URL using following URL format.

    Case 1) If you are directly applying filter on InfoObjects at Bex web URL :

    http://<Application server>:<port Number>/SAP/BW/BEX?&QUERY=<Query Name>&FILTER_IOBJNM=<Infoobject to be be filter>&FILTER_VALUE=<Filter value>

    Case 2) If you are using variables to pass filter value:

    http://<Application server>:<port Number>/SAP/BW/BEX?&QUERY=<Query Name>&var_name_1=<Variable Name 1>&var_value_ext_1=<value for Variable 1>



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 08, 2014 at 09:14 PM


    You can call the query url passing on parameters/variables through the URL but I don't see you get that returned as a csv file.

    hope that helps


    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Thierry,

      CSV file output can be achieved using Open hub service (OHD) present in SAP BW.

      But here again there will be some limitations like to pass parameters and filters at run time,still it can be manageable.

      Again ease of OHD solution depends on which SAP BW version you are using.

      Case 1) If you are on BW 7.3 then make Transformation from Bex query to OHD and keep output format as CSV, there will be limitations that you have to apply all static filters at Bex query level to make it source.

      Case 2) If you are on SAP BW 7.0 then use infoprovider as source for OHD , select all query fields as fields for OHD and keep filters at DTP level.

      Limitation persists same in both the cases, have to support static filter.

      Just check this solution if it is suffice.

      Or I have solution for Bex Output as xml format , in that xml run time filters are very much possible.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.