Understanding Initial Data Loading

After the completion of eSocial setup (which includes the activation of eSocial functionality, the activation, setup, and sequencing of initial events, the activation of participating companies, as well as legal code mappings), the next step is to load PeopleSoft’s initial data.

Initial data refers to foundational data that is stored in setup tables. It includes information about companies, establishments, job codes, shifts, taxable locations, service takers, employees and non-employees, all of which is vital in supporting various labor and payroll transactions.

The initial loading of events is launched through run control pages. These events must be submitted for all participating companies before the implementation of eSocial. Going forward, initial loading events need to be submitted, for example, when you activate a company (newly created or acquired), add new establishments to a new company, or when a company starts using a new setID for basic tables, which is defined on the SetID Group Page.

There are two initial load processes that need to be run, in this sequence:

  1. Load basic table data

  2. Load employee data

Initial Basic Table Data Loading

By default, the process includes the launching of these events:

  • S-1000 - Employer Data

  • S-1005 - Establishment and Building Site Table

  • S-1010 - Wage Types Table

  • S-1020 - Tax Location Table

Inactive initial events are not included in the eSocial Basic Tables Initial process.

Run this data loading process on the eSocial Basic Initial Page.

Initial Employee Data Loading

After the initial load process for basic table data is completed successfully, the next step is to send information about employees, which, based on the run control setup, can include active employees with temporary absence, employees who are fulfilling prior notice, as well as inactive employees who have recently been terminated but are expecting payments from the employer. Any individual who was hired on or after the company becomes active for eSocial reporting, as well as on or before the eSocial on PeopleSoft date specified for the company, his or her most current effective-dated employee data (in reference to the company’s eSocial on PeopleSoft date) will be reported to eSocial. Data for individuals who were hired after the eSocial on PeopleSoft date will be reported to eSocial using the S-2200 or S-2300 event.

Important:

As delivered, future rows for employees and non-employees are not considered during the initial employee data loading process. To support future rows, customers have to create their own triggers and launch them during S-2200 or S-2300 processing.

By default, the process includes the launching of these events:

  • S-2200 - Employees Initial Loading and Hiring

  • S-2300 - Workers who have no employment relationship – Begin

Data changes for employees with employment relationship after the initial data load will be reported to eSocial through S-2200 event rectifications, S-2205, or S-2206 events, depending on when the changes were made. For example, an employee (hire date: January 10th) was reported to eSocial through the S-2200 event. If a new effective-dated row is added today (May 1st) for this employee in the Job Data component, this contract data change will be reported to eSocial using the S-2206 event. If a new effective-dated row is also added today in the Personal Data component for the employee’s marital status change, this personal data change will be reported using the S-2205 event. However, if any of these changes is made in the row effective-dated January 10th, an S-2200 event (with the Rectification indicator turned on) will be created to report to eSocial that the hiring data has been modified.

Similarly, data changes for workers with no employment relationship will be reported through S-2300 event rectifications and the S-2306 event.

Important:

As delivered, existing rows with a future date are not considered during the initial employee data loading process. To support these rows, customers have to create their own triggers for S-2205, S-2206, or S-2306 to report the changes.

Run this data loading process on the eSocial Employee Initial Page.