SAP AIPR_BP_CURR_CONVERSION_SINGLE Function Module for









AIPR_BP_CURR_CONVERSION_SINGLE is a standard aipr bp curr conversion single 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 aipr bp curr conversion single FM, simply by entering the name AIPR_BP_CURR_CONVERSION_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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



Function AIPR_BP_CURR_CONVERSION_SINGLE 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 'AIPR_BP_CURR_CONVERSION_SINGLE'"
EXPORTING
ID_KOKRS = "
ID_WL_FROM = "
* ID_PROFIL = "
* ID_APPLIK = "
* ID_WRTTP = "
* ID_GNJHR = "
* ID_GJAHR = '0000' "
* ID_VERSN = '000' "
ID_WAERS_FROM = "
ID_WAERS_TO = "

IMPORTING
ED_WL_TO = "
ED_LEDNR_TO = "

EXCEPTIONS
ERROR_OCCURED = 1 ABEND_OCCURED = 2
.



IMPORTING Parameters details for AIPR_BP_CURR_CONVERSION_SINGLE

ID_KOKRS -

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

ID_WL_FROM -

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

ID_PROFIL -

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

ID_APPLIK -

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

ID_WRTTP -

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

ID_GNJHR -

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

ID_GJAHR -

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

ID_VERSN -

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

ID_WAERS_FROM -

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

ID_WAERS_TO -

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

EXPORTING Parameters details for AIPR_BP_CURR_CONVERSION_SINGLE

ED_WL_TO -

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

ED_LEDNR_TO -

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

EXCEPTIONS details

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

ABEND_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AIPR_BP_CURR_CONVERSION_SINGLE 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_ed_wl_to  TYPE BP_WGL, "   
lv_id_kokrs  TYPE KOKRS, "   
lv_error_occured  TYPE KOKRS, "   
lv_id_wl_from  TYPE BP_WGL, "   
lv_id_profil  TYPE BP_PROFIL, "   
lv_ed_lednr_to  TYPE BP_LEDNR, "   
lv_abend_occured  TYPE BP_LEDNR, "   
lv_id_applik  TYPE BP_APPLIK, "   
lv_id_wrttp  TYPE CO_WRTTP, "   
lv_id_gnjhr  TYPE IM_GNJHR, "   
lv_id_gjahr  TYPE GJAHR, "   '0000'
lv_id_versn  TYPE VERSN, "   '000'
lv_id_waers_from  TYPE WAERS, "   
lv_id_waers_to  TYPE WAERS. "   

  CALL FUNCTION 'AIPR_BP_CURR_CONVERSION_SINGLE'  "
    EXPORTING
         ID_KOKRS = lv_id_kokrs
         ID_WL_FROM = lv_id_wl_from
         ID_PROFIL = lv_id_profil
         ID_APPLIK = lv_id_applik
         ID_WRTTP = lv_id_wrttp
         ID_GNJHR = lv_id_gnjhr
         ID_GJAHR = lv_id_gjahr
         ID_VERSN = lv_id_versn
         ID_WAERS_FROM = lv_id_waers_from
         ID_WAERS_TO = lv_id_waers_to
    IMPORTING
         ED_WL_TO = lv_ed_wl_to
         ED_LEDNR_TO = lv_ed_lednr_to
    EXCEPTIONS
        ERROR_OCCURED = 1
        ABEND_OCCURED = 2
. " AIPR_BP_CURR_CONVERSION_SINGLE




ABAP code using 7.40 inline data declarations to call FM AIPR_BP_CURR_CONVERSION_SINGLE

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_id_gjahr) = '0000'.
 
DATA(ld_id_versn) = '000'.
 
 
 


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!