Testing DEV reports in QAS environment without releasing transport request objects

Tell me about it...

Some of you had the lucky of working in a client who had the concern of copying QAS data (or even PRD) to a DEV client, but the truth is that we're always standing at a lack of testing data in DEV environments, ending up with a thousand transport requests at the end of the project.

The most of you have dreamt of having a really good sandbox in DEV to perform unit testing, saving up time, numbers and patience. It would be great, wouldn't it?

For this purpose I've created a report that allows you to use QAS data for a DEV testing with no need of releasing the transport request in DEV nor importing that in QAS system.

How does it work?

The report I've created (Z_ASG_REMOTE_REPORT_SUBMIT) will be executed in the QAS environment (via SE38), so you can set the Report you want to test and the Destination (existing RFC in SM59) which have the very last version of your report (mostly DEV). It will create a temporary report in QAS, containing the current source code of the selected Report in the Destination and execute it.

What do I need?

1. Create a Transport Request to hold the objects below (SE09).
2. Create a Function Group named Z_ASG_REMOTE_REPORT (source code attached).
3. Create a Function Module named ZRS_TEXTPOOL_READ (source code attached) and set it as 'Remote-Enabled Module' (RFC).
4. Create a Function Module named ZRFC_READ_REPORT (source code attached) and set it as 'Remote-Enabled Module' (RFC).
5. Create a Report named Z_ASG_REMOTE_REPORT_SUBMIT (or whatever you want -- source code attached).
6. Activate all objects created before.
7. Release the Transport Request in DEV (SE09) and import it in QAS (STMS).

After following the steps above you'll be able to execute the Z_ASG_REMOTE_REPORT_SUBMIT in QAS system which will allow you to execute locked reports existing in DEV (or whatever reports existing in the Destination).

Important notes:

• It will work only for common REPORTs (WRITE, ALV, etc)
• It won't work with Logical Database PNP (HR Reports)
• It won't work with Module Pools
• It won't update Dictionary Objects in QAS. If you change any Dictionary Object in DEV that is referenced by your Report you should send it to QAS system.

Let me know if you can't get it working.

Hope it helps.

Kind regards,

Diêgo César