SAP ISM_RETURN_DATA_CHECK Function Module for Consistency Check on Return Data
ISM_RETURN_DATA_CHECK is a standard ism return data 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 Consistency Check on Return Data 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 return data check FM, simply by entering the name ISM_RETURN_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: JPISM
Program Name: SAPLJPISM
Main Program: SAPLJPISM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_RETURN_DATA_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_RETURN_DATA_CHECK'"Consistency Check on Return Data.
EXPORTING
PS_I_MVKE = "Sales Data for Material
EXCEPTIONS
FLAG_RETURN_NOT_SET = 1 DATE_MISSING = 2 DATE_NOT_VALID = 3 DATE_END_LT_DATE_FROM = 4
IMPORTING Parameters details for ISM_RETURN_DATA_CHECK
PS_I_MVKE - Sales Data for Material
Data type: MVKEOptional: No
Call by Reference: Yes
EXCEPTIONS details
FLAG_RETURN_NOT_SET -
Data type:Optional: No
Call by Reference: Yes
DATE_MISSING -
Data type:Optional: No
Call by Reference: Yes
DATE_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
DATE_END_LT_DATE_FROM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_RETURN_DATA_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_ps_i_mvke | TYPE MVKE, " | |||
| lv_flag_return_not_set | TYPE MVKE, " | |||
| lv_date_missing | TYPE MVKE, " | |||
| lv_date_not_valid | TYPE MVKE, " | |||
| lv_date_end_lt_date_from | TYPE MVKE. " |
|   CALL FUNCTION 'ISM_RETURN_DATA_CHECK' "Consistency Check on Return Data |
| EXPORTING | ||
| PS_I_MVKE | = lv_ps_i_mvke | |
| EXCEPTIONS | ||
| FLAG_RETURN_NOT_SET = 1 | ||
| DATE_MISSING = 2 | ||
| DATE_NOT_VALID = 3 | ||
| DATE_END_LT_DATE_FROM = 4 | ||
| . " ISM_RETURN_DATA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISM_RETURN_DATA_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