SAP ISM_SD_CHECK_UNSOLD_ITEM Function Module for IS-M: Checks for Return Item Data When Releasing Returns
ISM_SD_CHECK_UNSOLD_ITEM is a standard ism sd check unsold 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 IS-M: Checks for Return Item Data When Releasing Returns 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 sd check unsold item FM, simply by entering the name ISM_SD_CHECK_UNSOLD_ITEM into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDRETURNCHECK01
Program Name: SAPLJKSDRETURNCHECK01
Main Program: SAPLJKSDRETURNCHECK01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_SD_CHECK_UNSOLD_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 'ISM_SD_CHECK_UNSOLD_ITEM'"IS-M: Checks for Return Item Data When Releasing Returns.
EXPORTING
UNSOLD = "IS-M: Returns
POS = "
CUSTOMIZING = "IS-M: Customizing Table for Operation Type
* PROTOCOL = "IS-M: Return Log
RETURN = "IS-M: Messages
IMPORTING
OUT_ERROR = "
EXCEPTIONS
ISSUE_NOT_FOUND = 1
IMPORTING Parameters details for ISM_SD_CHECK_UNSOLD_ITEM
UNSOLD - IS-M: Returns
Data type: CL_ISM_SD_UNSOLDOptional: No
Call by Reference: Yes
POS -
Data type: CL_ISM_SD_UNSOLD_POSOptional: No
Call by Reference: Yes
CUSTOMIZING - IS-M: Customizing Table for Operation Type
Data type: TJKSDUNSOLDOptional: No
Call by Reference: Yes
PROTOCOL - IS-M: Return Log
Data type: CL_ISM_SD_DB_RETURN_PROTOCOLOptional: Yes
Call by Reference: Yes
RETURN - IS-M: Messages
Data type: CL_ISM_SD_MESSAGEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_CHECK_UNSOLD_ITEM
OUT_ERROR -
Data type: XFELDOptional: No
Call by Reference: Yes
EXCEPTIONS details
ISSUE_NOT_FOUND - Media issue not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_SD_CHECK_UNSOLD_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_unsold | TYPE CL_ISM_SD_UNSOLD, " | |||
| lv_out_error | TYPE XFELD, " | |||
| lv_issue_not_found | TYPE XFELD, " | |||
| lv_pos | TYPE CL_ISM_SD_UNSOLD_POS, " | |||
| lv_customizing | TYPE TJKSDUNSOLD, " | |||
| lv_protocol | TYPE CL_ISM_SD_DB_RETURN_PROTOCOL, " | |||
| lv_return | TYPE CL_ISM_SD_MESSAGE. " |
|   CALL FUNCTION 'ISM_SD_CHECK_UNSOLD_ITEM' "IS-M: Checks for Return Item Data When Releasing Returns |
| EXPORTING | ||
| UNSOLD | = lv_unsold | |
| POS | = lv_pos | |
| CUSTOMIZING | = lv_customizing | |
| PROTOCOL | = lv_protocol | |
| RETURN | = lv_return | |
| IMPORTING | ||
| OUT_ERROR | = lv_out_error | |
| EXCEPTIONS | ||
| ISSUE_NOT_FOUND = 1 | ||
| . " ISM_SD_CHECK_UNSOLD_ITEM | ||
ABAP code using 7.40 inline data declarations to call FM ISM_SD_CHECK_UNSOLD_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.Search for further information about these or an SAP related objects