What happens technically if I launch a BI object (e.g. report, query or web application) via the Java / EP runtime?
Technically a Launcher-iView (com.sap.ip.bi.bex) is being parametrized. For example if the object is a formatted report it is the parameter REPORT=xyz. That means technically a parametrized iView is executed (The portal navigation is per default not visible, only the iView directly in a browser window). You can save such an object directly in a portal role. Just create a BI iView, in our example the parameter REPORT=xyz has to be specified. The objects are also available via BI favorites or via the BI PFCG roles. Here the URL is being generated with placeholders similar to the ABAP runtime approach. Queries & Enterprise Reports are opened within a default template. The templates (for example the report default template 0REPORT_DEFAULT_TEMPLATE can be copied and modified according to your needs. In general however we recommend to stick with the default templates. The default templates are designed for enhanced viewing experience, they are not particularly designed to be easily changeabl
Related Questions
- Suppose I call a COM object from a .NET application, but COM object throws an error. What happens on the .NET end?
- What happens technically if I launch a BI object (e.g. report, query or web application) via the Java / EP runtime?
- What is a Web Clipping Application (WCA) / Palm Query Application (PQA)?
