SAP DD_INT_CHECK_VALUE_FOR_TYPE Function Module for
DD_INT_CHECK_VALUE_FOR_TYPE is a standard dd int check value for type 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 dd int check value for type FM, simply by entering the name DD_INT_CHECK_VALUE_FOR_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SINT
Program Name: SAPLSINT
Main Program: SAPLSINT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_INT_CHECK_VALUE_FOR_TYPE 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 'DD_INT_CHECK_VALUE_FOR_TYPE'".
EXPORTING
TYPEDEF = "
VALUE = "Value to be Checked
* QUOTATION_MODE = 'X' "
* WILDCARD = ' ' "
* MASK = ' ' "
* ESCAPE = ' ' "Escape character
* NON_STANDARD_OK = ' ' "
* APPLY_DYNP_RESTRICTIONS = ' ' "
IMPORTING
EXPANDED_VALUE = "
IS_PATTERN = "
ILLEGAL_FORMAT = "
TOO_LONG = "
INCOMPATIBLE = "
EXCEPTIONS
TYPE_NOT_EXISTS = 1 ILLEGAL_TYPE = 2
IMPORTING Parameters details for DD_INT_CHECK_VALUE_FOR_TYPE
TYPEDEF -
Data type: DFIESOptional: No
Call by Reference: Yes
VALUE - Value to be Checked
Data type:Optional: No
Call by Reference: Yes
QUOTATION_MODE -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
WILDCARD -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: Yes
MASK -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: Yes
ESCAPE - Escape character
Data type: CDefault: ' '
Optional: Yes
Call by Reference: Yes
NON_STANDARD_OK -
Data type: DDBOOL_DDefault: ' '
Optional: Yes
Call by Reference: Yes
APPLY_DYNP_RESTRICTIONS -
Data type: DDBOOL_DDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for DD_INT_CHECK_VALUE_FOR_TYPE
EXPANDED_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IS_PATTERN -
Data type: DDBOOL_DOptional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_FORMAT -
Data type: DDBOOL_DOptional: No
Call by Reference: No ( called with pass by value option)
TOO_LONG -
Data type: DDBOOL_DOptional: No
Call by Reference: No ( called with pass by value option)
INCOMPATIBLE -
Data type: DDBOOL_DOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
TYPE_NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_INT_CHECK_VALUE_FOR_TYPE 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_typedef | TYPE DFIES, " | |||
| lv_expanded_value | TYPE DFIES, " | |||
| lv_type_not_exists | TYPE DFIES, " | |||
| lv_value | TYPE DFIES, " | |||
| lv_is_pattern | TYPE DDBOOL_D, " | |||
| lv_illegal_type | TYPE DDBOOL_D, " | |||
| lv_illegal_format | TYPE DDBOOL_D, " | |||
| lv_quotation_mode | TYPE C, " 'X' | |||
| lv_too_long | TYPE DDBOOL_D, " | |||
| lv_wildcard | TYPE C, " ' ' | |||
| lv_mask | TYPE C, " ' ' | |||
| lv_incompatible | TYPE DDBOOL_D, " | |||
| lv_escape | TYPE C, " ' ' | |||
| lv_non_standard_ok | TYPE DDBOOL_D, " ' ' | |||
| lv_apply_dynp_restrictions | TYPE DDBOOL_D. " ' ' |
|   CALL FUNCTION 'DD_INT_CHECK_VALUE_FOR_TYPE' " |
| EXPORTING | ||
| TYPEDEF | = lv_typedef | |
| VALUE | = lv_value | |
| QUOTATION_MODE | = lv_quotation_mode | |
| WILDCARD | = lv_wildcard | |
| MASK | = lv_mask | |
| ESCAPE | = lv_escape | |
| NON_STANDARD_OK | = lv_non_standard_ok | |
| APPLY_DYNP_RESTRICTIONS | = lv_apply_dynp_restrictions | |
| IMPORTING | ||
| EXPANDED_VALUE | = lv_expanded_value | |
| IS_PATTERN | = lv_is_pattern | |
| ILLEGAL_FORMAT | = lv_illegal_format | |
| TOO_LONG | = lv_too_long | |
| INCOMPATIBLE | = lv_incompatible | |
| EXCEPTIONS | ||
| TYPE_NOT_EXISTS = 1 | ||
| ILLEGAL_TYPE = 2 | ||
| . " DD_INT_CHECK_VALUE_FOR_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM DD_INT_CHECK_VALUE_FOR_TYPE
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.| DATA(ld_quotation_mode) | = 'X'. | |||
| DATA(ld_wildcard) | = ' '. | |||
| DATA(ld_mask) | = ' '. | |||
| DATA(ld_escape) | = ' '. | |||
| DATA(ld_non_standard_ok) | = ' '. | |||
| DATA(ld_apply_dynp_restrictions) | = ' '. | |||
Search for further information about these or an SAP related objects