SAP ITS_RG_EXECUTE Function Module for









ITS_RG_EXECUTE is a standard its rg execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 its rg execute FM, simply by entering the name ITS_RG_EXECUTE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RESTGUI
Program Name: SAPLRESTGUI
Main Program: SAPLRESTGUI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ITS_RG_EXECUTE 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 'ITS_RG_EXECUTE'"
EXPORTING
* P_DOCUMENT = ' ' "
* P_WIN16_EXT = ' ' "
* P_EXEC_RC = ' ' "
* P_OPERATION = 'OPEN' "
* P_CD = ' ' "
* P_COMMANDLINE = ' ' "
* P_INFORM = ' ' "
* P_PROGRAM = ' ' "
* P_STAT = ' ' "
* P_WINID = ' ' "
* P_OSMAC_SCRIPT = ' ' "
* P_OSMAC_CREATOR = ' ' "

IMPORTING
P_RBUFF = "
PE_FRONTEND_ERROR = "
PE_PROG_NOT_FOUND = "
PE_GUI_REFUSE_EXECUTE = "
.



IMPORTING Parameters details for ITS_RG_EXECUTE

P_DOCUMENT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_WIN16_EXT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_EXEC_RC -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_OPERATION -

Data type:
Default: 'OPEN'
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_CD -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_COMMANDLINE -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_INFORM -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_PROGRAM -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_STAT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_WINID -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_OSMAC_SCRIPT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

P_OSMAC_CREATOR -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ITS_RG_EXECUTE

P_RBUFF -

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

PE_FRONTEND_ERROR -

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

PE_PROG_NOT_FOUND -

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

PE_GUI_REFUSE_EXECUTE -

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

Copy and paste ABAP code example for ITS_RG_EXECUTE 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_p_rbuff  TYPE STRING, "   
lv_p_document  TYPE STRING, "   SPACE
lv_p_win16_ext  TYPE STRING, "   SPACE
lv_p_exec_rc  TYPE STRING, "   SPACE
lv_p_operation  TYPE STRING, "   'OPEN'
lv_p_cd  TYPE STRING, "   SPACE
lv_pe_frontend_error  TYPE ABAP_BOOL, "   
lv_p_commandline  TYPE ABAP_BOOL, "   SPACE
lv_pe_prog_not_found  TYPE ABAP_BOOL, "   
lv_p_inform  TYPE ABAP_BOOL, "   SPACE
lv_pe_gui_refuse_execute  TYPE ABAP_BOOL, "   
lv_p_program  TYPE ABAP_BOOL, "   SPACE
lv_p_stat  TYPE ABAP_BOOL, "   SPACE
lv_p_winid  TYPE ABAP_BOOL, "   SPACE
lv_p_osmac_script  TYPE ABAP_BOOL, "   SPACE
lv_p_osmac_creator  TYPE ABAP_BOOL. "   SPACE

  CALL FUNCTION 'ITS_RG_EXECUTE'  "
    EXPORTING
         P_DOCUMENT = lv_p_document
         P_WIN16_EXT = lv_p_win16_ext
         P_EXEC_RC = lv_p_exec_rc
         P_OPERATION = lv_p_operation
         P_CD = lv_p_cd
         P_COMMANDLINE = lv_p_commandline
         P_INFORM = lv_p_inform
         P_PROGRAM = lv_p_program
         P_STAT = lv_p_stat
         P_WINID = lv_p_winid
         P_OSMAC_SCRIPT = lv_p_osmac_script
         P_OSMAC_CREATOR = lv_p_osmac_creator
    IMPORTING
         P_RBUFF = lv_p_rbuff
         PE_FRONTEND_ERROR = lv_pe_frontend_error
         PE_PROG_NOT_FOUND = lv_pe_prog_not_found
         PE_GUI_REFUSE_EXECUTE = lv_pe_gui_refuse_execute
. " ITS_RG_EXECUTE




ABAP code using 7.40 inline data declarations to call FM ITS_RG_EXECUTE

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.

 
DATA(ld_p_document) = ' '.
 
DATA(ld_p_win16_ext) = ' '.
 
DATA(ld_p_exec_rc) = ' '.
 
DATA(ld_p_operation) = 'OPEN'.
 
DATA(ld_p_cd) = ' '.
 
 
DATA(ld_p_commandline) = ' '.
 
 
DATA(ld_p_inform) = ' '.
 
 
DATA(ld_p_program) = ' '.
 
DATA(ld_p_stat) = ' '.
 
DATA(ld_p_winid) = ' '.
 
DATA(ld_p_osmac_script) = ' '.
 
DATA(ld_p_osmac_creator) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!