Esocial: Error sending Event S-1210 For Interns Terminated in Previous Month.
(Doc ID 2912362.1)
Last updated on MARCH 07, 2023
Applies to:
PeopleSoft Enterprise HCM Global Payroll Brazil - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
When running event S-2399 for interns, PS_GPBR_ES_IDCALT should be populated, but when running the event for an intern that was terminated in a month and the payment is in the next month, this table is not populated, causing error when transmitting event S-1210 to eSocial:
Steps to reproduce the issue:
- Navigate to Workforce Administration > Job Information > Job Data and add a row for an intern with termination in the end of the month (e.g. 09/28/2022, payment will be in the next month).
- Navigate to Global Payroll & Absence Mgmt > Termination Process > Mass Termination Request BRA, calculate and finalize the termination calculation.
- Navigate to Global Payroll & Absence Mgmt > Termination Process > eSocial Termination Events BRA and run event S-2399 to create the XML file.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll and calculate calendar group for 09/2022.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll and finalize calendar group for 09/2022.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > eSocial BRA > eSocial Payroll Events and run events S-1200 and S-1210 for Competency Year/Month=2022/09.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll and calculate calendar group for 10/2022.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll and finalize calendar group for 10/2022.
- Navigate to Global Payroll & Absence Mgmt > Absence and Payroll Processing > eSocial BRA > eSocial Payroll Events and run events S-1200 and S-1210 for Competency Year/Month=2022/10.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |