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

Function ISH_CHECK_FIELD_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 'ISH_CHECK_FIELD_TYPE'".
EXPORTING
DECIMALPLACES = "Number of decimal places
INPUT = "Input string
INPUT_TYPE = "Type of input string
LENGTH = "Number of allowed input characters
* LR_SCREEN = 'R' "Left/right justified screen output
* SCREEN_OR_DB = 'S' "Input source
IMPORTING
SCREEN = "Screen display
STORAGE = "DB storage
EXCEPTIONS
INPUT_TOO_LONG = 1 NOT_NUMERIC = 2 NO_DECIMALPOINT = 3 PARAM_DECIMALPLACES_WRONG = 4 PARAM_LENGTH_WRONG = 5 TOO_MANY_DECIMALPLACES = 6 WRONG_INPUT_SOURCE = 7 WRONG_INPUT_TYPE = 8
IMPORTING Parameters details for ISH_CHECK_FIELD_TYPE
DECIMALPLACES - Number of decimal places
Data type: NTSI-SPKOMOptional: No
Call by Reference: No ( called with pass by value option)
INPUT - Input string
Data type: NTSP-TWERTOptional: No
Call by Reference: No ( called with pass by value option)
INPUT_TYPE - Type of input string
Data type: NTSI-SPTYPOptional: No
Call by Reference: No ( called with pass by value option)
LENGTH - Number of allowed input characters
Data type: NTSI-SPLENOptional: No
Call by Reference: No ( called with pass by value option)
LR_SCREEN - Left/right justified screen output
Data type: CHAR1Default: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SCREEN_OR_DB - Input source
Data type: CHAR1Default: 'S'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISH_CHECK_FIELD_TYPE
SCREEN - Screen display
Data type: NTSP-TWERTOptional: No
Call by Reference: No ( called with pass by value option)
STORAGE - DB storage
Data type: NTSP-TWERTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_TOO_LONG - Input too long
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_NUMERIC - Input string is not numeric
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_DECIMALPOINT - Decimal point not supported
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_DECIMALPLACES_WRONG - Parameter DECIMALPLACES incompatible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAM_LENGTH_WRONG - Parameter LENGTH incompatible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TOO_MANY_DECIMALPLACES - Too many decimal places
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_INPUT_SOURCE - Illegal input source
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_INPUT_TYPE - Illegal input type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_CHECK_FIELD_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_screen | TYPE NTSP-TWERT, " | |||
| lv_decimalplaces | TYPE NTSI-SPKOM, " | |||
| lv_input_too_long | TYPE NTSI, " | |||
| lv_input | TYPE NTSP-TWERT, " | |||
| lv_storage | TYPE NTSP-TWERT, " | |||
| lv_not_numeric | TYPE NTSP, " | |||
| lv_input_type | TYPE NTSI-SPTYP, " | |||
| lv_no_decimalpoint | TYPE NTSI, " | |||
| lv_length | TYPE NTSI-SPLEN, " | |||
| lv_param_decimalplaces_wrong | TYPE NTSI, " | |||
| lv_lr_screen | TYPE CHAR1, " 'R' | |||
| lv_param_length_wrong | TYPE CHAR1, " | |||
| lv_screen_or_db | TYPE CHAR1, " 'S' | |||
| lv_too_many_decimalplaces | TYPE CHAR1, " | |||
| lv_wrong_input_source | TYPE CHAR1, " | |||
| lv_wrong_input_type | TYPE CHAR1. " |
|   CALL FUNCTION 'ISH_CHECK_FIELD_TYPE' " |
| EXPORTING | ||
| DECIMALPLACES | = lv_decimalplaces | |
| INPUT | = lv_input | |
| INPUT_TYPE | = lv_input_type | |
| LENGTH | = lv_length | |
| LR_SCREEN | = lv_lr_screen | |
| SCREEN_OR_DB | = lv_screen_or_db | |
| IMPORTING | ||
| SCREEN | = lv_screen | |
| STORAGE | = lv_storage | |
| EXCEPTIONS | ||
| INPUT_TOO_LONG = 1 | ||
| NOT_NUMERIC = 2 | ||
| NO_DECIMALPOINT = 3 | ||
| PARAM_DECIMALPLACES_WRONG = 4 | ||
| PARAM_LENGTH_WRONG = 5 | ||
| TOO_MANY_DECIMALPLACES = 6 | ||
| WRONG_INPUT_SOURCE = 7 | ||
| WRONG_INPUT_TYPE = 8 | ||
| . " ISH_CHECK_FIELD_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM ISH_CHECK_FIELD_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.| "SELECT single TWERT FROM NTSP INTO @DATA(ld_screen). | ||||
| "SELECT single SPKOM FROM NTSI INTO @DATA(ld_decimalplaces). | ||||
| "SELECT single TWERT FROM NTSP INTO @DATA(ld_input). | ||||
| "SELECT single TWERT FROM NTSP INTO @DATA(ld_storage). | ||||
| "SELECT single SPTYP FROM NTSI INTO @DATA(ld_input_type). | ||||
| "SELECT single SPLEN FROM NTSI INTO @DATA(ld_length). | ||||
| DATA(ld_lr_screen) | = 'R'. | |||
| DATA(ld_screen_or_db) | = 'S'. | |||
Search for further information about these or an SAP related objects