SAP ISU_SCHEDULE_DATA_TEST Function Module for INTERNAL: Check Schedule Data for Contracts
ISU_SCHEDULE_DATA_TEST is a standard isu schedule data test SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Check Schedule Data for Contracts 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 isu schedule data test FM, simply by entering the name ISU_SCHEDULE_DATA_TEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: ES43
Program Name: SAPLES43
Main Program: SAPLES43
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_SCHEDULE_DATA_TEST 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 'ISU_SCHEDULE_DATA_TEST'"INTERNAL: Check Schedule Data for Contracts.
IMPORTING
ERR_FIELD = "
CHANGING
XY_SCHED = "
EXCEPTIONS
SCHED_DATA_INVALID = 1
EXPORTING Parameters details for ISU_SCHEDULE_DATA_TEST
ERR_FIELD -
Data type: EENO_GEN-FELDNAMEOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISU_SCHEDULE_DATA_TEST
XY_SCHED -
Data type: ESCHEDOptional: No
Call by Reference: Yes
EXCEPTIONS details
SCHED_DATA_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_SCHEDULE_DATA_TEST 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_xy_sched | TYPE ESCHED, " | |||
| lv_err_field | TYPE EENO_GEN-FELDNAME, " | |||
| lv_sched_data_invalid | TYPE EENO_GEN. " |
|   CALL FUNCTION 'ISU_SCHEDULE_DATA_TEST' "INTERNAL: Check Schedule Data for Contracts |
| IMPORTING | ||
| ERR_FIELD | = lv_err_field | |
| CHANGING | ||
| XY_SCHED | = lv_xy_sched | |
| EXCEPTIONS | ||
| SCHED_DATA_INVALID = 1 | ||
| . " ISU_SCHEDULE_DATA_TEST | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SCHEDULE_DATA_TEST
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 FELDNAME FROM EENO_GEN INTO @DATA(ld_err_field). | ||||
Search for further information about these or an SAP related objects