Receiver 

Features

In the following section, special features for dealing with various receivers are explained.

BEx Query

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

·        global filters

·        values in the navigation block (dynamic filters including the presentation hierarchy)

·        filters from the restricted key figure selected

·        filters from the drilldown characteristics selected

The system first fills the variables and then fills the navigation block. In order to do this, a unique characteristic assignment must be possible. Selections for various InfoObjects can then be transferred, as long as the InfoObjects reference the same basic characteristic. Hierarchy nodes are triggered in selections and can then be transferred to the respective InfoObjects.

Even if the sender and receiver contain the same variables, the variables are handled separately.

You can find more information under BEx Query as Receiver.

Web application

The same is true for Web applications as for BEx queries. If a Web application contains several queries, the RRI is called separately for each query.

Crystal Report

When the RRI is called with a Crystal Report as the receiver, the variables are filled afterwards. Unlike with BEx queries, filters are not transferred.

Transaction and ABAP/4 Report

You call the RRI with a transaction or an ABAP/4 report as the receiver using the Web Application Server RRI. You can do this in an R/3 system, a CRM system, or in the BW system. The selections are then formatted by the BW system, which is unacquainted with the transaction or report. Assignments are done by the Web Application Server RRI using inverse transformation rules. To this end, there must be a complete chain from the DataSource in the source system, via the InfoSource and update rules, to the data target.  It is not mandatory that data is loaded using this chain.  If this chain does not exist, the RRI cannot transfer the selections to the source system.

It is only possible to call the RRI for fields that have an ABAP Dictionary reference. For ABAP reports this means that the parameter has to be:

PARAMETERS param LIKE <table_field>.

For transactions this means that screens have to have an ABAP Dictionary reference. Not every transaction can be called with the Web Application Server RRI. For some transactions (for example SV03), you have to program an auxiliary program if you want to call them using the RRI.

On this, see Creating Transactions as Receivers.

InfoSet Query

The same is true for InfoSet queries as for transactions and ABAP/4 reports.

Web addresses

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

On this, see Creating Web Addresses as Receivers.