SAP FCOM_CONVERT_VALUE_EX_2_I Function Module for









FCOM_CONVERT_VALUE_EX_2_I is a standard fcom convert value ex 2 i 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 fcom convert value ex 2 i FM, simply by entering the name FCOM_CONVERT_VALUE_EX_2_I into the relevant SAP transaction such as SE37 or SE38.

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



Function FCOM_CONVERT_VALUE_EX_2_I 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 'FCOM_CONVERT_VALUE_EX_2_I'"
  EXPORTING
   I_EXTERNAL =  "
   I_CURRENCY =  "

 IMPORTING
   E_INTERNAL =  "

EXCEPTIONS
   INPUT_NOT_NUMERICAL = 1    INVALID_DATE = 10    INVALID_TIME_FORMAT = 11    INVALID_TIME = 12    INVALID_HEX_DIGIT = 13    UNEXPECTED_ERROR = 14    TOO_MANY_DECIMALS = 2    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 FCOM_CONVERT_VALUE_EX_2_I

I_EXTERNAL -

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

I_CURRENCY -

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

EXPORTING Parameters details for FCOM_CONVERT_VALUE_EX_2_I

E_INTERNAL -

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

EXCEPTIONS details

INPUT_NOT_NUMERICAL -

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATE -

Data type:
Optional: No
Call by Reference: Yes

INVALID_TIME_FORMAT -

Data type:
Optional: No
Call by Reference: Yes

INVALID_TIME -

Data type:
Optional: No
Call by Reference: Yes

INVALID_HEX_DIGIT -

Data type:
Optional: No
Call by Reference: Yes

UNEXPECTED_ERROR -

Data type:
Optional: No
Call by Reference: Yes

TOO_MANY_DECIMALS -

Data type:
Optional: No
Call by Reference: Yes

MORE_THAN_ONE_SIGN -

Data type:
Optional: No
Call by Reference: Yes

ILL_THOUSAND_SEPARATOR_DIST -

Data type:
Optional: No
Call by Reference: Yes

TOO_MANY_DIGITS -

Data type:
Optional: No
Call by Reference: Yes

SIGN_FOR_UNSIGNED -

Data type:
Optional: No
Call by Reference: Yes

TOO_LARGE -

Data type:
Optional: No
Call by Reference: Yes

TOO_SMALL -

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATE_FORMAT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FCOM_CONVERT_VALUE_EX_2_I 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_e_internal  TYPE WKGXXX, "   
lv_i_external  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_i_currency  TYPE KWAER, "   
lv_too_many_decimals  TYPE KWAER, "   
lv_more_than_one_sign  TYPE KWAER, "   
lv_ill_thousand_separator_dist  TYPE KWAER, "   
lv_too_many_digits  TYPE KWAER, "   
lv_sign_for_unsigned  TYPE KWAER, "   
lv_too_large  TYPE KWAER, "   
lv_too_small  TYPE KWAER, "   
lv_invalid_date_format  TYPE KWAER. "   

  CALL FUNCTION 'FCOM_CONVERT_VALUE_EX_2_I'  "
    EXPORTING
         I_EXTERNAL = lv_i_external
         I_CURRENCY = lv_i_currency
    IMPORTING
         E_INTERNAL = lv_e_internal
    EXCEPTIONS
        INPUT_NOT_NUMERICAL = 1
        INVALID_DATE = 10
        INVALID_TIME_FORMAT = 11
        INVALID_TIME = 12
        INVALID_HEX_DIGIT = 13
        UNEXPECTED_ERROR = 14
        TOO_MANY_DECIMALS = 2
        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
. " FCOM_CONVERT_VALUE_EX_2_I




ABAP code using 7.40 inline data declarations to call FM FCOM_CONVERT_VALUE_EX_2_I

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!