Creating a Transaction As a
Receiver
Use
You can assign a transaction as a receiver to a sender query in the BI system.
Prerequisites
● 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 when the calling the transaction or report (for example, by entering a single value on the selection screen of the sender or by the cursor position when calling the object).
● Corresponding sender and receiver fields must normally 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. This makes it unclear which of the fields is to be supplied, meaning that neither of them is supplied.
● There has to be a complete chain from the DataSource in the source system to the InfoSource, through update rules right through to the target. See Transaction and ABAP/4 Report in Receivers.
Procedure
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 in the BI 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. This might be because the transaction uses a hidden initial screen and does not fill the parameter using the memory ID for the data element.
After creating the sender-receiver assignment as described above, proceed as follows:
...
1.
Select your
sender-receiver assignment and choose 
Assignment Details. More information:
Maintaining
Assignment Details.
2. Choose Table Field as the type. 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 no input help is 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 call 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 in a BEx query, the hierarchy is expanded before being passed on to the target program or the target transaction in the leaves of the parent node. In this case, a list of values is always passed on. It is not possible to pass on the node name itself to a transaction or program.