SAP HR_IN_PE_TRIGGER_WFLOW Function Module for FUNCTION MODULE FOR TRIGGERING WORKFLOW
HR_IN_PE_TRIGGER_WFLOW is a standard hr in pe trigger wflow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FUNCTION MODULE FOR TRIGGERING WORKFLOW 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 hr in pe trigger wflow FM, simply by entering the name HR_IN_PE_TRIGGER_WFLOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPADINPE2
Program Name: SAPLHRPADINPE2
Main Program: SAPLHRPADINPE2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_IN_PE_TRIGGER_WFLOW 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_IN_PE_TRIGGER_WFLOW'"FUNCTION MODULE FOR TRIGGERING WORKFLOW.
EXPORTING
IV_REQUEST_GUID = "P2E: Request GUID
IV_POLICY_GUID = "P2E: Policy GUID
IV_POLICY_VERSION = "Policy Guid
IV_STEP_ID = "P2E: Policy Step Id
IV_PERNR = "Personnel number
IV_SEQNM = "Sequence Number
IMPORTING
EV_WORKITEM_ID = "Work item ID
IMPORTING Parameters details for HR_IN_PE_TRIGGER_WFLOW
IV_REQUEST_GUID - P2E: Request GUID
Data type: PINPEW1-REGUIOptional: No
Call by Reference: Yes
IV_POLICY_GUID - P2E: Policy GUID
Data type: T7INPEW1-POGUIOptional: No
Call by Reference: Yes
IV_POLICY_VERSION - Policy Guid
Data type: T7INPEW1-VERSNOptional: No
Call by Reference: Yes
IV_STEP_ID - P2E: Policy Step Id
Data type: T7INPEW1-STPIDOptional: No
Call by Reference: Yes
IV_PERNR - Personnel number
Data type: PERSNOOptional: No
Call by Reference: Yes
IV_SEQNM - Sequence Number
Data type: T7INPEW1-APSEQOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_IN_PE_TRIGGER_WFLOW
EV_WORKITEM_ID - Work item ID
Data type: SWR_STRUCT-WORKITEMIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_IN_PE_TRIGGER_WFLOW 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_ev_workitem_id | TYPE SWR_STRUCT-WORKITEMID, " | |||
| lv_iv_request_guid | TYPE PINPEW1-REGUI, " | |||
| lv_iv_policy_guid | TYPE T7INPEW1-POGUI, " | |||
| lv_iv_policy_version | TYPE T7INPEW1-VERSN, " | |||
| lv_iv_step_id | TYPE T7INPEW1-STPID, " | |||
| lv_iv_pernr | TYPE PERSNO, " | |||
| lv_iv_seqnm | TYPE T7INPEW1-APSEQ. " |
|   CALL FUNCTION 'HR_IN_PE_TRIGGER_WFLOW' "FUNCTION MODULE FOR TRIGGERING WORKFLOW |
| EXPORTING | ||
| IV_REQUEST_GUID | = lv_iv_request_guid | |
| IV_POLICY_GUID | = lv_iv_policy_guid | |
| IV_POLICY_VERSION | = lv_iv_policy_version | |
| IV_STEP_ID | = lv_iv_step_id | |
| IV_PERNR | = lv_iv_pernr | |
| IV_SEQNM | = lv_iv_seqnm | |
| IMPORTING | ||
| EV_WORKITEM_ID | = lv_ev_workitem_id | |
| . " HR_IN_PE_TRIGGER_WFLOW | ||
ABAP code using 7.40 inline data declarations to call FM HR_IN_PE_TRIGGER_WFLOW
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 WORKITEMID FROM SWR_STRUCT INTO @DATA(ld_ev_workitem_id). | ||||
| "SELECT single REGUI FROM PINPEW1 INTO @DATA(ld_iv_request_guid). | ||||
| "SELECT single POGUI FROM T7INPEW1 INTO @DATA(ld_iv_policy_guid). | ||||
| "SELECT single VERSN FROM T7INPEW1 INTO @DATA(ld_iv_policy_version). | ||||
| "SELECT single STPID FROM T7INPEW1 INTO @DATA(ld_iv_step_id). | ||||
| "SELECT single APSEQ FROM T7INPEW1 INTO @DATA(ld_iv_seqnm). | ||||
Search for further information about these or an SAP related objects