SAP VALUATION_GET_OLD_VALUE Function Module for
VALUATION_GET_OLD_VALUE is a standard valuation get old value 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 valuation get old value FM, simply by entering the name VALUATION_GET_OLD_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: F107
Program Name: SAPLF107
Main Program: SAPLF107
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VALUATION_GET_OLD_VALUE 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 'VALUATION_GET_OLD_VALUE'".
EXPORTING
I_BWBER = "Valuation Area
I_BUZEI = "
* I_REM = "
I_UMBWM = "Valuation Method
I_CURTP = "Currency Type
* I_KUNNR = "Customer Number
* X_CURR = "
* X_CURR_VALUE = "
I_BELNR = "
I_BUKRS = "
I_GJAHR = "
IMPORTING
OLD_DIFFERENCE = "
EXCEPTIONS
NOTHING_FOUND = 1
IMPORTING Parameters details for VALUATION_GET_OLD_VALUE
I_BWBER - Valuation Area
Data type: BSBM-BWBEROptional: No
Call by Reference: No ( called with pass by value option)
I_BUZEI -
Data type: BSID-BUZEIOptional: No
Call by Reference: No ( called with pass by value option)
I_REM -
Data type: COptional: Yes
Call by Reference: Yes
I_UMBWM - Valuation Method
Data type: F107V-UMBWMOptional: No
Call by Reference: No ( called with pass by value option)
I_CURTP - Currency Type
Data type: F107V-CURTPOptional: No
Call by Reference: No ( called with pass by value option)
I_KUNNR - Customer Number
Data type: BSID-KUNNROptional: Yes
Call by Reference: No ( called with pass by value option)
X_CURR -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
X_CURR_VALUE -
Data type: BSBW-BWSHBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BELNR -
Data type: BSID-BELNROptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: BSID-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_GJAHR -
Data type: BSID-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VALUATION_GET_OLD_VALUE
OLD_DIFFERENCE -
Data type: BSBW-BWSHBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOTHING_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VALUATION_GET_OLD_VALUE 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_i_bwber | TYPE BSBM-BWBER, " | |||
| lv_nothing_found | TYPE BSBM, " | |||
| lv_old_difference | TYPE BSBW-BWSHB, " | |||
| lv_i_buzei | TYPE BSID-BUZEI, " | |||
| lv_i_rem | TYPE C, " | |||
| lv_i_umbwm | TYPE F107V-UMBWM, " | |||
| lv_i_curtp | TYPE F107V-CURTP, " | |||
| lv_i_kunnr | TYPE BSID-KUNNR, " | |||
| lv_x_curr | TYPE C, " | |||
| lv_x_curr_value | TYPE BSBW-BWSHB, " | |||
| lv_i_belnr | TYPE BSID-BELNR, " | |||
| lv_i_bukrs | TYPE BSID-BUKRS, " | |||
| lv_i_gjahr | TYPE BSID-GJAHR. " |
|   CALL FUNCTION 'VALUATION_GET_OLD_VALUE' " |
| EXPORTING | ||
| I_BWBER | = lv_i_bwber | |
| I_BUZEI | = lv_i_buzei | |
| I_REM | = lv_i_rem | |
| I_UMBWM | = lv_i_umbwm | |
| I_CURTP | = lv_i_curtp | |
| I_KUNNR | = lv_i_kunnr | |
| X_CURR | = lv_x_curr | |
| X_CURR_VALUE | = lv_x_curr_value | |
| I_BELNR | = lv_i_belnr | |
| I_BUKRS | = lv_i_bukrs | |
| I_GJAHR | = lv_i_gjahr | |
| IMPORTING | ||
| OLD_DIFFERENCE | = lv_old_difference | |
| EXCEPTIONS | ||
| NOTHING_FOUND = 1 | ||
| . " VALUATION_GET_OLD_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM VALUATION_GET_OLD_VALUE
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 BWBER FROM BSBM INTO @DATA(ld_i_bwber). | ||||
| "SELECT single BWSHB FROM BSBW INTO @DATA(ld_old_difference). | ||||
| "SELECT single BUZEI FROM BSID INTO @DATA(ld_i_buzei). | ||||
| "SELECT single UMBWM FROM F107V INTO @DATA(ld_i_umbwm). | ||||
| "SELECT single CURTP FROM F107V INTO @DATA(ld_i_curtp). | ||||
| "SELECT single KUNNR FROM BSID INTO @DATA(ld_i_kunnr). | ||||
| "SELECT single BWSHB FROM BSBW INTO @DATA(ld_x_curr_value). | ||||
| "SELECT single BELNR FROM BSID INTO @DATA(ld_i_belnr). | ||||
| "SELECT single BUKRS FROM BSID INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single GJAHR FROM BSID INTO @DATA(ld_i_gjahr). | ||||
Search for further information about these or an SAP related objects