SAP OIRA_EXECUTE_PROCESS Function Module for Checks the process and executes the selected program
OIRA_EXECUTE_PROCESS is a standard oira execute process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks the process and executes the selected program 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 oira execute process FM, simply by entering the name OIRA_EXECUTE_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIRA_APP02
Program Name: SAPLOIRA_APP02
Main Program: SAPLOIRA_APP02
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIRA_EXECUTE_PROCESS 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 'OIRA_EXECUTE_PROCESS'"Checks the process and executes the selected program.
EXPORTING
I_PROCESS = "Process ID
I_VARIANT = "ABAP: Name of variant (without program name)
I_PROGRAM = "ABAP program, current main program
I_NOSEL = "SSR - Indicator to skip selection screen
I_TCODE = "ABAP program, current transaction code
* I_TRTYP = ' ' "Transaction type
EXCEPTIONS
PROC_NO_DESC = 1 BT_NOT_FOUND = 2 BT_NO_DESC = 3 PROG_NOT_FOUND = 4 PROG_NOT_EXEC = 5
IMPORTING Parameters details for OIRA_EXECUTE_PROCESS
I_PROCESS - Process ID
Data type: OIRA_PROCOptional: No
Call by Reference: No ( called with pass by value option)
I_VARIANT - ABAP: Name of variant (without program name)
Data type: VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
I_PROGRAM - ABAP program, current main program
Data type: SYREPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_NOSEL - SSR - Indicator to skip selection screen
Data type: OIRA_NOSELOptional: No
Call by Reference: No ( called with pass by value option)
I_TCODE - ABAP program, current transaction code
Data type: SYTCODEOptional: No
Call by Reference: No ( called with pass by value option)
I_TRTYP - Transaction type
Data type: TRTYPDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PROC_NO_DESC - Process description not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BT_NOT_FOUND - Business type not found
Data type:Optional: No
Call by Reference: Yes
BT_NO_DESC - Business type description not found
Data type:Optional: No
Call by Reference: Yes
PROG_NOT_FOUND - Program not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROG_NOT_EXEC - Program is no executable
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIRA_EXECUTE_PROCESS 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_process | TYPE OIRA_PROC, " | |||
| lv_proc_no_desc | TYPE OIRA_PROC, " | |||
| lv_i_variant | TYPE VARIANT, " | |||
| lv_bt_not_found | TYPE VARIANT, " | |||
| lv_i_program | TYPE SYREPID, " | |||
| lv_bt_no_desc | TYPE SYREPID, " | |||
| lv_i_nosel | TYPE OIRA_NOSEL, " | |||
| lv_prog_not_found | TYPE OIRA_NOSEL, " | |||
| lv_i_tcode | TYPE SYTCODE, " | |||
| lv_prog_not_exec | TYPE SYTCODE, " | |||
| lv_i_trtyp | TYPE TRTYP. " ' ' |
|   CALL FUNCTION 'OIRA_EXECUTE_PROCESS' "Checks the process and executes the selected program |
| EXPORTING | ||
| I_PROCESS | = lv_i_process | |
| I_VARIANT | = lv_i_variant | |
| I_PROGRAM | = lv_i_program | |
| I_NOSEL | = lv_i_nosel | |
| I_TCODE | = lv_i_tcode | |
| I_TRTYP | = lv_i_trtyp | |
| EXCEPTIONS | ||
| PROC_NO_DESC = 1 | ||
| BT_NOT_FOUND = 2 | ||
| BT_NO_DESC = 3 | ||
| PROG_NOT_FOUND = 4 | ||
| PROG_NOT_EXEC = 5 | ||
| . " OIRA_EXECUTE_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM OIRA_EXECUTE_PROCESS
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_i_trtyp) | = ' '. | |||
Search for further information about these or an SAP related objects