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

Function CSM_CANCEL_COMMAND 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 'CSM_CANCEL_COMMAND'".
EXPORTING
COMMAND_NAME = "
EXCEPTIONS
ILLEGAL_COMMAND = 1 COMMAND_NOT_FOUND = 2 CANNOT_CANCEL_COMMAND = 3
IMPORTING Parameters details for CSM_CANCEL_COMMAND
COMMAND_NAME -
Data type: CHAR30Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_COMMAND -
Data type:Optional: No
Call by Reference: Yes
COMMAND_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
CANNOT_CANCEL_COMMAND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CSM_CANCEL_COMMAND 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_command_name | TYPE CHAR30, " | |||
| lv_illegal_command | TYPE CHAR30, " | |||
| lv_command_not_found | TYPE CHAR30, " | |||
| lv_cannot_cancel_command | TYPE CHAR30. " |
|   CALL FUNCTION 'CSM_CANCEL_COMMAND' " |
| EXPORTING | ||
| COMMAND_NAME | = lv_command_name | |
| EXCEPTIONS | ||
| ILLEGAL_COMMAND = 1 | ||
| COMMAND_NOT_FOUND = 2 | ||
| CANNOT_CANCEL_COMMAND = 3 | ||
| . " CSM_CANCEL_COMMAND | ||
ABAP code using 7.40 inline data declarations to call FM CSM_CANCEL_COMMAND
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