SAP HRVE_GET_CURRENCY Function Module for









HRVE_GET_CURRENCY is a standard hrve get currency 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 hrve get currency FM, simply by entering the name HRVE_GET_CURRENCY into the relevant SAP transaction such as SE37 or SE38.

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



Function HRVE_GET_CURRENCY 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 'HRVE_GET_CURRENCY'"
EXPORTING
IV_CURRENCY_DETERMINATION_DATE = "

IMPORTING
EV_CURRENCY = "
EV_CURRENCY_RATE_DATE = "
EV_ERROR_TEXT = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for HRVE_GET_CURRENCY

IV_CURRENCY_DETERMINATION_DATE -

Data type: D
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for HRVE_GET_CURRENCY

EV_CURRENCY -

Data type: WAERS
Optional: No
Call by Reference: Yes

EV_CURRENCY_RATE_DATE -

Data type: D
Optional: No
Call by Reference: Yes

EV_ERROR_TEXT -

Data type: SY-MSGV1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRVE_GET_CURRENCY 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_error  TYPE STRING, "   
lv_ev_currency  TYPE WAERS, "   
lv_iv_currency_determination_date  TYPE D, "   
lv_ev_currency_rate_date  TYPE D, "   
lv_ev_error_text  TYPE SY-MSGV1. "   

  CALL FUNCTION 'HRVE_GET_CURRENCY'  "
    EXPORTING
         IV_CURRENCY_DETERMINATION_DATE = lv_iv_currency_determination_date
    IMPORTING
         EV_CURRENCY = lv_ev_currency
         EV_CURRENCY_RATE_DATE = lv_ev_currency_rate_date
         EV_ERROR_TEXT = lv_ev_error_text
    EXCEPTIONS
        ERROR = 1
. " HRVE_GET_CURRENCY




ABAP code using 7.40 inline data declarations to call FM HRVE_GET_CURRENCY

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 MSGV1 FROM SY INTO @DATA(ld_ev_error_text).
 


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!