Generate People

Menu: People> Generate People

This screen aims to generate and link People People from the register of employees, dependents and candidates registered in the database. Only workers/ dependents and candidates who still do not have people related to them will be presented.

Start

The window has the wizard format, which enables running the process that comprises the following steps:

The process for searching and generating people registration on the database will be done from this window. The searching and generation of people will occur only for workers, dependents and candidates who still does not have a person bonded to them. The updating will occur only for people who already have bonded workers.

The process for searching and generating people registration on the database will be done from this window. The searching and generation of people will occur only for workers, dependents and candidates who still does not have a person bonded to them.

Through this window it is possible:

• Check the existence of person registered on the database with data equal or similar to the worker or dependent;
• Generate a person registration for each worker who does not have a person compatible on the database;
• Update the Person information with more recent information data on the database;
• Define which will be the compatibility criteria between the person and worker;
• Perform the same activities above mentioned for dependents;
• Bind the candidates to the same person bonded to the admitted worker.

When finishing the process, the information will be available in the processing LOG 121 - Generation of People.

Selection

Step 1 - Selection

In this step, it is possible to select which items below want to search/generate people. it is recommended following the order presented, that is, first of all, run the workers, after, the dependents e finally the candidates.

Generate

• Workers
• Select this field to consider only workers (employees, third party and partners) in the generation of people.
• Dependents
• Select this field to consider only dependents in the generation of people.
• Candidates
• Select this field to consider only external candidates in the generation of people.

Criteria for Workers

When selecting the Workers option, the system allows to define if wants to display or not the registers or only identify them for those that meet the conditions below:

All Registers
Select this field to display all registers, except those checked as Do Not Display. When this field is deselected, only criteria from the Display column will be adopted, when selected.

Workers without CPF* (View)
Select this field to consider workers who do not have CPF*. If the All Registers item is selected and the other items are selected for not be displayed, the workers who have CPF* will be also considered.

Workers without CPF* (Identify)
Select this field to display workers without CPF*, highlighting them in red and reporting the requested item.

Workers with duplicated CPF* (View)
Selected this field to present workers who have duplicated CPF*, that is, when there is more than one worker with the same CPF* on the database. If the All Registers item is selected, the workers who do not have duplicated CPF* will be also considered.

Workers with duplicated CPF* (Identify)
Select this field to display workers with duplicated CPF*, highlighting them in red and reporting the requested item.

Workers without birth date (View)
Select this field to consider workers with zeroed birth date. If the All Registers item is selected, the workers who have birth date will be also considered.

Workers without birth date (Identify)
Select this field to display workers without birth date, highlighting them in red and reporting the requested item.

Workers without CTPS* (Social Security Work Book) (View)
Select this field to consider collaborators without CTPS*. If the All Registers item is selected, the workers who have CTPS* will be also considered.

Employees without CTPS* (Identify)
Select this field to display workers without CTPS*, highlighting them in red and reporting the requested item.

Advanced Selection
This field will be enabled when the Advanced criterion is selected. Allows to use a rule and/or SQL filter to select registers.

Operators accepted in this field: = , <, > , <> , > =, (I.e. , LIKEand NOT LIKE.

Filter Example

NomFun = ('Maria')- will return only the worker with the nameMaria..
NomFun like ('Maria%') - all workers who start with Maria name will be checked, disregarding posterior names: Maria da Silva Santos, Maria da Conceição, Maria da Silva Pereira and Maria.
NomFun like ('%Silva%') - workers who have Silva in their names will be checked: Maria da Silva Santos and Maria da Silva Pereira.

Criteria for Dependents
It follows the same approach for Workers, however, the CTPS* and PIS* data will not be used here.

When the Dependents option is selected, allows defining if wants to display the registers or not, or only identify them for those that meet the conditions below:

• All Registers
  Select this field to display all registers, except those checked as Do Not Display. When this field is deselected, only criteria from the Display column will be adopted, when selected.
• Dependents without CPF* (view)
  Select this field to consider the dependents who do not have CPF*. If the All Registers item is selected and the other items are selected for not be displayed, the dependents who have CPF* will be also considered.
• Dependents with duplicated CPF* (view)
  Selected this field to present the dependents who have duplicated CPF*, that is, when there is more than one dependent with the same CPF* on the database. If the All Registers item is selected, the dependents who do not have duplicated CPF* will be also considered.
• Dependents with duplicated CPF* (Identify)
  Select this field to display dependents with duplicated CPF*, highlighting them in red and reporting the requested item.
• Dependents without birth date (view)
  Select this field to consider dependents with zeroed birth date. If the All Registers item is selected, the workers who have birth date will be also considered.
• Dependents without birth date (Identify)
  Select this field to display dependents without birth date, highlighting them in red and reporting the requested item.

Criteria for Candidates
Only candidates who have been admitted in the Personnel Management module through permanent employment and have a bonded person will be selected.

When selecting the Candidate option, 3 options are made available:

• Admitted Candidates
  This option is the one which already existed, and when processing, the candidates who are bonded to any worker and this worker has a person associated will be bonded.
• Candidate in the selection process
  When processing, the system will list the external candidates who are linked to any request and the candidate situation is 1 - Active in the process; with this option, the criteria will be also made available. When clicking the Selection button when this option active, the following fields for filter will be displayed:
  
  
  • CodRqu - requirement
  • NumCan - Candidate
• All
  In this case, the options of criteria will be also made available and the Selection button will present only the NumCan field - Candidate for the filter.

Through the Selection button, allows to use some ranges of type: Company, Type of Worker, Worker, Branch, Org. Unit, Cost Center, Job, Binding, Shift.

When pressing the Next button, the result of filters applied will be displayed in the next Confirmation window.

Confirmation

Step 2 - Confirmation
In this step, if the user has chosen the update option, the checkboxes Generate person when not found, Link the contributor's candidate to the person and Copy instructor information are not displayed. In the case of the button Criteria, it is not available and only employees who have links to people are displayed.

If the user has opted by generating, the system presents the data selected as set in the previous phase (Selection): Workers, Dependents or Candidates and the respective criteria. Only the registers that do not have a person bonded are presented. In this step the user can come back to the previous step.

Generate a person when it is not found
Select this field to generate a person, when it is not found from the worker or dependent.

Bind the worker’s candidate to the person
Select this field if the worker’s candidate will be also bonded to a person. This will occur when the candidate has already been turned permanent in the Personnel Management module and it has a person bonded. This indication corresponds to the process to Generate Candidates.

Copy the instructor information
Select this field to copy the courses released for the instructor teaches (Training > Courses > Instructors) and their availability (Training > Availability > Instructor) for the person that will be generated and/or bonded. Other information related to the instructor, for example, the instructor reported in the group information and its exceptions, can be converted in Others > Utilities > Conversion of InstructorsCoversion of Instructors.

This field will be available only if in Others > Indications - People folder, the Course Instructors field is equal to 1-People.

If opting to search/generate Workers, the routine will present the following data of Workers: Company, Type, ID Number, Name, Birth, CPF*, PIS*, CTPS*.

The workers will be presented according to the filters reported:

• When presenting the workers, will consider criteria that the user selected in the previous step, to display or not display them;
• If defined that all registers must be presented, all them will be displayed, except those selected as Do Not Display.
• If defined that all registers must not be presented, only those selected as Display will be presented.
• The advanced criterion will be considered only when there is a SQL filter or rule reported. Otherwise, it will be considered in the data load and also for identification;
• When presenting workers, the filters of company, branch, type of worker, ID number, org. unit, job, binding, shift and cost center which have been reported will be considered. The system will consider information referring to the current date.

In the advanced criterion, in the case of rule, it will receive as parameter the Worker register and will return if it is valid or not. They will be considered valid registers if the return of the rule is 0.

The same procedures above will be used if the user select to search/generate Dependents. In case of Candidates, only the candidates who do not have a person bonded will be presented, those who have been admitted in the Personnel Management and that the admitted worker has a person bonded. In this case, a binding between the candidate and the worker’s person will be created. When consulting the Associations folder in the person information, two bindings will be presented.

It is possible to open the information of the registers presented through a double click, allowing to adjust information of corresponding registers, since the routine does not obligate the binding between the worker and the person.

The window allows configuring the rules of comparison of workers with people. The same can be done for dependents.

When configuring the comparison criteria of workers, it will be possible:

• Registering one or more comparison criteria between the worker and the person;
• For each comparison criteria it will be possible to define which Worker fields will be compared to which Person fields;
• All numeric, date and string fields (except memo and photo fields) of Worker (R034FUN and R034CPL) and of Person (R033PES) can be included for comparison;
• It will be possible to determine if the fields will be compared when they are empty (null or equal to zero/space).

The same comparison criteria above is applied to the dependents:

It will be allowed to change the order of the criteria registered for dependents and workers.

By default, the routine will suggest to the customer the configurations below, for comparison of Workers:

• 1st criterion - CPF*, Name
• 2nd criterion - PIS*, Name;
• 3rd criterion - CTPS*, Name.

Generates people when does not find a person similar to the Worker.

Binds the worker’s candidate.

By default, the routine will suggest to the customer the configurations below, for comparison of Dependents:

• 1st criterion - CPF*, Name
• Generates people when does not find a person similar to the Dependent.

When selected to search/generate people from Workers or Dependents, the routine will ask the user if it wants to continue: “The system will check if there is a person similar to each one of the registers selected according to the criteria configured and this process can take time. Do you want to continue? (Y/N) ".

If the processing is confirmed, the routine will check if there is a person compatible for each selected register, considering the configured comparison rules.

To search a compatible person for a Worker or Dependent register, the following items will be observed:

• Considers each configured comparison criteria individually, according to the order registered of criteria;
• When checking a criterion, all configured fields will be compared;
• If one of the fields is configured for not be compared when it is empty, and it is empty, the criterion will be considered as invalid;
• When comparing the string fields, the blank spaces from the beginning to the end of the field will be ignored;
• The comparison of the Name field will be done differently, where the name must be considered when:

• Its entire content is equal;
• The first and the last name of the processed register are equal to the respective names of the person;
• The name of the processed register starts with the name of the person;
• The name of the person starts with the name of the processed register.

When a person is found for the selected register, it will be bonded to that register.

If a person is not found for the selected register and the system is configured to generate people and do not find compatible people, a person will be generated from the data of the selected register and will be bonded to it.

Example of people searches:

Considering as criteria for comparison of workers:

• 1st criterion - CPF* (do not compare to zero), Name;
• 2nd criterion - PIS* (do not compare to zero), Name;
• third criterion - CTPS* (do not compare to zero), Name;

Considering people below, who are registered on the database:

1. João Mendonca - CPF* 11111111-11 - Birth Date: 8/15/1978 - PIS*: 123456789 - CTPS*: 44455;
2. João de Souza - CPF* 11111111-11 - Birth Date: 1/1/1966 - PIS*: 44455577 - CTPS*: 0;
3. Maria Cabral - CPF* 0 - Birth Date: 12/12/1960 - PIS*: 131313 - CTPS*: 74747.

Considering the workers below:

• ID Number 100 - João da Silva Mendonça - CPF* - 11 111111111 - Birth Date: 15/8/1978-PIS*: 123456789 - CTPS*: 0;
• ID Number 200 - Carlos Ribeiro - CPF* - 11 111111111 - Birth Date: 15/8/1978 - PIS*: 123456789 - CTPS*: 0;
• ID Number 300 - JACOBS - CPF* 0 - Birth Date: 15/8/1978 - PIS*: 44455577 - CTPS*: 45678;
• ID Number 400 - Maria Cabral - CPF* 0 - Birth Date: 2/12/1960 - PIS*: 0 - CTPS*: 74747;

1. When searching if there is a person for the worker 100, the routine will:

• Compare the 1st criterion and find the person with code 1, because:

• the CPF* is different from zero and is equal
• the name is also equal, disregarding the its accentuation and comparing the first name to the last name.

2. When searching if there is a person for the worker 300, the routine will:

• Compare the 1st criterion, however, the person will not be found, because:

• The worker CPF* is equal to zero and, according to the configuration, this zeroed field must not be compared.

• Compare the 2nd criterion and find the person of code 2, because:

• the PIS* is different from zero and is equal to the person’s;
• The name is also equal, disregarding accentuation.

3. When searching if there is a person for worker 400, the routine will:

• Compare the 1st criterion, however, the person will not be found, because:

• The worker CPF* is equal to zero and, according to the configuration, this zeroed field must not be compared

• Compare the 2nd criterion, however, the person will not be found, because:

• the Pis* of the worker is equal to zero and, as configured, this zeroed field must not be compared

• Compare the 3rd criterion and find the person of code 3, because:

• the CTPS* is different from zero and is equal to the person’s;
• the name is also equal, disregarding the its accentuation and whereas the worker name is contained within the person name.

4. When searching if there is a person for the worker 200, the routine will not find any person, because:

• The CPF* is equal
• The name is different, even disregarding the accentuation

When selected to search/generate people from candidates, the routine will ask the user if it wants to continue: “The system will bind people to each selected worker and this process can take time. Do you want to continue? (Y/N) ".

If the user confirms the processing, the routine will bind the person who is bonded to its admission worker to each candidate.

Registration data
When selecting this option, the people register is updated based on the current situation of the data of the employee (basic data sheet, complementary data sheet, address, photos, among others).

Training courses an
d Improvement courses It makes updating / synchronization of the training courses / improvement of the employee to the person, in a collective way.

Generation

Step 3 - Generation
In this step, in the update process, the personnel records are updated with the data of the employees' records with active contracts that have the most recent date of admission. In the generation process, new persons are created for each worker, dependent or candidate, with the respective binding.

In this step, new people for each worker, dependent or candidate will be created, with the respective binding.

In the generation, in case of some conflict the system will adopt the criteria:

For training and improvement histories

• The history in the person is from a collaborator: will be overwritten when the new history is full, otherwise it will be overwritten only if the person's history worker is dismissed and the new employee is active. If both employees are dismissed or active, the employee's record of the most recent first branch history will be kept. When the new link is from a candidate or a dependent, it does not override.
• The person's existing record is from a candidate: will be overwritten if the new link is from a collaborator, dependent or a candidate with a most recent inclusion date.
• The person's existing history is for a dependent: will be overwritten if the new link is a contributor.

For the person's information, address, bank account and photo

• The information in the person is from a collaborator: will be overwritten if the employee's information worker is dismissed and the new employee is active. If both employees are dismissed or active, the employee's record of the most recent first branch history will be kept. When the new link is from a candidate or a dependent, it does not override.
• The information in the person is from a candidate: will be overwritten if the new link is a collaborator, dependent or a candidate with a most recent inclusion date.
• The information in the person is from a dependent: will be overwritten if the new link is a contributor.

Through the countryside Situation in this step you can track the completion status of the processing.

The routine will write a Log for each executed process, which can be viewed through the buttonLog. The log contains the parameters passed by the routine (selection options, filters, and configuration used for comparison) for each process executed. It also displays the person who was linked to the record, or if a new person was created for the record.

Veja também:

• Consist of information from People
• Delete People
• Generate People