SAP EDESK_INST_UPDATE_EXT Function Module for Update Instances Externally
EDESK_INST_UPDATE_EXT is a standard edesk inst update ext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Instances Externally processing and below is the pattern details for this FM, 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 edesk inst update ext FM, simply by entering the name EDESK_INST_UPDATE_EXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDESK_INST
Program Name: SAPLEDESK_INST
Main Program: SAPLEDESK_INST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDESK_INST_UPDATE_EXT 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 'EDESK_INST_UPDATE_EXT'"Update Instances Externally.
EXPORTING
IT_INSTANCES = "Tabellentyp für EDESK_INST_DIR
EXCEPTIONS
UPDATE_FAILED = 1
IMPORTING Parameters details for EDESK_INST_UPDATE_EXT
IT_INSTANCES - Tabellentyp für EDESK_INST_DIR
Data type: EDESK_INST_DIR_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
UPDATE_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EDESK_INST_UPDATE_EXT 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_it_instances | TYPE EDESK_INST_DIR_TAB, " | |||
| lv_update_failed | TYPE EDESK_INST_DIR_TAB. " |
|   CALL FUNCTION 'EDESK_INST_UPDATE_EXT' "Update Instances Externally |
| EXPORTING | ||
| IT_INSTANCES | = lv_it_instances | |
| EXCEPTIONS | ||
| UPDATE_FAILED = 1 | ||
| . " EDESK_INST_UPDATE_EXT | ||
ABAP code using 7.40 inline data declarations to call FM EDESK_INST_UPDATE_EXT
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