BEx Query as Receiver 

Use

You are able to assign a BEx query as a receiver to another BEx query acting as a sender in BW.

Features

So that a query can be called as a receiver with the RRI, you need to note certain guidelines when defining the query.

General

·        Characteristics that are to be filled from the sender query should be defined as free characteristics. A hierarchy node restriction, for example, can also be transferred to free characteristics as a property.

·        Changeable variables for the receiver query are not filled by the RRI.

·        Selections for various InfoObjects are transferred if the InfoObjects have the same reference characteristic.

Also see the BEx query section under Receivers.

Using hierarchies

When using hierarchies in queries, note the following cases:

Sender and receiver query use the same hierarchy or hierarchies, based on the same basic characteristic:

You can jump from a hierarchy node in the sender query to the same hierarchy node in the receiver query directly. The hierarchy settings are transferred by the RRI.

Sender and receiver query use different hierarchies:

The hierarchy settings for the receiver query remain unchanged and the selections for the RRI are triggered. It filters according to the node leaves.

A small number of InfoObjects that do differ are still dealt with by the system as assignable InfoObjects. This is a special development for Business Content. For example, values from account number (0ACCOUNT) can be transferred to cost element (0COSTELMNT), or to general ledger account (0GL_ACCOUNT). Also see Example of a BEx Query as a Receiver.

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

If the selections for 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, the receiver query does not:

The hierarchy is switched to inactive.

Hierarchies and compounded characteristics

So that values can be transferred correctly with hierarchies for compounded characteristics, you have to create a variable for the basic characteristic of the receiver query.

If you define the query without this variable, the dynamic filter will be used and the hierarchy will be deactivated because the InfoObject is compounded. By using this variable, which cannot be changed, the RRI can transfer the value to this variable and the hierarchy remains active.

Example

For special cases with various hierarchies and compounded characteristics, see the example Example of a BEx Query as a Receiver.