History Past
Warning
This documentation has information that applies only to some modules. Contents that have the icon 
indicate each case, position the mouse over this icon and see the description of the modules.
It allows to inform the employees' departures. Clearances are automatically included in the corresponding sheet processing when generating hours.
Allows you to include dates of end of forecast, in order to facilitate the control of employees who are away. It is through the information stored here that the periods of leave will be consulted, reflecting holidays, 13th salary, terminations, RAIS and others.
To exclude, all data is checked, excluding only those that have the same dates and situation. The system controls overlapping of errors by issuing an error message when encountering this situation.
- It is not allowed to register departures with situations of types 1, 16 and 18;
- By including separations with situations of types 15, 16, 17 or 18, the Situation of the Basic Tab (R034FUN.SitAfa) will not be updated;
- It is not possible to register a departure whose start or end date is contained in an existing notice to the employee, avoiding the overlap of information in the eSocial layout S-2230.
- It is not possible to register a removal without informing the end date, when this leave is prior to a prior notice. Thus avoiding a possible overlapping of remoteness to the warning;
- The Point and Dining Control only considers up to five departures in a single day;
- The rules by process of the history of departures are executed twice: one before and one after inclusion / change / deletion. In these rules it is possible to use user fields through the syntax 'TABLE.CAMPO'. To find out which screen executed the rule you can use the OriHisAfa system variable;
- When the start time and the end time are 00:00, the system ignores these two information, considering the spacing only for the dates;
- Informing the end date of unjustified absences is mandatory if it is more than one day.
Important
Calculation made to know if the month will be considered as worked or removed
Collaborator removed in the period from 01/01/1999 to 02/15/2000 by work accident. On 01/03/2000 he was fired, being calculated in the termination one of 13 of proportional and one of 13 of proportional Accident of work.
For the month to be considered as worked, the number of days worked must be greater than or equal to half of the month, otherwise it will be considered as retired.
Example:
| Qty days month | Half of the month (truncated) | Worked days | Days away | Month worked | Month away |
| 31 | 15 | 15 | 16 | Y | N |
| 30 | 15 | 14 | 16 | N | Y |
| 28 | 14 | 14 | 14 | Y | N |
| 29 | 14 | 14 | 15 | Y | N |
As the employee stayed away until 02/15 and from 02/16 to 02/29 = 15 days worked, that is, 15 is equal to half of the month, then the month is considered as being worked.
Medical License
The system considers Medical Leave Days to Pay settings in the Medical License tab of the Companies screen (FR030EMP).
Legal aspect
Faults and delays
When the employee, without good cause, fails or is late to work, the employer can deduct from the salary, amount corresponding to the absence. He may deduct, including weekly rest, when the employee does not fully meet his work schedule in the previous week.
Legal fouls
Article 473 of the CLT stipulates that an employee may no longer attend the service without prejudice to weekly salary or rest:
- Up to two (2) consecutive days, in case of death of the spouse, ascendant, descendant, sibling or person who, declared in his Work and Social Security Card, lives under its economic dependence;
- Up to 3 consecutive days, due to marriage;
- For one day, in case of childbirth, during the first week; (here is understood the 5 (five) days of paternity, provided in Const. Federal of 1988);
- For one day, every 12 (twelve) months of work, in case of voluntary donation of blood properly proven;
- Up to 2 (two) consecutive days or not, for the purpose of enlisting voters, under the terms of the respective law;
- In the period of time in which it must comply with the requirements of the Military Service referred to in letter "c" of art. 65 of Law 4,375 of August 17, 1964;
- On days when you are taking a college entrance exam to a higher education school;
- For as long as it takes, when you have to appear at court.
The Point and Dining Control module presents some restrictions when there is more than one withdrawal or schedules and departures registered on the same day. Therefore, the determination of the point in these situations can present different results than expected.
Contributor type
Enter the type of employee. Each type has a different use in the Human Capital Management | HCM. See below the characteristics of each one:
- Employee: is the type used for employees, employees or employees registered in the company;
- Third Party - is indicated for workers from other companies who render temporary service. For this type there is the Predicted Period field where you can enter the initial and final dates of the service rendering of this third party;
- Partner - It differs from a third party because it is a worker registered in other company located in the industrial park of the company owning the Human Capital Management | HCM module. This is an intermediate type between the employee and the third party.
Worker Enter the registration of the employee, third party, partner or click on the list button to consult the registered users.
Date Past Enter the start date of the removal.
Clearance Time Enter the start time of the removal. If you are informed 00:00 in this field and also in the field End Time, People Management | HCM ignores these two information and considers only the dates.
Note
Even if more than one employee is removed on the same date, only one will be considered for shipment to S-2230. The last leave of the day, ie the longest start time (Time Spacing).
Information
Situation
Please state the status of removal, vacation or dismissal.
If the situation is type 03 (Sickness) or 04 (Accident at Work) and a number of days are reported in the field Medical License Days, these will be calculated in the situation with type 14 (Medical License) of smaller code in the situation table.
Notes
- When reporting a situation of type 03 (Sickness), 04 (Accident at Work), 14 (Medical License) or 23 (Work Accident License), a screen will be displayed with the deviations of these types that were registered in the last 60 days. This since in the field Consisting of INSS (Tables> Values> Welfare> Definitions (FR026DEF)) is informed of the option "Yes - Independent of the CID".
- If in the field Consisting of INSS "Yes - Only Same CID" option is displayed, the screen with the last 60 day clearances will only be opened after informing the field Subgroup CID.
- If you are already informed in the Consisting of INSS the "N - No" option, and the screen with the last 60 day clearances will not be displayed in any case.
- To change the position of the non-retroactive distance: close the current distance and create another as a continuation of the previous one, informing the new situation;
- To change the status of the trip so that it is retroactive: change the field Situation and inform the date on which this change occurred in the field. Date Change Status.
Date Change Status When the situation of the removal is changed, in some occasions it is necessary to inform the date in which the change occurred.
To determine whether this field will be enabled, the system checks the ESocial reason, in the eSocial tab of the scenario of situations (FR010SIT).
When you change a status in the move history, the system checks the reason for the current situation and the reason for the new situation, and enables the change date when the change falls into one of the following conditions:
| ESocial reason for the current situation | ESocial reason for the new situation |
|---|---|
| 01 - Accident / Work Sickness | 03 - Accident / Non-work related illness |
| 01 - Accident / Work Sickness | 06 - Retirement due to disability |
| 03 - Accident / Non-work related illness | 01 - Accident / Work Sickness |
Reason Source of Change and
Inform the origin that caused the exchange of reason for the removal that is being registered.
If the reason is caused by a judicial determination (origin "3"), also inform the number of the judicial process that requested this change.
This information is used to generate eSocial layouts, such as the S-2230.
Date of birth
Specific information for situations of types 6 or 19 - Maternity Leave. Informing this date the system creates the stability history beginning on the date of delivery. Not informing, stability is created beginning on the date of removal.
Attendant
This field brings the information you have entered into the attendants (Tables> General> Medical Assistants (2)) and is authorized for situations of types: 3 - Sickness, 6 - Maternity Leave, 10 - Paid Employee Leave, 14 - Medical Leave (company pay) or 19 - Maternity.
Name Attendee Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the fiel
d Clerk, or you can be informed manually when you do not choose to register.
Class Organ Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the field Clerk, or can be manually informed according to the following options: 1 - Regional Council of Medicine (CRM) and 2 - Regional Council of Dentistry (CRO).
Professional Board Registration
Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the field Clerk, or can be manually entered the registration number in the professional council.
Note
The fields Name Attendee, Class Organ and Professional Board Registration are only required to be filled when the date of removal is equal to or later than the beginning of eSocial, defined in the Personnel Administration module under Companies> eSocial Settings (FR060DES), and when on the Situations screen ( FR010SIT), the situation of the removal is with the ESocial reason with the option "1 - Accident / Work-related illness" or "3 - Accident / Non-work-related illness".
UF Professional Council Automatically searches the information for the attendants (Tables> General> Medical Assistants (2)) when informing the field Clerk, or the acronym of the home state of the professional council may be entered manually.
Type Accident Traffic This field is enabled for situations of types: 3 - Sickness, 4 - Work Accident, 14 - Medical License (company pay) or 23 - Accident Work 15 days.
Also, it is only possible to inform you when the eSocial reason for the indicated situation is "1 - Accident / Disease not related to work".
ICD
This field is enabled for situations of types: 3 - Sickness, 4 - Work Accident, 6 - Maternity Leave, 10 - Paid Employee Leave, 14 - Medical Leave (paid company), 19 - Maternity Assistance or 23 - Work Accident License (Pgto Empresa).
For the generation of the eSocial layout S-2230, it is mandatory to inform the CID with four (4) characters if the reason for the removal is related to an accident or illness.
Subgroup CID
Inform the code of the subgroup of diseases that resulted in the employee being removed. If this code is related to the CNAE of the employee's branch as it appears in the table of CIDs by CNAE in Tables> General, an alert message will be issued suggesting to the next field Nexus Risk = Yes.
Example:
The dev branch has the CNAE 1749 tax = manufacture of other textiles, including weaving.
The removal occurred as a result of the Sub-group of the CID M75 = shoulder Injuries.
This field is available only when in the Miscellaneous Ticks screen (FR000ASS), the field Control Epidemiological Nexus "Yes", or when it is "N - No" and has the Safety and Medicine module, the field Subgroup CID Settings by Company ( FR110DEF), is set to "Y - Yes".
In the Personnel and Safety and Medicine modules, the records presented in the field survey Subgroups refer to diseases. Through the selected disease, the system carries the respective subgroup. The diseases presented in the research screen serve to facilitate the search of the subgroup.
Nexus Venture
Valid information:
- S: Inform Yes when this departure is at risk of being considered in the Technical Epidemiological Nexus (NTEP). If the disease subgroup code (CID) is related to the employee's CNAE, the system will suggest "S";
- N: Inform No when there is no possibility of the disease coming to be considered in the epidemiological link.
This field will be available if the field Control Epidemiological Nexus is set to "Yes".
Expert Decision Date
Inform the date of the decision on the expert's report evaluating whether or not the removal will be considered in the Epidemiological Nexus.
This field will be available if the field Control Epidemiological Nexus is set to "Yes".
Date Home Nexo Inform the date on which the sick leave was changed to Accident at Work. This field will be filled automatically when the CAT registration in the system occurs.
Example:
The collaborator was removed on 02/01/2008 by the 3-AID-disease situation, by the subgroup of M75 disease that has relation with the CNAE of the affiliate of the collaborator.
On 11/02/2008, CAT was registered with this employee. The start date of the link will be 11/02/2008.
This field will be available if the field Control Epidemiological Nexus is set to "Yes".
Initial Situation
It presents the initial situation of separation that originated the Epidemiological Nexus. This field will only be enabled if the start date of the nexus is fulfilled.
This field will be available if the field Control Epidemiological Nexus is set to "Yes".
Cause Resignation
Requested only in the schedule of dismissal.
Consider Turn-Over Indicate whether or not the removal should be considered in Turn-Over.
Days Justified For situations of type 03 (sickness benefit) or 04 (accident at work), this data will appear, where we can indicate the number of days of paid medical leave, which must be paid by the company. This number of days will be taken for pay as a leaf, in the event code that contains the characteristic 01N or 02N, being disregarded as days of remoteness.
In Point Control and Canteen, these days will be calculated in the first situation with Type 14-Medical License 15 days registered in the table, or in the code entered in the field Justified Days in the record of the situation.
Same Reason Within 60 days
Inform if the removal occurs for the same reason as the previous one (accident / illness) within 60 days. This field is used to generate information for the eSocial layout S-2230.
Qty of Missing Hours
Requested only for fault schedules. It is currently used by the Personnel Administration when the employee did not miss the full day.
Days Forecast If you enter a number of days, based on this value the system will automatically feed the field Expected Completion
.
This field will be disabled when the situation type is 15 - Faults.
End Date Inform the end date of the removal.
Note
If the reason for the eSocial is "1 - Accident / Work Sickness", it is not mandatory to fill in the fields Days Forecast and End Date. If these fields are left blank, the tag qtdDiasAfast of the S-2230 layout will be reset to zero.
Time End End time of the removal. If you are informed 00:00 in this field and also in the field Time Spacing, People Management | HCM ignores these two information, considering the departure only for the dates.
Expected Completion
Inform the expected end date of the removal. This information will be used to control the termination of the removal and listed in reports. The date foreseen for termination of leave will be requested only for leave schedules of types 06 (maternity leave), 11 (paternity leave), 12 (collective holidays), 13 (prior notice worked) and 14 (Medical Leave company)).
The date entered for the forecast of termination of the departure, will also be used for the count in the distribution of the Transportation Ticket.
Return Examination
Valid information:
- S: Yes, exams will be generated in the Medicine module. Types 03 (sickness allowance), 04 (occupational accident), 05 (military service), 06 (maternity leave) and 14 (Medical leave (company pay);
- N: No exam will be generated.
The exam will be generated with the start date of the removal, since it is not known what the effective date the employee's return to work.
Reason Rais
Through this field the user can inform the corresponding situation, according to the established in the RAIS manual. In the Point Control and Canteen module, this field is only available if it is integrated with the Personnel Administration, Safety or Medicine modules.
The information in this field will overwrite what you are informed in the situation record.
Note
Space to type any message related to the spacing, which can be listed in the reports through the variable ObsAfa in the Generator.
In the case of departures from the situation 21 - Holidays Risen already in advance, the observations are obligatory to the e-Social, they will be sent to the Government provided that the date of completion is not fulfilled.
Extensions
Warning
This documentation applies only to the module: AP.
Available only on departures whose Situation has marked "Yes" in the field Control Extension, in Tables> General> Situations.
The extension of licenses and withdrawals of different types occurs mainly in public agencies, and with each extension, it is necessary to record the act number, the start and end dates, the date of publication and the number of the official bulletin that was published, as well as the sequential number of the medical report. However, these data are merely informative, not interfering with the official dates of removal.
Monitoring
It allows to record information related to the Technical Epidemiological Nexus.
Date Acomp
Corresponds to the date of follow-up of the removal.
Next Date
It may be used to indicate the date of the next follow-up when known.
Seq. Resource
Corresponds to the sequence of the appeal against the INSS to request non-application of the NTEP, proving that there is no causal link between work and remoteness.
Dt. Decision
Corresponds to the decision date of the appeal against the INSS.
Result
It corresponds to the result of the resource that can be "Favorable" or "Opposite."
Next
Matches whether the next resource was opened by the company, employee or there is no more recourse.
This folder will be available for all modules when you have in the owner the modules Administration of Personnel and Safety and Medicine. And if in the screen of several signals the field Control Epidemiological Nexus are with s.
Documents
Allows you to register documents for removal.
When clicking the right button on the option “Show Field”, it is possible to configure the fields of the window. When defining the fields selected on this window, the Web has the same definitions as the fields on this window, exception the user fields.
Alt. Reason Complement
Provide supplementary information on removal, when the reason for removal of the eSocial is changed from "3 - Accident / Non - Work - Related Disease" to "1 - Accident / Work Sickness" and the origin of the reason for the change is at the initiative of the employer . The tab is only available in this situation, and the information entered here is used to generate the eSocial layout S-2230.
The fields in this tab are treated identically to the same name, located on the Directory tab.
Veja também:
English
Español
