SAP RH_PM_CONVERT_CURRENCY Function Module for

Search SAP Function Modules

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

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

Function RH_PM_CONVERT_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 'RH_PM_CONVERT_CURRENCY'"
  EXPORTING
   PLVAR =  "
   OTYPE =  "
   OBJID =  "
*  BEGDA = '19000101' "
*  ENDDA = '99991231' "
*  ISTAT = '1' "
   BETRG =  "
*  FREQU = ' ' "
   CURCY =  "

 IMPORTING
   R_TOTAL =  "
   R_CURCY =  "

EXCEPTIONS
   NO_ACTIVE_PLVAR = 1    NO_CONVERSION_FACTOR = 2    NO_CURRENCY = 3 

.

IMPORTING Parameters details for RH_PM_CONVERT_CURRENCY

PLVAR -

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

OTYPE -

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

OBJID -

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

BEGDA -

Data type: P1000-BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: P1000-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ISTAT -

Data type: P1000-ISTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

BETRG -

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

FREQU -

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

CURCY -

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

EXPORTING Parameters details for RH_PM_CONVERT_CURRENCY

R_TOTAL -

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

R_CURCY -

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

EXCEPTIONS details

NO_ACTIVE_PLVAR -

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

NO_CONVERSION_FACTOR -

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

NO_CURRENCY -

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

Copy and paste ABAP code example for RH_PM_CONVERT_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.

ABAP code using 7.40 inline data declarations to call FM RH_PM_CONVERT_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.

Search for further information about these or an SAP related objects