SAP SXPG_COMMAND_CHECK_INT Function Module for
SXPG_COMMAND_CHECK_INT is a standard sxpg command check int 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 sxpg command check int FM, simply by entering the name SXPG_COMMAND_CHECK_INT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSXP
Program Name: SAPLSSXP
Main Program: SAPLSSXP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SXPG_COMMAND_CHECK_INT 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 'SXPG_COMMAND_CHECK_INT'".
EXPORTING
COMMANDNAME = "
* OPERATINGSYSTEM = SY-OPSYS "
* TARGETSYSTEM = "
* ADDITIONAL_PARAMETERS = ' ' "
IMPORTING
PROGRAMNAME = "
DEFINED_PARAMETERS = "
ALL_PARAMETERS = "
EXCEPTIONS
COMMAND_NOT_FOUND = 1 SYSTEM_FAILURE = 10 PARAMETERS_TOO_LONG = 2 SECURITY_RISK = 3 WRONG_CHECK_CALL_INTERFACE = 4 X_ERROR = 5 TOO_MANY_PARAMETERS = 6 PARAMETER_EXPECTED = 7 ILLEGAL_COMMAND = 8 COMMUNICATION_FAILURE = 9
IMPORTING Parameters details for SXPG_COMMAND_CHECK_INT
COMMANDNAME -
Data type: SXPGCOLIST-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
OPERATINGSYSTEM -
Data type: SXPGCOLIST-OPSYSTEMDefault: SY-OPSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)
TARGETSYSTEM -
Data type: RFCDISPLAY-RFCHOSTOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDITIONAL_PARAMETERS -
Data type: SXPGCOLIST-PARAMETERSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SXPG_COMMAND_CHECK_INT
PROGRAMNAME -
Data type: SXPGCOLIST-OPCOMMANDOptional: No
Call by Reference: No ( called with pass by value option)
DEFINED_PARAMETERS -
Data type: SXPGCOLIST-PARAMETERSOptional: No
Call by Reference: No ( called with pass by value option)
ALL_PARAMETERS -
Data type: SXPGCOLIST-PARAMETERSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
COMMAND_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETERS_TOO_LONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SECURITY_RISK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_CHECK_CALL_INTERFACE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOO_MANY_PARAMETERS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_EXPECTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_COMMAND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SXPG_COMMAND_CHECK_INT 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_commandname | TYPE SXPGCOLIST-NAME, " | |||
| lv_programname | TYPE SXPGCOLIST-OPCOMMAND, " | |||
| lv_command_not_found | TYPE SXPGCOLIST, " | |||
| lv_system_failure | TYPE SXPGCOLIST, " | |||
| lv_operatingsystem | TYPE SXPGCOLIST-OPSYSTEM, " SY-OPSYS | |||
| lv_defined_parameters | TYPE SXPGCOLIST-PARAMETERS, " | |||
| lv_parameters_too_long | TYPE SXPGCOLIST, " | |||
| lv_targetsystem | TYPE RFCDISPLAY-RFCHOST, " | |||
| lv_security_risk | TYPE RFCDISPLAY, " | |||
| lv_all_parameters | TYPE SXPGCOLIST-PARAMETERS, " | |||
| lv_additional_parameters | TYPE SXPGCOLIST-PARAMETERS, " SPACE | |||
| lv_wrong_check_call_interface | TYPE SXPGCOLIST, " | |||
| lv_x_error | TYPE SXPGCOLIST, " | |||
| lv_too_many_parameters | TYPE SXPGCOLIST, " | |||
| lv_parameter_expected | TYPE SXPGCOLIST, " | |||
| lv_illegal_command | TYPE SXPGCOLIST, " | |||
| lv_communication_failure | TYPE SXPGCOLIST. " |
|   CALL FUNCTION 'SXPG_COMMAND_CHECK_INT' " |
| EXPORTING | ||
| COMMANDNAME | = lv_commandname | |
| OPERATINGSYSTEM | = lv_operatingsystem | |
| TARGETSYSTEM | = lv_targetsystem | |
| ADDITIONAL_PARAMETERS | = lv_additional_parameters | |
| IMPORTING | ||
| PROGRAMNAME | = lv_programname | |
| DEFINED_PARAMETERS | = lv_defined_parameters | |
| ALL_PARAMETERS | = lv_all_parameters | |
| EXCEPTIONS | ||
| COMMAND_NOT_FOUND = 1 | ||
| SYSTEM_FAILURE = 10 | ||
| PARAMETERS_TOO_LONG = 2 | ||
| SECURITY_RISK = 3 | ||
| WRONG_CHECK_CALL_INTERFACE = 4 | ||
| X_ERROR = 5 | ||
| TOO_MANY_PARAMETERS = 6 | ||
| PARAMETER_EXPECTED = 7 | ||
| ILLEGAL_COMMAND = 8 | ||
| COMMUNICATION_FAILURE = 9 | ||
| . " SXPG_COMMAND_CHECK_INT | ||
ABAP code using 7.40 inline data declarations to call FM SXPG_COMMAND_CHECK_INT
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 NAME FROM SXPGCOLIST INTO @DATA(ld_commandname). | ||||
| "SELECT single OPCOMMAND FROM SXPGCOLIST INTO @DATA(ld_programname). | ||||
| "SELECT single OPSYSTEM FROM SXPGCOLIST INTO @DATA(ld_operatingsystem). | ||||
| DATA(ld_operatingsystem) | = SY-OPSYS. | |||
| "SELECT single PARAMETERS FROM SXPGCOLIST INTO @DATA(ld_defined_parameters). | ||||
| "SELECT single RFCHOST FROM RFCDISPLAY INTO @DATA(ld_targetsystem). | ||||
| "SELECT single PARAMETERS FROM SXPGCOLIST INTO @DATA(ld_all_parameters). | ||||
| "SELECT single PARAMETERS FROM SXPGCOLIST INTO @DATA(ld_additional_parameters). | ||||
| DATA(ld_additional_parameters) | = ' '. | |||
Search for further information about these or an SAP related objects