SAP ASSET_VALUATION_DATE_GET_30 Function Module for









ASSET_VALUATION_DATE_GET_30 is a standard asset valuation date get 30 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 asset valuation date get 30 FM, simply by entering the name ASSET_VALUATION_DATE_GET_30 into the relevant SAP transaction such as SE37 or SE38.

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



Function ASSET_VALUATION_DATE_GET_30 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 'ASSET_VALUATION_DATE_GET_30'"
EXPORTING
* I_VORGN = ' ' "
* I_BWASL = ' ' "
* I_AWTYP = ' ' "
I_BUDAT = "
I_ANTS = "
* I_BLDAT = '99999999' "
* I_BUDAT_WE = '99999999' "
* I_BZDAT_RE = '99999999' "

CHANGING
C_BZDAT = "

EXCEPTIONS
GSVOR_NOT_ASCERTAINABLE = 1 MISSING_DATE = 2 MISSING_TRANSACTION_TYPE = 3 INVALID_GSVOR = 4 INVALID_TRANSACTION_TYPE = 5 DIFFERENT_FISCAL_YEARS = 6
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLAMAV_001 Determination of Value Date According to User-Defined Rules

IMPORTING Parameters details for ASSET_VALUATION_DATE_GET_30

I_VORGN -

Data type: ANBZ-VORGN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BWASL -

Data type: TABW-BWASL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_AWTYP -

Data type: ANBZ-AWTYP
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUDAT -

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

I_ANTS -

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

I_BLDAT -

Data type: ANBZ-BLDAT
Default: '99999999'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUDAT_WE -

Data type: ANBZ-BUDAT
Default: '99999999'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BZDAT_RE -

Data type: ANBZ-BUDAT
Default: '99999999'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for ASSET_VALUATION_DATE_GET_30

C_BZDAT -

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

EXCEPTIONS details

GSVOR_NOT_ASCERTAINABLE -

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

MISSING_DATE -

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

MISSING_TRANSACTION_TYPE -

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

INVALID_GSVOR -

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

INVALID_TRANSACTION_TYPE -

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

DIFFERENT_FISCAL_YEARS -

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

Copy and paste ABAP code example for ASSET_VALUATION_DATE_GET_30 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_c_bzdat  TYPE ANBZ-BZDAT, "   
lv_i_vorgn  TYPE ANBZ-VORGN, "   ' '
lv_gsvor_not_ascertainable  TYPE ANBZ, "   
lv_i_bwasl  TYPE TABW-BWASL, "   ' '
lv_missing_date  TYPE TABW, "   
lv_i_awtyp  TYPE ANBZ-AWTYP, "   ' '
lv_missing_transaction_type  TYPE ANBZ, "   
lv_i_budat  TYPE ANBZ-BUDAT, "   
lv_invalid_gsvor  TYPE ANBZ, "   
lv_i_ants  TYPE ANTS, "   
lv_invalid_transaction_type  TYPE ANTS, "   
lv_i_bldat  TYPE ANBZ-BLDAT, "   '99999999'
lv_different_fiscal_years  TYPE ANBZ, "   
lv_i_budat_we  TYPE ANBZ-BUDAT, "   '99999999'
lv_i_bzdat_re  TYPE ANBZ-BUDAT. "   '99999999'

  CALL FUNCTION 'ASSET_VALUATION_DATE_GET_30'  "
    EXPORTING
         I_VORGN = lv_i_vorgn
         I_BWASL = lv_i_bwasl
         I_AWTYP = lv_i_awtyp
         I_BUDAT = lv_i_budat
         I_ANTS = lv_i_ants
         I_BLDAT = lv_i_bldat
         I_BUDAT_WE = lv_i_budat_we
         I_BZDAT_RE = lv_i_bzdat_re
    CHANGING
         C_BZDAT = lv_c_bzdat
    EXCEPTIONS
        GSVOR_NOT_ASCERTAINABLE = 1
        MISSING_DATE = 2
        MISSING_TRANSACTION_TYPE = 3
        INVALID_GSVOR = 4
        INVALID_TRANSACTION_TYPE = 5
        DIFFERENT_FISCAL_YEARS = 6
. " ASSET_VALUATION_DATE_GET_30




ABAP code using 7.40 inline data declarations to call FM ASSET_VALUATION_DATE_GET_30

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 BZDAT FROM ANBZ INTO @DATA(ld_c_bzdat).
 
"SELECT single VORGN FROM ANBZ INTO @DATA(ld_i_vorgn).
DATA(ld_i_vorgn) = ' '.
 
 
"SELECT single BWASL FROM TABW INTO @DATA(ld_i_bwasl).
DATA(ld_i_bwasl) = ' '.
 
 
"SELECT single AWTYP FROM ANBZ INTO @DATA(ld_i_awtyp).
DATA(ld_i_awtyp) = ' '.
 
 
"SELECT single BUDAT FROM ANBZ INTO @DATA(ld_i_budat).
 
 
 
 
"SELECT single BLDAT FROM ANBZ INTO @DATA(ld_i_bldat).
DATA(ld_i_bldat) = '99999999'.
 
 
"SELECT single BUDAT FROM ANBZ INTO @DATA(ld_i_budat_we).
DATA(ld_i_budat_we) = '99999999'.
 
"SELECT single BUDAT FROM ANBZ INTO @DATA(ld_i_bzdat_re).
DATA(ld_i_bzdat_re) = '99999999'.
 


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!