PYFG - PY200C

Payroll Calculation
Code Category: PYFG
Code Value: PY200C
Short Description: Entering "DEBUG" in this field will cause information regarding payroll calculation (History record information, CDH assignment, and calculation) to be displayed on the screen. Entering "DEBUG2" in this field will cause pay assignment and Pay String spreading information to be displayed on the screen. Entering "DEBUG3" will cause the calendar and schedule information to be displayed on the screen. This is for BusinessPLUS diagnostic use ONLY.
Medium Description: POS WITH ID - PY200 will look for job / position entries that have been tagged with the ID for the employee being calculated. This is for use with the patch by position functionality when the same position may need to be associated with different calendars depending on the employee. Using this common code value implies that positions are entered with IDs on the job / position screen.ALLOW MULTIPLE FORCE CALCS - This option provides the capability to run multiple, simultaneous payroll force calcs (PYPAFC). Caution-It is important that each employee be included in only one force calc list at a time. The user must make very careful use of selection criteria to separate employees into distinct lists when running under this option. Employees who happen to be in multiple lists at the same time may yield erroneous values.
Long Description: Enter the ID of the employee to debug.
Associated Numeric Values
1: Enter the dollar amount desired at which the system will warn when adjustments are made above this level.
2: Numeric value (2) controls which Special Code on the employee CDH assignment determines the dynamic priority for calculation.
3: This value represents the number of days in an outside date range prior to the period begin date that are allowable and included in the calculation by py200. This value will only come into play when PY-GEN-MSTR process switch 29 (Allow Outside Dates) is set to "Y." For example, if the value is "130," the program will permit outside dates that are between 130 days prior to the period begin date up to the period begin date. If this value is not specified and the Allow Outside Dates switch is set, the program uses a default value of 180 days.
4: Dates Option. Allows the user to specify the date range that applies for each pay assignment. The date range is important in identifying the default pay assignment to use when a given timecard date is entered. For all settings, if a date is blank, the effective date is used instead. If effective dates are blank, the begin date is set to "00000000" and the end date is set to "20501231." Set to zero (will appear blank) to use the default Effective Begin / End dates.
Set to 1.00000 to use the Patch Begin / End dates.
Set to 2.00000 to use the Retro Date as the begin date and Effective End date.
Set to 3.00000 to use the Retro Date as the begin date; otherwise, same as Option #1.
Set to 4.00000 to use the Paid Begin / End dates.
5: Reserved for future use.
Associated Codes
1: One method for troubleshooting problems in a Contribution, Deduction, or Hour calculation code is to use the WARN statement. If the variable NVAR0 is used in a calculation code and the user wants to know what value has been assigned at a certain point in the calculation code, the user would inset a line in the calculation code, such as-
WARN ("NVAR0",NVAR0)
This causes the value of NVAR0 to be printed in the temporary file WARN200. By entering "SHOWWARNS" in "Codes (1)" field, the value of NVAR0 will be displayed on the screen, as well as, printed in the WARN200 file.
Set Code 1 to "NO HIRE WARN" to turn off hire date warnings.
2: "PYPD-PCT-OVR" activates a setting to alter the standard spreading logic for Spread-by-Effort. For Spread-by-Effort where the PYPD-PERCENT is zero (no paid days on the calendar schedule for this Pay Line), the PYPD-PERCENT is changed to 1.0000. Spreading to this line will then be based on a full share of the effort against the CDH amount.
3: Entering "LIMITOVR" in this field directs the system to check amounts from overridden history entries against the Limit field on the CDH ASSIGNMENT screen (PYUPEC, PYUPED, or PYUPEH). If the limit is exceeded then the limit is substituted for the amount of the CDH.
Entering "ALL DAILY" indicates that all timecards will be entered on the Daily PAYROLL TIMECARD ENTRY screens.
Entering "ALL DAILY" sets all employees to process in daily timecards; all timecards will be entered on the daily timecard entry screens. Daily patching is inactivated.
Entering "ALL PATCH" is the same as entering "ALL DAILY," but daily patching will also occur for all employees. The daily patch hour will split across all pay assignments for the employee.
Entering "PATCH BY PAY" is the same as entering "ALL PATCH," except the daily patch hour will split only across pay assignments whose pay class contains the daily patch hour.
4: Entering "SPLIT RATE" indicates that hours may be paid at multiple rates if a mid-period rate change has occurred.
5: Reserved for future use.
Associated Descriptions
1: Description 1 can be set to "USE OVERRIDE OT RATE" which causes py200 to use the OT rate found on the actual "O" pay assignment rather than following the rules in PYFG / PYRATE common code.
Set this description to "DON'T CHECK EMPL CALENDAR" to bypass certain employee calendar error checking, specifically the checks for 1) no paid days in the calendar for the period, 2) no paid hours in the calendar for the period, and 3) no paid days for the employee for the period are bypassed. This calendar option is primarily for users that input all hours via daily timecards and do not do any patching, spreading, etc.
2: Description 2 can be set in the following ways:
FLSA DATE PERIOD END - place per end date on cnt / ded amts
FLSA DATE PERIOD BEGIN - place per beg date on cnt / ded amts
FLSA DATE ACROSS PERIOD - spread amt across paid days in per.
PRORATE PATCH - will prorate the number of hours patched from the calendar by FTE on PYUPEM.
This setting is used to set dates for cnt / ded amounts which occur in previous paid histories and are now being considered as part of FLSA calculations. See switch 26 in entity definition process switches for a fuller description.
3: This is designed for fire-fighter types of pay situations. Enter "NEGATIVE PATCH OK" to direct the system to patch negative value for hours when computing the number of hours to be patched, if necessary. This is useful if more hours have been entered in timecard than the system would normally patch. When "NEGATIVE PATCH OK" appears in this field, the system will patch negative hour amounts to arrive at the number of hours derived from the CALENDAR DEFINITION.
For example, if an employee is on an 80-hour calendar and takes 96 hours of vacation, if "NEGATIVE PATCH OK" appears in this field, the system will patch - 16 hours of vacation so that the employee receives 80 hours' worth of pay.
4: Can be set to DAILY TC WRITEBACK, PER BEGIN or DAILY TC WRITEBACK, PER END and controls the date used for certain system timecard entries or other Force Calc calculations when the actual date is unclear or ambiguous. For examples, as a function of this setting:

Accumulated round-off error between pay history and system timecards will be posted to the period begin or period end date.
FLSA calculations for undated items like contributions will be posted to the period begin or end date.
Manually entered hand-checks will be posted to the period begin or end date.

5: Reserved for future use.