Security Settings -Company
It comprises the configurations required for the Security module in relation to the control of WAC issuing, PPE delivery, IPA/CIPATR, Brigade, LTCAT, ERPP, PSS and Service Order.
WAC
Nature of Injury
Report the origin of information for the Description and Nature of Injury fields.
In this field, the default option is “0 - According to the Description of Injuries in the Wac”. If selecting the option “1 - According to the Nature of Injuries”, each nature of injury will be presented in a line of the Description and Nature of Injuries fields.
Likely Diagnosis
Report the origin of information for the Likely Diagnosis field.
In this field, the default option is “0 - According to the Likely Diagnosis in the Wac”. If selecting the option “1 - According to the ICD Description”, each nature of injury will be presented in the Likely Diagnosis field.
Generate Absence Record
Defines if, when registering a labor accident, a absence record will be created or not.
Table of Totaling Items
Allows to report the table of Totaling Items which is related to the company. This field is enabled only if the Personnel Management module is integrated with database.
Totalizer Hrs. Work
Allows to report the totalizer of worked hours which has type of sum 3. This field is enabled only if the Personnel Management module is integrated with database.
Totalizer Hrs. Away
Allows to report the totalizer of absence hours which has type of sum 3. This field is enabled only if the Personnel Management module is integrated with database.
WAC Issuing
Allows to define which type of information will be listed in the WAC form, section of Medical Certificate and field 63-Notes.
WAC
Report the code of the WAC model. The Personnel Management module already offers the FPHI007.PRE for this purpose. For the Security and Medicine module counts on the model: SMAC001.GER.
First name Button
Report the name of the first button which will be enabled on the window of labor accident register. Only one item can be used for each button, that is, a model or a rule.
1st Button Model
Report the name of the first button report model to be used on the window of labor accident register.
1st Button Rule
Report the name of the rule that will be run when pressing the first button in the labor accident register. All information in the R086Cat and R086Act tables will be passed to the rule and model. In the rules, it is possible using the syntax 'Tabela.Campo' for current information about the accident, however, these information can be changed. For example, the user wants to change the Accident Description field and, before pressing the Change button, it calls the rule through the customized button. If using the R086ACT.DesAct rule, the value of the Description field already changed will be used. However, after running the rule, the user can press the Cancel button, and the changes of the Description field will be undone. The user must be in know about this possibility and, depending of the situation, it must choose to use the ExecSQL to search for information to be used in the rule.
Name 2nd Button
Report the name of the second button which will be enabled on the window of labor accident register. Only one item can be used for each button, that is, a model or a rule.
2nd Button Model
Report the name of the second button report model to be used on the window of labor accident register.
2nd Button Rule
Report the name of the rule that will be run when pressing the second button in the labor accident register. All information in the R086Cat and R086Act tables will be passed to the rule and model. In the rules, it is possible using the syntax 'Tabela.Campo' for current information about the accident, however, these information can be changed. For example, the user wants to change the Accident Description field and, before pressing the Change button, it calls the rule through the customized button. If using the R086ACT.DesAct rule, the value of the Description field already changed will be used. However, after running the rule, the user can press the Cancel button, and the changes of the Description field will be undone. The user must be in know about this possibility and, depending of the situation, it must choose to use the ExecSQL to search for information to be used in the rule.
3rd Button Name
Report the name of the second button which will be enabled on the window of labor accident register. Only one item can be used for each button, that is, a model or a rule.
3rd Button Model
Report the name of the second button report model to be used on the window of labor accident register.
3rd Button Rule
Report the name of the rule that will be run when pressing the second button in the external candidate information. All information in the R086Cat and R086Act tables will be passed to the rule and model. In the rules, it is possible using the syntax 'Tabela.Campo' for current information about the accident, however, these information can be changed. For example, the user wants to change the Accident Description field and, before pressing the Change button, it calls the rule through the customized button. If using the R086ACT.DesAct rule, the value of the Description field already changed will be used. However, after running the rule, the user can press the Cancel button, and the changes of the Description field will be undone. The user must be in know about this possibility and, depending of the situation, it must choose to use the ExecSQL to search for information to be used in the rule.
Investigation
Report the code of the Investigation model which corresponds to the SMAC009.GER model (Register for investigation of occurrences). It will be used in Security > Accidents > Register for Investigation of Occurrences (Investigation button) and by the menu: Security > Accidents > List.
Print Buttons
For the fields below, when selecting Y - Yes, their respective tabs will be made available, for details on the Labor Accident window (
- Details the Accident Cause
- Details the Causative Agent
- Details the Injury Location
- Details the Nature of Injury
PPE
PPE delivery without instruction
The option selected in this field controls the Use Instruction field, present on the PPE Distribution window (
- Y - Yes: the PPE delivery can happen without the user has instruction of use.
- N - No: the delivery of PPE will be allowed for workers who do not have instruction of use.
PPE Protocol
Inform the report model which will be used in the PPE delivery.
PPEs Distribution
Inform the report model which will be used to list the PPEs distributed.
PPE per Employee Allows to define which procedure will be used in the PPEs delivery estimation registered per worker (Security > PPE > PPE per > Worker) in relation to those defined per Org. Unit, Job, Org. Unit/Job and EHG:
- Does not overlap other definitions - The PPEs defined per Org. Unit, Job, Org. Unit/Job and EHG are also considered in the estimation.
- When the EHG routine is as “Active EHG Only” or “Active and Keep Legacy”: Besides the PPEs defined per worker, only the PPEs defined per EHG will be considered. When the EHG routine is as “Deactivate” or “Under Implementation”: Besides the PPEs defined per worker, only the PPEs defined per EHG will be considered.
- Overlap the other definitions - Only the PPEs registered in PPE per > Worker will be considered.
Worker 20 - Org. Unit 1.1.1
PPE per Org. Unit:
Org. Unit = 1.1.1 - PPEs = 2 - Brigade Glove, 5 - Facial Mask, 6 - Glasses
PPE per Worker
Worker = 20 - PPEs = 3 - Special Glasses
Considering the definition of the PPE Per Worker field:
- Does not overlap with other definitions: The result of the pending EPIs should bring the EPIs 2, 3, 5 and 6.
- Overlaps the other definitions: The result of pending PPEs must bring only the PPE 3.
Generate pending for Document
This information will be used in Security > List, in the models: SMEP001 (Form for PPE Control) and SMEP002 (Form for PPE Control - Empty):
- Yes, from the models mentioned above, a register will be generated in the table for registering the documents (R034RED).
- No, the pending for document will not be generated.
Note
This information will be suggested on the input window of the SMEP001 and SMEP002 models.
Type of Document
Report the type of document which will be used in the document generation. The Type of Document is registered in Tables > General > Types of Documents.
Note
This information will be suggested on the input window of the SMEP001 and SMEP002 models.
Default Authentication in EPI Delivery
Define the action that the system must always adopt during the delivery of an EPI, among the following options:
- 0 - Ask the user: default behavior where, for each EPI delivered, the system displays an authentication confirmation message, allowing to choose between electronic or printed authentication.
- 1 - Not authenticate: no message is presented during the delivery of an EPI; the field Signed Protocol screen of EPI - Individual (FR096DIE) receives "N - No" for new records, allowing the field value to change according to current behavior.
- 2 - Electronic Authentication: no message is presented during the delivery of an EPI; the field Signed Protocol screen of EPI - Individual (FR096DIE) receives "N - No" for new records; the Electronic Authentication screen ( FRBIOSEN).
- 3 - Printed Authentication: no message is displayed during delivery of an EPI; the field Signed Protocol screen of EPI - Individual (FR096DIE) receives "N - No" for new records; the Printed Authentication report, which is defined by the Distribution of PPE.
This resource is used only by the individual distribution of the PPE, and does not exist in the collective distribution.
CIPA*
Suggestions. Alternate
Define about the suggestion of alternates:
- Yes, in the register of CIPA meetings, the system will suggest the alternate as participant.
- No, the alternate will not be suggested in the CIPA meetings.
Reports the Alternate
This field allows to define the way to indicate an alternate (substitute) for a CIPA/CIPATR member, without it has not been previously registered as alternate. Options:
- Only Alternate: will be accepted only the members who are registered with function 5 (alternate).
- Any member, without criticize: will be accepted any member from CIPA/CIPATR without presenting the alert message.
- Any member, criticizes: will be accepted any member from CIPA/CIPATR after presenting an alert message.
Stability of Alternate
Define about the stability of alternates:
- Yes, allows to generate stability for all alternates registered in the function 5, also during the mandate.
- No, the stability will occur only on the candidature period.
Restricts Functions
This field allows to define the treatment that will be given to the functions of urban CIPA members. The valid options are:
- Yes: the default will remain, according to the NR-5.
- No: the functions of members will not be consisted.
A President can have origin E - Elected assigned and, to the Vice-President can be assigned origin I - Indicated.
Note
This restriction will not be applied for the CIPATR (Internal Commission for the Prevention of Rural Labor Accidents) from NR-31.
Minutes of Election
Report the model that will list information about the minutes of CIPA/CIPATR election.
Minutes of Taking Office
Report the model that will list information about the minutes of CIPA/CIPATR taking office.
Minutes of Meeting
Report the model that will list information about the minutes of CIPA/CIPATR meetings.
Proof of Application
Define a report template to use when you want to issue a proof of application to Cipa. The voucher is issued by the Receipt the candidate registration screen (FR100CAN).
LTCAT
Fill in this guide for LTCAT print information. When issuing any report that uses this information, the system first checks to see if they are populated in the LTCAT tab of the PPRAFR583CAD). If it does not find it, check the same fields in this tab of the security settings screen by company. If both are empty, the section will not appear in reports.
LTCAT Introduction
Space intended for comments on LTCAT to be printed
AC Presentation
Identify which of the Approval Certifications must be considered.
- E - PPE: considers the AC that is registered in the PPE.
- F - Supplier: considers the AC that is registered in the Supplier.
- A - Both - Supplier and PPE: considers the CA to be informed in both the EPI and the Supplier.
- D - Supplier - Considering Distribution of PPE: verifies the distribution of the EPI according to the valid CA when the EPI was distributed with the informed supplier. If the supplier is not reported in the PPE distribution, it will be considered the CA according to the validity reported in the PPE information. If in the PPE distribution, the supplier is not reported, it will be considered the CAs of all suppliers of this PPE, since if valid.
- C - Distribution - Considering CA informed in the distribution of PPE: verifies the EPI distributions that were performed for the employee considering the CA informed in the Distribution.
Note
When the option C is selected and the Certificate of Approval field of the PPE distribution is not reported (blank), the system consider the same rule run when the CA Presentation option is with value D.
Conclusion LTCAT
Space for comments on LTCAT to be printed, referring to the text of conclusion of the LTCAT.
Brigade
Criticizes Brigade
Used in the inclusion of the new brigade member.
- Y - Yes: when reporting the new member, a criticism about the shift and org. unit will be done.
- N - No: allows registering members from different shifts and org. units.
ERPP
Note
The ERPP tab is not available when the EHG Routine field is configured as 1-Activate EHG Only, on the Security Configuration window (
Presents Jobs and Salaries Activities
When in Others > Indications, Information tab, the Management per Competencies field is set as 3-Activate without legacy, this window is not displayed.
In order to optimize the registering of activities related to the ERPP, the following windows have been made available in the Jobs and Salaries module:
- Jobs > Activities > Activities.
- Jobs > Activities > Specific Activities.
- Jobs > Activities > Area Activities.
Utiliza PSH (Prevention, Safety and Health)
The PSH has arose to manage security and health questions in the company, allowing to develop evaluations items which are controlled by evaluators through information registered.
Reports Examinations
This field is informational only, for use in rules and customized reports.
Service Order
According to the terms in the item 1.7b from the NR-1 of the Ministry of Labor and Employment (MTE), it is for the employee to develop service orders about Labor Security and Medicine, by raising the awareness of employees. This information will be used in the LTCAT - Service Order model along with the other PPRA registration information.
Note
The SMSG010 - LTCAT - Service Order model considers only field information Introduction and Guidance, the SMSG011 - LTCAT - Service Order model considers the information for all fields: Introduction , Internal Rules, Work Accident Procedures and Statement of responsibility.
Inform a text to be displayed in the field Introduction of the service order.
Inform a text that will be displayed in the field Internal Rules of the service order.
Report the list of procedures in the Service Order, which must be run when there is a labor accident.
- Communicate the supervision when there is a labor accident, accident on the way to work or professional disease;
- Request the HR to open CAT - Work Accident Notice, after characterization of the accident, etc.
Note
This field is enabled only if the GHE routine is available.
Report the term of responsibility which will be used in the Service Order, confirming that the worker is aware about the orientations received, risks due to the activities and disciplinary sanctions to which it is subject about its noncompliance.
Note
This field is enabled only if the GHE routine is available.
English
Español


