Example of a Query as a Receiver
The following example contains two peculiarities: The queries linked using the RRI use different hierarchies, and the basic characteristic of the hierarchy in the receiver query is a compounded characteristic.
From a query on a cost element, you want to display the corresponding account. The queries are based on two different InfoCubes.
The sender query uses a hierarchy that is based on the basic characteristic cost element (0COSTELMNT). The receiver query uses a hierarchy that is based on the characteristic account number (0ACCOUNT).
Hierarchies that are based on different characteristics cannot normally be transferred. However this a special case: The characteristics cost element (0COSTELMNT) and account number (0ACCOUNT) have the same key and are recognized by the system as similar characteristics whose values can be transferred to one another. The same link exists between account number (0ACCOUNT) and general ledger account (0GL_ACCOUNT). If this was not the case, the hierarchy in this example could not be transferred with the RRI.
Defining Your Receiver Query
As the hierarchy basic characteristic is a compounded characteristic (account number is compounded to chart of accounts), you have to create a variable for characteristic account number so that the values can be transferred correctly.
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 display hierarchy remains active.
Create a variable with the following properties for characteristic account number:
Variable Type |
Characteristic Value Variable |
|---|---|
Processing Type |
Manual entry/Default value |
Variable represents |
selection option |
Variable value is |
Optional |
Input Ready |
Switched on |
Changeable with query navigation |
Switched off |
Creating Sender/Receiver Assignments
Create a sender/receiver assignment for both of your queries. You do not need to maintain the assignment details.
Executing the Jump
When the hierarchies for both queries are structured in the same way, the jump from the sender query to the receiver query appears as follows:
When the hierarchies for both queries are structured differently, the jump from the sender query to the receiver query appears as follows:
