Start of Content Area

Function documentation BEx Query As a Receiver  Locate the document in its SAP Library structure

Use

You can assign a BEx Query in BI as a receiver to another BEx Query as sender.

Features

To call a query as a receiver using the RRI, you need to be aware of a few guidelines for query definition.

General

      Characteristics to be filled from the sender query must be defined as free characteristics. Free characteristics can have properties assigned to them, for example a hierarchy node.

      Changeable variables for the recipient query are not filled by the RRI.

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

See 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 added from account number (0ACCOUNT) to cost element (0COSTELMNT) or to general ledger account (0GL_ACCOUNT). More information: Example for a BEx Query As a Receiver.

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

If the RRI selections 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 apply 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.

Example

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

 

 

 

End of Content Area