SAP ISU_EDM_DAYTYPE_CHECK Function Module for
ISU_EDM_DAYTYPE_CHECK is a standard isu edm daytype check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 edm daytype check FM, simply by entering the name ISU_EDM_DAYTYPE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDM_CONSISTENCY_CHECKS
Program Name: SAPLEEDM_CONSISTENCY_CHECKS
Main Program: SAPLEEDM_CONSISTENCY_CHECKS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISU_EDM_DAYTYPE_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 'ISU_EDM_DAYTYPE_CHECK'".
EXPORTING
X_DAYTYPE = "
EXCEPTIONS
DAYTYPE_NOT_CONSISTENT = 1
IMPORTING Parameters details for ISU_EDM_DAYTYPE_CHECK
X_DAYTYPE -
Data type: V_EDAYTYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
DAYTYPE_NOT_CONSISTENT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_EDM_DAYTYPE_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_x_daytype | TYPE V_EDAYTYPE, " | |||
lv_daytype_not_consistent | TYPE V_EDAYTYPE. " |
  CALL FUNCTION 'ISU_EDM_DAYTYPE_CHECK' " |
EXPORTING | ||
X_DAYTYPE | = lv_x_daytype | |
EXCEPTIONS | ||
DAYTYPE_NOT_CONSISTENT = 1 | ||
. " ISU_EDM_DAYTYPE_CHECK |
ABAP code using 7.40 inline data declarations to call FM ISU_EDM_DAYTYPE_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