Modifying the Employee Selection Process
This topic discusses how employees are selected during EDI processing of outgoing transactions and how you could modify this selection for your organization.
Note: Modifying the selection process involves changes to PeopleTools Application Engine programs. Such changes must be made by technical users with a good understanding of PeopleTools and PeopleCode.
The EDI outgoing transactions (P45, P46, P14, P35, and WNU) are application engine programs. These programs call other application engine programs that determine the employees selected for processing. By modifying these application engine programs you can change the employee population that is selected during EDI processing.
See the product documentation for PeopleTools: Application Engine and PeopleTools: PeopleCode Developer's Guide
To illustrate how employee selection works, consider the Works Number Update (WNU) transaction. When you run the WNU process, the GPGB_EDI application engine program, which is the controlling program, calls the GPGB_EDIWNU application engine program. The GPGB_EDIWNU program:
Runs the GPGB_EDIWNU.WNU.EEs step that uses SQL to select the list of employees who match the run control parameters.
For each employee identified in the list, a call is made to GPGB_EDIWNU.WNUConf. This program:
Calls GPGB_EDI_EXT.Confirm PeopleCode.
The PeopleCode returns a value of Y or N to indicate whether the employee should be processed. This is the PeopleCode that you need to modify if you want to override the employee selection process.
If GPGB_EDI_EXT.Confirm returns a value of Y, GPGB_EDIWNU.WNUConf calls GPGB_EDIWNU.WNUEEs to write the employee information to the flat file.
Note: The GPGB_EDI_EXT.Confirm.Status PeopleCode includes comments that provide more information about the changes required.