SAP ME_CHECK_POINTS Function Module for NOTRANSL: Prüfen, ob eine Einheit als Punkteeinheit zulässig ist
ME_CHECK_POINTS is a standard me check points SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfen, ob eine Einheit als Punkteeinheit zulässig ist 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 me check points FM, simply by entering the name ME_CHECK_POINTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEKO
Program Name: SAPLMEKO
Main Program: SAPLMEKO
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_CHECK_POINTS 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 'ME_CHECK_POINTS'"NOTRANSL: Prüfen, ob eine Einheit als Punkteeinheit zulässig ist.
EXPORTING
I_UNIT = "Purchase Order Unit of Measure
EXCEPTIONS
DIMENSION_NOT_MAINTAINED = 1 DIMENSION_CHECK_FAILED = 2 UNIT_NOT_VALID = 3
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_SAPLMEKO_001 Extend Communication Structure KOMK for Pricing
EXIT_SAPLMEKO_002 Extend Communication Structure KOMP for Pricing
IMPORTING Parameters details for ME_CHECK_POINTS
I_UNIT - Purchase Order Unit of Measure
Data type: EINA-MEINSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DIMENSION_NOT_MAINTAINED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DIMENSION_CHECK_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNIT_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_CHECK_POINTS 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_unit | TYPE EINA-MEINS, " | |||
| lv_dimension_not_maintained | TYPE EINA, " | |||
| lv_dimension_check_failed | TYPE EINA, " | |||
| lv_unit_not_valid | TYPE EINA. " |
|   CALL FUNCTION 'ME_CHECK_POINTS' "NOTRANSL: Prüfen, ob eine Einheit als Punkteeinheit zulässig ist |
| EXPORTING | ||
| I_UNIT | = lv_i_unit | |
| EXCEPTIONS | ||
| DIMENSION_NOT_MAINTAINED = 1 | ||
| DIMENSION_CHECK_FAILED = 2 | ||
| UNIT_NOT_VALID = 3 | ||
| . " ME_CHECK_POINTS | ||
ABAP code using 7.40 inline data declarations to call FM ME_CHECK_POINTS
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 MEINS FROM EINA INTO @DATA(ld_i_unit). | ||||
Search for further information about these or an SAP related objects