SAP ORAENQ_INIT Function Module for Initialization and getting parameters
ORAENQ_INIT is a standard oraenq init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialization and getting parameters 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 oraenq init FM, simply by entering the name ORAENQ_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STD8
Program Name: SAPLSTD8
Main Program: SAPLSTD8
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ORAENQ_INIT 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 'ORAENQ_INIT'"Initialization and getting parameters.
EXPORTING
* I_INST_ID = "Oracle monitor: Instance ID
I_SNAPSHOT_FROM = "Oracle monitor: snapshot ID
I_SNAPSHOT_TO = "Oracle monitor: snapshot ID
IMPORTING Parameters details for ORAENQ_INIT
I_INST_ID - Oracle monitor: Instance ID
Data type: ORA_INST_IDOptional: Yes
Call by Reference: Yes
I_SNAPSHOT_FROM - Oracle monitor: snapshot ID
Data type: ORA_SNAPSHOT_IDOptional: No
Call by Reference: Yes
I_SNAPSHOT_TO - Oracle monitor: snapshot ID
Data type: ORA_SNAPSHOT_IDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ORAENQ_INIT 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_inst_id | TYPE ORA_INST_ID, " | |||
| lv_i_snapshot_from | TYPE ORA_SNAPSHOT_ID, " | |||
| lv_i_snapshot_to | TYPE ORA_SNAPSHOT_ID. " |
|   CALL FUNCTION 'ORAENQ_INIT' "Initialization and getting parameters |
| EXPORTING | ||
| I_INST_ID | = lv_i_inst_id | |
| I_SNAPSHOT_FROM | = lv_i_snapshot_from | |
| I_SNAPSHOT_TO | = lv_i_snapshot_to | |
| . " ORAENQ_INIT | ||
ABAP code using 7.40 inline data declarations to call FM ORAENQ_INIT
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