SAP HR_EVENT_CHECK Function Module for

Search SAP Function Modules

HR_EVENT_CHECK is a standard hr event check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr event check FM, simply by entering the name HR_EVENT_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function HR_EVENT_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 'HR_EVENT_CHECK'"
  EXPORTING
*  SW_REFRESH = 'X' "Refresh internal tables
*  SW_CHECK_BY_PROCESS = ' ' "Pair formation and time ticket generation check

TABLES
   PDC =  "Transferred time events
   PDCERR =  "Numbers of rejected time events
   PDC_ADD =  "

EXCEPTIONS
   NO_AUTH = 1    LOCK_FAILURE = 2    WRONG_VERSION = 3    PDSNR_MISSING = 4    WRONG_DATA = 5    CLUSTER_ARCHIVED = 6    TECHNICAL_ERROR = 7 

.

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_SAPLRPPD_001 User exit for processing statuses from time events and pair formation

IMPORTING Parameters details for HR_EVENT_CHECK

SW_REFRESH - Refresh internal tables

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SW_CHECK_BY_PROCESS - Pair formation and time ticket generation check

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

TABLES Parameters details for HR_EVENT_CHECK

PDC - Transferred time events

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

PDCERR - Numbers of rejected time events

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

PDC_ADD -

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

EXCEPTIONS details

NO_AUTH - No cluster authorization

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

LOCK_FAILURE - Internal error when locking

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

WRONG_VERSION - Incorrect version of cluster

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

PDSNR_MISSING - No sequential number for PDC messages

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

WRONG_DATA - Missing table entry etc.

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

CLUSTER_ARCHIVED -

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

TECHNICAL_ERROR -

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

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

ABAP code using 7.40 inline data declarations to call FM HR_EVENT_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.

Search for further information about these or an SAP related objects