SAP OIJ_EL_GET_EMACTIVE_STATUS Function Module for APO-TSW : Retrieve global BW customizing
OIJ_EL_GET_EMACTIVE_STATUS is a standard oij el get emactive status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for APO-TSW : Retrieve global BW customizing 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 oij el get emactive status FM, simply by entering the name OIJ_EL_GET_EMACTIVE_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_EL_IF_ETS
Program Name: SAPLOIJ_EL_IF_ETS
Main Program: SAPLOIJ_EL_IF_ETS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_EL_GET_EMACTIVE_STATUS 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 'OIJ_EL_GET_EMACTIVE_STATUS'"APO-TSW : Retrieve global BW customizing.
IMPORTING
E_USEEM = "APO-TSW: BW-related IS-Oil changes flag
EXCEPTIONS
NO_DATA_FOUND = 1
EXPORTING Parameters details for OIJ_EL_GET_EMACTIVE_STATUS
E_USEEM - APO-TSW: BW-related IS-Oil changes flag
Data type: OI0_SELKZOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DATA_FOUND - Data not found in table
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIJ_EL_GET_EMACTIVE_STATUS 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_e_useem | TYPE OI0_SELKZ, " | |||
| lv_no_data_found | TYPE OI0_SELKZ. " |
|   CALL FUNCTION 'OIJ_EL_GET_EMACTIVE_STATUS' "APO-TSW : Retrieve global BW customizing |
| IMPORTING | ||
| E_USEEM | = lv_e_useem | |
| EXCEPTIONS | ||
| NO_DATA_FOUND = 1 | ||
| . " OIJ_EL_GET_EMACTIVE_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_EL_GET_EMACTIVE_STATUS
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