SAP ISM_2SD_DELIVERYTYPE_CHECK Function Module for Check Whether Delivery Type Selected for LES
ISM_2SD_DELIVERYTYPE_CHECK is a standard ism 2sd deliverytype check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Delivery Type Selected for LES 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 ism 2sd deliverytype check FM, simply by entering the name ISM_2SD_DELIVERYTYPE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JMSD2SD
Program Name: SAPLJMSD2SD
Main Program: SAPLJMSD2SD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_2SD_DELIVERYTYPE_CHECK 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 'ISM_2SD_DELIVERYTYPE_CHECK'"Check Whether Delivery Type Selected for LES.
EXPORTING
IN_LIEFERART = "Delivery Type
EXCEPTIONS
NOT_FOUND = 1 NOT_MARKED = 2
IMPORTING Parameters details for ISM_2SD_DELIVERYTYPE_CHECK
IN_LIEFERART - Delivery Type
Data type: LIEFERARTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
NOT_MARKED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_2SD_DELIVERYTYPE_CHECK 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_not_found | TYPE STRING, " | |||
| lv_in_lieferart | TYPE LIEFERART, " | |||
| lv_not_marked | TYPE LIEFERART. " |
|   CALL FUNCTION 'ISM_2SD_DELIVERYTYPE_CHECK' "Check Whether Delivery Type Selected for LES |
| EXPORTING | ||
| IN_LIEFERART | = lv_in_lieferart | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NOT_MARKED = 2 | ||
| . " ISM_2SD_DELIVERYTYPE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISM_2SD_DELIVERYTYPE_CHECK
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