SAP LXDCK_LINK_INSERT Function Module for Insert decision and cancel TO link to DB
LXDCK_LINK_INSERT is a standard lxdck link insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Insert decision and cancel TO link to DB 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 lxdck link insert FM, simply by entering the name LXDCK_LINK_INSERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXDCK_MDCSN
Program Name: SAPLLXDCK_MDCSN
Main Program: SAPLLXDCK_MDCSN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXDCK_LINK_INSERT 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 'LXDCK_LINK_INSERT'"Insert decision and cancel TO link to DB.
EXPORTING
IT_LXDTO = "Table type decision TO link
EXCEPTIONS
NOT_SAVED = 1 SYSTEM_FAILURE = 2 COMMUNICATION_ERROR = 3
IMPORTING Parameters details for LXDCK_LINK_INSERT
IT_LXDTO - Table type decision TO link
Data type: LXDCK_LXDTO_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_SAVED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXDCK_LINK_INSERT 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_lxdto | TYPE LXDCK_LXDTO_T, " | |||
| lv_not_saved | TYPE LXDCK_LXDTO_T, " | |||
| lv_system_failure | TYPE LXDCK_LXDTO_T, " | |||
| lv_communication_error | TYPE LXDCK_LXDTO_T. " |
|   CALL FUNCTION 'LXDCK_LINK_INSERT' "Insert decision and cancel TO link to DB |
| EXPORTING | ||
| IT_LXDTO | = lv_it_lxdto | |
| EXCEPTIONS | ||
| NOT_SAVED = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| COMMUNICATION_ERROR = 3 | ||
| . " LXDCK_LINK_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM LXDCK_LINK_INSERT
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