SAP SXI_CONFIG_PROCESS Function Module for
SXI_CONFIG_PROCESS is a standard sxi config process 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 sxi config process FM, simply by entering the name SXI_CONFIG_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXI_PMI_CONFIG
Program Name: SAPLSXI_PMI_CONFIG
Main Program: SAPLSXI_PMI_CONFIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SXI_CONFIG_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 'SXI_CONFIG_PROCESS'".
EXPORTING
* IM_ADDCOMPS = "XI Components of PMI Monitoring Process
* IM_CENTRALCOMP = "XI Component of PMI Monitoring Process
* IM_PROCID = "SPI: Process Type ID
* IM_MODIFYCOMPS = "XI Components of PMI Monitoring Process
* IM_PROC_ACTION = "
IM_XIDOMAIN = "Domain in XI System Landscape
* IM_E2ETRACE = 0 "
* IM_PROCESSNAME = "
IMPORTING
EX_ERRORTEXT = "
TABLES
EX_PMIPROCID = "XI Process Type of PMI Monitoring
EX_PMIDEST = "PMI Component and Destination for XI Component
EX_NOPINGDESTS = "
EXCEPTIONS
NOT_AUTHORIZED = 1 RFCDEST_NOT_CREATED = 2 NO_PROCESS_DELETION = 3 NO_CENTRAL_COMPONENT = 4
IMPORTING Parameters details for SXI_CONFIG_PROCESS
IM_ADDCOMPS - XI Components of PMI Monitoring Process
Data type: SXICOMPONENTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_CENTRALCOMP - XI Component of PMI Monitoring Process
Data type: SXICOMPONENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_PROCID - SPI: Process Type ID
Data type: SPIPROCTPOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_MODIFYCOMPS - XI Components of PMI Monitoring Process
Data type: SXICOMPONENTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_PROC_ACTION -
Data type: SXMSYESNOOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_XIDOMAIN - Domain in XI System Landscape
Data type: SXIDOMAINOptional: No
Call by Reference: No ( called with pass by value option)
IM_E2ETRACE -
Data type: SXMSFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_PROCESSNAME -
Data type: SPIPROCTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SXI_CONFIG_PROCESS
EX_ERRORTEXT -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SXI_CONFIG_PROCESS
EX_PMIPROCID - XI Process Type of PMI Monitoring
Data type: SXIPMIPROCIDOptional: No
Call by Reference: Yes
EX_PMIDEST - PMI Component and Destination for XI Component
Data type: SXIPMIDESTOptional: No
Call by Reference: Yes
EX_NOPINGDESTS -
Data type: SXIPMIDESTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RFCDEST_NOT_CREATED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PROCESS_DELETION -
Data type:Optional: No
Call by Reference: Yes
NO_CENTRAL_COMPONENT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SXI_CONFIG_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_im_addcomps | TYPE SXICOMPONENTS, " | |||
| lv_ex_errortext | TYPE STRING, " | |||
| lt_ex_pmiprocid | TYPE STANDARD TABLE OF SXIPMIPROCID, " | |||
| lv_not_authorized | TYPE SXIPMIPROCID, " | |||
| lt_ex_pmidest | TYPE STANDARD TABLE OF SXIPMIDEST, " | |||
| lv_im_centralcomp | TYPE SXICOMPONENT, " | |||
| lv_rfcdest_not_created | TYPE SXICOMPONENT, " | |||
| lv_im_procid | TYPE SPIPROCTP, " | |||
| lt_ex_nopingdests | TYPE STANDARD TABLE OF SXIPMIDEST, " | |||
| lv_no_process_deletion | TYPE SXIPMIDEST, " | |||
| lv_im_modifycomps | TYPE SXICOMPONENTS, " | |||
| lv_no_central_component | TYPE SXICOMPONENTS, " | |||
| lv_im_proc_action | TYPE SXMSYESNO, " | |||
| lv_im_xidomain | TYPE SXIDOMAIN, " | |||
| lv_im_e2etrace | TYPE SXMSFLAG, " 0 | |||
| lv_im_processname | TYPE SPIPROCTXT. " |
|   CALL FUNCTION 'SXI_CONFIG_PROCESS' " |
| EXPORTING | ||
| IM_ADDCOMPS | = lv_im_addcomps | |
| IM_CENTRALCOMP | = lv_im_centralcomp | |
| IM_PROCID | = lv_im_procid | |
| IM_MODIFYCOMPS | = lv_im_modifycomps | |
| IM_PROC_ACTION | = lv_im_proc_action | |
| IM_XIDOMAIN | = lv_im_xidomain | |
| IM_E2ETRACE | = lv_im_e2etrace | |
| IM_PROCESSNAME | = lv_im_processname | |
| IMPORTING | ||
| EX_ERRORTEXT | = lv_ex_errortext | |
| TABLES | ||
| EX_PMIPROCID | = lt_ex_pmiprocid | |
| EX_PMIDEST | = lt_ex_pmidest | |
| EX_NOPINGDESTS | = lt_ex_nopingdests | |
| EXCEPTIONS | ||
| NOT_AUTHORIZED = 1 | ||
| RFCDEST_NOT_CREATED = 2 | ||
| NO_PROCESS_DELETION = 3 | ||
| NO_CENTRAL_COMPONENT = 4 | ||
| . " SXI_CONFIG_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM SXI_CONFIG_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.Search for further information about these or an SAP related objects