SAP UNIT_CORRESPONDENCE_CHECK Function Module for Check whether two units have the same dimension









UNIT_CORRESPONDENCE_CHECK is a standard unit correspondence check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check whether two units have the same dimension processing and below is the pattern details for this FM, 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 unit correspondence check FM, simply by entering the name UNIT_CORRESPONDENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCV0
Program Name: SAPLSCV0
Main Program: SAPLSCV0
Appliation area: *
Release date: 14-Mar-2000
Mode(Normal, Remote etc): Normal Function Module
Update:



Function UNIT_CORRESPONDENCE_CHECK 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 'UNIT_CORRESPONDENCE_CHECK'"Check whether two units have the same dimension
EXPORTING
UNIT_IN = "Unit of measurement
UNIT_OUT = "Unit of measurement

EXCEPTIONS
DIMENSIONS_ARE_DIFFERENT = 1 UNIT_IN_NOT_FOUND = 2 UNIT_OUT_NOT_FOUND = 3
.



IMPORTING Parameters details for UNIT_CORRESPONDENCE_CHECK

UNIT_IN - Unit of measurement

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

UNIT_OUT - Unit of measurement

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

EXCEPTIONS details

DIMENSIONS_ARE_DIFFERENT - Dimensions are different

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

UNIT_IN_NOT_FOUND - UNIT_IN is not maintained

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

UNIT_OUT_NOT_FOUND - UNIT_OUT is not maintained

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

Copy and paste ABAP code example for UNIT_CORRESPONDENCE_CHECK 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_unit_in  TYPE T006-MSEHI, "   
lv_dimensions_are_different  TYPE T006, "   
lv_unit_out  TYPE T006-MSEHI, "   
lv_unit_in_not_found  TYPE T006, "   
lv_unit_out_not_found  TYPE T006. "   

  CALL FUNCTION 'UNIT_CORRESPONDENCE_CHECK'  "Check whether two units have the same dimension
    EXPORTING
         UNIT_IN = lv_unit_in
         UNIT_OUT = lv_unit_out
    EXCEPTIONS
        DIMENSIONS_ARE_DIFFERENT = 1
        UNIT_IN_NOT_FOUND = 2
        UNIT_OUT_NOT_FOUND = 3
. " UNIT_CORRESPONDENCE_CHECK




ABAP code using 7.40 inline data declarations to call FM UNIT_CORRESPONDENCE_CHECK

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 MSEHI FROM T006 INTO @DATA(ld_unit_in).
 
 
"SELECT single MSEHI FROM T006 INTO @DATA(ld_unit_out).
 
 
 


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!