SAP IM_SM_CHECK_SD_DELETE_ITEM Function Module for NOTRANSL: Loeschen PM/SM-Auftrag
IM_SM_CHECK_SD_DELETE_ITEM is a standard im sm check sd delete item SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Loeschen PM/SM-Auftrag 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 im sm check sd delete item FM, simply by entering the name IM_SM_CHECK_SD_DELETE_ITEM into the relevant SAP transaction such as SE37 or SE38.
Function Group: IMSM
Program Name: SAPLIMSM
Main Program: SAPLIMSM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IM_SM_CHECK_SD_DELETE_ITEM 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 'IM_SM_CHECK_SD_DELETE_ITEM'"NOTRANSL: Loeschen PM/SM-Auftrag.
EXPORTING
OBJNR = "Object Number
EXCEPTIONS
ORDER_NOT_FOUND = 1 DELETION_NOT_ALLOWED = 2
IMPORTING Parameters details for IM_SM_CHECK_SD_DELETE_ITEM
OBJNR - Object Number
Data type: CAUFVD-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORDER_NOT_FOUND - Order not found
Data type:Optional: No
Call by Reference: Yes
DELETION_NOT_ALLOWED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IM_SM_CHECK_SD_DELETE_ITEM 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_objnr | TYPE CAUFVD-OBJNR, " | |||
| lv_order_not_found | TYPE CAUFVD, " | |||
| lv_deletion_not_allowed | TYPE CAUFVD. " |
|   CALL FUNCTION 'IM_SM_CHECK_SD_DELETE_ITEM' "NOTRANSL: Loeschen PM/SM-Auftrag |
| EXPORTING | ||
| OBJNR | = lv_objnr | |
| EXCEPTIONS | ||
| ORDER_NOT_FOUND = 1 | ||
| DELETION_NOT_ALLOWED = 2 | ||
| . " IM_SM_CHECK_SD_DELETE_ITEM | ||
ABAP code using 7.40 inline data declarations to call FM IM_SM_CHECK_SD_DELETE_ITEM
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 OBJNR FROM CAUFVD INTO @DATA(ld_objnr). | ||||
Search for further information about these or an SAP related objects