!!!DEFINE PAY COMPONENT USAGES [Pay component usages|PAY COMPONENT USAGES] are the High Line defined reasons for which a [pay component|PAY COMPONENTS] may be created. [Pay component usages|PAY COMPONENT USAGES] are created and maintained through the Define Pay Component Usages (IPCU) form by High Line only. Users may not alter the usage set ups established in this table. __‘Define Pay Component Usages’ Usage and Examples__ Define Pay Component Usages data is stored in the [P2K_PR_PC_USAGES] tables. ;[Usage|PC_USAGE_CODE]: This field displays the High Line assigned pay component usage code which uniquely identifies the usage within the system. PC_Usage_Code is a mandatory 4-digit numeric field. ;[Type|PC_USAGE_TYPE]: This field classifies the major usage category to which a PC usage belongs, for example, time, earnings, benefits, legislative, statistical, or user defined. PC_Usage_Type is a mandatory fixed lexicon ([X_PC_USAGE_TYPE]). ;[Description|DESCRIPTION]: This field describes the purpose of the [pay component usage|PAY COMPONENT USAGES]. Description is a 50-character alphanumeric field. ;[PC G/L Type|PC_GL_TYPE]: This field indicates the type of general ledger account associated with the [pay component|PAY COMPONENTS] for this usage. E.G. A general account or a specific tax liability account for the employee’s work or residence tax jurisdiction. PC_GL_Type is an optional fixed lexicon ([X_PC_GL_TYPE]). ;[Legislation|LEGISLATION]: This field indicates that the usage is used for the specified legislation only. This information is mostly used for legislated taxation [pay components|PAY COMPONENTS]. Legislation is an optional field you may fill from the fixed lexicon ([X_LEGISLATION]). ;[Unique|UNIQUE_ITEM]:If the Unique Item toggle is checked, one and only one [pay component|PAY COMPONENTS] may be defined with this usage (e.g. gross, net). If the toggle is not checked, more than one [pay component|PAY COMPONENTS] may share this usage. Unique_Item is an optional toggle field. ;[Mandatory|MANDATORY]: If the Mandatory toggle is checked, there must be a [pay component|PAY COMPONENTS] with this usage. If the toggle is not checked, the usage is completely optional. Mandatory is an optional toggle field. !Associated Pay Components ;[PC|PC_CODE]: A PC Code is a unique number code from 1 to 9,999 assigned to uniquely identify the [pay component|PAY COMPONENTS] within the system. ;[Abbreviation|PC_ABBREVIATION]: This field holds a short description of the [pay component|PAY COMPONENTS] used for printing on check and deposit statements, lists and pay registers. ;[PC Description|DESCRIPTION]: This field provides a short description of the [pay component|PAY COMPONENTS]. ;[Element|ELEMENT_CODE]: This field displays the pay element associated to the [pay component|PAY COMPONENTS] with this usage. ;[Element Description|DESCRIPTION]: This field provides a short description of the element. ;[Basic|BASIC_ELEMENT]: If the ‘Basic’ toggle is checked, the element is made up by a list of [pay components|PAY COMPONENTS] only, and is considered a basic [element|PAY ELEMENTS]. If the toggle is not checked, the [element|PAY ELEMENTS] may be made up by a list of [pay components|PAY COMPONENTS] and also refers to another [element|PAY ELEMENTS] (also known as an element mapping). This type of [element|PAY ELEMENTS] is known as a compound [element|PAY ELEMENTS]. By mapping one [element|PAY ELEMENTS] to another it is possible to greatly reduce the amount of [pay component|PAY COMPONENTS] keying that is required to set-up all of the required [elements|PAY ELEMENTS].