SAP SXO_IMPL_ACTIVE Function Module for
SXO_IMPL_ACTIVE is a standard sxo impl active 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 sxo impl active FM, simply by entering the name SXO_IMPL_ACTIVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEXO
Program Name: SAPLSEXO
Main Program: SAPLSEXO
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SXO_IMPL_ACTIVE 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 'SXO_IMPL_ACTIVE'".
EXPORTING
IMP_NAME = "Implementation name for an enhancement
* NO_DIALOG = SEEX_FALSE "
* CALL_BY_CUSTOMIZING = SEEX_FALSE "
CHANGING
* PROTOCOL = "Log Generation Interface
EXCEPTIONS
BADI_NOT_EXISTING = 1 IMP_NOT_EXISTING = 2 ALREADY_ACTIVE = 3 DATA_INCONSISTENCY = 4 ACTIVATION_NOT_ADMISSABLE = 5 ACTION_CANCELED = 6 ACCESS_FAILURE = 7
IMPORTING Parameters details for SXO_IMPL_ACTIVE
IMP_NAME - Implementation name for an enhancement
Data type: RSEXSCRN-IMP_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
NO_DIALOG -
Data type: SEEX_BOOLEANDefault: SEEX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALL_BY_CUSTOMIZING -
Data type: SEEX_BOOLEANDefault: SEEX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SXO_IMPL_ACTIVE
PROTOCOL - Log Generation Interface
Data type: SPROT_U_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
BADI_NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IMP_NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ALREADY_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_INCONSISTENCY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTIVATION_NOT_ADMISSABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTION_CANCELED -
Data type:Optional: No
Call by Reference: Yes
ACCESS_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SXO_IMPL_ACTIVE 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_imp_name | TYPE RSEXSCRN-IMP_NAME, " | |||
| lv_protocol | TYPE SPROT_U_TAB, " | |||
| lv_badi_not_existing | TYPE SPROT_U_TAB, " | |||
| lv_no_dialog | TYPE SEEX_BOOLEAN, " SEEX_FALSE | |||
| lv_imp_not_existing | TYPE SEEX_BOOLEAN, " | |||
| lv_already_active | TYPE SEEX_BOOLEAN, " | |||
| lv_call_by_customizing | TYPE SEEX_BOOLEAN, " SEEX_FALSE | |||
| lv_data_inconsistency | TYPE SEEX_BOOLEAN, " | |||
| lv_activation_not_admissable | TYPE SEEX_BOOLEAN, " | |||
| lv_action_canceled | TYPE SEEX_BOOLEAN, " | |||
| lv_access_failure | TYPE SEEX_BOOLEAN. " |
|   CALL FUNCTION 'SXO_IMPL_ACTIVE' " |
| EXPORTING | ||
| IMP_NAME | = lv_imp_name | |
| NO_DIALOG | = lv_no_dialog | |
| CALL_BY_CUSTOMIZING | = lv_call_by_customizing | |
| CHANGING | ||
| PROTOCOL | = lv_protocol | |
| EXCEPTIONS | ||
| BADI_NOT_EXISTING = 1 | ||
| IMP_NOT_EXISTING = 2 | ||
| ALREADY_ACTIVE = 3 | ||
| DATA_INCONSISTENCY = 4 | ||
| ACTIVATION_NOT_ADMISSABLE = 5 | ||
| ACTION_CANCELED = 6 | ||
| ACCESS_FAILURE = 7 | ||
| . " SXO_IMPL_ACTIVE | ||
ABAP code using 7.40 inline data declarations to call FM SXO_IMPL_ACTIVE
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 IMP_NAME FROM RSEXSCRN INTO @DATA(ld_imp_name). | ||||
| DATA(ld_no_dialog) | = SEEX_FALSE. | |||
| DATA(ld_call_by_customizing) | = SEEX_FALSE. | |||
Search for further information about these or an SAP related objects