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

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

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
14 26-Nov-2021 10:22 3 KB mmcfarland to previous
13 26-Nov-2021 10:22 3 KB JAiken to previous | to last
12 26-Nov-2021 10:22 3 KB JEscott to previous | to last
11 26-Nov-2021 10:22 3 KB JEscott to previous | to last
10 26-Nov-2021 10:22 3 KB JEscott to previous | to last
9 26-Nov-2021 10:22 3 KB JEscott to previous | to last
8 26-Nov-2021 10:22 3 KB JEscott to previous | to last
7 26-Nov-2021 10:22 3 KB JEscott to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
5 26-Nov-2021 10:22 3 KB JEscott to previous | to last
4 26-Nov-2021 10:22 4 KB JEscott to previous | to last
3 26-Nov-2021 10:22 3 KB JEscott to previous | to last
2 26-Nov-2021 10:22 3 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
IPCU
IPCU

Version management

Difference between version and

At line 3 changed one line
[Pay component usages|PAY COMPONENT USAGES] are the predefined reasons for which a [pay component|PAY COMPONENTS] may be created.
[Pay component usages|PAY COMPONENT USAGES] are the High Line defined reasons for which a [pay component|PAY COMPONENTS] may be created.
At line 5 changed one line
Pay Component Usages can be viewed on the Define Pay Component Usages (IPCU) form. Users can not alter the usage set ups established in this table.
[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.
At line 8 changed one line
The Define Pay Component Usages data is stored in the [P2K_PR_PC_USAGES] tables.
__‘Define Pay Component Usages’ Usage and Examples__
At line 10 changed 8 lines
;[Usage|PC_USAGE_CODE]: This field displays the predefined 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 a PC usage belongs to. 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. The description is a 50-character alphanumeric field.
;[PC G/L Type|PC_GL_TYPE]: This field defines the type of general ledger account associated with the [pay component|PAY COMPONENTS] for this usage. Example: 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 defines 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 that can be selected from the fixed lexicon ([X_LEGISLATION]).
;[Unique Item|UNIQUE_ITEM]:If the Unique Item toggle is set to ON, one and only one [pay component|PAY COMPONENTS] can be defined with this usage (sicuh as gross, net). If the toggle is set to OFF, more than one [pay component|PAY COMPONENTS] can share this usage. Unique_Item is an optional toggle field.
;[Mandatory|MANDATORY]: If the Mandatory toggle is set to ON, there must be a [pay component|PAY COMPONENTS] with this usage. If the toggle is set to OFF, the usage is completely optional. Mandatory is an optional toggle field.
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.
At line 24 changed 6 lines
;[Basic|BASIC_ELEMENT]: If the Basic toggle is set to ON, 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 set to OFF, the [element|PAY ELEMENTS] can be made up by a list of [pay components|PAY COMPONENTS] and also refers to another [element|PAY ELEMENTS] (also known as 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].
----
![Notes|Edit:Internal.IPCU]
[{InsertPage page='Internal.IPCU' default='Click to create a new notes page'}]
;[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].
This page (revision-14) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop