SAP FMCA_STRING_TO_AMOUNT_CONVERT Function Module for Convert String to Amount









FMCA_STRING_TO_AMOUNT_CONVERT is a standard fmca string to amount convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert String to Amount 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 fmca string to amount convert FM, simply by entering the name FMCA_STRING_TO_AMOUNT_CONVERT into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_STRING_TO_AMOUNT_CONVERT 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 'FMCA_STRING_TO_AMOUNT_CONVERT'"Convert String to Amount
EXPORTING
STRING = "
* DECIMAL_SEPARATOR = "
* THOUSANDS_SEPARATOR = "
* WAERS = ' ' "

IMPORTING
BETRG = "

EXCEPTIONS
CONVERT_ERROR = 1
.



IMPORTING Parameters details for FMCA_STRING_TO_AMOUNT_CONVERT

STRING -

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

DECIMAL_SEPARATOR -

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

THOUSANDS_SEPARATOR -

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

WAERS -

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

EXPORTING Parameters details for FMCA_STRING_TO_AMOUNT_CONVERT

BETRG -

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

EXCEPTIONS details

CONVERT_ERROR -

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

Copy and paste ABAP code example for FMCA_STRING_TO_AMOUNT_CONVERT 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_betrg  TYPE STRING, "   
lv_string  TYPE STRING, "   
lv_convert_error  TYPE STRING, "   
lv_decimal_separator  TYPE STRING, "   
lv_thousands_separator  TYPE STRING, "   
lv_waers  TYPE STRING. "   SPACE

  CALL FUNCTION 'FMCA_STRING_TO_AMOUNT_CONVERT'  "Convert String to Amount
    EXPORTING
         STRING = lv_string
         DECIMAL_SEPARATOR = lv_decimal_separator
         THOUSANDS_SEPARATOR = lv_thousands_separator
         WAERS = lv_waers
    IMPORTING
         BETRG = lv_betrg
    EXCEPTIONS
        CONVERT_ERROR = 1
. " FMCA_STRING_TO_AMOUNT_CONVERT




ABAP code using 7.40 inline data declarations to call FM FMCA_STRING_TO_AMOUNT_CONVERT

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_waers) = ' '.
 


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!