Show TOC

Creating a Transaction as a ReceiverLocate this document in the navigation structure


You can assign a transaction as a receiver to a sender query in the BW system.

  • If you want to go from a Web application to a transaction or ABAP/4 report using the RRI, an ITS has to be assigned for the target system beforehand.

  • The value of the input field to be supplied must be known at the time of the jump (for example by entering a single value on the selection screen of the sender or by the cursor position at the time of the jump).

  • Sender and receiver fields that correspond to one another generally must link to the same data element or at least to the same domain, otherwise the values cannot be assigned to one another.

  • The assignment of sender and receiver fields must always be a 1:1 assignment. For example, the transactions called from the start screen cannot have two input fields of the same data type. Then it is not clear which of the fields is to be supplied, which means neither of them is supplied.

  • There has to be a complete chain from the DataSource of the source system to the InfoSource, through update rules up to the target. See also the section Transaction and ABAP/4 Report in Receiver.


Simple Cases:

  1. Specify a query or an InfoProvider as sender and choose Create.

  2. Choose Transaction as the report type for the receiver.

  3. Choose a target system, either local for a transaction within the BW system or Source System for a transaction in another SAP system.

  4. Specify the required transaction as the receiver report.

  5. Choose Apply. You return to the Maintain Sender-Receiver Assignments screen.

Complex Cases:

For some transactions, it is necessary to make a detailed assignment. One reasons for this can be that the transaction uses a hidden initial screen and does not fill the parameters using the MemoryID of the data element.

Proceed as follows after you have created the sender/receiver assignment as described above.

  1. Select your sender-receiver assignment and choose Assignment Details. See also Maintain Assignment Details.

  2. As the type, choose Table Field. The columns Field Name, Data Element, Domain, and Set-/Get Parameter become input ready.

  3. Specify the field name, data element, domain and parameter ID for the receiver transaction. You need to know this information because input help is not available. You can usually find the parameter ID in the ABAP dictionary entry for the data element.

Further Option:

You can define a transformation or InfoSource with DataSource that you use to define an assignment between InfoObjects in the sending source system and the fields in the target.

Further Option:

You can use BAdI SMOD_RSR00004 to define the mapping logic: In previous releases, customer exit EXIT_SAPLRSBBS_002 was used. This is now obsolete and has been replaced by the BAdI.

If the RRI Jump Still Does not Work:

Many transactions and programs are not prepared for a call with parameters from the RRI, for example because programs with additional screens are called in transactions and the sender and target fields are not compatible.

In this case, a custom program containing all the necessary parameters and tables as selections fields and that then calls the actual transaction with the ABAP command

CALL TRANSACTION or calls the desired program with SUBMIT can help.

See the documentation about the ABAP commands and SAP Notes 363203 and 694244 (as an example for calling transaction KSB5) and SAP Note 383077 (RRI: Transaction call fails).

Individual fields must be declared as PARAMETERS, and tables must be declared as TABLES. You can only call tab pages from within this type of custom development.

If you jump from a node of a BEx query, the hierarchy is expanded before being passed to the target program or the target transaction in the leaves of the parent node. In this scenario, a list of values is always passed. It is not possible to pass the node name itself to a transaction or program.