SAP RS_BEX_REPORT_SAVE_RFC Function Module for Report Designer RFC module

Search SAP Function Modules

RS_BEX_REPORT_SAVE_RFC is a standard rs bex report save rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Report Designer RFC module processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for rs bex report save rfc FM, simply by entering the name RS_BEX_REPORT_SAVE_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: RS_BEX_REPORT_RFC
Program Name: SAPLRS_BEX_REPORT_RFC
Main Program: SAPLRS_BEX_REPORT_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RS_BEX_REPORT_SAVE_RFC pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'RS_BEX_REPORT_SAVE_RFC'"Report Designer RFC module
  EXPORTING
   I_REPORT_HEADER =  "Report Designer: Report ID for Loading and Saving
   I_REPORT_RUNTIME_XML =  "Runtime XML
   I_REPORT_DESIGN_XML =  "Designtime XML
   I_REPORT_VERSION =  "Report Version
   I_TEXT =  "Report Designer: Text Table
   I_S_PARAMS =  "Parameter for Enterprise Report Save_RFC

 IMPORTING
   E_SUBRC =  "Return Value from ABAP Statements
   E_MAX_MESSAGE_TYPE =  "Message Type

TABLES
   I_T_XREF =  "Structure for RFC Interface RS_BEX_REPORT_load/save
*  E_T_MESSAGE =  "Message Texts
*  I_T_ERPTTEXTS =  "RFC Structure for Language-Specific Enterprise Report Texts

EXCEPTIONS
   X_MESSAGE = 1 

.

IMPORTING Parameters details for RS_BEX_REPORT_SAVE_RFC

I_REPORT_HEADER - Report Designer: Report ID for Loading and Saving

Data type: RSER_X_HEADER
Optional: No
Call by Reference: No ( called with pass by value option)

I_REPORT_RUNTIME_XML - Runtime XML

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

I_REPORT_DESIGN_XML - Designtime XML

Data type: STRING
Optional: No
Call by Reference: No ( called with pass by value option)

I_REPORT_VERSION - Report Version

Data type: CHAR3
Optional: No
Call by Reference: No ( called with pass by value option)

I_TEXT - Report Designer: Text Table

Data type: RSER_X_TEXT
Optional: No
Call by Reference: No ( called with pass by value option)

I_S_PARAMS - Parameter for Enterprise Report Save_RFC

Data type: RSER_IPAR_OBJSET
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RS_BEX_REPORT_SAVE_RFC

E_SUBRC - Return Value from ABAP Statements

Data type: SYSUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

E_MAX_MESSAGE_TYPE - Message Type

Data type: SYMSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RS_BEX_REPORT_SAVE_RFC

I_T_XREF - Structure for RFC Interface RS_BEX_REPORT_load/save

Data type: RSER_X_ERPTXREF
Optional: No
Call by Reference: Yes

E_T_MESSAGE - Message Texts

Data type: BICS_PROV_T_MESSAGE
Optional: Yes
Call by Reference: Yes

I_T_ERPTTEXTS - RFC Structure for Language-Specific Enterprise Report Texts

Data type: RSER_X_ERPTTEXTS
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

X_MESSAGE - Cancellation

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RS_BEX_REPORT_SAVE_RFC Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM RS_BEX_REPORT_SAVE_RFC

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects