SAP HRPY_PROCESS_FIRE_EVENT Function Module for Initiation of Event
HRPY_PROCESS_FIRE_EVENT is a standard hrpy process fire event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initiation of Event 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 hrpy process fire event FM, simply by entering the name HRPY_PROCESS_FIRE_EVENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRST1
Program Name: SAPLHRST1
Main Program: SAPLHRST1
Appliation area: P
Release date: 23-Jun-1999
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HRPY_PROCESS_FIRE_EVENT 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 'HRPY_PROCESS_FIRE_EVENT'"Initiation of Event.
EXPORTING
* IMP_PROCESSID = "No Longer Used!!
* IMP_STEPID = "No Longer Used!!
* IMP_RUNID = "No Longer Used!!
* IMP_PARAID = "No Longer Used!!
* IMP_PARCEL = "Set Identifier
* IMP_EVENT_NAME = 'JOB_ENDED' "
TABLES
* IMP_CONTAINER = "
IMPORTING Parameters details for HRPY_PROCESS_FIRE_EVENT
IMP_PROCESSID - No Longer Used!!
Data type: T52SP-PROCESSIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_STEPID - No Longer Used!!
Data type: T52SPS-STEPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_RUNID - No Longer Used!!
Data type: T52SPS-RUNIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_PARAID - No Longer Used!!
Data type: T52SPS-PARAIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_PARCEL - Set Identifier
Data type: PAY_PM_PARAIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IMP_EVENT_NAME -
Data type: SWETYPECOU-EVENTDefault: 'JOB_ENDED'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HRPY_PROCESS_FIRE_EVENT
IMP_CONTAINER -
Data type: SWCONTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRPY_PROCESS_FIRE_EVENT 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: | ||||
lt_imp_container | TYPE STANDARD TABLE OF SWCONT, " | |||
lv_imp_processid | TYPE T52SP-PROCESSID, " | |||
lv_imp_stepid | TYPE T52SPS-STEPID, " | |||
lv_imp_runid | TYPE T52SPS-RUNID, " | |||
lv_imp_paraid | TYPE T52SPS-PARAID, " | |||
lv_imp_parcel | TYPE PAY_PM_PARAID, " | |||
lv_imp_event_name | TYPE SWETYPECOU-EVENT. " 'JOB_ENDED' |
  CALL FUNCTION 'HRPY_PROCESS_FIRE_EVENT' "Initiation of Event |
EXPORTING | ||
IMP_PROCESSID | = lv_imp_processid | |
IMP_STEPID | = lv_imp_stepid | |
IMP_RUNID | = lv_imp_runid | |
IMP_PARAID | = lv_imp_paraid | |
IMP_PARCEL | = lv_imp_parcel | |
IMP_EVENT_NAME | = lv_imp_event_name | |
TABLES | ||
IMP_CONTAINER | = lt_imp_container | |
. " HRPY_PROCESS_FIRE_EVENT |
ABAP code using 7.40 inline data declarations to call FM HRPY_PROCESS_FIRE_EVENT
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 PROCESSID FROM T52SP INTO @DATA(ld_imp_processid). | ||||
"SELECT single STEPID FROM T52SPS INTO @DATA(ld_imp_stepid). | ||||
"SELECT single RUNID FROM T52SPS INTO @DATA(ld_imp_runid). | ||||
"SELECT single PARAID FROM T52SPS INTO @DATA(ld_imp_paraid). | ||||
"SELECT single EVENT FROM SWETYPECOU INTO @DATA(ld_imp_event_name). | ||||
DATA(ld_imp_event_name) | = 'JOB_ENDED'. | |||
Search for further information about these or an SAP related objects