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

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

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
53 26-Nov-2021 10:22 11 KB jaiken to previous
52 26-Nov-2021 10:22 11 KB kparrott to previous | to last
51 26-Nov-2021 10:22 11 KB jmyers to previous | to last
50 26-Nov-2021 10:22 11 KB jmyers to previous | to last
49 26-Nov-2021 10:22 11 KB jmyers to previous | to last
48 26-Nov-2021 10:22 11 KB jmyers to previous | to last
47 26-Nov-2021 10:22 10 KB jmyers to previous | to last
46 26-Nov-2021 10:22 10 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
45 26-Nov-2021 10:22 10 KB jmyers to previous | to last WORK_RULE_CODE ==> WORK_RULE (Field)
44 26-Nov-2021 10:22 10 KB JMyers to previous | to last
43 26-Nov-2021 10:22 10 KB JMyers to previous | to last
42 26-Nov-2021 10:22 10 KB JMyers to previous | to last
41 26-Nov-2021 10:22 10 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IDDP
IDDP

Version management

Difference between version and

At line 1 changed 2 lines
[{TableOfContents }]
!!!DEFINE DEPARTMENTS
[{TableOfContents }] <-- only if tabbed form
!!!DEPARTMENTS
[{Image src='IDDP.JPG' width='360' align='right' link='attach/IDDP/IDDP.JPG'}]
At line 13 changed one line
Department codes must be unique within an entity. This entity is the organization to which they are accountable for operational management purposes. Departments may be associated with second entity for legal reasons. The second connection enables a department to be the responsibility of a different entity for external government reporting purposes while still being part of the organization structure of the original entity.
Department codes must be unique within an entity. This entity is the organization to which they are accountable for operational management purposes. Departments may be associated with second entity for legal reasons. The second connection enables a department to be the
responsibility of a different entity for external government reporting purposes while still being part of the organization structure of the original entity.
At line 17 changed one line
When defining departments, we recommend that you do not build any hierarchical meaning into the department codes. They should simply reflect the function of that area of the organization and not the division or reporting structure above them. This makes departments easier to manage and reduces the maintenance required should an organization restructuring take place.
When defining departments, High Line recommends you do not build any hierarchical meaning into the department codes. They should simply reflect the function of that area of the organization and not the division or reporting structure above them. This makes departments easier to manage and reduces the maintenance required should an organization restructuring take place.
At line 19 changed one line
Department data is stored in the [P2K_CM_DEPARTMENTS],[P2K_CM_DEPARTMENT_DETAILS], [P2K_CM_POSITION_DETAILS], [P2K_CM_GL_COMPANIES], [P2K_CM_ALLOWED_COST_CENTERS] and [P2K_CM_COORDINATORS]
‘Define Departments’ Usage and Examples
At line 21 changed 2 lines
;[Department | DEPARTMENT_CODE]:The department code is a user-defined code that uniquely identifies an area of the organization.
Department data is stored in the [P2K_CM_DEPARTMENTS] and [P2K_CM_DEPARTMENT_DETAILS] tables.
;[Department | DEPARTMENT_CODE]:The department code is a user-defined code that uniquely identifies an area of the organization.
Department_Code is a 16-character alphanumeric mandatory field.
At line 28 added 5 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) you may use to look up the value.
;[Operational Entity | ENTITY_CODE]:This field holds the entity to which the department reports to for operational reasons.
;[Legal Entity | ENTITY_CODE]:This field displays the entity to which the department legally belongs. The legal entity is set up when the department is newly added. Legal Entity cannot be changed once the department is added into the system.
;[Change Reason | CHANGE_REASON]:This field displays the ‘Change Reason’ code, which provides the rationale as to why information has been created or changed as of an effective date.
At line 25 changed one line
;[Standing | STANDING]:‘Standing’ is used to indicate whether the record is active, frozen or obsolete. Active will default.
%%information This function is [date sensitive] and changes made in these areas below the [date navigator] may be split with a new effective date.%%
At line 27 removed one line
;[Legal Entity | ENTITY_CODE]:This field displays the entity to which the department legally belongs. The legal entity is set up when the department is newly added.
At line 29 changed one line
;[Operational Entity | ENTITY_CODE]:This field holds the entity to which the department reports to for operational reasons.
;[FieldNameInHdr]:description
At line 31 removed one line
;[Change Reason | CHANGE_CODE]:This field displays the ‘Change Reason’ code, which provides the rationale as to why information has been created or changed as of an effective date.
At line 33 removed 2 lines
%%information This function is [date sensitive|DATE SENSITIVE] and changes made in these areas below the [date navigator|DATE SENSITIVE NAVIGATOR] may be split with a new effective date.%%
\\
At line 36 changed one line
!!Definition tab
[{Image src='IDDP_DEFINITION.JPG' width='360' align='right' link='attach/IDDP/ILDI_DEFINITION.JPG'}]
!!DEFINITION
At line 38 removed one line
At line 40 removed one line
At line 42 changed 3 lines
;[Industry | INDUSTRY_CODE]:This field holds the user-defined industry codes. Although we will provide some of the codes, additional codes may have to be set up by the user, as described earlier in this workbook. This field may need to be completed after the industry codes have been set up.
EEOC_Function is an optional [fixed lexicon] ([X_EEOC_FUNCTION]) you may use to look up the value.
;[Industry | INDUSTRY_CODE]:This field holds the user-defined industry codes. Although High Line will provide some of the codes, additional codes may have to be set up by the user, as described earlier in this workbook. This field may need to be completed after the industry codes have been set up.
At line 46 removed one line
At line 50 added 2 lines
[{Image src='DISTR_EDITOR.JPG' width='360' align='right' link='attach/IDDP/DISTR_EDITOR.JPG'}]
;[Distribution | DISTRIBUTION_MASK]:This is the edit mask for the distribution code that provides a default value which overlays the distribution code on the position and assignment records. You would normally enter the segments of the distribution for the wages associated with the department and enter the value ‘?’ for the other segments. See the section on ‘Distribution Defaulting Logic’ in this manual for more detail.
At line 49 changed one line
;[Distribution | DISTRIBUTION_MASK]:This is the edit mask for the distribution code that provides a default value which overlays the distribution code on the position and assignment records. You would normally enter the segments of the distribution for the wages associated with the department and enter the value ‘?’ for the other segments.\\ \\See the section on ‘[Distribution Defaulting Logic|DISTRIBUTION DEFAULTING LOGIC]’ for more detail.\\ \\The information displayed in the Distribution Editor screen is based on the set up in the G/L Segments ([IDGS]) form. \\ \\If, on the [IDGS] form, the segment values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided on the Distribution Editor for that segment.\\ \\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 code created, you may 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 newly created distribution code returned to the previous form then you may choose ‘Cancel Edit’.
The information displayed in the Distribution Editor screen is based on the set up in the G/L Segments (IDGS) form, which is described later in this workbook.
At line 51 changed one line
;[Burden Method | BURDEN_METHOD]:‘Burden Method’ is used to indicate the method used for the burden calculation in the Labor GL process of the Payroll module.
If, on the IDGS form, the segment values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided on the Distribution Editor for that segment.
At line 53 changed 2 lines
;[Burden Percent / Rate | BURDEN_PERCENT]:This field displays the burden percentage or rate accounted for this department. If the Burden Method is ‘Percentage Method’, then this field should specify a percentage, if the Burden Method is ‘Hourly Rate’, then this field should specify a rate.
;:For more information on Burden see the [ALLOCATION] page.
As each segment is chosen the segments will be concatenated in a display at the bottom
of the form.
At line 56 changed one line
;[Parent Dept | PARENT_DEPT]:This field describes the department in relation to other departments in the organization. This field is for documentation purposes only and the information displayed will not be used for processing.
When you are satisfied with the distribution code created, you may choose ‘Return Code’. This will take the full or partial distribution and place it back on the previous form in the Distribution field.
At line 58 changed 10 lines
;[Work Rule |WORK_RULE (Field)]:Work rules are used to determine standard processing information required to create pay headers and transactions for an employee. Work Rule is the default for employees occupying positions in that department.
;[Auth Area | AUTHORIZATION_CODE]:The authorization code is a user-defined code that uniquely identifies the authorized area within the organization. Authorization area is the default area for employees occupying positions in that department.
;[Work Division|WORK_DIVISION_CODE]:A work division is a subdivision of an operational entity.
;[Batch Code | BATCH_CODE]:The batch code (if entered) may be used with the various time generation programs (Generate Pay Transaction - UPTG). This program typically is used to create pay transactions for groups of employees and is often set to batch by department. Batch code will be used to allow a group of departments to be created into one batch, rather than created as separate batches. The same batch code may be repeated in numerous department records to group departments for payroll purposes.
;[Phone # | PHONE_NUMBER]:This is the main phone number of the department. The format of the phone number will be determined by the associated Country code. 3144662421 will format to (314) 466-2421
If you do not want the newly created distribution code returned to the previous form then
you may choose ‘Cancel Edit’.
;[Burden Method | BURDEN_METHOD]:‘Burden Method’ is used to indicate the method used for the burden calculation in the Labour GL process of the Payroll module.Burden Method is an optional [fixed lexicon] ([X_BURDEN_METHOD]) you may use to look up the value.
;[Burden Percent / Rate | BURDEN_RATE]:This field displays the burden percentage or rate accounted for this department. If the Burden Method is ‘Percentage Method’, then this field should specify a percentage, if the Burden Method is ‘Hourly Rate’, then this field should specify a rate.
''Burdening and Fringing will be discussed further during Payroll Advanced Training.''
;[Parent Dept | PARENT_DEPT]:This field describes the department in relation to other departments in the organization. This field is for documentation purposes only and the information displayed will not be used for processing.
;[Work Rule | WORK_RULE_CODE]:Work rules are used to determine standard processing information required to create pay headers and transactions for an employee. Work Rule is the default for employees occupying positions in that department. ''Work Rules will be discussed further during Basic Salary Administration training.''
;[Auth Area | AUTHORIZATION_CODE]:The authorization code is a user-defined code that uniquely identifies the authorized area within the organization. Authorization area is the default area for employees occupying positions in that department. ''If your implementation includes the Payroll application, the authorization area on the department definition must be completed.''
;[Batch Code | BATCH_CODE]:The batch code (if entered) may be used with the ePersonality time generation program (Generate Pay Transaction - UPTG). This program typically is used to create pay transactions for groups of employees and is often set to batch by department. Batch code will be used to allow a group of departments to be created into one batch, rather than created as separate batches. The same batch code may be repeated in numerous department records to group departments for payroll purposes. Further discussion of the concepts of batches, batch codes
and time generation is included in the Payroll and Advanced Payroll courses.
;[Phone # | PHNONE_NUMBER]:This is the main phone number of the department. The format of the phone number will be determined by the associated Country code. 3144662421 will format to (314) 466-2421
At line 69 removed one line
At line 71 changed 5 lines
;[Email |EMAIL_ADDRESS(Field)]:This field displays the email address or domain name of the department.
\\
----
!!Location tab
;[Email | EMAIL_ADDRESS]:This field displays the email address or domain name of the department.
!!LOCATION
[{Image src='IDDP_LOCATION.JPG' width='360' align='right' link='attach/IDDP/ILDI_LOCATION.JPG'}]
At line 78 removed one line
At line 80 removed one line
At line 82 removed one line
At line 84 removed one line
At line 86 changed 3 lines
;[Zip/Postal | ZIP_POSTAL]:This field will display the mailing code. The formatting (either Zip or Postal) will be determined by the associated Country code.\\''U.S.A.: Zip Code 55426 Canada: Postal Code M1M 1M1''
;[Zip/Postal | ZIP_POSTAL]:This field will display the mailing code. The formatting (either Zip or Postal) will be determined by the associated Country code.
''U.S.A.: Zip Code 55426 Canada: Postal Code M1M 1M1''
At line 91 removed one line
At line 93 removed one line
At line 95 removed one line
At line 97 removed one line
At line 99 changed 5 lines
;[Zip/Postal | ZIP_POSTAL]:This field will display the mailing code. The formatting (either Zip or Postal) will be determined by the associated Country code.\\''U.S.A.: Zip Code 55426 Canada: Postal Code M1M 1M1''
\\ \\
----
!!Positions tab
;[Zip/Postal | ZIP_POSTAL]:This field will display the mailing code. The formatting (either Zip or Postal) will be determined by the associated Country code.
''U.S.A.: Zip Code 55426 Canada: Postal Code M1M 1M1''
[{Image src='IDDP_ASSIGNMENTS.JPG' width='360' align='right' link='attach/IDDP/ILDI_ASSIGNMENTS.JPG'}]
!!ASSIGNMENTS
The Assignments tab allows you to view all of the employees connected to this department on the As Of Date. The employee name, person code, and employment status will be displayed.
%%warning This tab is for viewing purposes only; you may not edit the data.%%
[{Image src='IDDP_POSITIONS.JPG' width='360' align='right' link='attach/IDDP/ILDI_POSITIONS.JPG'}]
!!POSITIONS
At line 108 removed 31 lines
\\ \\
----
!!Allow Cost Center tab
The cost centers defined here are used by the timesheet WEPTCCM, 'My Non Pre-defined Matrix Timecard'.
;[Cost Center | DCC_ID]:
;[Start Date | START_DATE]:
;[End Date |END_DATE]:
\\ \\
----
!!Coordinator tab
This tab allows you to define a Department Coordinator for different types of roles. The Department Coordinator functionality is open ended to allow you to specify any kind of departmental role. The department coordinator can then be the recipient of emails generated by workflows.
There are ten different coordinator types that can be used with no specific logic behind the types. These can be used as required.
The workflow engine will use the Department Coordinator that starts before/end after the date of the action.
There can be multiple coordinators of the same type per department at the same time.
%%information __Example__\\There is a business role of Manager of Compensation. There are three managers assigned to specific departments and should receive the workflow correspondence (email only).\\__Set Up__\\
#Update the managers’ positions onto the departments. SQL can be used to do so ([P2K_CM_COORDINATORS]).\\If the positions are used when a person leaves the position and another person fills the position there is less maintenance required versus using the the person code.
#On the [IMWA], use the “Action Directed To” to the value of Department Coordinator.
#Add the workflow UserCalc logic ([IMUC]); use the Recipient Type equal to the Coordinator Type.%%
;[Coordinator_Type|COORDINATOR_TYPE]:This field identifies the type of coordinator.
;[Start Date|START_DATE]/[End Date|END_DATE]:This field identifies the start and end dates of when the coordinator is being used/referenced.
;[Person|PERSON_CODE]:If the coordinator is a specific individual, that person is identified in this field.
;[Position|POSITION_CODE]:This field identifies a position who's active occupant(s) are designated as the coordinator.
----
![Notes|Edit:Internal.IDDP]
[{InsertPage page='Internal.IDDP' default='Click to create a new notes page'}]
This page (revision-53) was last changed on 26-Nov-2021 10:22 by jaikenTop