Step by Step guide of Report-to- Report Interface in BW Reporting Applies to: SAP BI 7.0. For more information, visit the Business Intelligence Home Page Summary This paper gives a detail understanding and use of Report-to-Report Interface in BW Reporting. The document guides to understand the various options available to drill down from one report to another. Also the steps will guide to learn the process of building RRI interfaces between reports. Author: Mohammed Nazeer Ali Company: Deloitte Consulting Created on:15 August 2009 Author Bio Mohammed Nazeer Ali is currently working in Deloitte Consulting India Pvt. Ltd. He is working on SAP BI 7.0 from last 3 years and has worked on ECC 6.0 and CRM 5.0 extraction. 2009 SAP AG 1
Table of Contents Introduction... 3 Scenario... 3 RRI Interface Functionality:... 3 Step1: setting up RRI... 3 Step2: setting up the RRI Assignment... 5 Step3: Results... 6 Related Content... 7 Disclaimer and Liability Notice... 8 2009 SAP AG 2
Introduction Report-to-Report Interface (RRI) help to enhance the capabilities of BW queries, and drilling through from one query to another. Setting up the query with the free characteristics and other options may not help the business user with granularity of data needed for decision making. Therefore, the use of RRI component may result handy. Report-to-Report Interface has many names, such as query jump targets (From a query, the destination to which you branch is called a Jump Target), drill through functionality, and the RRI naming conventions. All address the same functionality in SAP BW. Scenario To demonstrate the functionality and usage of RRI, the scenario uses two queries. One is the Orders and sales values for Sold to party (ZSD_C03_Q009). The other query is Open orders and quantity for Sold to party (ZSD_C03_Q001). RRI Interface Functionality: Please follow the steps below to understand the use of RRI in BW Reports. Step1: setting up RRI To get started with RRI setup, from the initial screen select SAP Menu Business Explorer Query Maintain Sender-Recipient Mapping. Also, can use the T-code: RSBBS as shown The t-code will display the RRI screen as shown. The RRI function works for query level and the InfoProvider-level (All queries of InfoProvider) as shown. For now, I will discuss only the query level RRI, as One Query process and choose ZSD_C03_Q009 query as the sender. 2009 SAP AG 3
To do this, use the F4 input help to view all the queries in the system. This paper uses Orders and sales values for sold to party (ZSD_C03_Q009). Click on the create option, and we will the screen below The sender/receiver relationship has several choices to choose from, the different report types available are Report Type BEx query BW Java Web Application BW 3.x Web Application BW Crystal Report InfoSet Query Transaction ABAP Report Web Address Own Report Type Description Jumps to a query that was created using BEx Query designer Jumps to a BEx Web Application that is an executed web template created using BEx Web Application Designer. Note: this function requires Java based runtime of SAP NetWeaver BW Same function as above, but used for SAP BW 3.x Web Application. Jumps to a formatted report in Crystal Enterprise. Jumps to an InfoSet query Jumps to a transaction in SAP system Jumps to an ABAP/4 report in SAP system Jumps to any web address and pass the parameters in the URL Jumps to any target of Web or SAP GUI for HTML. In this paper we identified the report type as BEx query. Next, the target system needs to be confirmed. The RRI gives option of selecting either a local system or source system. We will select the local system and the query used as a target is one set up to display open orders and quantity for sold to party (ZSD_C03_Q001) as shown 2009 SAP AG 4
Step2: setting up the RRI Assignment Click on the Assignment Details button, to select or identify the fields to be assigned from sender to receiver. To make changes to the individual fields choose the required settings from the dropdown list of the respective cells. In the example, I will select the type as InfoObject and field name 0SOLD_TO and selection type as single value as shown When the system calls up the receiver, the settings made in the Field assignments dialog box are set. This completes the necessary configuration settings for the RRI to work. Note: Jump targets that have been assigned to the BEx query cab be selected in Web Applications and in the BEx Analyzer. They can be accessed from the context menu under the GoTo function. 2009 SAP AG 5
Step3: Results The following illustration shows the execution of the sender (ZSD_C03_Q009), choose the Sold to Party and use the context menu option GoTo Open Orders (ZSD_C03_Q001) set as receiver. The result of initial setup of the RRI will allow the query jump. Open the BEx Analyzer and execute the Sender (ZSD_C03_Q009) as shown From the context menu of the Sold to Sony Electronics select GoTo Open orders as shown The RRI query jump will display the Receiver as shown 2009 SAP AG 6
Related Content Also, for more details please refer the following links https://forums.sdn.sap.com/thread.jspa?messageid=7846103#7846103 https://forums.sdn.sap.com/thread.jspa?messageid=7578814#7578814 https://forums.sdn.sap.com/thread.jspa?messageid=7642507#7642507 For more information, visit the Business Intelligence Home Page NAZEER ALI MOHAMMED 2009 SAP AG 7
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. 2009 SAP AG 8