This page (revision-25) was last changed on 26-Nov-2021 10:22 by jmyers

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
25 26-Nov-2021 10:22 4 KB jmyers to previous
24 26-Nov-2021 10:22 4 KB JMyers to previous | to last
23 26-Nov-2021 10:22 5 KB RForbes to previous | to last
22 26-Nov-2021 10:22 5 KB RForbes to previous | to last SC_VARIABLE ==> $C_VARIABLE
21 26-Nov-2021 10:22 5 KB JMyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 6 changed one line
For example, the string “BIWEEKLY” could represent a Processing Frequency, a database item such as a Group Code or even another [User Calc|USERCALC].
For example, the string “BIWEEKLY” could represent a Processing Frequency, a database item such as a Group Code or even another UserCalc.
At line 8 changed one line
Operand Types declare what value the operand will have, and how to process it within the User Calc.
Operand Types declare what value the Operand will have, and how to process it within the UserCalc
At line 10 added one line
At line 11 changed one line
Variable Operand Types commonly begin with a $ sign, this denotes a variable that holds its value beyond the life of the current [User Calc]. The only exception to this is the ‘V’ sign that begins a Local Variable that is only available for reference during the life of the User Calc.
Variable Operand Types commonly begin with a $ sign, this denotes a variable that holds its value beyond the life of the current [UserCalc]. The only exception to this is the ‘V’ sign that begins a Local Variable that is only available for reference during the life of the UserCalc.
At line 15 changed one line
*[$C - User Variable|$C_VARIABLE], User Variables ([IMVR])
*[SC - User Variable|SC_VARIABLE], User Variables ([IMVR])
At line 35 changed one line
Database Operand Types are Database fields, Wage Basis, User Calc Calculation types, and User Calc Function/Qualification types.
Database Operand Types are Database fields, Wage Basis, UserCalc Calculation types, and UserCalc Function/Qualification types.
At line 38 changed 2 lines
*[UC - User Calc Calculation|UC_DATABASE]
*[UF - User Calc Function/Qualifier|UF_DATABASE]
*[UC - UserCalc Calculation|UC_DATABASE]
*[UF - UserCalc Function/Qualifier|UF_DATABASE]
At line 53 removed one line
* To Calendar Date
At line 63 removed 2 lines
*[CE - Element to Calendar Date|CE_ELEMENT]
*[CL - Calendar|CL_ELEMENT] used by CE, above
At line 68 changed one line
There are eight [pay components|PAY COMPONENTS] values available
There are eight [Pay Components|PAY COMPONENTS] values available
At line 81 changed one line
*[SN - Sundry "Life to Date|SN_PAY_COMPONENT]
At line 85 changed one line
Statistics are similar to pay components; they hold payroll amounts by employee. However, statistics allow different capabilities. Statistics are used to hold information for each employee that is not easily accessed with pay components.
Statistics are similar to pay components - they hold payroll amounts by employee. However, statistics allow different capabilities. Statistics are used to hold information for each employee that is not easily accessed with pay components.
At line 87 changed one line
For example, the YTD or MTD value of the Gross Earnings pay component may be referenced, but if there is a need to know the YTD value of Gross Earnings from last year or two years previous, that value is not readily available. A statistic may be used to hold that value until needed.
For example, the YTD or MTD value of the Gross Earnings pay component may be referenced, but if there is a need to know the YTD value of Gross Earnings from last year or 2 years previous, that value is not readily available. A statistic may be used to hold that value until needed.
At line 89 changed one line
%%information It is important to note that while statistical values may be read and used by User Calcs, they may not be modified as they are Database items. (Database items may not be updated by User Calcs).%%
%%information It is important to note that while statistical values may be read and used by UserCalcs, they may not be modified as they are Database items. (Database items may not be updated by UserCalcs).%%
At line 91 changed one line
If the value of a statistic is to be modified with a User Calc, you must update the current value of the pay component that is linked to the statistic.
If the value of a statistic is to be modified with a UserCalc, you must update the current value of the pay component that is linked to the statistic.
At line 106 removed one line
*[LEX - Obtain "Displayed Value" for a lexicon|LEX_WORKFLOW]
At line 105 added one line
[CLEANUP]
At line 107 added 3 lines
[{If var='loginstatus' contains 'authenticated'
At line 110 changed 2 lines
![Notes|Edit:Internal.UC+OPERAND+TYPES]
[{InsertPage page='Internal.UC+OPERAND+TYPES' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.UC+OPERAND+TYPES]
[{InsertPage page='Internal.UC+OPERAND+TYPES' default='Click to create a new discussion page'}]
}]