Rsbbs Assignment Details Hair

Purpose

The purpose of this page is to clarify the understanding of the system logic and requirements in relation to report-report interface (RRI), when you jump to a target with Goto.

Overview

The report-report interface (RRI) allows you to call a jump target from a BEx query executed in Analysis. You can use the RRI to jump from the executed query (sender) to another report (receiver) containing more information. You can call targets in BW systems and beyond.

You can use the report-report interface to call targets that you have defined in your query. To be able to call the targets from executed queries, you must define the targets for the query with the sender/receiver assignment. The sender/receiver assignment is defined in transaction RSBBS in the BW system.

Transaction RSBBS

In Analysis, you can assign the following receivers:

  • Query
    • If you call a query with Goto, a new workbook is opened with the query.
  • Web address
  • The following targets are opened in the web browser:
    • ABAP transaction. The transaction must be classified for using SAP GUI for HTML.
    • ABAP Report
    • BEx Web Application (3.x and 7.0)
    • Crystal Report
    • Xcelsuis dashboard

To make the described RRI, you will need first to confirm that you fulfill the requirements of the SAP note 1739153 – “SAP BW Backend requirements for Analysis Office 1.3 or higher”.

For the assignment you will need to go to transaction RSBBS:

Select the query (sender):

Click to create:

On “Target System” area, you will select the target system. You can choose to jump to the same system that you are working or for a different one.

On “Report Type” area, you will choose the target report type that you will jump to. You can choose to jump to:

  • BW Query
  • BEx Web Application
  • BW 3.x Web Application
  • Crystal Report
  • BW XCelsius
  • Infoset Query
  • Transaction
  • ABAP Report
  • Web Address
  • Analysis for Office
  • Or to a specific document:
      • Attached Documents (via ArchiveLink)
      • Data Overviews from E-Recruiting
      • Data Overviews from Succession Planning
      • Employee Profile
      • Messages for Check Result
      • BWATR Object

On “Report”, you will choose the target Query or Object.

Click to apply and so you will define the target for the report-to-report jump (RRI).

Now, when you open your sender query, you will be able to right click and select “go to”

So you will be able to jump to the target query:

Related Content

Related Documents

You can find more information about the report-report interface and the sender/receiver assignment in the SAP NetWeaver documentation in the SAP Help Portal under http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/5b96c6517f2e24e10000000a42189b/frameset.htm.

Related SAP Notes/KBAs

1466118 Analysis Office hardware & software requirments
1518359 SAP BusinessObjects Analysis Office Release schedule

__________________________________________________________________________________________________________

Link to this page: https://wiki.scn.sap.com/wiki/x/Z7viGg

SAP BusinessObjects Analysis for Office tutorial: http://scn.sap.com/docs/DOC-7679

Analysis for Office SCN: http://scn.sap.com/community/businessobjects-analysis-ms-office

Analysis for Office main page: http://help.sap.com/boao

Analysis for Office Wiki page: http://wiki.scn.sap.com/wiki/x/kgxBGQ

Define the mapping in transaction RSBBS

The transaction RSBBS is used to create and maintain jump targets for one or several queries. In the "Assignment Details" of a specific jump target you can define how to map the infoobjects available in the sender query to the infoobjects available in the reciever query.

As long as no explicit mapping is defined by the user, the mappings of all infoobjects of the sender query are set to "Generic". In this case the the implicit rules described in the SAP Note 1053310 will apply.

Sometimes the functionality of these rules is not that trivial and might lead to some behaviour that is not expected in the first place. In the following I want to provide such a scenario where the usage of a "Generic" mapping leads to an unexpected behaviour of the RRI interface and I will explain how this behaviour can be analysed.

Sample Scenario

Sender Query: RRI_SENDER_QUERY

  • The query contains the following characteristics in drilldown: Country, Employee, Calendar Year/Month
  • The query does not contain any global filters

Receiver Query: RRI_RECEIVER_QUERY

  • The query contains the following characteristics in drilldown: Person, Calendar Year/Month
  • The query does not contain any global filters

Transaction RSBBS:

  • The query RRI_SENDER_QUERY contains the query RRI_RECEIVER_QUERY as a jump target
  • The mapping is set to "Generic" for all infoobjects:

Executing the jump

Now let us jump from the first line of the sender query to the receiver query:

1. Run the sender query:

2. Jump to the receiver query

As you can see from the screenshot above, the receiver report does not contain any data ("No Applicable Data Found."). The following filters have been automatically applied by the RRI Interface:

  • Calendar Year = 2010
  • Person = 90
    Filter: "Calendar Year = 2010"
    This filter can be easily explained as we jumped from the first row of the sender query an here Calendar Year/Month = 07.2010.

Filter: "Person = 90"
This filter seems rather confusing. In the sender query Person is not in drilldown and there is no filter applied on Person in the receiver query by default. So where does this filter come from?

Analyzing the jump

Let us jump again from the first line of the sender query to the receiver query but this time we activate the RRI debug flag when
executing the senderquery:

1. Run the sender query and activate the RRI debug flag:

2. Jump to the receiver query -> Debugger is opened

*The query stops at a predefined breakpoint in the function 'RSBBS_SELDR_TO_MAPPING'

  • In this function we can check the mappings identified on the sender side (independent from the receiver side). The information is stored in the internal table E_THX_MAPPING.

For now we just ignore the Debugger and continue the execution (by pressing button F8).

3. Debugger is opened a second time

  • The query stops again in the Debugger, this this at a predefined breakpoint in the form SHOW_TRANSFORMATION.
  • In this form we can check the mapping which is to be applied on the receiver side. The information is stored in the internal table I_THX_TRANSFORMATION_TO.

Again we just ignore the Debugger and continue the execution (by pressing button F8).

4. The Receiver query is displayed

  • Again the result of the receiver query is dipslayed but this time also detailed information on the mapping during the RRI jump is provided.

Given this information we see that the filters both on Calendar Year and Person comes from an attribute mapping:

The reason for this attribute mapping is as follows:

  • The receiver query does not contain the infobjects Employee or Calendar Year/Month but it contains the infoobjects Person (which is an attribute of Employee) and Calendar Year (which is an attribute of Calendar Year/Month). This behaviour is also explained in the SAP Note 1053310.
  • In case that the implicit attribute mapping on the infoobject Person should not occurs, it would be necessary to remove the generic mapping from the infoobject Employee in transaction RSBBS (the mapping on infoobject Person is irrelevant in this scenario!). You could either set the mapping on the infoobject Employee to "Delete" or explicitely map the infoobject Employee to the infoobject Employee.

    0 comments

    Leave a Reply

    Your email address will not be published. Required fields are marked *