SAP SDME_ODT_TC_AGI_CHECK_DEL Function Module for
SDME_ODT_TC_AGI_CHECK_DEL is a standard sdme odt tc agi check del 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 sdme odt tc agi check del FM, simply by entering the name SDME_ODT_TC_AGI_CHECK_DEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDME_ODT
Program Name: SAPLSDME_ODT
Main Program: SAPLSDME_ODT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SDME_ODT_TC_AGI_CHECK_DEL 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 'SDME_ODT_TC_AGI_CHECK_DEL'".
EXPORTING
DELETE_LINE = "
TABLES
MSGLIST = "
EXCEPTIONS
CHECK_FAILED = 1
IMPORTING Parameters details for SDME_ODT_TC_AGI_CHECK_DEL
DELETE_LINE -
Data type: ANYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SDME_ODT_TC_AGI_CHECK_DEL
MSGLIST -
Data type: TCDAT_MSG_LISTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHECK_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SDME_ODT_TC_AGI_CHECK_DEL 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: | ||||
| lt_msglist | TYPE STANDARD TABLE OF TCDAT_MSG_LIST, " | |||
| lv_delete_line | TYPE ANY, " | |||
| lv_check_failed | TYPE ANY. " |
|   CALL FUNCTION 'SDME_ODT_TC_AGI_CHECK_DEL' " |
| EXPORTING | ||
| DELETE_LINE | = lv_delete_line | |
| TABLES | ||
| MSGLIST | = lt_msglist | |
| EXCEPTIONS | ||
| CHECK_FAILED = 1 | ||
| . " SDME_ODT_TC_AGI_CHECK_DEL | ||
ABAP code using 7.40 inline data declarations to call FM SDME_ODT_TC_AGI_CHECK_DEL
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