Definitions

In this option are informed some data that will determine the form of treatment of the markings, the rules of calculation and other markings that involve the routine of calculation and its registrations.

The registration of General settings for calculation is by company, so after the registration of the definitions is necessary to inform you on the register of the company.

As the calculation is daily and the contributor can be transferred to another company, general definitions can change every day.

Calculation Definition
Enter a code for the Calculation Definition. This code will be entered in the company register, so she use this setting for calculation of the hours.

General

Use Off Time Inform if on the day off the system should consider working hours if the employee has worked hours.

• "S - Yes": considers working hours. If you have hours, those that are within these hours will not be considered extras;
• "N - No": consider only day off. All hours performed on this day will be considered extras.

Night Conversion Calculation
Tell whether night hours should be converted at the beginning or end of the counting rule.

In order for the time to be converted, it must be marked "S" in the Night Node field of the situation register.

Example:

HorSit[050] = (HorSit[051] * 8) / 7;

The field value must be = 1-Convert before the Calculation rules for this situation.

Tags Reading Report Enter the name of the report template that should list any markings that are rejected for calculation.

Example:

HRAU001. GER
If the company doesn't choose to list the rejected, this field must be blank.
The report will be listed at the end of the reading. The standard model is Hrau001.ger.

Model Point Card Icon This field is used to inform a calculation template that can be generated by the dot card icon, located in the Main menu of the Point and Canteen Control. The models can be telling, Point Card, balances, Hour bank, frequency, timesheet.

The icon will be disabled if no template is entered and restricted to users who are allowed to access the Calculations> Calculation> List screen.

Report to Screenshots To list the report, under Calculations> Calculation> Accounts> Collaborator, using the List on the Date Settings screen. This button will only be enabled if informed a model in this field.

Dismissal situation Please state the code of the situation for dismissed employees. When generating the clearance of resignation is necessary to inform this code.

Control of Verified Days Report used routine of Verified Days:

• "0": does not use control of days checked;
• "1": uses control of verified days and cancels the generation of events (in the integration) for the collaborator if the same own some day with exception that was not verified and generates the log of error;
• "2": uses control of verified days but does not cancel the generation of events (in the integration) for the collaborator if it has some day with exception that was not marked as verified. A log will be generated in the integration informing that the employee has been calculated and still has days with unchecked exception.

When the Verified Days routine is used, the system will behave as follows:

• The calculation screen will show a new signaling, which will allow you to inform if the days that have already been marked as verified should or should not be recalculated.
• It will be shown on the Date Record screen. Verified, which may be signaled by the user, for example, to confirm some accuracy that will be excepted. This field is only available to users who have permission to change the UsuVer field of the R066APU table in the CBDS. The field Verified will also be shown on the Contest Contributors screen, in the Employee Determination list, but only for consultation.
• Also in the Collaborator Settings screen, two checkboxes will be shown. By selecting "Exceptions only", clicking on show only days with exceptions will be displayed. With "unverified days Only" selected, will display only the days that have not been marked as checked. If both options are selected, both conditions will be applied to the search.
• In the calculation of integration will be made a consistency that will send a message to the log when the developer have some day with exception that was not verified. In this case, if the loop "1" in this assignment, the contributor will not be calculated. If it is informed "2", it will be calculated normally.
• In the Report Generator, in the Calculation templates, the ESomNVe variable can be included in the input screen, allowing only unchecked days to be selected. The parameters of this variable are the same as the ESomExc variable.
• In the hit date screen, if the user recalculates the count on a day that is already marked as Verified, the system will display a message advising that if changes are confirmed, the Verified will be lost.

Track Reasons for Success Indicate if the Fixed Reasons routine will be used. When "S" is entered, it will be shown in the status register screen, in Tables> Situations> Register, field Required Match Reason, and in the Collaborator Settings screen the No Motive column will be displayed. In this column will be marked the days that have situations whose registration requires that a reason, field Required Match Reason = "S"), and do not have a typed subject.

Control Observation Specify whether to use the Watch Control routine. When "S" is informed, a new column will be enabled in the Date and Justify Results screens. This new column allows the registration of a notice for each situation.

User who changed the situation Set whether in the Hits on Date a field appears in the situation grid that shows the last user who changed the situation. This information is obtained through the Hit Log (R067LAC) and has a limitation: If any log information is deleted / changed, this field in the Date Hit screen may contain inconsistent information.

Days to return Set the number of days prior to the initial calculation date to recalculate. You are only allowed to enter the value from 1 to 10.

Beat and Day Tolerance Through this button you can set the tolerance treatment by beat and a day.

• "1 - Independent Evaluation": evaluates each tolerance (before and after) of each marking separately, consisting of the information in the Time Tolerance tab in the field Total Daily Faults (the Point Control and Canteen does not consider field information Total Daily Extras).

Example 1:

Schedule

Time	Tolerance Before	Tolerance After
8 AM	07:55	08:05
12 AM	11:55	12:05
1:30 PM	13:25	13:35
17:30	17:25	17:35

The Time Tolerance tab has no information in the Total Daily Faults, do not consider if you have information in the field Total Daily Extras.

• Clocking events : 07:55-12:05-13:35-17:25.
  In this case, the markings do not exceed the tolerances before and after each marking registered, making 8:00 hours of day work;
• Clocking events : 07:53-12:05-13:37-17:25.
  The first appointment of the day exceeds two minutes of tolerance registered and the third appointment exceeds two minutes of tolerance registered.

In this case are cleared:

• 07:53 hours of day work
• 00:07 minutes late daytime
• 00:07 minutes of daytime overtime.

Time

Time	Tolerance Before	Tolerance After
22:00	9:55	22:05
00:00	23:55	00:05
01:00	00:55	1:05
05:00	04:55	05:05

 

• Made markings: 21:55 - 00:05 - 01:05 - 04:55
  In this case, the markings do not exceed the tolerances before and after each marking registered, taking 06:00 hours of night work;
• Made markings: 21:53 - 00:05 - 01:07 - 04:55
  The first appointment of the day exceeds two minutes of tolerance registered and the third appointment exceeds two minutes of tolerance registered.

In this case, are cleared:

• 05:53 hours of night work
• 00:07 minutes late Night
• 00:07 minutes of daytime overtime.

Example 2:

Schedule

Time	Tolerance Before	Tolerance After
8 AM	07:55	08:05
12 AM	11:55	12:05
1:30 PM	13:25	13:35
17:30	17:25	17:35

On the Time Tolerance tab in the Total Daily Faults 00:10, do not consider if you have information in the field Total Daily Extras.

• Clocking events : 07:55-12:05-13:35-17:25.
  As the markings do not exceed the tolerances before and after each registered marking, 08:00 hours of day work are cleared;
• Clocking events : 07:53-12:05-13:37-17:25.
  The first appointment of the day exceeds two minutes of tolerance registered, will be generated 00:07 minutes daytime overtimes. The third appointment exceeds two minutes from time, but tolerance as has informed 00:10 minutes in the field daily Total Fouls, these 00:07 minutes of absences will not be considered, with the daytime working hours 08:00.

Time

Time	Tolerance Before	Tolerance After
22:00	9:55	22:05
00:00	23:55	00:05
01:00	00:55	1:05
05:00	04:55	05:05

On the Time Tolerance tab, in the Total Daily Faults, informed 00:10, does not consider if you have information in the field Total Daily Extras.

• Made Markings: 21: 55- 00: 05- 01:05 - 04:55
  In this case, the markings do not exceed the tolerances before and after each marking registered, taking 06:00 hours of night work;
• Made markings: 21:53 - 00:05 - 01:07 - 04:55
  The first marking of the day exceeds two minutes of the registered tolerance and is generated 00:07 minutes extra days. The third mark exceeds two minutes of the time tolerance, however as it has reported 00:10 minutes in the field Total Daily Faults, these 00:07 minutes of fouls will not be considered, taking 06:00 hours of night work.

• "2 - Dependent Assessment": evaluates each tolerance (before and after) of each tag entered together, consisting of the information from the Time Tolerance tab in the field Total Daily Faults and the countryside Total Daily Extras.

Example 1:

Schedule

Time	Tolerance Before	Tolerance After
8 AM	07:55	08:05
12 AM	11:55	12:05
1:30 PM	13:25	13:35
17:30	17:25	17:35

On the Time Tolerance tab in the Total Daily Faults reported 00:09 and in the field Total Daily Extras reported 00:09.

• Clocking events : 07:55-12:05-13:35-17:25.
  The individual clocking events do not exceed tolerances before and after, but the sums of the clocking events beyond the daily total registered for overtimes and fouls.

In this case, are cleared:

• 07:50 hours of day work;
• 00:05 minutes early departure;
• 00:05 minutes late;
• 00:10 minutes of extras.

• Clocking events : 07:53-12:05-13:37-17:25.
  The first appointment of the day exceeds two minutes of tolerance registered and the third appointment exceeds two minutes of tolerance registered.

In this case, are cleared:

• 07:48 hours of day work;
• 00:05 minutes early departure;
• 00:07 minutes of daytime delay;
• 00:12 minutes overtime hours.

Time

Time	Tolerance Before	Tolerance After
22:00	9:55	22:05
00:00	23:55	00:05
01:00	00:55	1:05
05:00	04:55	05:05

• Made markings: 21:55 - 00:05 - 01:05 - 04:55.
  The individual markings do not exceed the tolerances before and after, but the sum of the markings exceeds the daily total registered for extras and faults:
  • 05:50 hours of day work
  • 00:
  • 05 minutes early night departure
  • 00:05
  minutes late night 00:05 minutes of daytime extras 00:05 minutes of nighttime extras

• Made markings: 21:53 - 00:05 - 01:07 04:55. The first appointment of the day exceeds two minutes of tolerance registered and the third appointment exceeds two minutes of tolerance registered.

In this case, are cleared:

• 07:48 hours of day work;
• 00:05 minutes early night departure;
• 00:07 minutes late night;
• 00:07 minutes of daytime overtime;
• 00:05 minutes of overtime at night.

Example 2:

Schedule

Time	Tolerance Before	Tolerance After
8 AM	07:55	08:05
12 AM	11:55	12:05
1:30 PM	13:25	13:35
17:30	17:25	17:35

On the Time Tolerance tab in the Total Daily Faults reported 00:09 and in the field Total Daily Extras reported 00:09.

• Markings taken: 07:56 - 12:05 - 13: 34-17: 25.
  The individual clocking events do not exceed tolerances before and after, and the sums of the clocking events also do not exceed the daily total registered for overtimes and fouls.

In this case, it will be clearing 08:00 hours of daytime work.

• Markings taken: 07:56 - 12:05 - 13:37 - 17:25.
  The third mark exceeds two minutes of the registered tolerance.

In this case, are cleared:

• 07:48 hours of day work;
• 00:05 minutes early departure;
• 00:07 minutes of daytime delay.

(Did not generate overtime as the sum of the day was 00:09 minutes)

Time:

Time	Tolerance Before	Tolerance After
22:00	9:55	22:05
00:00	23:55	00:05
01:00	00:55	1:05
05:00	04:55	05:05

On the Time Tolerance tab in the Total Daily Faults reported 00:09 and in the field Total Daily Extras reported 00:09.

• Made markings: 21:54 - 00:05 - 01:04 - 04:55.
  The individual markings do not exceed the tolerances before and after and the sums of markings also do not exceed the daily total registered for extras and faults.

In this case, will be with 06:00 hours of night work.

• Made markings: 21:56 - 00:05 - 01:07 - 04:55. The third mark exceeds two minutes of the registered tolerance.

In this case, are cleared:

• 05:48 hours of night work;
• 00:05 minutes early night departure;
• 00:07 minutes late night.

(It did not generate overtime, as the sum of the day was 00:09 minutes)

Example 3:

Time:

Time	Tolerance Before	Tolerance After
8 AM	07:55	08:05
12 AM	11:55	12:05
1:30 PM	13:25	13:35
17:30	17:25	17:35

On the Time Tolerance tab in the Total Daily Faults informed 00:15, and in the field Total Daily Extras informed 00:15.

• Markings taken: 08:15 - 12:00 - 13:30 - 17:30

The first clocking events exceeded the tolerance after, but the sum of the clocking events do not exceed the daily total registered for overtimes and fouls. However, as the tolerance after the marking has been exceeded, the daily total of registered absences will not be considered.

In this case, will be cleared:

• 07:45 hours of day work
• 00:15 minutes late daytime

• Markings taken: 08:05 - 11:55 - 13:35 - 17:30.

The individual clocking events do not exceed the tolerance before/after, and the sum of the clocking events also do not exceed the daily total registered for overtimes and fouls.

In this case, 8:00 hours of day work are cleared (no hours were missed, as the sum of the day was 00:15 minutes).

• Markings taken: 08:05 - 11:55 - 13:35 - 17:25.

The individual clocking events do not exceed the tolerance before/after, but the sum of the clocking events go beyond the daily total registered for overtimes and fouls.

In this case, are cleared:

• 07:40 hours of day work;
• 00:10 minutes early departure;
• 00:10 minutes late daytime

Other situations with tolerance:

1. Tolerance Calculations "Meal Failures" and "Total Daily Faults"

• Tolerance-dependent evaluation: whereas the achievement of the general analysis of the day, the system evaluates first the total tolerance, then the meal tolerance and input/output.

Example:

Time: 08:00 13:30 12:00 18:00
In meal tolerance: 00:05
Daily faults tolerance: 00:12
Tags: 08:00 12:00 13:35 17:52

Computed value:

08:22 = work
00:08 = early departure

The daily absences tolerance is not applied, because the daily total is 13 minutes. Already the meal is applied, because the duration of the meal was only 5 minutes. Thus, only the early departure listed as missing.

• Independent evaluation of tolerance: the routine always considers first the meal/input/output.

Example:

Time: 08:00 13:30 12:00 18:00
In meal tolerance: 00:05
Daily faults tolerance: 00:12
Tags: 08:00 12:00 13:35 17:52

Computed value:

08:30 = work

First, meal tolerance is applied, thus reducing the faults of 13 for 8 minutes. Then the daily tolerance is applied, whereas 8 less than 12 is applying the tolerance.

2. Offset / Offset Calculations / Compensations and Daily Fault Tolerances

• When a period of absence is in removal/release and in tolerance of "Faults in the meal" or "tolerance" input/output Shortages, the period will be generated as work, respecting the tolerance;
• When a period of absence is in removal/release and in tolerance for "daily Total Fouls", the period will be generated as removal/release, respecting the removal/release;
• When a period of absence is in compensation and in any of the daily lack tolerances, it shall work, respecting the tolerance.

See the ApuDiu and ApuNot variables documentation for information about how they are calculated on dates with daily fault tolerances.

Retroactive Settlement
Set whether the system will send the user the confirmation request at all times when a retroactive hit is being made on the Point Management module's hit screens. The purpose of the treatment in Point Management is to identify the adjustments made in the calculation and in the time bank in periods that are already closed.

Check incomplete day
Define if a day that is incomplete at the time of calculation should be checked or not.

Situation for incomplete work
Indicate a situation to calculate the hours of the day that you have an incomplete day. If the situation is informed, the system will generate the total number of hours scheduled for the day in this situation. If you are not informed, the system will perform the calculation normally. This field is optional and is only available if the field Check incomplete day enabled.

Example:

The employee works from 10:00 p.m. to 5:00 p.m. and the calculation takes place every day at 03:00 p.m. When performing the calculation on 10/11 at 03:00, the system does not calculate the 09/11 of this employee if the parameter Check incomplete day is equal to "N - No".

Complementary Work with Waiting Calculation
Determine if the waiting hours will be considered to complement the driver's workday, according to law 13.103, when they are not complete.

Number of days to hit
Determine the number of days to make hits after the employee's date of disconnection, compared to the current date. Available only when field Allows settlement of dismissed employeesfrom the Permissions for Calculation Code screen (FRESH) is not marked and has a Point and Dining Control module integrated with Point Management.

Calculate Holiday Faults on Relay Scale
Determine if there will be the calculation of missed times on relay scale. When there is no calculation, you can optionally set the fault situation on the relay scale holiday on the Calculation Situations screen (FR060DSI).

Clocking events

Consider Interval Please inform yourself if there is a minimum interval between markings for the point calculation:

• "1 - Do not Consider": all point markings should go to the counting.
• "2 - Second Date and Time of Markings": consider only the first mark made in the period reported in the field Limit of Markings.
  Example:

  On 04/11/99, when leaving the company at 18:00 hours, passed the badge on the collector twice, by mistake. In the calculation of hours there, to this day, for this contributor, because for the second marking of 18:00 hours there will be no output.

  In this case, use this option by entering a two minute limit in the Limit of Markings would facilitate maintenance. Thus the system will consider only the first appointment held within this range: from 18:00 to 18:02.

  Markings done:
  • 18
  18:00 (marking scorned in the counting).
• "3 - Second Date, Time, Clock and Function of Markings": consider only the first mark made in the period reported in the field Limit of Markings, taking into account the clock and the function in which the markings were made.
  

  Exampl

  e:On 04/11/99, when leaving the company at 18:00 hours use the function 01 to mark the point and function 04 to justify the overtime to do next. Passes the badge on the collector twice with the function 01, by mistake. And then passes the badge with the 04 function to start the overtime. In the calculation of the hours there will be, for this day, divergence for this employee, because the second appointment with function 01 will be left over.

  In this case, use this option by entering a two minute limit in the Limit of Markings would facilitate maintenance. Thus the system will consider only the first appointment, disregarding other clocking events with the same clock and function performed in the range of 18:00 to 18:02.

  Markings done:
  • 18:00 - Function 01 (marking considered for calculation as output).
  • 18:00 - Function 01 (marking scorned in the calculation).
  • 18:01 - Function 04 (marking considered for calculation as the start of overtime).
• "4 - Second Date, Time and Use of Marking": consider only the first marking performed in the period reported in the field Limit of Markings, taking into account the use of the marking in which the markings were made.
  Example:

  On 05/11/2017, when leaving the company at 12:00 o'clock the employee mistakenly passed the badge twice in different clocks and the same uses. Therefore, in the calculation of the hours there will be for this day, duplicate markings:

  In this case, using this option with a limit of two minutes in the field Limit of Markings facilitate maintenance. And the system will consider only the first marking:

  Mark at 12:00 - Use 2 - Point Marking

  Mark

  at 12:01 PM - Use 2 - Point Marking
  • When th
  Mark at 12:00 - Use 2 - Point Marking Marking at 12:01 pm - Use 18 - Paid Paid

Interval Between Tags Enter the number of minutes between 0 and 9, which must exist between the clocking events made by the developer.
Thus, if you enter 3 in this data, it means that between the markings made by the employee there should be an interval of three minutes. If, for example, this contributor mark 08:00, 08:01, 08:02 and 12:00, only the clocking events 08:00 and 12:00 will be accepted. The other two are ignored.

Limit of Markings Can be 0 to 9. Fill in this information only when the company imposes a limit on the amount of clocking events that the developer can perform on the day, if the developer exceed the limit, the excess clocking events s are ignored. If there are no limits, let this reset.

Consider Markings Permission Inform if markings without Permission should be considered in the counting.

Separation Day Normal Day Each marking read, the Time and Cafeteria Control performs a calculation to check that day belongs to clocking events . The result of this calculation is called the separation threshold. This data modifies the separation limit, adding or subtracting from this limit, the value reported. To use the Control point and Cafeteria, let this reset.

Example:

1. Calculate the separation limit of a time with the following markings: 08:00 - 12:00 - 13:00 - 18:00. In this case it verifies that from 18:00 a day (end of the day) until 08:00 hours the next day, there is an interval of 14 hours;

2. It is calculated half the interval between 18:00 and 08:00 hours which is 01:00 am;
3. Finally, add 100 minutes (value set by Point Control and Canteen) and we will limit 02:40 hours, ie, the markings beyond 02:40 hours will be considered for the next day. The given Separation Limit can be used to modify this limit.

So if you enter 01:00, the limit will be shifted to 03:40 hours (02:40 + 01:00 = 03:40), and the markings after 03:40 hours will be considered for the next day. If it is entered-01:00 the limit will be 01:40 hours (02:40-01:00 = 01:40).

If the time is 08:00 - 12:00 - 13:30 - 18:30, the divisor will be 01:15 hours, adding up to 100 minutes, you reach the limit of 02:55 hours. This value can be informed individually for each time. For this, see Tables> Schedules.

Discard Intermediate Meals Indicate whether intermediate markings, held during the meal hours, should be disregarded in the calculation. The clocking events will not be deleted but rather disregarded in the calculation.

Consider Pairs Normal Days Indicate whether the clocking events made on average days should be distributed in pairs or not.

Consider Pairs Days Off Indicate whether the clocking events made on days off must be distributed in pairs or not.

Use Direction for Allocation The direction is provided by the turnstiles, along with the date and time of the appointment, indicating if the clocking events is incoming or outgoing. The direction will facilitate the allocation and the automatic search of the schedule, because the system will know which is the Entry and what is the output of the day marking at the time of allocation.

To use the direction, the collectors must be properly configured for the Provider.

From this signaling will be enabled the column Direction in the grid of the Accounts screen, in Calculations> Calculation> Results> Contributors.

Example:

Screenshots

• The employee's schedule is from 6:00 a.m. to 10:20 p.m. and from 11:00 a.m. to 2:00 p.m.
• The mobile range is from 10:00 a.m. to 12:00 p.m.

The second marking will not be considered for the calculation, since it has use "4 - Point + Dining" and is outside the moving range.

The third marking, also with use "4 - Point + Dining", will be considered for calculation, since it is within the mobile range. Thus, meal times are not mandatory, so no marking is required for the calculation, nor for allocation.

Use Tag Regularization Please state whether to use the regularization routine for the origin of the marking.

The origin of the settlement is to be able to change the source of the screen marking of hits. Clocking events with origin "and" (electronics) and "G" (generated) cannot be changed. Only clocking events from "D" (Typed) can be changed to "R" (Regulated).

Allow Recording Unedged Tags Please inform if the changed markings on the hit can be recorded without being calculated.

Eliminate Clocking Events
Indicate how the system should eliminate the markups for employees who use the Delete Markup routine (field Delete Tags of the basic data sheet):

• "0 - Always Delete": considered in any calculation;
• "1 - Only in Reading": considered when the calculation is of type "0 - Reading";
• "2 - Recalculation only": considered for the calculations of type "1 - Recalculation" and "4 - Recalculating Calculation in days already changed";
• "3 - Only in the Accounts": considered for the calculations of the type Hit, Set by Rule and Move Markings;
• "4 - Reading and Recalculation": considered when the calculation is of type "0 - Reading", "1 - Recalculation" and "4 - Recalculating Calculation in days already changed";
• "5 - Reading": considered when the calculation is of the type "0 - Reading", considered for the Calculations of type Type, Set by Rule and Move Markings;
• "6 - Recalculation and Settlements": considered for calculations of type "1 - Recalculation" and "4 - Recalculate Calculation in days already altered"; considered for the Calculations of type Hit, Set by Rule and Move Markings.

Justify Digitized Tags Allows you to enable the routine to justify and comment the typed in setting the collaborator. If the field is empty, the routine will not be active.

When the check is "O - Optional" or "S - Yes", the fields in the Date Settings screen will be added: Justification, description and Note.

The justifications of typed markings are registered in Tables> Reasons> Justification of Markings. And on the screen of hits, the user just inform the code background and observation, if you must. Can only be justified with origin clocking events "D" (typed) and "R" (regulated). The goal is to inform the reason the clocking events was entered and no electronics or generated by the system.

Randomly Generated Tags Is to generate appointments with different hours every day. That is, if the base clocking events for 08:00, will be raised next this time and no clocking events every day at the same time. The clocking events are generated taking into account the tolerances Before and After reported in the register of the schedule.

Only random markings for Type "1 - Rigid" and "5 - Mobile Meal" will be generated, with uses 3 and 9 and With Tolerances Before and After with different time of the Base Time.

Consider Direction by Order of Tags Inform if is considered the order of markings:

• "S - Yes": automatically in the calculation the calculation will assign an Input and Output direction for the markings in the order in which they are presented on the date. This will only be executed when there is an even number of markings on the day and the time is non-mandatory at the meal;
• "N - No": no Input and Output direction will be adopted for the markings.

Example:

• Consider Direction by Order of Tags: Yes
• Registered hours for the employee: 07:00 10:00 10:15 13:15
• Markings made by the employee: 12:57 13:07
• Calculation: 00:10/03:41/Working 101 001 early departure/Late 04:57 103.

Report Enter a tax report template, from the 1510 concierge, which will be called on the hit date screen, button List.Portaria.

Programming / Removals

Schedule Overlaps Holiday Indicate whether a schedule of time or bridge exchange, performed on a holiday day, prevails over the same or not. If "S" is informed, the schedule time code will prevail, otherwise the time of day will be 9997 (Holiday).

Limit Days Allows you to enter the number of days retroactive to the current server date that the system users will have to perform the schedules. The system will not allow the difference between the current date and the starting time of the programming is greater than the value reported in this field.

Example:

• Date of the server: 10/20/2000
• Days Limit Retroactive Schedules: 03

In this case, the minimum date in which the user can register a programming is 10/17/2000. If he tries to include a 10/16/2000 day programming, the system will block.

Obligate Final Date in Schedules It allows to opt for mandatory end date in the schedules.

• "S - Yes": mandatory end date information for the schedules and the system will suggest the end date with the start date value. Its purpose is to prevent users from including scheduling of scale changes, compensations, request for overtime, request by cost center, projection of schedules, exchange of apportionment, warning or readiness, permissions, exchange of place, exchange of cost, no end date;
• "N - No": the schedules can be registered without end date.

Consider Time Projection Exchange Indicate whether the original time of day should be projected or whether the time schedule scheduling.

Consider Bridges for Projection
Indicate whether the original time of day should be projected or whether the time bridge programming.

Bridge Overlays Time Shift Indicate whether the bridge should prevail over the programming of Changing Hours, when both occur on the same day.

Example:

• The 02/11 is a holiday.
• On November 17 the time is 50.
• A bridge of the day 02/11 to 17/11 day.

With the bridge, the day 02/11 the developer would do 50 hours, and the last day 17/11 he would have the holiday. Except for the day 02/11 was made a trading schedule for daylight saving time 06.

Uses Request Overtime Report if Overtime Request routine is used. This routine is intended to control the programming for authorization of Overtime.

• "1 - No Uses": does not use Overtime Request routine. By selecting this option, the Programming without request will be disabled.

• "2 - By Center of Cost": the requests will be registered by Center of Cost. Selecting this option will enable, in Collaborators> Settings, the option "Request H. Extras", with two sub-menus:
  • R
  • equests by Cost Center
  Approvals

• "3 - Individual": the requests will be registered by Employee. Selecting this option will be enabled, in Collaborators> Settings, the option "Request H. Extras", with a sub-menu:
  • Requests by Employee
  Approvals

Programming without request
Inform if authorization schedules can be registered for overtime without having registered applications.

Displays T. Time in Manage Inform yourself if in the scheduling menu that is shown on the Manage Schedules screen, under Calculations> Calculation> Manage Schedules, you should show the option to "Schedule Change".

Automatic Recalculation in Schedules / Offsets Inform whether the automatic calculation recalculation routine will be used.

• "S - Yes": when registering a schedule or spacing, the system will ask if the user wants to recalculate the affected period;
• "N - No": The message will not be displayed and no recalculation will be performed.

Change Point Prior to Branch Transfer Lets you perform or not hits to the developer transferred between the start date of the period for calculation of the transfer and the date of transfer. This option only impacts to the new destination company / branch register).

Example:

Period of calculation: 12/16/2013 to 1/15/2014

Developer 10 transferred 1 company for the company on the day 1/6/2014 2.

• If the Change Point Prior to Branch Transfer is "S - Yes", it will be possible to make adjustments between 16/12/2013 to 06/01/2014 (in company 2);
• If the Change Point Prior to Branch Transfer is "N - No", it will only be possible to make correct results from 06/01/2014 (in company 2).

Calculate On Notice
Set whether the calculation of warnings will be performed natively through the calculation calculation.

Discounting Hours Worked on Warning Defines if hours worked should be discounted in programming report.

Screens

This guide will be visible to the user only if there are web instances of Point Control and Canteen defined in the system owner. If not, this tab will not appear on the screen.

Show all Employees not only Exceptions
Enter the Exceptions priority display option on the Accounts screen.

• "S - Yes": All employees will be shown, even if in the web version the option to display only employees with exceptions is selected. In the case of dates, the system continues to display only those with exceptions;
• "N - No": The web version will follow the display setting chosen in the Settings screen.

Uses Auxiliary Frame Whether or not the frame help on the hit screen.

• "S - Yes": in the settings screen of the Point Control and Web Cache, a new frame, for which any html file can be loaded via process rule 434. Also check the property Auxiliary Frame Height in this screen;
• "N - No": the frame and the hit screen will continue with its default appearance.

Auxiliary Frame Height
Set the height, in pixels, to the Frame Assist in the hit screen. If it is informed "0" will not be shown on the frame. This field will only be enabled if "S" is Uses Auxiliary Frame.

Height Frame Collaborators
Set the height, in pixels, of the employee grid in the Point Control and Web Cache settings screen. The default height for this grid is 140.

Color Electronic Marking
Set the color for the display of electronic tags, origin "E", listed in the calculation grid of the Spot Control and Web Cache hits screen. This property is not applied on the screen of hits at the time.

Color Marking Set the color for the display of the markings entered ("D" origin) listed in the score grid of the Point Control and Web Cache settings screen. This property is not applied on the screen of hits at the time.

Generated Marking Color
Set the color to display the generated markings, origin "G", listed in the score grid of the checkpoint hits of the Point Control and Web Cache. This property is not applied on the screen of hits at the time.

Color Marking Regularized
Set the color for the display of regularized markings, origin "R", listed in the check grid of the Spot Control and Web Cache hits screen. This property is not applied on the screen of hits at the time.

Hide Search Button Inform whether to hide fields from the Spot Control and Web Cache settings screen.

Rules

Rule Start Calculation Calculation
In this field you can enter the code of a rule that will be executed before the calculation is started and before the calculation rule is called. The DatIni and DatFim can be used to return, respectively, the initial and final dates that will be cleared. Unlike the Calculation rule, this rule will be executed only once before starting the calculation of calculation, and will not be performed when the calculation is made through the screen of hits.

Rule Top Contributor Calculation
This field can be informed the code of a rule that will be executed at the beginning of the calculation of each employee. The DatIni and DatFim can be used to return, respectively, the initial and final dates that will be cleared. In regulation, the records can be consulted directly with the command ' table. Field ', which is available R034FUN table fields for reading.

Rule Delete Tags Enter the rule code to handle the markings before the calculation calculation. This rule will be called whenever the calculation is carried out, including on the hits. The system will first call the rule of eliminating markings, after the daily calculation rule.

Example:

Delete point clocking events on certain occasions. To remove the clocking events can be used the following variables:

• MDatAc: Returns the date that the markup was performed.
• MHorAc: Returns the time the dial was made.
• MCdPlt: Returns the code of the site where the markup was performed.
• MCdRlg: returns the clock code in which the dialing was performed.
• MomMar: Returns the time when the markup was performed. The values are 1-before the schedule, 2-, 3-hours-after hours
• MSeqAc: Returns the marking sequence.
• MCdFnc: Returns the code for the markup function.
• MOriMa: Returns the origin of the tag.
• MIgnMa: variable used to indicate that a markup should be ignored during the calculation calculation. To be ignored, the value 1 must be assigned to the variable.

Determination Rule
Enter the code of the rule to be used for calculating the calculation, in the process of reading / calculation, recalculation and individual hits. The rules are registered in Resources> Rule Editor.

Rule After Write Calculation
Enter the rule code to use after writing the calculation. This rule is used to perform specific treatment tables, after the recording of the calculation. Because it is a generic rule, some system variables and scheduler functions that were available for other calculation rules, especially when working with data in memory during the calculation, should not be used in this rule, since in this case, after the calculation , they will no longer have the information available.

Use only when there is no other way to treat the information cleared by another rule already available, preferably use only ExecSql commands.

The rule will be executed in the following routines/fabrics:

1. Routine of calculation and recalculation of the calculation, after the end of the recording of the calculation of each employee;
2. Screen Hits on Date (FRACEDAT) after clicking on the Record, at each date;
3. Screen Justify Results (FRACEJAC), after clicking the Record, at each date;
4. Screen Results by Rule (FRACEREG), after clicking the Process, by employee;
5. Screen Settings - Enter Situations(FRACEDIG), after clicking the Record, at each date;
6. Screen Real Estate Management (FRMNTREF), after clicking the Record, to each employee;
7. In the web version of the system, for all dates selected in the grid Contributor Marks, by clicking the Record of the screen Related searches.

Rule Consistency of Accounts Enter the code of the rule to be used to consist of changes made by users to individual hits. The registration of the rules is done in the option> Rules Editor.

This rule respects the View All from the Miscellaneous screen> Markings> Point tab, to define whether the rule will be called only on changes in situations or also changes in markings.

The consistency rule is used to limit managerial success.

Example:

Certain users may only replace the fault situation with a justified or withdrawn situation.

Refectory Calculation Rule This field can be informed the code rule for calculating the cafeteria, if the company use. The reported rule will be valid for all the refectories of all companies. This rule is called after the calculation of daily calculation and after "Recording" in the maintenance of cafeteria (the rule is not called day by day, as it is called the rule of calculation).

The information on the employee's register and the period being calculated (DatIni and DatFim) will be available. Other information should be searched via cursors. In this rule you can normally use the ExecSQL function for any table.

Rule Overtime Approval This field aims to inform a rule to cancel the authorization of overtime at the time of the calculation of calculation. This rule will be called before the verification rule. To cancel the authorization of time is necessary to finalize the rule with the Cancel (1).

Rule Insert Tags Inform the code rule that will insert clocking events for the calculation of calculation. Markings entered by this rule will only be written to the database if usage 16 for the IMUsAc variable is reported. Otherwise, they are only stored in memory and considered for the calculation of calculation, not being shown on the windows of hits. To enter the markings, certain variables must be used for this rule.

Rule After Records Enter the code of the Rule that will be executed after the recording of a hit, in this rule only the Recalculation function can be used. The calculation will be executed is the same Dials move when the user writes the changes to this screen. In other words, the calculation is 1 type, without reallocating markings.

Till the last date, limited to the period end date of calculation selected. For further calculation already processed when there is, if the user has this need should be executed via web services, exclusively.

Rules G6

Employee Calculation Start Rule
Used to carry out a procedure before each employee is counted, being executed only once for each employee, even if they are checked for several days.

Determination Rule
Used to perform customizations in the calculation of standard hours of the system, being possible to modify the hours cleared by the system and also to create new situations.

Rule Consistency of Accounts
Used to make consistencies in the hits made by each employee, being executed whenever the correct answers are made and when recording them.

Rule After Write Calculation
Used to perform procedures at the end of the calculation. The rule is executed once for each employee, regardless of the number of days cleared.

Setting Process

Allows you to configure the parameters that interfere with the system set-up process.

Days to expire
Number of business days that the employee has to make hits. The calculation is done based on the date of calculation. After the pendency expires, it is automatically forwarded to the manager.

Limit days after point closure
Number of business days limit that the employee has to make hits after the end date of the calculation code. The deadline for each pending will not exceed this limit.

Blocks pending after expires
Indicates whether to block the pendency for the employee after it expires.

Allows to assume pendency of led
Indicates whether the manager can make an appointment on a pending day that is with the employee.

Lets you complete pending unpaid
Indicates whether the manager can complete pending unpaid.

Refer to the Point Management Manual for more information on calculation history.

Veja também:

• Screen settings to manage Schedules
• Situations of Verification