ABAP capture result of submitted program using cl_salv_bs_runtime_info

Posted by -

Let's talk about a hypothetical scenario,

You are meditating in your fortress of solitude. A wild customer appears virtually/physically.The person shows you a report output and wants you to fetch exact data as the report displays in your current development.

Scared, you begin to analyse the code of the report to reuse its logic only to see your fear come out alive i.e. the report has all the logic embedded.

Proudly, you suggest refactoring the report, extracting the logic globally, and using it for your objects.

Swiftly, your hope helicopter is shot down by the customer's stinger missile of an increase in testing efforts and with support troops of "nearing the deadline" hand a lack of super users to confirm the original report works as intended post refactor.

Now, If the above scenario is not so much hypothetical in your experience, you are left with some limited choices.

1. Copy the logic ( Hello dark side)

2. Somehow get the output of the report.

  In today's post, I wanted to talk about an easy way to capture the result of a submitted program as long as the program uses ALV .

There is a class that can be very helpful in this scenario:cl_salv_bs_runtime_info

You can use this class to:

 - Set ALV output to false using SET method.

 - Submit your target program.

 - Get the output using GET_DATA_REF method.

- Set ALV output to true using SET method if you want to display your own ALV.

Here is a simple demo using the ALV demo report: BALSD02_GRID.

Executing the report gives you the below output.

Now, let's submit this report inside our program.   

Executing the report gives the below output which is the same dataset including Client field which the above program suppressed in display.


As always, hope this information helps you in your day to day work.




Popular posts from this blog

ABAP read excel(.XLSX) file to internal table in ABAP using CL_FDT_XL_SPREADSHEET

Posted by -
You are given a requirement to upload data to a custom DB table where the user provides you with the file path of the excel on his PC and the report loads the data from it to the Custom table. For experienced Abapers, the requirement is quite straightforward, except that the user wants to upload an XLSX file. There are not many options to read data from XLSX/XLS file. The TEXT_CONVERT_XLS_TO_SAP  function module is one of them but is a performance killer and uses OLE. In this post, I wanted to showcase How we can read data from the XLSX files using CL_FDT_SPOREADSHEET class. Let's start with uploading the file. Now that we have the file in xstring table, let's pass it to CL_FDT_XL_SPREADSHEET to get its object reference. From the object reference, we can retrieve each worksheet data. The data is returned in the form of an anonymous data object which can be dereferenced into a field symbol and passed to the target internal table. Below is the cod
Read more

ABAP convert internal table to excel (.xlsx) format and Send email or download

Posted by -
Reporting is incomplete without file interfacing. Sometimes the requirement is to send a file via email or download it to a PC. but what to do when the user requests the file in XLSX format? In today's post, I am sharing how to convert an internal table to .xlsx format and then send it to a PC or email. One of the quickest ways I found it been done is using SALV classes. Below is the Code snippet Now once you have the xstring with you, simply pass it to relevant libraries to handle the output. Downloading to PC: Sending via Email It's that simple. Hope you like the post and use it in your day to day work.
Read more

Application Logging in ABAP

Posted by -
Image
Whether you are working with integration or a critical application or a complex report, logging becomes an obvious choice and activity.  Traditionally, Abapers have been logging information using a custom DB table defined specifically for a particular application. While useful, The approach has some flaws,      - Every application needs to have its own logging table      - Record purging/archiving needs to be set up in order to make sure old records are either deleted         or archived.      - There is no reusability of either the setup or the logic to log. With the introduction of Application Logging from SAP, the traditional approach can be left out.  In this post, I will be talking about how we can leverage the SAP application Logging Library to make logging easy. What is an application log? An application log is a rich type log. It contains information like User, Time, Expiry date of the log along with the actual message raised by the
Read more