SAP RM_CHECK_RPOINT_CHANGES Function Module for NOTRANSL: Verprobung: Wurden Zählpunkte verändert?

Search SAP Function Modules

RM_CHECK_RPOINT_CHANGES is a standard rm check rpoint changes 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: Verprobung: Wurden Zählpunkte verändert? 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 rm check rpoint changes FM, simply by entering the name RM_CHECK_RPOINT_CHANGES into the relevant SAP transaction such as SE37 or SE38.

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

Function RM_CHECK_RPOINT_CHANGES 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 'RM_CHECK_RPOINT_CHANGES'"NOTRANSL: Verprobung: Wurden Zählpunkte verändert?
  EXPORTING
   IF_APLAL =  "Group Counter
   IF_PLNNR =  "Key for Task List Group
   IF_PLNTY =  "
   IF_DATE =  "Date and Time, Current (Application Server) Date
   IF_PKOSA =  "Cost Collector for Production Process PROCNR
   IF_VERID =  "Production Version
   IF_WERKS =  "Plant
   IF_MATNR =  "Material Number
   IF_CHECK_OPEN_LOG =  "

EXCEPTIONS
   FIND_ROUTING_ERROR = 1    FIND_REPPOINT_STRUC_ERROR = 2    RPOINT_STRUCTURE_CHANGED = 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_SAPLBARM_001 Customer Exit: RM_BACKFLUSH_CHECK
EXIT_SAPLBARM_002 Customer Exit: RM_BACKFLUSH_GO
EXIT_SAPLBARM_003 Customer Exit: RM_CANCEL_BACKFLUSH_CHECK
EXIT_SAPLBARM_004 Customer Exit: RM_CANCEL_BACKFLUSH_GO

IMPORTING Parameters details for RM_CHECK_RPOINT_CHANGES

IF_APLAL - Group Counter

Data type: PLNAL
Optional: No
Call by Reference: Yes

IF_PLNNR - Key for Task List Group

Data type: PLNNR
Optional: No
Call by Reference: Yes

IF_PLNTY -

Data type: PLNTY
Optional: No
Call by Reference: Yes

IF_DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

IF_PKOSA - Cost Collector for Production Process PROCNR

Data type: PKOSA_D
Optional: No
Call by Reference: Yes

IF_VERID - Production Version

Data type: VERID
Optional: No
Call by Reference: Yes

IF_WERKS - Plant

Data type: WERKS_D
Optional: No
Call by Reference: Yes

IF_MATNR - Material Number

Data type: SA_MATNR
Optional: No
Call by Reference: Yes

IF_CHECK_OPEN_LOG -

Data type: C
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FIND_ROUTING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

FIND_REPPOINT_STRUC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

RPOINT_STRUCTURE_CHANGED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RM_CHECK_RPOINT_CHANGES 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.

ABAP code using 7.40 inline data declarations to call FM RM_CHECK_RPOINT_CHANGES

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.

Search for further information about these or an SAP related objects