SAP RS_CHECK_CONV_EX_2_IN Function Module for Conversion check external -> internal









RS_CHECK_CONV_EX_2_IN is a standard rs check conv ex 2 in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion check external -> internal 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 rs check conv ex 2 in FM, simply by entering the name RS_CHECK_CONV_EX_2_IN into the relevant SAP transaction such as SE37 or SE38.

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



Function RS_CHECK_CONV_EX_2_IN 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 'RS_CHECK_CONV_EX_2_IN'"Conversion check external -> internal
EXPORTING
INPUT_EXTERNAL = "Input (external format)
TABLE_FIELD = "Dictionary field name
* QUERY = "

IMPORTING
INPUT_I_FORMAT = "Internal format, moved according to character.

EXCEPTIONS
INPUT_NOT_NUMERICAL = 1 INVALID_DATE = 10 INVALID_TIME_FORMAT = 11 INVALID_TIME = 12 INVALID_HEX_DIGIT = 13 UNEXPECTED_ERROR = 14 INVALID_FIELDNAME = 15 FIELD_AND_DESCR_INCOMPATIBLE = 16 INPUT_TOO_LONG = 17 NO_DECIMALS = 18 INVALID_FLOAT = 19 TOO_MANY_DECIMALS = 2 CONVERSION_EXIT_ERROR = 20 MORE_THAN_ONE_SIGN = 3 ILL_THOUSAND_SEPARATOR_DIST = 4 TOO_MANY_DIGITS = 5 SIGN_FOR_UNSIGNED = 6 TOO_LARGE = 7 TOO_SMALL = 8 INVALID_DATE_FORMAT = 9
.



IMPORTING Parameters details for RS_CHECK_CONV_EX_2_IN

INPUT_EXTERNAL - Input (external format)

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

TABLE_FIELD - Dictionary field name

Data type: TABFIELD
Optional: No
Call by Reference: No ( called with pass by value option)

QUERY -

Data type:
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RS_CHECK_CONV_EX_2_IN

INPUT_I_FORMAT - Internal format, moved according to character.

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INPUT_NOT_NUMERICAL - Non-numeric input

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_DATE - Invalid date

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_TIME_FORMAT - Invalid time format

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_TIME - Invalid time

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_HEX_DIGIT - Incorrect hex character

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UNEXPECTED_ERROR - Unintercepted error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_FIELDNAME - Field not in Dictionary

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FIELD_AND_DESCR_INCOMPATIBLE - Output field does not match Dictionary description

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INPUT_TOO_LONG - Input longer than output length of output field

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_DECIMALS - Decimal separator without subsequent decimal places

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_FLOAT - Invalid floating point entry

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOO_MANY_DECIMALS - Too many places after the decimal point

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CONVERSION_EXIT_ERROR - Error in conversion exit

Data type:
Optional: No
Call by Reference: Yes

MORE_THAN_ONE_SIGN - +/- sign input multiple times

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ILL_THOUSAND_SEPARATOR_DIST - Separation between thousands not = 0 mod 3

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOO_MANY_DIGITS - Too many characters in whole number field

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

SIGN_FOR_UNSIGNED - No +/- signs allowed

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOO_LARGE - Value too large

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOO_SMALL - Value too small

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_DATE_FORMAT - Invalid date format

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RS_CHECK_CONV_EX_2_IN 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_input_external  TYPE C, "   
lv_input_i_format  TYPE C, "   
lv_input_not_numerical  TYPE C, "   
lv_invalid_date  TYPE C, "   
lv_invalid_time_format  TYPE C, "   
lv_invalid_time  TYPE C, "   
lv_invalid_hex_digit  TYPE C, "   
lv_unexpected_error  TYPE C, "   
lv_invalid_fieldname  TYPE C, "   
lv_field_and_descr_incompatible  TYPE C, "   
lv_input_too_long  TYPE C, "   
lv_no_decimals  TYPE C, "   
lv_invalid_float  TYPE C, "   
lv_table_field  TYPE TABFIELD, "   
lv_too_many_decimals  TYPE TABFIELD, "   
lv_conversion_exit_error  TYPE TABFIELD, "   
lv_query  TYPE TABFIELD, "   
lv_more_than_one_sign  TYPE TABFIELD, "   
lv_ill_thousand_separator_dist  TYPE TABFIELD, "   
lv_too_many_digits  TYPE TABFIELD, "   
lv_sign_for_unsigned  TYPE TABFIELD, "   
lv_too_large  TYPE TABFIELD, "   
lv_too_small  TYPE TABFIELD, "   
lv_invalid_date_format  TYPE TABFIELD. "   

  CALL FUNCTION 'RS_CHECK_CONV_EX_2_IN'  "Conversion check external -> internal
    EXPORTING
         INPUT_EXTERNAL = lv_input_external
         TABLE_FIELD = lv_table_field
         QUERY = lv_query
    IMPORTING
         INPUT_I_FORMAT = lv_input_i_format
    EXCEPTIONS
        INPUT_NOT_NUMERICAL = 1
        INVALID_DATE = 10
        INVALID_TIME_FORMAT = 11
        INVALID_TIME = 12
        INVALID_HEX_DIGIT = 13
        UNEXPECTED_ERROR = 14
        INVALID_FIELDNAME = 15
        FIELD_AND_DESCR_INCOMPATIBLE = 16
        INPUT_TOO_LONG = 17
        NO_DECIMALS = 18
        INVALID_FLOAT = 19
        TOO_MANY_DECIMALS = 2
        CONVERSION_EXIT_ERROR = 20
        MORE_THAN_ONE_SIGN = 3
        ILL_THOUSAND_SEPARATOR_DIST = 4
        TOO_MANY_DIGITS = 5
        SIGN_FOR_UNSIGNED = 6
        TOO_LARGE = 7
        TOO_SMALL = 8
        INVALID_DATE_FORMAT = 9
. " RS_CHECK_CONV_EX_2_IN




ABAP code using 7.40 inline data declarations to call FM RS_CHECK_CONV_EX_2_IN

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!