step-by-step guide to linking webi documents using ... · step-by-step guide to linking webi...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Step-by-step Guide to Linking WebI

Documents using OpenDocument in

SAP BusinessObjects Enterprise XI

3.1

Applies to:

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.

https://www.sdn.sap.com/irj/boc

Step-by-step Guide to Linking WebI Documents using OpenDocument in SAP BusinessObjects Enterprise XI 3.1


© 2010 SAP AG 2

Table of Contents

Overview ............................................................................................................................................................. 3

Steps to Link two WebI documents ................................................................................................................. 6

Steps to pass parameter values from one WebI document to another ........................................................ 13 Passing a Single Value .............................................................................................................................................. 13

Passing Multiple Values ............................................................................................................................................. 16

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



© 2010 SAP AG 3

Overview

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.

http://<servername>:<port>/OpenDocument/opendoc/openDocument.jsp?<parameter1>&<parame

ter2>&...&<parameterN>

Ampersand (&) is used to join all the parameters.

ServerName and port refers to the BO Enterprise server name and port.

Parameters to be used in our example are iDocID, sType, sRefresh, sWindow, lsS, lsM.

Following is the brief description of the parameters to be used.

Parameter Description Valid Values

iDocID Document identifier. Document identifier (InfoObjectID).

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.



© 2010 SAP AG 4

lsM<Prompt1-text>=<value1>;<value2>;<value n>&lsS<Prompt2-text>=<value1>&lsS<Prompt3-

text>=<value1>

Now let us create two sample Web Intelligence (WebI) reports which can be used further to show linking together using OpenDocument.

Report A: Inventory Report with details on Plant, Issued and Received Stock.

Report B: Inventory Report with details on Material hierarchy, Material Group and Total Stock.

Create a mandatory prompt on MaterialGroup dimension object with Prompt Text as “MaterialGroup”.



© 2010 SAP AG 6

Steps to Link two WebI documents

1. Right-click Report B. Click Properties. A window displays the document information.

2. Make a note of the ID of the document. In this example ID of Report B is 5241. This ID is used to

refer to Report B while creating OpenDocument statement for linking Report A to Report B.

3. Open Report A in Edit Report mode.

4. Right-click the cells of the Plant Column.

5. Click Hyperlinks > New Hyperlink. A new window appears.



© 2010 SAP AG 7

6. Type the following statement in the new window.

http://<servername:port>/OpenDocument/opendoc/openDocument.jsp?iDocID=5241&sType=w

id&sRefresh=Y&sWindow=Same

7. Click the Parse button. In this example, IDocID= 5241 (ID of Report B), sType = wid (as target document is in Web intelligence document format).



© 2010 SAP AG 8

Once Parse button is clicked, following screen displays with the parts of the URL parsed into sections

depending on parameters specified in OpenDocument URL.



© 2010 SAP AG 9

8. Specify the Tool Tip and Target Window as follows. Click OK.



© 2010 SAP AG 11

We can view the formula generated by this URL code.

9. Go to Edit Report Mode in Report A. Click View Structure button.

10. Double-click Plant Column. Press Ctrl+Enter.

The following generated formula is visible.



© 2010 SAP AG 12

11. Run Report A. Place the cursor on Plant column. It will show the tooltip text.

12. Click on any hyperlink text in Plant column in Report A.

The prompt created on Report B opens in the current window. On specifying the prompt values for

MaterialGroup, Report B opens in the current window.



© 2010 SAP AG 13

Steps to pass parameter values from one WebI document to another

Passing a Single Value

Sample Use Case: Displaying the material details report (Report B) for material group „MG2‟ on selecting any Plant in Report A.


2. Right-click on the Plant column cells. Click Hyperlinks > Edit Hyperlink.

3. Add a parameter lsSMaterialGroup=MG2.

4. Click Parse button > OK.



© 2010 SAP AG 14

Here, lsS[NAME] parameter has [NAME]=MaterialGroup i.e. Prompt Text in Report B. Single value passed to lsSMaterialGroup is MG2.

We can view the formula generated by this URL code below.

5. Go to Edit Report mode in Report A.

6. Click the View Structure button > double-click Plant Column.

7. Press Ctrl+Enter.




© 2010 SAP AG 15

8. Run Report A. Click any hyperlink text in Plant column. Report B opens in the current window with data displayed only for MaterialGroup=MG2.



© 2010 SAP AG 16

Passing Multiple Values

Sample Use Case: Displaying the material details report (Report B) for material group „MG1‟ and „MG2‟ on selecting any Plant in Report A.


2. Right-click the Plant column cells.

3. Click Hyperlinks > Edit Hyperlink. Add a parameter lsMMaterialGroup=MG1;MG2.


Here, lsM[NAME] parameter has [NAME]=MaterialGroup i.e. Prompt Text in Report B.

Multiple values passed to lsMMaterialGroup are MG1 & MG2.



© 2010 SAP AG 17

We can view the formula generated by this URL code.


6. Click View Structure button. Double-click Plant Column.





© 2010 SAP AG 18

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.



© 2010 SAP AG 20

Steps to pass on-click value as parameter value from one WebI document to another

1. Open Report A in Edit Query mode.

2. Drag one more dimension object MaterialGroup in the Result Objects pane.

3. Run the query and save the report.

Sample Use Case: Displaying the material hierarchy report (Report B) for material group selected in Report A.


2. Right-click the MaterialGroup column cells. Click Hyperlinks > Edit Hyperlink

3. Add parameter lsSMaterialGroup=([MaterialGroup]).


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.



© 2010 SAP AG 26

We can view the formula generated by using the following URL code.


6. Click View Structure button. Double-click MaterialGroup Column.





© 2010 SAP AG 27

8. Run Report A and click on MG1 value in MaterialGroup column. Report B opens in the current window with data for MaterialGroup=MG1 only.



© 2010 SAP AG 28

9. Run Report A and click on MG2 value in MaterialGroup column. Report B opens in the current window with data for MaterialGroup=MG2 only.



© 2010 SAP AG 29

Prompt Text in Target WebI document has Spaces

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>])


2. Click View Structure button. Double-click MaterialGroup Column.

3. Press Ctrl+Enter. Edit the lsS<Prompt-text> parameter in the formula editor as follows.

4. Click tick icon to check the formula for correctness. Click OK. .

="<a

href=\"http://<servername:port>/OpenDocument/opendoc/openDocument.jsp?iDocID=5241&sTy

pe=wid&sRefresh=Y&sWindow=Same&lsS" + URLEncode("Enter Material Group") + "="

+([MaterialGroup])+ "\" title=\"Navigate to Report B\" target=\"_self\"

nav=\"web\">"+[MaterialGroup]+"</a>"



© 2010 SAP AG 30

5. Go to View Results button.

6. Right-click any cell in the MaterialGroup column > click Hyperlinks > Edit Hyperlink.

The following Hyperlink code is generated from the formula.

http://<servername:port>/OpenDocument/opendoc/openDocument.jsp?iDocID=5241&sType=wid&

sRefresh=Y&sWindow=Same&lsS" + URLEncode("<prompt name having spaces>") +

"=([<Object-Name>])



© 2010 SAP AG 32

Related Content

How to Use The openDocument URL Command

WebI trick - drill among multiple reports

SAP BusinessObjects Community

For more information, visit the Business Objects homepage.

http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/800f7400-bf3e-2b10-fa81-c6c74f457ab4?QuickLink=index&overridelayout=true

http://wiki.sdn.sap.com/wiki/display/BOBJ/WebI+trick+-+drill+among+multiple+reports

http://www.sdn.sap.com/irj/boc

https://www.sdn.sap.com/irj/boc



© 2010 SAP AG 33

Disclaimer and Liability Notice

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.