Splitting of Events for Multiple Impacted Companies

In PeopleSoft HCM, certain data is organized in ways that are different from how the eSocial environment collects information, which is by company. Subsequently, when an update of such data occurs and it triggers an insertion of a row in the driver and cross-reference tables, the system needs to do the same for all companies that use the updated information. The splitting of the row (creating new ones) ensures that the correct number of entries are loaded to staging tables, which are later used to generate XML files for all impacted companies.

The splitting of events applies to these types of data:

• Information that is keyed by setID, such as basic table data.

  See the Understanding SetID and Company Mapping topic for more information.

• Employee data that is keyed by employee ID.

  An example of it is employee’s personal data. An employee may have jobs with different companies and while job data is keyed by employee record number (which corresponds to a company), personal data isn’t. When the employee updates his or her personal information, the updated information needs to be sent to all companies where he or she has a contract.

• Payroll elements, which can be used by multiple companies.

Note:

Splitting of events is handled as part of the initial data loading and online transaction processes.