Report To Report Interface (RRI) involving a receiver workbook from RSRT
Objective: To leverage RRI functionality in SAP BW / SAP BI and jump to a workbook from a query.
Scenario: A report is to be created involving calculation of certain key figures based on row/record comparison, and this row comparison is to consider only the data which is in the result set(ie the data which has been filtered through variable entries). So the only way of achieving this was by implementing static excel formulae in a workbook. Furthermore it was required to jump from a similar query into this particular workbook with excel formulae. Transaction RSBBS doesn’t provide any options to jump into a workbook.
Approach: RSBBS eventhough doesn’t provide any options to jump into workbook directly, it provides options to jump into ABAP reports and Transactions. I’ve chosen jumping into transactions, which are nothing but commands to execute underlying ABAP reports. All workbooks can be executed through transaction RRMXP, where we need to input either the workbook ID or query name or both. The initial plan was to jump to transaction RRMXP and make sure that the transaction RRMXP gets executed for a specific variant involving the desired workbook.
Pre-Requisite: This scenario is only useful when executed from RSRT, as the transaction RRMXP has only SAPGUI for windows under GUI support. Hence the user needs to have authorizations to RSRT. SAPGUI for HTML is not supported hence a jump from portal is not allowed.
Realization: Implementation of this approach was a two step process, where the first step was to create a transaction with variant that could execute the workbook and the second was to jump from the Bex query into the workbook.
Step 1: Creating a Transaction with Variant to run the desired workbook.
Workbook ID: Execute the workbook and select workbook settings from BEx Analyzer to collect the workbook ID.
Workbook ID: OMQPMUO7UYA99XB91L011AID9
When a workbook is launched from SAP system, through favorites or User menu, then transaction code RRMXP is used.
We need to create a transaction code for RRMXP and then make sure that it gets called only for the specific workbook.
Creating a Transaction Variant:
To create a Transaction variant, first execute transaction SHD0 – Transaction and Screen Variants.
Enter transaction code to which we would like to create a variant, here it is RRMXP and click on create.
Click on continue.
The system now offers us with the RRMXP transaction to enter the values. Here we input the previously collected workbook ID, or we can search our workbook from the possible entries (F4) help as well.
Click on Continue and we would be offered with a CONFIRM SCREEN ENTRIES screen. Carry out the highlighted changes in this screen.
Choose the checkboxes ‘W.content’ and ‘Output only’ against the workbook ID. This will make sure to enter the specified workbook ID in the RRMXP screen when executed with this variant.
Enter a screen variant name and a short description.
Click on “Exit and Save”.
Also mark the field QUERY as ‘OUTPUT ONLY’. This will make sure that the field is greyed out or disabled for user input when the transaction is executed with the created variant.
Click on SAVE.
Now create a transaction variant and associate it with the created screen variant.
Enter a Transaction Variant Name, click on the display change icon, this will highlight the insert row icon and then click on the insert row icon.
Use the F4 help in the first inserted row to choose the created screen variant and click on Save.
To test we can click on execute and it should automatically populate the workbook ID in RRMXP screen.
We can observe that the workbook ID is entered and greyed out, which makes it impossible for the user to edit the workbook ID. Also the Query field is greyed out. This was possible due to the selection of the checkbox “Output Only” in the change screen variant screen previously.
Also upon continuing further on the above screen by hitting enter, we can view the workbook getting executed:
Now we need to create a transaction to run with the variant ZPF_VAR1. This can be done in two ways, either create a transaction with variants from SE93 or from SHD0. Here I’m choosing SHD0 transaction.
From SHD0 click on GOTO and choose “Create Variant Transaction”.
In the screen that follows choose “Transaction with Variant (Variant Transaction)” radio button after specifying the name of your required transaction.
The name of the transaction and the transaction variant is automatically proposed if you navigate to SE93 screen from SHD0 transaction using the GO TO option.
Save the transaction, and execute the newly created transaction ZRRMXP to test its working:
Step 2: Create an RRI from the report to the workbook.
Enter the sender query name and click on CREATE.
In the screen that follows choose the radio button as TRANSACTION and enter the created transaction in the ‘REPORT’ field. Click on Transfer.
Maintain field assignment by choosing assignment details as highlighted below.
Click on Save.
Execute the sender report:
We can find our transaction in the context menu, Goto option now.
Click on ZRRMXP.
And we have achieved a jump from a query into a workbook without even being prompted with a ZRRMXP screen as expected previously. Once the transaction was chosen there was a direct jump to the workbook.
Conclusion: By leveraging the Transaction Code or the ABAP program option, it is possible to include a workbook as a receiver in a Report To Report Interface Scenario.