This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
SAP BusinessObjects XI 3.1. For more information, visit the Business Objects homepage.
Summary
This document explains how to link two Web Intelligence (WebI) reports together through OpenDocument functionality in step-by-step manner. It explains the procedure to navigate from one WebI report to another; passing parameter values from a WebI report to other; passing on-click value from one WebI report to another; and displaying the linked report based on the parameter value passed to it.
Author: Vineeta Singh
Company: Infosys
Created on: 26 April 2010
Author Bio
Vineeta works at Infosys Technologies as a SAP BW developer. She has experience in both SAP BW and SAP BusinessObjects XI 3.1.
Steps to Link two WebI documents ................................................................................................................. 6
Steps to pass parameter values from one WebI document to another ........................................................ 13 Passing a Single Value .............................................................................................................................................. 13
Steps to pass on-click value as parameter value from one WebI document to another .............................. 20 Prompt Text in Target WebI document has Spaces ................................................................................................... 29
Related Content ................................................................................................................................................ 32
Disclaimer and Liability Notice .......................................................................................................................... 33
Step-by-step Guide to Linking WebI Documents using OpenDocument in SAP BusinessObjects Enterprise XI 3.1
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
OpenDocument is functionality in BusinessObjects which enables URL reporting and linking documents similar to RRI functionality in SAP BW.
It basically provides URL access to multiple document types by passing a URL string to a BusinessObjects Enterprise server. OpenDocument provides commands to control how reports are generated and displayed.
We can use OpenDocument feature in BusinessObjects Enterprise to create cross-system links to and from the following document types:
.wid: Web Intelligence version 6.x documents
.rep: Desktop Intelligence documents
.rpt: Crystal reports
.car: OLAP Intelligence Reports
This document deals with linking of two web intelligence documents (.wid) using OpenDocument feature implementation in a step-by-step manner.
OpenDocument URL creation syntax An OpenDocument URL is generally structured as follows in a java implementation as is the case in this example.
sType The file type of target document or report. • wid • rpt • car
sRefresh Indicates whether a refresh should be forced when the target document or report is opened.
• Y • N
sWindow Indicates whether the target report will open in the current browser window or whether a new window will be launched.
• Same (current browser window) • New (new browser window is launched)
lsS[NAME] Specifies a value for a single prompt. [NAME] is the text of the prompt.
hard-coded value or dimension object
lsM[NAME] Specifies multiple values for a prompt. [NAME] is the text of the prompt.
hard-coded values separated by semicolon(;) or dimension object
In case there are multiple prompts in target document e.g. Prompt1 accepts multiple input values,
Prompt2 accepts single input value and Prompt 3 accepts single input value, Use the combination of lsS and lsM parameters joined by ampersand (“&”) in the OpenDocument URL as follows.
Step-by-step Guide to Linking WebI Documents using OpenDocument in SAP BusinessObjects Enterprise XI 3.1
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
8. Run Report A. Click any hyperlink text in Plant column. Report B opens in the current window with data is displayed for Material Groups MG1 and MG2.
Step-by-step Guide to Linking WebI Documents using OpenDocument in SAP BusinessObjects Enterprise XI 3.1
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Here, lsS[NAME] parameter has [NAME]=MaterialGroup i.e. Prompt Text in Report B. ([MaterialGroup]) refers to Dimension Object name which is passed to lsSMaterialGroup parameter. This captures the value in the cell in MaterialGroup Column in Report A when clicked.
Step-by-step Guide to Linking WebI Documents using OpenDocument in SAP BusinessObjects Enterprise XI 3.1
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
In the following scenario, the prompt text in the target WebI document has spaces. In this case, the prompt text is “Enter Material Group” in Report B.
The lsS<prompt> parameter in OpenDocument URL in Report A should be as follows using URLEncode() function.
lsS” + URLEncode(“<prompt name having spaces>”) + “=” +([<object-name>])
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.