SAP ISU_CHECK_INPUT_DATA Function Module for Private: Check Day Profile Allocation









ISU_CHECK_INPUT_DATA is a standard isu check input data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Private: Check Day Profile Allocation 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 check input data FM, simply by entering the name ISU_CHECK_INPUT_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: EEDM_SYNPROF
Program Name: SAPLEEDM_SYNPROF
Main Program: SAPLEEDM_SYNPROF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_CHECK_INPUT_DATA 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_CHECK_INPUT_DATA'"Private: Check Day Profile Allocation
CHANGING
XY_OBJ = "Object Structure for Synthetic Profiles
X_EEDM_SYNPROFALLOC_SCREEN = "Table Control Data for Day Profile Allocation

EXCEPTIONS
ERROR_OCCURRED = 1 NOT_AUTHORIZED = 2 DATA_INVALID = 3
.



CHANGING Parameters details for ISU_CHECK_INPUT_DATA

XY_OBJ - Object Structure for Synthetic Profiles

Data type: EEDM_SYNPROF_OBJECT
Optional: No
Call by Reference: Yes

X_EEDM_SYNPROFALLOC_SCREEN - Table Control Data for Day Profile Allocation

Data type: EEDM_SYNPROFALLOC_SCREEN
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURRED -

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: Yes

DATA_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_CHECK_INPUT_DATA 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_obj  TYPE EEDM_SYNPROF_OBJECT, "   
lv_error_occurred  TYPE EEDM_SYNPROF_OBJECT, "   
lv_not_authorized  TYPE EEDM_SYNPROF_OBJECT, "   
lv_x_eedm_synprofalloc_screen  TYPE EEDM_SYNPROFALLOC_SCREEN, "   
lv_data_invalid  TYPE EEDM_SYNPROFALLOC_SCREEN. "   

  CALL FUNCTION 'ISU_CHECK_INPUT_DATA'  "Private: Check Day Profile Allocation
    CHANGING
         XY_OBJ = lv_xy_obj
         X_EEDM_SYNPROFALLOC_SCREEN = lv_x_eedm_synprofalloc_screen
    EXCEPTIONS
        ERROR_OCCURRED = 1
        NOT_AUTHORIZED = 2
        DATA_INVALID = 3
. " ISU_CHECK_INPUT_DATA




ABAP code using 7.40 inline data declarations to call FM ISU_CHECK_INPUT_DATA

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!