This page (revision-35) was last changed on 26-Nov-2021 10:22 by Lilia Urtan

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

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
35 26-Nov-2021 10:22 10 KB Lilia Urtan to previous
34 26-Nov-2021 10:22 10 KB jlawler to previous | to last
33 26-Nov-2021 10:22 10 KB jlawler to previous | to last
32 26-Nov-2021 10:22 10 KB jmyers to previous | to last
31 26-Nov-2021 10:22 10 KB jmyers to previous | to last WORK_RULE_CODE ==> WORK_RULE (Field)
30 26-Nov-2021 10:22 10 KB jmyers to previous | to last
29 26-Nov-2021 10:22 10 KB jmyers to previous | to last
28 26-Nov-2021 10:22 10 KB jmyers to previous | to last
27 26-Nov-2021 10:22 9 KB JMyers to previous | to last
26 26-Nov-2021 10:22 9 KB JMyers to previous | to last
25 26-Nov-2021 10:22 9 KB JMyers to previous | to last
24 26-Nov-2021 10:22 9 KB JMyers to previous | to last
23 26-Nov-2021 10:22 12 KB RForbes to previous | to last
22 26-Nov-2021 10:22 12 KB JMyers to previous | to last
21 26-Nov-2021 10:22 12 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IDJB
IDJB

Version management

Difference between version and

At line 3 changed 12 lines
A Job is used to describe a function, task or role that is a recognized requirement within the organization.\\
\\
A job is always associated with a unit, which determines the employment rules applicable to the job. \\
\\
Employees may be assigned to a job, either permanently through a work assignment record, or temporarily through a payroll transaction. In either case, the employee's record inherits certain information from the job, such as a default pay rate and general ledger distribution. This defaulting process reduces the amount of information that must be entered on an employee’s record to ‘exceptions’ and ‘overrides’ only.\\
\\
Collective agreements within unionized organizations usually contain a list of jobs that apply to the union. Jobs are usually generic in nature and many different employees may do the same job.\\
\\
The same job code may be used in different units but it is recommended that they be unique. \\
\\
Job details are date sensitive. This means that as the job information changes over time, a complete history of the job may be kept. \\
\\
A Job is used to describe a function, task or role that is a recognized requirement within the organization.
A job is always associated with a unit, which determines the employment rules applicable to the job.
Employees may be assigned to a job, either permanently through a work assignment record, or temporarily through a payroll transaction. In either case, the employee's record inherits certain information from the job, such as a default pay rate and general ledger distribution. This defaulting process reduces the amount of information that must be entered on an employee’s record to ‘exceptions’ and ‘overrides’ only.
Collective agreements within unionized organizations usually contain a list of jobs that apply to the union. Jobs are usually generic in nature and many different employees may do the same job.
The same job code may be used in different units but it is recommended that they be unique.
Job details are date sensitive. This means that as the job information changes over time, a complete history of the job may be kept.
At line 16 changed 7 lines
A job code may be frozen to ensure the job is no longer used for new changes, while it still remains available for inquiry on historical information. \\
\\
It is recommended that meaningful code names be chosen for job codes (i.e. accountant, analyst, benefit administrator, carpenter, consultant, controller, craftsman, engineer, entertainer, inspector, lecturer, manager, payroll clerk, president, programmer, stagehand, supervisor, teacher, technician, vice-president, etc.). \\
\\
!‘Maintain Jobs’ Usage and Examples\\
\\
Job data is stored in the [P2K_CM_JOBS] and [P2K_CM_JOB_DETAILS] tables.\\
A job code may be frozen to ensure the job is no longer used for new changes, while it still remains available for inquiry on historical information.
It is recommended that meaningful code names be chosen for job codes (i.e. accountant, analyst, benefit administrator, carpenter, consultant, controller, craftsman, engineer, entertainer, inspector, lecturer, manager, payroll clerk, president, programmer, stagehand, supervisor, teacher, technician, vice-president, etc.).
!‘Maintain Jobs’ Usage and Examples
Job data is stored in the [P2K_CM_JOBS] and [P2K_CM_JOB_DETAILS] tables.
At line 25 changed 2 lines
;[Standing|STANDING]:Standing is used to indicate whether the record is active, frozen or obsolete. Active will default
Standing is an optional fixed lexicon [(X_STANDING)]. \\
;[Standing|STANDING]:Standing is used to indicate whether the record is active, frozen or obsolete. Active will default. Standing is an optional fixed lexicon ([X_STANDING]).
At line 28 changed one line
;[Unit|UNIT_CODE]:This field shows the unit to which the job belongs. Unit_Code from [IDUN] [(P2K_CM_UNITS)] is a 16-character alphanumeric mandatory field.
;[Unit|UNIT_CODE]:This field shows the unit to which the job belongs. Unit_Code from [IDUN] ([P2K_CM_UNITS]) is a 16-character alphanumeric mandatory field.
At line 30 changed one line
;[Entity|ENTITY_CODE]:This field displays the entity to which the job belongs. Entity_Code from [IDEN] [(P2K_CM_ENTITIES)] is a 16-character alphanumeric mandatory field.
;[Entity|ENTITY_CODE]:This field displays the entity to which the job belongs. Entity_Code from [IDEN] ([P2K_CM_ENTITIES]) is a 16-character alphanumeric mandatory field.
At line 33 changed one line
\\
At line 40 changed one line
;[Job Type|JOB_TYPE]:This field allows you to classify the job into a specific type. Job_Type is an optional user-defined lexicon [(X_JOB_TYPE]).
;[Job Type|JOB_TYPE]:This field allows you to classify the job into a specific type. Job_Type is an optional user-defined lexicon ([X_JOB_TYPE]).
At line 42 changed one line
;[Job Class|JOB_CLASS]:This field associates the job to a specific class. Job_Class is an optional user-defined lexicon [(X_JOB_CLASS)].
;[Job Class|JOB_CLASS]:This field associates the job to a specific class. Job_Class is an optional user-defined lexicon ([X_JOB_CLASS]).
At line 44 changed one line
;[WC Class|WCB_CLASS]:This field associates the job to a specific Workers’ Compensation classification used to determine the WC category for reporting and WC Contribution. WCB_Class is an optional user-defined lexicon [(X_WCB_CLASS)].
;[WC Class|WCB_CLASS]:This field associates the job to a specific Workers’ Compensation classification used to determine the WC category for reporting and WC Contribution. WCB_Class is an optional user-defined lexicon ([X_WCB_CLASS]).
At line 48 changed one line
;[Occupation|OCCUPATION_CODE]:This field associates the job to a specific occupation. Occupation_Code from [IDOC] [(P2K_CM_OCCUPATIONS)] is an optional field.
;[Occupation|OCCUPATION_CODE]:This field associates the job to a specific occupation. Occupation_Code from [IDOC] ([P2K_CM_OCCUPATIONS]) is an optional field.
At line 50 changed one line
;[EEO Category|EEO_CATEGORY]:This field associates the job to a specific EEO Category. EEO_Category is an optional user-defined lexicon [(X_EEO_CATEGORY)].
;[EEO Category|EEO_CATEGORY]:This field associates the job to a specific EEO Category. EEO_Category is an optional user-defined lexicon ([X_EEO_CATEGORY]).
At line 52 changed one line
;[Job Profile|JOB_PROFILES_CODE]:This field associates the job to a specific job profile; the ‘job posting’ information linked to the Recruitment application. Job_Profiles_Code from [IDJP] [(P2K_RE_JOB_PROFILES)] is an optional user-defined field.
;[Job Profile|JOB_PROFILES_CODE]:This field associates the job to a specific job profile; the ‘job posting’ information linked to the Recruitment application. Job_Profiles_Code from [IDJP] ([P2K_RE_JOB_PROFILES]) is an optional user-defined field.
At line 55 changed one line
\\
At line 58 changed one line
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine standard payroll processing information required to create pay headers and pay transactions for an employee. Work_Rule_Code from [IDWR ][(P2K_CM_WORK_RULES)] is an optional 16-character alphanumeric field.
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine standard payroll processing information required to create pay headers and pay transactions for an employee. Work_Rule_Code from [IDWR ]([P2K_CM_WORK_RULES]) is an optional 16-character alphanumeric field.
At line 75 changed one line
;[Range|RANGE_CODE]:This field displays the salary or wage range associated with the job. Range_Code from [ISSR] [(P2K_SA_SALARY_RANGES)] is a 16-character alphanumeric optional field.
;[Range|RANGE_CODE]:This field displays the salary or wage range associated with the job. Range_Code from [ISSR] ([P2K_SA_SALARY_RANGES]) is a 16-character alphanumeric optional field.
At line 77 changed one line
;[Scale|SCALE_CODE] [Step|STEP_CODE]: This field displays the salary or wage scale/step code. Scale_Code and Step_Code from [ISSR] [(P2K_SA_WAGE_SCALES)] and [(P2K_SA_WAGE_SCALE_STEPS)] is a combined 16-character alphanumeric optional field.
;[Scale|SCALE_CODE] [Step|STEP_CODE]: This field displays the salary or wage scale/step code. Scale_Code and Step_Code from [ISSR] ([P2K_SA_WAGE_SCALES]) and ([P2K_SA_WAGE_SCALE_STEPS]) is a combined 16-character alphanumeric optional field.
At line 82 changed one line
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure the associated rate is being stored or displayed in (i.e. hourly, weekly, biweekly, semi-monthly, monthly, annual or contract). This field may be defaulted from the Scale/Step definition or the Salary Range definition. Rate_Basis is an optional fixed lexicon [(X_RATE_BASIS)].
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure the associated rate is being stored or displayed in (i.e. hourly, weekly, biweekly, semi-monthly, monthly, annual or contract). This field may be defaulted from the Scale/Step definition or the Salary Range definition. Rate_Basis is an optional fixed lexicon ([X_RATE_BASIS]).
At line 92 changed one line
;[Premium|PREMIUM_CODE]: This field shows the user-defined code that uniquely identifies this premium within the organization. Premium_Code from [ISPM] [(P2K_SA_PREMIUMS)]is a mandatory LOV field.
;[Premium|PREMIUM_CODE]: This field shows the user-defined code that uniquely identifies this premium within the organization. Premium_Code from [ISPM] ([P2K_SA_PREMIUMS])is a mandatory LOV field.
At line 94 changed one line
;[Premium Rate|[PREMIUM_RATE]:This field displays the rate that is used defaulted from this premium. Premium_Rate from [ISPM] [(P2K_SA_PREMIUM_DETAILS)] is an optional field populated from the data of the premium chosen.
;[Premium Rate|[PREMIUM_RATE]:This field displays the rate that is used defaulted from this premium. Premium_Rate from [ISPM] ([P2K_SA_PREMIUM_DETAILS]) is an optional field populated from the data of the premium chosen.
At line 96 changed one line
;[Basis|RATE_BASIS]: The rate basis is the unit of measure in which the associated rate is being stored or displayed for the defaulted Premium Rate. Rate_Basis from [ISPM] [(P2K_SA_PREMIUM_DETAILS)] is an optional fixed lexicon [(X_RATE_BASIS)] defaulted from the data of the premium chosen.
;[Basis|RATE_BASIS]: The rate basis is the unit of measure in which the associated rate is being stored or displayed for the defaulted Premium Rate. Rate_Basis from [ISPM] ([P2K_SA_PREMIUM_DETAILS]) is an optional fixed lexicon ([X_RATE_BASIS]) defaulted from the data of the premium chosen.
At line 98 changed one line
;[Override Rate|PREMIUM_RATE]:The user may enter the override rate that applies to the premium when it is associated with the job. Premium_Rate from [ISPM] [(P2K_SA_PREMIUM_USAGES)] is an optional field you may use to override the defaulted premium rate.
;[Override Rate|PREMIUM_RATE]:The user may enter the override rate that applies to the premium when it is associated with the job. Premium_Rate from [ISPM] ([P2K_SA_PREMIUM_USAGES]) is an optional field you may use to override the defaulted premium rate.
At line 100 changed 2 lines
;[Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the overridden rate. Rate_Basis from [ISPM] [(P2K_SA_PREMIUM_USAGES)] is an optional fixed lexicon [(X_RATE_BASIS)] you may use to override the overridden rate basis.
\\
;[Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the overridden rate. Rate_Basis from [ISPM] ([P2K_SA_PREMIUM_USAGES]) is an optional fixed lexicon ([X_RATE_BASIS]) you may use to override the overridden rate basis.
At line 106 changed one line
;[Sequence #|SPLIT_SEQUENCE]:This field defines the sequential order of the distribution mask for this job. You may define one or multiple distribution masks with splits. Split_Sequence from [ ] [(P2K_CM_DISTRIBUTIONS)] is a 5 digit mandatory field.
;[Sequence #|SPLIT_SEQUENCE]:This field defines the sequential order of the distribution mask for this job. You may define one or multiple distribution masks with splits. Split_Sequence from [ ] ([P2K_CM_DISTRIBUTIONS]) is a 5 digit mandatory field.
At line 108 changed one line
;[Distribution Mask|DISTRIBUTION_CODE]:If a specific distribution segment code is to receive a portion (even 100%) of the costs, this field identifies part or all of that code. This is normally the distribution of the wages associated with the job. Distribution_Code from [(P2K_CM_DISTRIBUTION)] is a 50 character alphanumeric mandatory field.\\The Distribution Editor button in the Distribution tab form on job provides an editor to aid in the creation of the correct distribution code. The information displayed in the Distribution Editor is based on the set up in the G/L Segments form. If Segment Values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided. As each segment is chosen the segments will be concatenated in a display at the bottom of the form. When you are satisfied with the distribution created, choose ‘Return Code’. This will take the full or partial distribution and place it back on the previous form in the Distribution field. If you do not want the new distribution to be returned to the previous form then, choose ‘Cancel Edit’.
;[Distribution Mask|DISTRIBUTION_CODE]:If a specific distribution segment code is to receive a portion (even 100%) of the costs, this field identifies part or all of that code. This is normally the distribution of the wages associated with the job. Distribution_Code from ([P2K_CM_DISTRIBUTION]) is a 50 character alphanumeric mandatory field.\\The Distribution Editor button in the Distribution tab form on job provides an editor to aid in the creation of the correct distribution code. The information displayed in the Distribution Editor is based on the set up in the G/L Segments form. If Segment Values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided. As each segment is chosen the segments will be concatenated in a display at the bottom of the form. When you are satisfied with the distribution created, choose ‘Return Code’. This will take the full or partial distribution and place it back on the previous form in the Distribution field. If you do not want the new distribution to be returned to the previous form then, choose ‘Cancel Edit’.
At line 110 changed one line
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by a Distribution pick list of authorized assignments. There are several choices that may be made, although all these values are specifically used for defaulting down to lower levels. Split_Rule from [(P2K_CM_DISTIRBUTIONS)] is an optional fixed lexicon [(X_SPLIT_RULE)] you may use to look up the value.
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by a Distribution pick list of authorized assignments. There are several choices that may be made, although all these values are specifically used for defaulting down to lower levels. Split_Rule from ([P2K_CM_DISTRIBUTIONS]) is an optional fixed lexicon ([X_SPLIT_RULE]) you may use to look up the value.
At line 112 changed one line
;[Dist %|SPLIT_PERCENT]:If the split rule is ‘by percent’ then indicate the percent in this field. You must enter the percentage has a whole number, not a decimal. For example, to indicate 6% you would enter 6, not. 06 Split_Percent from [(P2K_CM_DISTRIBUTIONS)] is a 5-digit optional percentage field.
;[Dist %|SPLIT_PERCENT]:If the split rule is ‘by percent’ then indicate the percent in this field. You must enter the percentage has a whole number, not a decimal. For example, to indicate 6% you would enter 6, not. 06 Split_Percent from ([P2K_CM_DISTRIBUTIONS]) is a 5-digit optional percentage field.
At line 114 changed one line
;[User%|USER_PERCENT]:This value in this field is for display purposes only and is defaulted once the Dist % is complete. User_Percent from [(P2K_CM_DISTRIBUTIONS)] is a 5-digit optional percentage field.
;[User%|USER_PERCENT]:This value in this field is for display purposes only and is defaulted once the Dist % is complete. User_Percent from ([P2K_CM_DISTRIBUTIONS]) is a 5-digit optional percentage field.
At line 116 changed one line
;[Amount|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field. Split_Amount from [(P2K_CM_DISTRIBUTIONS)] is an 18 digit optional numeric field.
;[Amount|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field. Split_Amount from ([P2K_CM_DISTRIBUTIONS]) is an 18 digit optional numeric field.
At line 118 changed one line
;[Start Date|START_DATE]:For Distribution Pick Lists, this is the start date from this distribution may be used. For Funds, this is the start date that the fund becomes available. Start_Date from [(P2K_CM_DISTRIBUTIONS)]is an 18 digit optional numeric field.
;[Start Date|START_DATE]:For Distribution Pick Lists, this is the start date from this distribution may be used. For Funds, this is the start date that the fund becomes available. Start_Date from ([P2K_CM_DISTRIBUTIONS])is an 18 digit optional numeric field.
At line 121 changed one line
For funds, this is the end of that fund's availability. End_Date from [(P2K_CM_DISTRIBUTIONS)]is an 18 digit optional numeric field.
For funds, this is the end of that fund's availability. End_Date from ([P2K_CM_DISTRIBUTIONS])is an 18 digit optional numeric field.
This page (revision-35) was last changed on 26-Nov-2021 10:22 by Lilia UrtanTop