S-2240 - Environmental Working Conditions

Non periodic event. This event layout records information about the working environments and conditions of workers. It captures workers’ workplace locations, the types of activities they perform that are considered unhealthy and dangerous, the risks and hazards that they are exposed to at work, as well as the usage of protection equipment and its effectiveness in keeping workers safe. The information collected in this event is also used for special retirement financing.

General Rules

Here are several general rules that apply to the Environmental Working Conditions event:

  • For S-2240 events to be generated and submitted properly for companies:

  • The S-2200 and S-2300 events must be processed and submitted to the Government already.

  • An Environmental Working Conditions event is triggered whenever a working environment, activity, or condition of a worker is reported in the Worker’s Conditions BRA component, the effective date entered is equal to or greater than the Health/Safety Go Live date (for example, January 1, 2019), and that the worker belongs to an employee classification that is specified on the Labor Regime page.

    Note:

    For initial loading, the process takes the working conditions record of each eligible worker with an effective date that is either the same as the go-live date, or is the most current as of the go-live date, and generates S-2240 events.

Initial Loading

The S-2240 event is a non periodic event that is also included in the initial load process for employee data (GPBR_ES_ILE). When the initial load process runs for the S-2240 event and a company, the system generates an S-2240 event for the worker’s conditions record of each eligible worker that is associated with that company. If a worker has multiple worker’s conditions records, the process takes the one with the same effective date as the company’s Health/Safety Go Live date if available, or the one with the most current (maximum) effective date as of the go-live date, to be used for initial loading.

Note:

The initial load process does not generate events for future-dated worker’s conditions. If a worker’s conditions record has a future-dated row at the time of initial load, the system creates a driver record for it, which will then be handled by the non periodic process (GPBR_ES_MNP) later.

After the initial loading of worker’s conditions is completed, the eSocial system reports any new, deleted, or changes to worker’s conditions to the Government using the S-2240 event.

Online Transactions After Initial Loading

Here are several examples that describe the behaviors of the S-2240 event when worker’s conditions are created, updated, or deleted from the PeopleSoft system after initial loading process is completed:

  • When a worker is hired, rehired, transferred to a company, or has a different worker condition (for example, a new workplace, a new work activity, a new work hazard, a new protection equipment and so on), Oracle recommends that you add a worker’s conditions record (or an effective-dated row) to the PeopleSoft Human Resources Monitor Health and Safety: Worker Conditions Page to capture the information for the worker as soon as possible. When that happens, the system creates an S-2240 event using information from both the worker’s conditions record, and the worker’s current job data row. For instance, you add a worker’s condition record for a worker who just got hired. When the system creates an S-2240 event, it uses data from the worker’s condition record and the hire job data row, which is current as of the effective date of the worker’s condition record.

  • When a worker’s conditions record is added for an employee who works at a service taker location, the system generates an S-2240 event for it using information from the worker’s conditions record, current job data, and current payee parameters (where the employee is associated with one or more service takers). The system generates a mapping error and cannot create an S-2240 event if:

    • The employee does not associate with a service taker on the Payee Parameters Page.

    • The employee is associated with a service taker on the Payee Parameters BRA page, but there is no Service Taker Establishment workplace code specified on the Worker Conditions page for the employee.

    • The employee is associated with a service taker on the Payee Parameters BRA page, and a Service Taker Establishment workplace code is specified on the Worker Conditions page for the employee, but the service taker is not listed on the PeopleSoft Human Resources Monitor Health and Safety: Workplace Table BRA Page.

  • When a worker’s conditions record is added with an retroactive effective date (for example, August 1, 2019 and the current effective date is September 1, 2019) for a row that is added on the Payee Parameters page for the same retroactive effective date, the system generates an S-2240 event using information from this worker’s conditions record, and the worker’s job data row and payee parameters row (for example, service taker) that are current as of the retroactive effective date.

  • If, after initial loading, a worker’s conditions record is added, and:

    • The record has a retroactive effective date (for example, June 1, 2019) that is earlier than the effective date of the record used in initial loading (for example, June 20, 2019) and the go-live date, no event will be created.

    • The record has a retroactive effective date (for example, June 30, 2019) that is later than the effective date of the record used in initial loading (for example, June 20, 2019) but earlier than the go-live date, the system rectifies the S-2240 event for the initial loading with information from the worker’s conditions record that has the retroactive date.

  • If a worker’s conditions record is added after the worker is terminated (the record’s effective date is greater than the worker’s termination date), no event will be generated.

  • Suppose that a worker’s conditions record is created after a worker is transferred to a different establishment of the company and an S-2240 event is submitted to the Government to report the change.

    • If updates are made to the worker’s conditions record (the one added for the transfer, with an effective date of August 1, 2019 for example), the system rectifies the S-2240 event for the modified worker’s conditions record with the updated data, and the information from the worker’s current job data row as of the August 1, 2019 effective date.

    • If updates are made to the worker’s conditions record (the one before the transfer, with an effective date of January 1, 2019 for example), the system rectifies the S-2240 event for the modified worker’s conditions record with the updated data, and the information from the worker’s current job data row as of the January 1, 2019 effective date.

  • A worker can have more than one employment within a company or in different companies. When the first job data row (employee record = 0) and a worker’s conditions record are added for the worker, the system creates an S-2240 event with information from this worker’s conditions record and the Hire job data row for employee record 0. Later, when the second job data row (employee record = 1) and another worker’s conditions record are inserted, the system creates an S-2240 event for the second employment with information from this worker’s conditions record and the Hire job data row for employee record 1.

  • If a worker’s conditions record (previously submitted to the Government) is deleted, the system creates an S-3000 event to remove it from the Government’s system.

  • If a worker’s conditions record (the one used in initial loading) is deleted, the system rectifies the S-2240 event for the initial loading with information from the worker’s current worker’s conditions record as of the go-live date.