Make the most out of Query Execution – Part 2.
[Part 1 of the Blog Series | Make the most out of Query Execution – Part 1.] Further to the earlier blog we can also use the Query_view_data web service of function module to test our queries as well. This comes very handy when you are doing an Upgrade especially when it comes to a technical upgrade where queries are tested across the sandbox system and Production system as soon as the technical upgrade is over. In many cases this is a painstakingly slow and tedious process where often queries are manually executed and compared for various things like number of rows , overall result , authorizations etc. This also consumes a lot of time and effort by having resources who have to execute the queries and compare. Instead of doing it manually you can create a program in the sandbox system which calle the query in both the production and sandbox systems. You of course have to create an RFC connection between the two and then execute the RRW3_QUERY_VIEW_DATA in the sandbox and production systems simultaneously and then compare the outputs of the E_CELL_DATA for results – the data output of the queries can be out into an internal table and two internal tables – one each for the Sandbox and Production system can be compared. What this does is : ** The program can be automated to a high degree and then produce formatted output with a little bit of ABAP programming ** Since the same program is used to run queries otherwise also – the same performance tuning yardsticks apply to both. Create an RFC connection to your production system from the sandbox system. In usual cases the sandbox system is a copy of production that is taken.