SAP DDUT_INPUT_CHECK Function Module for DD: Simulation of Input Checks of DYNP for an ABAP Dictionary Field
DDUT_INPUT_CHECK is a standard ddut input 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 DD: Simulation of Input Checks of DYNP for an ABAP Dictionary Field 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 ddut input check FM, simply by entering the name DDUT_INPUT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDFC
Program Name: SAPLSDFC
Main Program: SAPLSDFC
Appliation area: S
Release date: 30-Apr-1999
Mode(Normal, Remote etc): Normal Function Module
Update:
Function DDUT_INPUT_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 'DDUT_INPUT_CHECK'"DD: Simulation of Input Checks of DYNP for an ABAP Dictionary Field.
EXPORTING
* TABNAME = "Name of Table (or Data Element)
* FIELDNAME = "Name of Field to be Checked
* CALLING_PROGRAM = "Name of calling program
* STRUCNAME = "Name of Suitable Structure in Calling Program
* VALUE = "Value to be Checked
* VALUE_IS_EXTERNAL = ' ' "Is Value to be Checked in External Representation
* ACCEPT_ALL_INITIAL = ' ' "If 'X', accept initial values in foreign key fields
* VALUE_LIST = "Value List (in Table Structure)
* NO_FORKEY_CHECK = ' ' "No foreign key check required
IMPORTING
MSGID = "Possibly Message Class of Error Message
MSGTY = "Possibly Severity of Error Message
MSGNO = "Possibly Number of Error Message
MSGV1 = "Possibly First Parameter for Error Message
MSGV2 = "Possibly Second Parameter for Error Message
MSGV3 = "Possibly Third Parameter for Error Message
MSGV4 = "Possibly Fourth Parameter for Error Message
VALUE_INTERNAL = "Internal Representation of VALUE
CHANGING
* ADDITIONAL_FIELDS = "Contents of Other Foreign Key Fields
TABLES
* FAILURE_TAB = "Messages for Failed Checks
EXCEPTIONS
NO_DDIC_FIELD = 1 ILLEGAL_MOVE = 2
IMPORTING Parameters details for DDUT_INPUT_CHECK
TABNAME - Name of Table (or Data Element)
Data type: DFIES-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
FIELDNAME - Name of Field to be Checked
Data type: DFIES-LFIELDNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
CALLING_PROGRAM - Name of calling program
Data type: SY-REPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
STRUCNAME - Name of Suitable Structure in Calling Program
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
VALUE - Value to be Checked
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
VALUE_IS_EXTERNAL - Is Value to be Checked in External Representation
Data type: DDBOOL_DDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACCEPT_ALL_INITIAL - If 'X', accept initial values in foreign key fields
Data type: DDBOOL_DDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
VALUE_LIST - Value List (in Table Structure)
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_FORKEY_CHECK - No foreign key check required
Data type: DDBOOL_DDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DDUT_INPUT_CHECK
MSGID - Possibly Message Class of Error Message
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
MSGTY - Possibly Severity of Error Message
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
MSGNO - Possibly Number of Error Message
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
MSGV1 - Possibly First Parameter for Error Message
Data type: SY-MSGV1Optional: No
Call by Reference: No ( called with pass by value option)
MSGV2 - Possibly Second Parameter for Error Message
Data type: SY-MSGV2Optional: No
Call by Reference: No ( called with pass by value option)
MSGV3 - Possibly Third Parameter for Error Message
Data type: SY-MSGV3Optional: No
Call by Reference: No ( called with pass by value option)
MSGV4 - Possibly Fourth Parameter for Error Message
Data type: SY-MSGV4Optional: No
Call by Reference: No ( called with pass by value option)
VALUE_INTERNAL - Internal Representation of VALUE
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for DDUT_INPUT_CHECK
ADDITIONAL_FIELDS - Contents of Other Foreign Key Fields
Data type: DCFIELDDATSOptional: Yes
Call by Reference: Yes
TABLES Parameters details for DDUT_INPUT_CHECK
FAILURE_TAB - Messages for Failed Checks
Data type: DDFKEYRCOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_DDIC_FIELD - Field to be Checked has no DDIC Reference
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_MOVE - Cannot copy to VALUE_INTERNAL
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DDUT_INPUT_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_msgid | TYPE SY-MSGID, " | |||
lv_tabname | TYPE DFIES-TABNAME, " | |||
lt_failure_tab | TYPE STANDARD TABLE OF DDFKEYRC, " | |||
lv_no_ddic_field | TYPE DDFKEYRC, " | |||
lv_additional_fields | TYPE DCFIELDDATS, " | |||
lv_msgty | TYPE SY-MSGTY, " | |||
lv_fieldname | TYPE DFIES-LFIELDNAME, " | |||
lv_illegal_move | TYPE DFIES, " | |||
lv_msgno | TYPE SY-MSGNO, " | |||
lv_calling_program | TYPE SY-REPID, " | |||
lv_msgv1 | TYPE SY-MSGV1, " | |||
lv_strucname | TYPE C, " | |||
lv_msgv2 | TYPE SY-MSGV2, " | |||
lv_value | TYPE SY, " | |||
lv_msgv3 | TYPE SY-MSGV3, " | |||
lv_value_is_external | TYPE DDBOOL_D, " SPACE | |||
lv_msgv4 | TYPE SY-MSGV4, " | |||
lv_accept_all_initial | TYPE DDBOOL_D, " SPACE | |||
lv_value_list | TYPE DDBOOL_D, " | |||
lv_value_internal | TYPE DDBOOL_D, " | |||
lv_no_forkey_check | TYPE DDBOOL_D. " SPACE |
  CALL FUNCTION 'DDUT_INPUT_CHECK' "DD: Simulation of Input Checks of DYNP for an ABAP Dictionary Field |
EXPORTING | ||
TABNAME | = lv_tabname | |
FIELDNAME | = lv_fieldname | |
CALLING_PROGRAM | = lv_calling_program | |
STRUCNAME | = lv_strucname | |
VALUE | = lv_value | |
VALUE_IS_EXTERNAL | = lv_value_is_external | |
ACCEPT_ALL_INITIAL | = lv_accept_all_initial | |
VALUE_LIST | = lv_value_list | |
NO_FORKEY_CHECK | = lv_no_forkey_check | |
IMPORTING | ||
MSGID | = lv_msgid | |
MSGTY | = lv_msgty | |
MSGNO | = lv_msgno | |
MSGV1 | = lv_msgv1 | |
MSGV2 | = lv_msgv2 | |
MSGV3 | = lv_msgv3 | |
MSGV4 | = lv_msgv4 | |
VALUE_INTERNAL | = lv_value_internal | |
CHANGING | ||
ADDITIONAL_FIELDS | = lv_additional_fields | |
TABLES | ||
FAILURE_TAB | = lt_failure_tab | |
EXCEPTIONS | ||
NO_DDIC_FIELD = 1 | ||
ILLEGAL_MOVE = 2 | ||
. " DDUT_INPUT_CHECK |
ABAP code using 7.40 inline data declarations to call FM DDUT_INPUT_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."SELECT single MSGID FROM SY INTO @DATA(ld_msgid). | ||||
"SELECT single TABNAME FROM DFIES INTO @DATA(ld_tabname). | ||||
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty). | ||||
"SELECT single LFIELDNAME FROM DFIES INTO @DATA(ld_fieldname). | ||||
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno). | ||||
"SELECT single REPID FROM SY INTO @DATA(ld_calling_program). | ||||
"SELECT single MSGV1 FROM SY INTO @DATA(ld_msgv1). | ||||
"SELECT single MSGV2 FROM SY INTO @DATA(ld_msgv2). | ||||
"SELECT single MSGV3 FROM SY INTO @DATA(ld_msgv3). | ||||
DATA(ld_value_is_external) | = ' '. | |||
"SELECT single MSGV4 FROM SY INTO @DATA(ld_msgv4). | ||||
DATA(ld_accept_all_initial) | = ' '. | |||
DATA(ld_no_forkey_check) | = ' '. | |||
Search for further information about these or an SAP related objects