MY_VALUATION_LEVEL_GET SAP Function module

MY_VALUATION_LEVEL_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MY_VALUATION_LEVEL_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LIFO
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM MY_VALUATION_LEVEL_GET - MY VALUATION LEVEL GET

CALL FUNCTION 'MY_VALUATION_LEVEL_GET' "
  EXPORTING
    i_myxxfo =                  " tmy01-myxxfo
*   i_tabid =                   " my_tabid      Indicates database tables for LIFO/FIFO valuation
  IMPORTING
    e_val_level =               " tcurm-mykey_cus
    e_mymp_level =              " tcurm-mymp_cus
    e_tcurm =                   " tcurm
    e_up_level =                " xfeld         Checkbox
  EXCEPTIONS
    NO_LIFO = 1                 "
    NO_FIFO = 2                 "
    .  "  MY_VALUATION_LEVEL_GET

ABAP code example for Function Module MY_VALUATION_LEVEL_GET

The ABAP code below is a full code listing to execute function module MY_VALUATION_LEVEL_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_val_level  
 
 TYPE TCURM-MYKEY_CUS
,
ld_e_mymp_level  
 
 TYPE TCURM-MYMP_CUS
,
ld_e_tcurm  
 
 TYPE TCURM
,
ld_e_up_level  
 
 TYPE XFELD
.

 

SELECT single MYXXFO 
  FROM TMY01 
  INTO @DATA(ld_i_myxxfo).


DATA(ld_i_tabid) = 'Check type of data required'.
.

CALL FUNCTION 'MY_VALUATION_LEVEL_GET'
  EXPORTING
    i_myxxfo =                   ld_i_myxxfo
*   i_tabid =                    ld_i_tabid
  IMPORTING
    e_val_level =                ld_e_val_level
    e_mymp_level =               ld_e_mymp_level
    e_tcurm =                    ld_e_tcurm
    e_up_level =                 ld_e_up_level
  EXCEPTIONS
    NO_LIFO =                    1
    NO_FIFO =                    2
    .  "  MY_VALUATION_LEVEL_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_val_level
 
 TYPE TCURM-MYKEY_CUS ,
ld_i_myxxfo
 
 TYPE TMY01-MYXXFO ,
ld_e_mymp_level
 
 TYPE TCURM-MYMP_CUS ,
ld_i_tabid
 
 TYPE MY_TABID ,
ld_e_tcurm
 
 TYPE TCURM ,
ld_e_up_level
 
 TYPE XFELD .



SELECT single MYXXFO 
  FROM TMY01 
  INTO ld_i_myxxfo.

ld_i_tabid = 'Check type of data required'.