PYFG - PY220C

Code Category: PYFG
Code Value: PY220C
Short Description: "DEBUG" for debug information (BusinessPLUS only).
Medium Description: Not required.
Long Description: Not required.
Associated Numeric Values
1: If a date range is used which straddles a periods beg / end dates, the user may choose a constant percentage instead of days worked in that range divided by days worked in the period. Enter that percent here (optional).
2: The hour number to be used in the timecard batch, in which the retro payment is attached. This hour must be defined in the hour definition screen (PYUPHH).
3: The misc. code box number on the hour definition or contribution definition screen which contains the hour number of the hour to map this hour to. See Assoc. Code 1 below.
4-5: Reserved for future use.
Associated Codes
1: "DETAIL-PAY" causes either the original hour codes, or mapped hour codes to be used in the timecard batch. If associated value 3 is 0, the original hour codes will be used. Otherwise, the hour number in the misc. code box given in assoc. value 3 above is used.
2: "NO-RETRO-RPT" causes no report to be printed.
3: "NO-WARN-RP" causes no warning report to be printed.
4: "NO-WARNINGS" causes warnings to be suppressed.
5: The values "USE-HISTORY" AND "USE-TIMECARD" control retroactive pay calculations. (If nothing is specified, "USE-TIMECARD" is the default.)
If "USE- HISTORY" is specified, history information will always be used for retroactive pay calculations. If a period could potentially be split as may happen when the operator selects "Date Range" in answer to the runtime question-"How would you like to select the periods?" the process will proportion out the history information based on the employee's calendar.
If "USE-TIMECARD" is specified, system timecards will be used for retroactive pay but only when the operator selects "Date Range" in answer to the runtime question-"How would you like to select the periods?" In all other cases, history will be used for the calculations even though the common code setting is "USE-TIMECARD." This makes sense-History information is generally more accurate as it includes hand checks, etc., that are not part of system timecards. Therefore, the process always tries to use history. It is only when a period could potentially be split that system timecards are used instead of his
Associated Descriptions
1-5: Reserved for future use.