SAP RSCR_LAUNCH_REPORT Function Module for Call a CR Guid (possibly with BBS handle)
RSCR_LAUNCH_REPORT is a standard rscr launch report SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call a CR Guid (possibly with BBS handle) 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 rscr launch report FM, simply by entering the name RSCR_LAUNCH_REPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSCR
Program Name: SAPLRSCR
Main Program: SAPLRSCR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RSCR_LAUNCH_REPORT 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 'RSCR_LAUNCH_REPORT'"Call a CR Guid (possibly with BBS handle).
EXPORTING
I_GUID = "CR Report ID
* I_HANDLE = "Handle for Writing/Reading Cluster Tables
IMPORTING
E_SUBRC = "Return Value, Return Value after ABAP Statements
IMPORTING Parameters details for RSCR_LAUNCH_REPORT
I_GUID - CR Report ID
Data type: RSCR_RPTIDOptional: No
Call by Reference: Yes
I_HANDLE - Handle for Writing/Reading Cluster Tables
Data type: RSBBS_HANDLEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSCR_LAUNCH_REPORT
E_SUBRC - Return Value, Return Value after ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSCR_LAUNCH_REPORT 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.DATA: | ||||
lv_i_guid | TYPE RSCR_RPTID, " | |||
lv_e_subrc | TYPE SY-SUBRC, " | |||
lv_i_handle | TYPE RSBBS_HANDLE. " |
  CALL FUNCTION 'RSCR_LAUNCH_REPORT' "Call a CR Guid (possibly with BBS handle) |
EXPORTING | ||
I_GUID | = lv_i_guid | |
I_HANDLE | = lv_i_handle | |
IMPORTING | ||
E_SUBRC | = lv_e_subrc | |
. " RSCR_LAUNCH_REPORT |
ABAP code using 7.40 inline data declarations to call FM RSCR_LAUNCH_REPORT
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."SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
Search for further information about these or an SAP related objects