J_1BNFE_GET_CONVERSION_UOM SAP Function module - Get Conversion for Unit of Measurement

J_1BNFE_GET_CONVERSION_UOM 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 J_1BNFE_GET_CONVERSION_UOM into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM J_1BNFE_GET_CONVERSION_UOM - J 1BNFE GET CONVERSION UOM

CALL FUNCTION 'J_1BNFE_GET_CONVERSION_UOM' "Get Conversion for Unit of Measurement
  EXPORTING
    iv_ordered_uom =            " bstme         Purchase Order Unit of Measure
*   iv_matnr =                  " matnr         Material Number
*   iv_lifnr =                  " lifnr         Account Number of Vendor or Creditor
  IMPORTING
    ev_umren =                  " ekpo-umren    Denominator for Conversion of Order Unit to Base Unit
    ev_umrez =                  " ekpo-umrez    Numerator for Conversion of Order Unit to Base Unit
* CHANGING
*   cv_lmein =                  " ekpo-lmein    Base Unit of Measure
  EXCEPTIONS
    CONVERSION_NOT_FOUND = 1    "               no conversion found
    .  "  J_1BNFE_GET_CONVERSION_UOM

ABAP code example for Function Module J_1BNFE_GET_CONVERSION_UOM

The ABAP code below is a full code listing to execute function module J_1BNFE_GET_CONVERSION_UOM 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_ev_umren  
 
 TYPE EKPO-UMREN
,
ld_ev_umrez  
 
 TYPE EKPO-UMREZ
.

 

SELECT single LMEIN 
  FROM EKPO 
  INTO @DATA(ld_cv_lmein).


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

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

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

CALL FUNCTION 'J_1BNFE_GET_CONVERSION_UOM'
  EXPORTING
    iv_ordered_uom =             ld_iv_ordered_uom
*   iv_matnr =                   ld_iv_matnr
*   iv_lifnr =                   ld_iv_lifnr
  IMPORTING
    ev_umren =                   ld_ev_umren
    ev_umrez =                   ld_ev_umrez
* CHANGING
*   cv_lmein =                   ld_cv_lmein
  EXCEPTIONS
    CONVERSION_NOT_FOUND =       1
    .  "  J_1BNFE_GET_CONVERSION_UOM

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_cv_lmein
 
 TYPE EKPO-LMEIN ,
ld_ev_umren
 
 TYPE EKPO-UMREN ,
ld_iv_ordered_uom
 
 TYPE BSTME ,
ld_ev_umrez
 
 TYPE EKPO-UMREZ ,
ld_iv_matnr
 
 TYPE MATNR ,
ld_iv_lifnr
 
 TYPE LIFNR .



SELECT single LMEIN 
  FROM EKPO 
  INTO ld_cv_lmein.

ld_iv_ordered_uom = 'Check type of data required'.
ld_iv_matnr = 'Check type of data required'.
ld_iv_lifnr = 'Check type of data required'.