Bank definitions of Hours
In this screen are made some of the parameterizations that define the operation of the time bank. The settings made on this screen will be valid for all existing banks.
Closing the Week by Scale Inform if the closing of the week will occur on the day indicated in the field Closing of the Week or on the day of the DSR, as follows:
- "S - Yes":
- The closing of the week will always take place on the day of the DSR according to the employee's scale, including Scale Exchange, Changing Hours and bridge it's the Scale history. That is, when in the Periods tab of the time bank register is informed "S - Weekly" in the Credits or Debits columns, the compensation period will start from the first day with 9999 hours that is found, regardless of the day of the week in which it occurs;
- This option will also affect the week count for hour compensation when bank period records, the option "S - Weeks" is reported in the Credit Timeout or Debt Timeout columns. In this situation, the system will consider as a week the period between the day following the last DSR (day of the closing of the week) and DSR (next day with 9999 hours). For this reason, the weeks may be more or less than seven days, depending on the frequency with which the 9999 schedule occurs in the employee scale and also the schedules and histories that change the daytime code;
- The weeks count described above will also be performed in the hour bank overflow routine. That is to say, for the verification of the weekly limit of credits / debits, the system will consider as one week the period from the day after the DSR immediately preceding the date of launch and the next DSR (next day with time 9999) .
- This option should not be used when there are collaborators that have 6x2 scales (two consecutive DSR's);
- Using this option will cause loss of performance when you use the public transport.
- "N - No": the closing of the week will always occur on the day indicated in the field Closing of the Week.
Closing of the Week This field is set the day of the closing of the week for the Bank of hours. This markup is used by the system to calculate the clearing date of the postings when weekly credits / debits are used. The closing of the week may also be carried out according to the day of the DSR (see mark closing of the Week byScale).
Month closure Report when the closing of the month for the Bank of hours. This mark is used by the system to calculate the clearing date of the postings when monthly credits / debits are used.
Options:
- "A - Determination Period": the closing of the month will always occur at the end date of the calculation period;
- "F - Sheet Period": month closure will always occur on the end date of the calculation sheet period.
Check Limits Indicate how the verification of the hour limits from the bank.
The overflow checking is performed by the system to each release, i.e. the database overflow hours will be considered normally at the end of each period if you find any, even though, at the end of this period, the employee is not with overflow.
Example:
For a particular developer, have a period between 12/22/2014 and 1/20/2015 and the maximum of 40 credit hours.
From 22/12 to 27/12, this employee was 43 hours, that is, there was a three hour overflow at this bank until then.
After the day 27/12, the developer had several faults, coming to the end of the period (1/20/2015) with a balance of 04:00.
In this situation, the three hours that generated overflow on 27/12 will be integrated into the Personnel Administration module at the end of the period, even though at that moment it had a balance of 4:00.
The procedure for calculating the time for situation, this means that the order of the situation/influence compensation order under the result, when set to check limits the difference.
For maximum credit control, debits must be processed before credits. The same logic applies to debt control, where it is mandatory that the credits are processed before debits.
Example:
Bank hours with maximum daily credit of two hours.
The collaborator made 1:00 am missing and 4:00 extras on the day.
- Making the check by Difference: four credit hours minus one hour of debit = 03:00 => will be generated 1:00 am burst time.
Remembering that to the maximum daily control of credit, it is mandatory that the compensation order or the order of situation must first be debts and then credits.
Check Period Limits Indicate how the verification of the bank hour limits should be done when the separation of the hour bank closing is by period.
This field is displayed only if there is a time bank registered with the following parameters on the Bank of Hours screen (FR011BHR):
- Separation Closing in Periods = "Y - Yes";
- Maximum Credit in the Period = non-zero value;
- Maximum Debit in the Period = non-zero value.
Example:
Bank hours with maximum credit in the period of 20 hours.
The employee did 24 extra hours in the period and three hours left.
- Making the check by Difference: 24:00 credit less 03:00 debit = 21:00 => will be generated 01:00 overflow.
- Checking by Total: 24:00 credit => will be generated 4:00 pm overflow.
Important
When selecting the value "D - Difference (Credit - Debit)" in the fields Check Limits and Check Period Limits, the threshold overflow query may present a number of credits and debits greater than the limit registered in the time bank, since the overflow will be considered from the difference between the postings.
Releases (D) in the verification of Limits
Is typed on the screen releases database maintenance Hours to check the limits of Bank hours.
Launches (N) in the verification of Limits
Overdue debits are written in the calculation of the Integration (Bank of Hours screen) when checking the hours bank limits.
Example:
Maximum flow rate in period = 08:00
In a period it has 8:00 PM negatives
Gera - 08:00 to the bank
To calculate the verification with Annul Debts = 50% generates + 04:00 in the Bank.
Balance of the Bank of Hours = - 4:00 p.m.
If in the next competency generate in the calculation - 5:00, it will take to the Bank only - 4:00 am, totaling the - 08:00 of the limit and - 1:00 will lead to overflow.
Launches (B) in the verification of Limits
Is Allowance in the calculation of releases integration (database screen Hours) to check the limits of Bank hours.
Example:
Maximum credit period = 08:00
In a period it has 08:00 positive
Generates + 08:00 for the bank
When calculating the calculation with Advance Subscription = S and 50% generate - 04:00 in the bank.
Bank balance of Hours = + 04:00
If in the next skill to generate in the score +5: 00, it will lead to the Bank only +4: 00, totaling the +8: 00 limit and +1: 00 will lead to overflow.
Releases (G) in the verification of Limits
Consists of Items Generation to check the limits of Bank hours. The launch of type "G" is always generated on the last date of the bank period.
Example:
When calculating the integration at the end of the period, it will generate Source Release "G".
If, after the generation of events, there are more Originals "A" releases, the system will also consider Source "G".
Without this signaling, the system will only consider "A" origin.
Postings (R) in the verification of Limits
Consist of launching uploaded by Rule to check the limits of Bank hours. That is, with a rule it will generate event with Source Release = "R" and will check.
Type Compensation
Inform how the offsetting of the time bank entries should be made.
Options:
- "1 - Day / Situation": the compensation will be made respecting the chronological order in which the launches occurred. The order informed for the situations, defined in the Situations of the bank's registration screen, will only be considered when same-day postings occur.
- "2 - Period / Situation / Day": the compensation will be made in a differentiated way. When the launches that will compensate for another existing launch different calculations occur, he shall be deemed to be the chronological order. However, when these releases occur in the same calculation, compensation will be made based on the order of the situation.
Check out Examples of Types of Compensation.
Moment Compensation
To inform in which routine of the module Control of Point and Canteen will be made the compensation of the launches of the bank of hours.
Options:
- "1 - Calculation of Calculation": standard treatment, where compensation is made during calculation calculation;
- "2 - Calculation of Integration": will do the compensation when calculating the integration. Then the entries in the R011LAN table will appear without compensation made.
If there is a change of option 2 - Calculation of Integration to 1 - Calculation of Calculation, it is necessary that the user perform the recalculation of the bank of hours and period will always be discounted in the integration.
Note
This parameter was added to avoid problems with the performance of the verification. This occurs because of the compensation order period, forcing the system to undo and redo all the compensation period each day, for a release at the end of the month may have priority in compensation that had been held by another release in the beginning of the month.
If the compensation is made in the calculation of integration, the same will be performed only once, without repeating the process unnecessarily.
The downside to the compensation in the calculation of integration is not having, during the month, the updated information of how many hours of each release have already been taken care of, but this information is only used by the system for the calculation of integration and in some reports of Bank of hours. For the calculation of integration there are no problems, but the reports may not work. It is therefore necessary to make a choice between being able to use the reports and have a better performance of the verification.
If there is any process that reads the field R011LAN.QtdPag (amount of hours already paid from the launch) or table R011ASS (compensation of the postings), it will not be possible to opt for offsetting the hours in the integration calculation.
To opt for compensation in the calculation of integration, the user can access the database maintenance screen for hours without problems, because the releases are displayed on this screen regardless of the compensation.
Generate Credit Integration Discharged
Indicate whether, to laid-off employees, the net profit of the Bank must be paid on incorporation.
This assignment is valid only for positive hours due subsequent to the period in which the employee was fired. The hours that expire within this period will always be paid on integration.
Generate Debit Integration Discharged
Indicate whether, to employees laid off, the negative balance of the Bank should be discounted in the integration.
This assignment is valid only for the time due adverse after the period in which the employee was fired. The hours that expire within this period will always be discounted on integration.
Veja também:
English
Español
