Deduction Definition - PYUPDD

Three pages are used to define the various contributions, deductions, and hours (CDH) that may be assigned to any given employee. To define contributions, use the Payroll (PY) Contribution Definition (PYUPCC) page; for deductions use the Payroll (PY) Deduction Definition (PYUPDD) page; and for hours use the Payroll (PY) Hour Definition (PYUPHH) page. Although these three pages are very similar, there are important differences in the Process Switches tab settings – Process Switches are unique between Contributions, Deductions, and Hours.

After defining contributions, deductions, and hours, the Payroll (PY) Employee CDH Assignment (PYUPEC) pages are used to assign the definitions to employees. Note: These pages are populated from Human Resources (HR) module.

The top portion of this page is the master definition record. A master record is an entry with a unique number. The tabs in the lower portion of the page are used to record the detail. The user may have multiple detail entries with the same number but different characteristics. For example, different rates associated with various beginning and ending dates.

Main Window

No: Enter four digits (0001-9999) to uniquely identify the contribution, deduction, or hour being defined. The system automatically groups contributions, deductions, and hours by adding a lead 1, 2, or 3 (respectively) to the number entered. Thus, all contributions are designated by 1###, deductions by 2###, and hours by 3### (where ### is the three-digit code entered in this field).

Code: Enter up to eight characters that describe the contribution, deduction, or hour (for example, FIT, FICA). This code is used on a number of reports and pages for identification.

Title: Enter up to 20 characters as the title of the contribution, deduction, or hour (for example, Federal Income Tax, Social Security).

XTD: The system default for this field is set to Y. A Y in this field causes the system to store to-date accumulators for each employee assigned this contribution, deduction, or hour. These to-date amounts are kept on an inception-to-date, fiscal year-to-date, calendar year-to-date, tax year-to-date, and period-to-date basis. Selecting <none> will turn the accumulators off.

CDH Detail Information

Main Information

Details

Begin/End Dates: Enter the first and last date for which this contribution, deduction, or hour is to be considered active. Enter the date in MM/DD/YY or MM/DD/YYYY format. The begin date must be less than or equal to the end date. An end date must be entered if a begin date is specified. If the definition is always active, leave this field blank. The fields accept year values up to 2099. 

Status: A code representing the status of the definition. The following is a list of codes supported by the system:  A= Active,  I = Inactive.

Priority: Up to four characters indicating the priority of the definition in the payroll calculation process. For example, this field is used to ensure that regular hours are paid and tax deferred deductions are taken before FIT is calculated. Blanks have precedence over digits (0 being high, 9 being low). Digits have precedence over characters (A being high, Z being low). Entries with a leading blank have a higher precedence than entries with a trailing blank (in other words, <blank>A has a higher precedence than A<blank>). This priority may be overridden on an employee-by-employee basis. This is accomplished by placing a Y in switch 23 in page three (3) of the CDH definition.
Typical priority ranges are:

Freq: A two-character code representing the frequency with which the assignment record is to be taken into consideration. This field may be used in conjunction with the Bx field.
The following is a list of codes supported by the system:
Freq = XX and Box = ##, where XX is a frequency match code (Fq) in the frequency match code box number (##) on the PY Pay Period Definition (PYUPPR) page.

• Freq = A (Active for every pay period)Box = blank

• Freq = A# (where # is a value between 1 and 9, as previously defined on the PY Pay Period Definition page, representing the period sequence in which this record should be considered active)Box = blank

• Freq = I# (where # is a value between 1 and 9, as previously defined on the PY Pay Period Definition page, representing the period sequence in which the record should be considered inactive)Box = blank

Box: A two-character code representing the frequency match code box number on the Pay Period Definition record. This field is used in conjunction with the Freq field.  The record will be considered active when the period being processed contains the same frequency match code (Freq) in the box number specified (Box). If Box contains 00, the system will search all boxes numbered 1 through 10 to find the frequency match code. Box = ## and Freq = XX, where ## identifies the number of the frequency match code box on the Pay Period Definition page, and XX is a frequency match code as defined on the Pay Period Definition page.

Pay Base: A two-digit number (1- 42) representing one of the 42 possible Pay Bases used as an input value for the definition's computation. Pay Bases are used to reference stored, running balances (accumulators) of pay amounts. If a definition is to be based on the result of a series of previously processed definitions, the number of the Pay Base storing the desired balance should be input here. This ensures that the value will be pre-loaded and will not have to be specifically loaded (using the LOAD statement) at the beginning of the calculation formula. For example, the FIT deduction is typically calculated after processing an employee's pay, any tax deferred deductions, and taxable contributions that have been defined. While some calculations are based on gross pay, FIT needs to be based on the 3 - FIT Pay pay base that typically contains gross pay minus any tax deferred pay and taxable contributions. For this reason, the number 3 would be input for the FIT deduction definition.
This field (in conjunction with the Hour Base field) also controls how the dollars/hours associated with this definition will be spread, if an employee has multiple pay assignments. Dollars/hours for this CDH will be spread across pay assignments according to the relative percentages of the values in each pay assignment's Pay Base specified in this field. For example, if this field contains a 6 (individual Pay Base 6 - FICA), the dollars for the CDH will be spread across pay assignments in the same ratio as FICA taxable dollars have been accumulated.
This field and the Hour Base field, as mentioned above, work in conjunction as follows:

• If both fields are blank, contribution and deduction definitions will spread according to Pay Base #1; hour definitions will spread according to hour base #1.

• If both fields are specified, contribution and deduction definitions will spread according to Pay Base specified in the Pay Base field; hour definitions will spread according to the hour base specified in the Hour Base field.

• If only one field contains a value, all CDHs will spread according to Pay Base/Hour Base specified in the Pay Base/Hour Base fields, respectively.

Exceptions:

• If there are no entries in the Pay Base and Hour Base fields, hours defined as accrual-type hours (an A in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page.

• If the ACCRs To PM Only field on the PY Entity Definition page contains a Y, hours defined as accrual-type hours (an A in the hour type field on the PY Hour Definition page) will spread only to the primary pay assigned regardless of entries in the Pay Base and Hour Base fields.

• Hours defined as patch-type hours (a P in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page, not on the entries in the Pay Base and Hour Base fields. However, if the Spread by Pay Base/Hour Base field on the PY Hour Definition page contains a Y, the hour will spread based on the entries in the Pay Base and Hour Base fields even though the hour is a patch-type hour.

• Hours defined as patch-type hours (a P in the hour type field on the PY Hour Definition page) will spread only to pay assignments that have the same Pay Class as the class that owns the patch hour. For example, if John Smith is assigned a patch-type hour because he belongs to Pay Class 200, that patch hour will only spread to pay assignments that indicate class 200 in the Pay String.

Hour Base: Two-digit number (1 - 42) representing one of the 42 possible Hour Bases used as the input value in the definition's computation. Hour bases are used to reference running balances (accumulation of hours worked, accrued, or taken). If a definition is to be based on the result of previously processed definitions along with the number of hours worked, accrued, or taken, the desired hour base number should be input here. This ensures that the value will be pre-loaded and will not have to be specifically loaded (using the LOAD statement) at the beginning of the calculation for. For example, certain retirement plans are based on the number of hours actually paid. Only hours paid at a regular rate are to be included. For this type of deduction, the number 2 would be input to access the hour base that stores number of hours paid at the regular rate.
This field (in conjunction with the Pay Base field) also controls how the dollars/hours associated with this definition will be spread, if an employee has multiple pay assignments. Dollars for this CDH will be spread across pay assignments according to the relative percentages of the values in each pay assignment's hour base specified in this field. For example, if this field contains a 2 (indicating hour base 2 - REG), the hours for the CDH will be spread across pay assignments in the same ratio as Regular hours have been accumulated.
This field and the Pay Base field, as mentioned above, work in conjunction as follows:

• If both fields are blank, contribution and deduction definitions will spread according to Pay Base #1; hour definitions will spread according to hour base #1.

• If both fields are specified, contribution and deduction definitions will spread according to Pay Base specified in the Pay Base field; hour definitions will spread according to hour base specified in the Hour Base field.

• If only one field contains a value, all CDHs will spread according to Pay Base/Hour Base specified in the Pay Base/Hour Base fields, respectively.

Exceptions:

• If there are no entries in the Pay Base and Hour Base fields, hours defined as accrual-type hours (an A in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page.

• If the ACCRs To PM Only field on the PY Entity Definition page contains a Y, hours defined as accrual-type hours (an A in the Hour Type field on the PY Hour Definition page) will spread only to the primary pay assignment regardless of entries in the Pay Base and Hour Base fields.

• Hours defined as patch-type hours (a P in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page, not on the entries in the Pay Base and Hour Base fields. However, if the Spread by Pay Base/Hour Base field on the PY Hour Definition page contains a Y, the hour will spread based on the entries in the Pay Base and Hour Base fields even though the hour is a patch-type hour.

• Hours defined as patch-type hours (a P in the Hour Type field on the PY Hour Definition page) will spread only to pay assignments that have the same Pay Class as the class that owns the patch hour. For example, if John Smith is assigned a patch-type hour because he belongs to Pay Class 200, that patch hour will only spread to pay assignments that indicate class 200 in the Pay String.

GL Dr/Cr Object: Up to eight characters containing the General Ledger object code to be debited and credited. This object code is referenced in the General Ledger Subsystem Interface Utility (GLUTSPSI) utility for pay postings to the General Ledger. Enter !UNIT in the object fields to cause the value found in the unit field of the employee definition to be used as the object code. Entering NOPOST results in no posting to the General Ledger.

JL Dr/Cr Object: Up to eight characters containing the Journal Ledger object code to be debited and credited. This object code is referenced in the General Ledger Subsystem Interface Utility for pay postings to the Journal Ledger. Entering NOPOST results in no posting to the Journal Ledger.

Special Information

Value/Description 01-10: These fields are for various uses. For example, the FICA deduction uses these fields to specify the rate and maximums to be used when calculating the FICA deduction. A health deduction may use these fields to define a table of rates for determining the deduction amount for an employee. Refer to the Calc Codes page for more information about calculations. Up to 10 values and their descriptions (numbered 1 - 10) may be associated with a given detail entry. The values may be up to 12 digits (11 digits for negative numbers), including five places to the right of the decimal point. The descriptions may be up to 20 characters describing the associated value. The specific uses of the values are dependent upon the particular definition and how the value is being referenced in the contribution, deduction, or hour calculation. 

Hour Bases

Hour Base Flags: The specific options displayed on this tab depend on your system setup. Hour Bases are used to reference running balances (accumulation of hours worked, accrued, or taken). If a definition is to be based on the result of previously processed definitions along with the number of hours worked, accrued, or taken, the desired Hour Base number should be input here. This ensures that the value will be pre-loaded and will not have to be specifically loaded (using the LOAD statement) at the beginning of the calculation. For example, certain retirement plans are based on the number of hours actually paid. Only hours paid at a regular rate are to be included. For this type of deduction, the number 2 would be input to access the Hour Base that stores number of hours paid at the regular rate.
This field (in conjunction with the Pay Base field) also controls how the dollars/hours associated with this definition will be spread, if an employee has multiple pay assignments. Dollars for this CDH will be spread across pay assignments according to the relative percentages of the values in each pay assignment's Hour Base specified in this field. For example, if this field contains a 2 (indicating Hour Base 2 - REG), the hours for the CDH will be spread across pay assignments in the same ratio as regular hours have been accumulated.
This field and the Pay Base field, as mentioned above, work in conjunction as follows:

• If both fields are blank, contribution and deduction definitions will spread according to Pay Base #1; hour definitions will spread according to Hour Base #1.

• If both fields are specified, contribution and deduction definitions will spread according to Pay Base specified in the Pay Base field; hour definitions will spread according to Hour Base specified in the Hour Base field.

• If only one field contains a value, all CDHs will spread according to Pay Base/Hour Base specified in the Pay Base/Hour Base fields, respectively.

Exceptions:

• If there are no entries in the Pay Base and Hour Base fields, hours defined as accrual-type hours (an A in the Hour Type field on the Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment (PYUPEP) page.

• If the ACCRs To PM Only field on the Entity Definition page contains a Y, hours defined as accrual-type hours (an A in the Hour Type field on the Hour Definition page) will spread only to the primary pay assigned regardless of entries in the Pay Base and Hour Base fields.

• Hours defined as patch-type hours (a P in the Hour Type field on the Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page, not on the entries in the Pay Base and Hour Base fields. However, if the spread by Pay Base/Hour Base field on the Hour Definition page contains a Y, the hour will spread based on the entries in the Pay Base and Hour Base fields even though the hour is a patch-type hour.

• Hours defined as patch-type hours (a P in the Hour Type field on the Hour Definition page) will spread only to pay assignments that have the same Pay Class as the class that owns the patch hour. For example, if John Smith is assigned a patch-type hour because he belongs to Pay Class 200, that patch hour will only spread to pay assignments that indicate class 200 in the Pay String.

Pay Bases

Pay Base Flags: The specific options displayed on this tab depend on your system setup. Pay Bases are used to reference stored, running balances (accumulators) of pay amounts. If a definition is to be based on the result of a series of previously processed definitions, the number of the Pay Base storing the desired balance should be input here. This ensures that the value will be pre-loaded and will not have to be specifically loaded (using the LOAD statement) at the beginning of the calculation formula. For example, the FIT deduction is typically calculated after processing an employee's pay, any tax deferred deductions, and taxable contributions that have been defined. While some calculations are based on gross pay, FIT needs to be based on the 3 - FIT Pay pay base that typically contains gross pay minus any tax deferred pay and taxable contributions. For this reason, the number 3 would be input for the FIT deduction definition.
This field (in conjunction with the Hour Base field) also controls how the dollars/hours associated with this definition will be spread, if an employee has multiple pay assignments. Dollars/hours for this CDH will be spread across pay assignments according to the relative percentages of the values in each pay assignment's Pay Base specified in this field. For example, if this field contains a 6 (Pay Base 6 - FICA), the dollars for the CDH will be spread across pay assignments in the same ratio as FICA taxable dollars have been accumulated.
This field and the Hour Base field, as mentioned above, work in conjunction as follows:

• If both fields are blank, contribution and deduction definitions will spread according to Pay Base #1; hour definitions will spread according to Hour Base #1.

• If both fields are specified, contribution and deduction definitions will spread according to Pay Base specified in the Pay Base field; hour definitions will spread according to Hour Base specified in the Hour Base field.

• If only one field contains a value, all CDHs will spread according to Pay Base/Hour Base specified in the Pay Base/Hour Base fields, respectively.

Exceptions:

• If there are no entries in the Pay Base and Hour Base fields, hours defined as accrual-type hours (an A in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page.

• If the ACCRs To PM Only field on the PY Entity Definition page contains a Y, hours defined as accrual-type hours (an A in the Hour Type field on the PY Hour Definition page) will spread only to the primary pay assigned regardless of entries in the Pay Base and Hour Base fields.

• Hours defined as patch-type hours (a P in the Hour Type field on the PY Hour Definition page) will spread according to the values in the Effort fields on the PY Employee Pay Assignment page, not on the entries in the Pay Base and Hour Base fields. However, if the spread by Pay Base/Hour Base field on the PY Hour Definition page contains a Y, the hour will spread based on the entries in the Pay Base and Hour Base fields even though the hour is a patch-type hour.

• Hours defined as patch-type hours (a P in the Hour Type field on the PY Hour Definition page) will spread only to pay assignments that have the same Pay Class as the class that owns the patch hour. For example, if John Smith is assigned a patch-type hour because he belongs to Pay Class 200, that patch hour will only spread to pay assignments that indicate class 200 in the Pay String.

Process Switches

The deduction process switches are used to define special conditions to be considered when processing a given contribution. The specific options displayed on this tab depend on your system setup.

01: Track Arrears

• Y = Track Arrears in the normal fashion; automatically recover arrearage in subsequent payrolls and post amounts to the GL.

• R = Track Arrears and create billing entries in AR rather than automatically recover in subsequent payrolls.

• A = Track Arrears for auditing purposes only; no GL postings and no automatic recovery of arrearage. These audit transactions will be marked as AU in the Arrears Type code. They will not be accumulated into the normal Arrears Balance, which is used in the automatic recovery mechanism. They will be visible on the Payroll (PY) Arrears Tracking (PYUPAT) page and will be included on the standard report (PYREFLAR).

02-03: Reserved for future use.

04: Anniversary XTD Enter Y in this field if the calendar year-to-date value in the accumulator record is to be substituted by the anniversary year-to-date value.

05: Pay Base Control (Crtl) Enter Y in this field to indicate that this deduction must be assigned to an employee for the associated Pay Base to be accumulated. For example, if this were the FIT deduction and this field is left blank, the system would accumulate taxable FIT wages based on employees' earnings regardless of whether or not there was withholding. By entering Y in this field, the system will only accumulate taxable FIT wages if this deduction is expressly assigned to the employee. This allows the user to treat earnings as non-taxable for certain employees.
Pay bases accumulate based on the +, - on the Pay Base tab of a CDH definition. Pay Base control means that we can turn on/off this control when dollars are accumulated into a given pay base. Originally the presence of a contribution assignment in the proper date range would turn on accumulation for controlled pay bases. It is now possible to control a pay base by the presence of a contribution/deduction in the history record. Thus, if a pay base is subject to history driven control, the presence of a controlling CDH in history turns on accumulation for that time frame.
The pay base number that appears on the Main tab of the definition is the base which will be controlled. A blank in switch 5 means no control, a Y or A means control by assignment, and an H means control by history. A pay base may be controlled by several different contributions, though it is usually recommended to use as few as possible (one is ideal). Control must be either by assignment or history. There will also be a warning if control is set but no pay base number appears on the Main tab.

06: Bond Type Enter Y in this field to indicate that a regular deduction will be taken each Pay Period and set aside for purchasing bonds. If this field contains a Y, the Bond Balance report will be printed when payroll is processed. When defining the employee's deduction assignment (Deduction Assignment (PYUPED) page), the amount to be deducted per period and the bond purchase price are specified.

07: Reserved for future use.

08: Spread Flag A flag of C allows spreading of contribution to be set via a calculation code.

09: TC spread flag This flag is used to determine how this deduction will spread to Pay Strings entered through timecard pages. If this deduction is to always spread to Pay Strings entered through timecards, enter Y, or leave the field blank. If this deduction is never to spread to Pay Strings entered through timecards enter N. If this deduction is to spread to Pay Strings entered through timecards only when all of the employee's paid hours are entered through timecards, enter P. The P setting will check pay base 1 to see whether activity has occurred on assigned lines. A value of H acts similar to P but checks for hours in Hour Base 1, deciding whether activity has occurred on assigned lines, rather than checking for dollars in pay base.

10: Spread w/No Pay This flag is used to identify an employee who is to receive a contribution without any hour activity in a payroll. This allows the payroll process to handle the contribution independent of any earnings the employee may have received. Enter Y to enable this flag.
Example: A contribution is setup to provide for the payment of medical premiums for retired employee. Because the retirees will not receive any pay, but only the medical contribution, that contribution must be set up as Spread w/No Pay.

11-15: Reserved for future use.

16: Check (Chk) Stub Flag This flag is used to help format PY checks and EFTs. Its use varies depending on your check format. Some sites will not use this flag.

17: Retire Pay Code (Cd) Special code for state-specific retirement systems. When used in STRS, this code can be either an M, for monthly, A for annually, H for hourly or D for Daily. This code tells the STRS subsystem how to calculate the pay rate for this hour when it is reported to STRS. This reference is needed to determine what the STRS pay code will be on a given line of the STRS detail report.

18: Reserved for future use.

19: Deduction Reg. An N in this field will prevent this deduction form being printed on the deduction register.

20: Count as Salary Set this switch to Y and patch PB amounts for this CDH will spread to pay assignment lines of the same pay class if the CDH is entered on a timecards override line. The patch PB amounts are used to affect salary dollars for patch salary hours on assigned lines. Thus, a direct contribution could be cost against an override GLKEY yet still reduce the patch salary amount accordingly. In cases where there is more than one pay assignment in the pay class, the CDH amount is spread in proportion to the salaries on the assignments.

21: Reserved for future use.

22: XTD always ITD: A Y in this switch allows the accumulator to accumulate inception to date. This allows inception to date to be kept even when there is a date range on the employee contribution/deduction assignment.

23: Dynamic Priority A Y in this switch allows for the priority, for the specified employee, to be figured dynamically. NU Common Code, with a Category/Value of PYFG/PY200C, Numeric Value 2 needs to have the Special Code field (1, 2, 3, or 4) which will contain the dynamic priority.

24: Set by Contract A Y causes CDH amount to be set by contract ID. Contract IDs are a way of grouping Pay Lines based on specific Pay Line parts, which constitute a key. The cluster CTFC and its attributes are used to read and set values for a specific contract ID. 

25: Client Defined Switch This switch is used as a marker that the client can define. The title of this switch is setup in NU Common Code, with a Category/Value of PYFG/PY335C in description one. The text in that description will appear next to this field. Washington State specific = DRS.

26: Client Defined Switch This switch is used as a marker that the client can define. The title of this switch is setup in NU Common Code, with a Category/Value of PYFG/PY335C in description two. The text in that description will appear next to this field. Washington State specific = DRS Earn or Paid.

27: Contract XTD Enter the appropriate code in this switch to designate how this amount affects the contract accumulator. Available Codes: E = Earned, P = Paid, Q = Retro Earnings, E = Exception to be included in Retro process, R = Retro Pay, U = Retro Pay Request, V = Retro Spread Pay, B = Both Earnings and Pay, O = Retro Earnings and Pay, L = LWOP Request, K = LWOP Taken, M = LWOP Earned and Paid, W = Long Term LWOP Patch.

28: Contract Retro Enter the appropriate Contract Retro switch. R = Retro Pay, X = Exception to be included in Retro process, X = LWOP Request.

29: Encumbrance Enter the appropriate code in this switch: E = Include this CDH in the calculation and create a PYEN transaction for it. Y = Include this CDH in the calculation but do not create a PYEN transaction.

30-32: Reserved for future use.

33: Mandatory Y/N - Option to mark mandatory deductions and contributions.  If the Protect Net option is enabled and there is not enough net pay, mandatory deductions/contributions are still calculated.

34: Addl Amt on Supp - Used to stop additional amounts on supplemental pay periods (period type is not REG).

35-42: Reserved for future use.

Misc Code/Relate To Code

Misc Codes

Misc Code 1-8: There are eight, four-character miscellaneous codes that may be specified for each contribution, deduction, or hour (CDH) definition.
The first miscellaneous code is reserved for Quarterly 941 reports and W-2 page processing. The following types of deductions, contributions, and hours must contain the proper associated miscellaneous code as noted below.

To support multiple state schemes for state income tax, city income tax, state unemployment, state disability, and worker compensation, miscellaneous code 1 must hold the corresponding abbreviation: SIT, CIT, SUI, SDI, WORK.
Miscellaneous code 2 must hold the two letter state abbreviation and a two digit postal state code. For example, California's miscellaneous code 2 would be CA06. SIT, SUI, SDI, and WORK are all state specific and miscellaneous code 1 and 2 are all that is required. For CIT further information is required in miscellaneous code 3. An arbitrary two-character city code and an arbitrary two-digit index. This CIT index must be unique if there are multiple CIT deductions defined. For example, the city income tax for Red Bluff might have RB01 in miscellaneous code 3. The two-digit indexes are used to build accumulator records for Pay Bases associated with these state specific categories. 
61xx for SIT, xx is the state index
62xx for CIT, xx is the city index
63xx for SUI, xx is the state index
64xx for SDI, xx is the state index
65xx for WORK, xx is the state index
The second through sixth miscellaneous codes are for distribution vectors or other reporting needs (for example, PERS). These codes work in conjunction with the CDH distribution vectors on the PY Employee Pay Assignment page. Through their use, the system can be directed to post (or not post) the CDH to a particular Pay String. 
For example, to ensure that only the health contribution being defined (and no other contribution) is posted to a certain Pay String, enter HLTH in the second miscellaneous code box on this page. Then, on the PY Employee Pay Assignment page, identify any Pay Strings where this contribution is to be posted by entering I2HLTH in the first group of the CDH distribution vector fields. This code directs the system to include (I) all contributions with HLTH in the second (2) miscellaneous code as previously defined on the PY Contribution Definition page. 
Alternatively, to ensure that the health contribution being defined is not posted to a certain Pay String, enter HLTH in the second miscellaneous code box on this page. Then, on the PY Employee Pay Assignment page, identify any Pay Strings where this contribution is not to be posted by entering X2HLTH in the first group of the CDH distribution vector fields. This code directs the system to exclude (X) all contributions with HLTH in the second (2) miscellaneous code as previously defined on the Contribution Definition page.
The sixth miscellaneous code may be used to designate where to find the pay rate if the record type (Rec Type field on the Pay Assignment page) is entered in this field (for example, enter PM to pay at the rate associated with the employee's primary pay assignment).
The seventh miscellaneous code is used for timecard mapping. For example, if two different Pay Classes, Pay Class 100 and 200, both have overtime hours but the hours number differs depending on the employee's Pay Class, timecard mapping may be used to minimize data entry time for timecard hours. Given that overtime hour number 3102 is used for Pay Class 100, and overtime hour number 3202 is used for Pay Class 200, timecard mapping allows the data entry person to simply enter 002 for overtime hours. When timecard mapping is in place, the system will check the employee's Pay Class and automatically change the 002 entry to 102 or 202 depending on the employee's Pay Class.
To set up timecard mapping in this field, enter the hour number (for example, 3002 or 002) which, during timecard entry, will be converted to the hour being defined. In the example above, 3002 would be entered in the seventh miscellaneous code box for hour numbers 3102 and 3202. Also, to use this feature, a Y must be entered in the Map Timecard Hrs field on the PY Entity Definition (PYUPGN) page and the hour number that is to be associated with each Pay Class must be entered in the PY Pay Class Definition (PYUPPY) page.
The eighth miscellaneous code indicates the position (which box number) where this CDH should be printed on the posting registers. Entering 1-5 directs the system to print the CDH in that particular box number. Leaving the field blank causes the system to print the CDH in box 6. Entering NONE in this field causes this CDH not to be printed on the posting register. 

Relate To Codes

Relate To 1-8: This field is required to create pick lists on certain HR pages when assigning CDHs. The valid codes are: ADDL, BENC, BEND, BOND, EFT, MISC, and TSA.

CDH Calc Code Information

CDH Calc Code Information: Enter calculation code information in this text field. For a listing of clusters and attributes, including those that can be used in Payroll calc codes, refer to PYUPCL documentation.

Tools for Deductions

Copy CDH Definition

Select Tools, then Copy CDH Definition on PYUPCC, PYUPDD and PYUPHH pages. The tool copies an existing CDH definition to a new (non-existing) CDH. The copy utility copies the master definition (py_cdh_mstr), the detail definition (pym_cdh_dtl) defined by date ranges which includes the pay and hour bases and the calc code (pys_src_dtl) to the new CDH Number. If the source CDH does not exist or the destination CDH already exists an error message displays. 

After you select the Copy CDH Definition Tool, a pop-up window appears that inquires the Source CDH Number, Destination CDH Number and a Date to select the CDH Detail information. The Source CDH Number is a drop-down that contains all CDHs currently defined in the system. The format is CDH Number concatenated with the short description and defaults to the CDH on the current page. The date uses a standard date control so only valid dates are supplied. The Destination CDH is free format and will give an error message if the CDH entered is not valid or already exists.

After the utility is run, a status displays the number of CDH Definitions (should always be one), CDH Detail Definitions (should never be more than one) and CDH Calc Code records that were successfully copied. If no date is given, the source date defaults to current date.

Copy CDH Calc Codes

Select Tools, then Copy CDH Calc Codes on PYUPCC, PYUPDD and PYUPHH pages. This utility is intended to copy a Calc Code from one CDH to a range of CDHs. First select the appropriate CDHs to copy from and to. Click the Check button to verify the inputs. If the CDHs that are going to be copied to are correct, click Copy. The page displays a warning if the destination CDHs already have calc codes present. Those calc codes will be replaced with the calc code from the From CDH. After the copy is selected, the number of CDHs that the calc code was copied to is reported. If, after you review the CDHs, you realize you made a mistake and change any of the drop-downs, the Copy button becomes inactive and the Check button is re-enabled, forcing the user to verify their inputs again.