Receivers 

Features

In the following, we will explain how to deal with the peculiarities of the various receivers.

BEx Query

When the RRI is called, the sender query transfers the following filters to the receiver query:

·        Global filters

·        Navigation block values (dynamic filters exclusively from the presentation hierarchies)

·        Filters from the selected, restricted key figure

·        Filters from the selected drilldown characteristics

The system fills the variables and then the navigation block. In doing so, a unique characteristic assignment has to be possible. Selections from different InfoObjects can then be transferred if the InfoObjects reference the same basic characteristic. Hierarchy nodes are expanded in selections and can then be transferred to the respective InfoObjects.

If the sender and receiver include the same variables, the variables are handled separately again.

For more information, see BEx Query As a Receiver.

Web Application

For Web applications, the same applies as for BEx Queries. If a Web application contains multiple queries, the RRI is called for each query separately.

Crystal Report

When calling the RRI with a Crystal Report as the receiver, only the variables are filled. There is no transfer of filters as with BEx Queries.

Transaction and ABAP/4 Report

Calling the RRI with a transaction or an ABAP/4 Report as the receiver is done with the RRI from the SAP NetWeaver Application Server. This is possible in an ERP system, a CRM system or within the BI system. The selections are prepared by the BI system that does not recognize the transaction or the report. The assignment is transferred from the RRI of the SAP NetWeaver Application Server using inverse transformation rules. There must also be a complete chain from the DataSource of the source system to the InfoSource, through transformations up to the InfoProvider. This does not mean that data absolutely has to be loaded using this chain. If this chain does not exist, the RRI cannot transfer the selections to the source system.

Calling the RRI only works for fields with dictionary reference. For ABAP reports, this means that the parameter has to be

PARAMETERS param LIKE <table_field>

.   For transactions, this means that the Dynpro has to have a dictionary reference. Not every transaction can be called with the RRI of the SAP Application Server. For some transactions (such as SV03), you need to program a utility program if you still want to call it using the RRI.

See also Creating a Transaction As a Receiver.

InfoSet Query

The same applies to InfoSet queries as does for transactions and ABAP/4 reports.

Web Address

When calling the RRI with a Web address as receiver, the assignment details have to be maintained. You have to specify the name of the input field in the field name column. URL variables cannot be used.

See also Creating a Web Address As a Receiver.