ESOCIAL: S-2230 Event Rectification is Generated for a Different Absence.
(Doc ID 2532931.1)
Last updated on NOVEMBER 09, 2019
Applies to:PeopleSoft Enterprise HCM Global Payroll Brazil - Version 9.2 and later
Information in this document applies to any platform.
Scenario 1 - When vacations are cancelled due a sick leave and the vacation leave has already been sent to the eSocial(event S-2230), a rectification of the event S-2230 is created for the sick leave without the medical information.
The event S-2230 for the vacations should be excluded( event S-3000) and a new event S-2230 should be created for the accident leave.
Scenario 2 - Employee had a a sick leave from 08/08/2018 with 952 days. XML for event S-2230 was generated correctly.
- The same employee returned from the sick leave on 10/15/2018.
XML with the leave end date was created, what is correct.
- Employee had vacations from 01/02/2019 to 01/21/2019. It was generated a rectification of the first XML(sick leave) with the information of the vacation.
Scenario 3 - An employee is on vacation. The XML with the start and end date of vacation has been generated and returned with success from the eSocial.
But, the vacations was interrupted due a maternity leave, then the vacation end date was anticipated.
However, when anticipating the vacation end date, the event of rectification does not have the infoAfastamento tag This causes the error in the XML file structure.
Code 17 - The structure of the XML file is in disagreement with the XSD schema The element 'evtAfstTemp' in namespace .... has incomplete content. List of possible elements expected:'infoAfastamento' in namespace......
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