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 3 removed 2 lines
At line 15 changed 2 lines
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 20 changed one line
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.
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.
At line 22 changed one line
‘Define Departments’ Usage and Examples
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]
At line 24 changed 3 lines
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.
;[Department | DEPARTMENT_CODE]:The department code is a user-defined code that uniquely identifies an area of the organization.
At line 28 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|FIXED LEXICON] (X_STANDING) you may use to look up the value.
;[Standing | STANDING]:‘Standing’ is used to indicate whether the record is active, frozen or obsolete. Active will default.
;[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 31 changed 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. Legal Entity cannot be changed once the department is added into the system.
At line 35 changed 3 lines
[{Image src='IDDP_DEFINITION.JPG' width='360' align='right' link='attach/IDDP/IDDP_DEFINITION.JPG'}]
!!Define Departments (IDDP) - Definition
\\
----
!!Definition tab
At line 38 added one line
At line 40 added one line
At line 41 changed 2 lines
EEOC_Function is an optional [fixed lexicon|FIXED LEXICON|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.
;[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.
At line 46 added one line
At line 46 changed 2 lines
;[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’.
;[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|FIXED LEXICON] ([X_BURDEN_METHOD]) you may use to look up the value.
;[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’.
;[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.
At line 52 changed 2 lines
;[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.
;[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.''
;[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.
At line 65 added one line
At line 67 added one line
At line 69 added one line
At line 58 removed one line
;[Email | EMAIL_ADDRESS]:This field displays the email address or domain name of the department.
At line 72 added 2 lines
;[Email |EMAIL_ADDRESS(Field)]:This field displays the email address or domain name of the department.
\\
At line 61 changed 2 lines
[{Image src='IDDP_LOCATION.JPG' width='360' align='right' link='attach/IDDP/IDDP_LOCATION.JPG'}]
!!Define Departments (IDDP) - Location
!!Location tab
At line 78 added one line
At line 80 added one line
At line 82 added one line
At line 84 added one line
At line 69 changed 2 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 added one line
At line 93 added one line
At line 95 added one line
At line 97 added one line
At line 77 removed 2 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''
At line 100 added 2 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''
\\ \\
At line 81 changed 2 lines
!!Define Departments (IDDP) - Positions
!!Positions tab
At line 108 added 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