RFC Did not Return Data (SAP Library - ALV Grid Control (BC-SRV-ALV))

RFC Did not Return Data

A message telling you that no data was returned by the RFC is issued if no data was passed at any point in the MiniALV architecture. Perform the following steps to localize the error more exactly:

Go to transaction SMW0 to check if your proxy report has been released for the Internet. To do this, choose Internet release ® Reports and on the next screen Release ® Display release. (See also: Prerequisites).

Test if your proxy report in the SAP System outputs data. If not, you must check your report.

Test your report with the function module FLOW_LOGIC_ALV_CALL (for add-on applications: FLOW_LOGIC_MINIALV_CALL ) in the Function Builder (transaction SE37). The function module should fill the internal tables (for example, ET_DATA ). If the tables are empty, the problem is related to the backend: either the RFC, the report or an associated variant contains errors or does not exist.

The following is only relevant to the Standard MiniALV: Run the report as a batch job (see below). If this does not work, frontend objects are generated during processing (see Prerequisites). Use the method offline() to rule this out. Consider the following exceptional case: The ALV Grid Control must be instantiated. The constructor of the ALV Grid Control can determine whether the report runs in the Web or in the SAP GUI. If the report runs in the Web, no frontend object is generated. As a result, the report runs through in batch mode. However, if the report is executed offline, the ALV Grid Control must be attached to a container which is not instantiated. The report RSAA_WORKPLACE (Standard MiniALV) shows the proper usage of the offline() method.

Try to display the sample report BALVST01_GRID (for add-on MiniApps: BCALV_MINIALV ) instead of your report with the MiniALV in the browser. If the MiniALV service does not display the report, check if the sample report is released for the Web (see Prerequisites). Release the report if required. Then republish the MiniALV service using transaction SE80 . If the sample report is still not displayed, check if other MiniApps work. If not, the error is related to the ITS.

Check whether the system logon was correct, or whether the user logged on is authorized to display the report.

Check whether the function ITS_PING is used in your report or in a function module called by your report. This function is not compatible with MiniApps. It causes the report to terminate if the report was started by means of a MiniApp in which case the data is not delivered through RFC. Use the module GUI_IS_ITS or the static method CL_GUI_OBJECT=>WWW_ACTIVE instead of the ITS_PING function.

Executing the Report in the Background (Batch Job)

To test if the report runs in batch mode, proceed as follows (only relevant to the Standard MiniALV):

On the initial screen of the ABAP Editor (transaction SE38), enter the name of your proxy report and choose Program ® Execute ® Background.

On the subsequent screen, you must enter a selection variant if the report has a selection screen. Then choose Execute immediat.

Choose Job overview and then Execute (F8) to display a list of your jobs.

Your report should have the status Active (running) or Finished. Refresh the job display until the status changes into Finished.

Note

If the status is set to Ready, you generate frontend objects. Use the method offline() to rule this out.

Select the report and choose Spool.

Select the output for your report and choose Display contents (F6).

If you now see your list, the report is suited for Web Reporting. However, the output refers only to the selection variant chosen. If, depending on the selection, you generate frontend objects at another point in the program code, the same report may not run through in batch mode.

Note

For more information on job management, see Background Processing in the CCMS documentation.