SAP /ISDFPS/SEND_COMMAND_EXEC_UPD Function Module for
/ISDFPS/SEND_COMMAND_EXEC_UPD is a standard /isdfps/send command exec upd 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 /isdfps/send command exec upd FM, simply by entering the name /ISDFPS/SEND_COMMAND_EXEC_UPD into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ISDFPS/CS_COMMAND
Program Name: /ISDFPS/SAPLCS_COMMAND
Main Program: /ISDFPS/SAPLCS_COMMAND
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function /ISDFPS/SEND_COMMAND_EXEC_UPD 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 '/ISDFPS/SEND_COMMAND_EXEC_UPD'".
EXPORTING
ICOMMAND = "
* OBJ_TYPE = '/ISDFPS/CM' "
* SERIAL_ID = '0' "
TABLES
* EXTENSIONIN = "
* XIFORCE = "
* UPSLINK = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
IMPORTING Parameters details for /ISDFPS/SEND_COMMAND_EXEC_UPD
ICOMMAND -
Data type: /ISDFPS/C_CS_CMD-COMMANDOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: '/ISDFPS/CM'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /ISDFPS/SEND_COMMAND_EXEC_UPD
EXTENSIONIN -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
XIFORCE -
Data type: /ISDFPS/BAPI_XI_FORCEOptional: Yes
Call by Reference: No ( called with pass by value option)
UPSLINK -
Data type: BAPI_UPSLINK_COREOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /ISDFPS/SEND_COMMAND_EXEC_UPD 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_icommand | TYPE /ISDFPS/C_CS_CMD-COMMAND, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_xiforce | TYPE STANDARD TABLE OF /ISDFPS/BAPI_XI_FORCE, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " '/ISDFPS/CM' | |||
| lt_upslink | TYPE STANDARD TABLE OF BAPI_UPSLINK_CORE, " | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID. " |
|   CALL FUNCTION '/ISDFPS/SEND_COMMAND_EXEC_UPD' " |
| EXPORTING | ||
| ICOMMAND | = lv_icommand | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| EXTENSIONIN | = lt_extensionin | |
| XIFORCE | = lt_xiforce | |
| UPSLINK | = lt_upslink | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| . " /ISDFPS/SEND_COMMAND_EXEC_UPD | ||
ABAP code using 7.40 inline data declarations to call FM /ISDFPS/SEND_COMMAND_EXEC_UPD
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 COMMAND FROM /ISDFPS/C_CS_CMD INTO @DATA(ld_icommand). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = '/ISDFPS/CM'. | |||
| "SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects