BEx Query as Recipient

Use

You can assign a BEx Query in BW as recipient to another BEx Query as sender.

Features

In order to be able to call a query as a recipient with the RRI you need to be aware of a few guidelines during query definition.

General

Characteristics that are to be filled from the sender query must be defined as free characteristics. A hierarchy node restriction can also be transferred to free characteristics as a property, for example.
Changeable variables for the recipient query are not filled by the RRI.
Selections for various InfoObjects are transferred when the InfoObjects have the same reference characteristic.

See also the section BEx Query under Receivers.

Using Hierarchies

When using hierarchies in the query, you should be aware of the following cases:

Sender and receiver queries use the same hierarchy or hierarchies that are based on the same basic characteristic.

Jumping from one node in the hierarchy of the sender query to the same node of the hierarchy in the receiver query works as usual. The hierarchy settings are transferred with the RRI.

Sender and receiver queries use different hierarchies:

The hierarchy setting for the receiver query remains unchanged and the selections for the RRI are deleted. The system filters by leaves in the node.

Note

A few InfoObjects are different from one another, but they are treated as assignable by the system. This is a special development for Business Content. For example, values are transferred from account number (0ACCOUNT) to cost element (0COSTELMNT) or to general ledger account (0GL_ACCOUNT). For more information, see the Example for a BEx Query As a Receiver.

The receiver query uses a hierarchy, but the sender query does not:

If the selections of the RRI only consist of single values, the hierarchy setting for the receiver query remains unchanged; otherwise the hierarchy is deactivated.

The sender query uses a hierarchy, but the receiver query does not:

The hierarchy is set to inactive.

Hierarchies and Compound Characteristics

With hierarchies for compound characteristics, you have to create a variable for the basic characteristic of the hierarchy for the receiver query so that the values can be transferred correctly.

If you were to define the query without these variables, the dynamic filter would be used and the hierarchy would be deactivated due to the compounding of the InfoObject. When you use this non-changeable variable, the RRI can transfer the value to this variable and the hierarchy remains active.

Using Variables

If you go from a query to a query with variables, the variable screen for the target query is only displayed if it was not possible to fill all variables when calling it. This is especially the case if the variable screen contains optional variables only.

Unlike hierarchy node variables, hierarchy variables are not applied.

Adding Targets Dynamically

You can use the BAdI RS_BBS_BADI_DYNAMIC to extend the context menu for targets dynamically from an executed BEx query. As a result, further recipients are added to the recipients in the sender/receiver assignment. This means that the context menu is not extended until runtime and is defined by the the column, row, cell content (and key figure value), query, or InfoProvider.

Example

As a special case with different hierarchies and compounded characteristic, see the example Example for BEx Query as Receiver.