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

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
31 26-Nov-2021 10:22 11 KB jmyers to previous
30 26-Nov-2021 10:22 12 KB jmyers to previous | to last
29 26-Nov-2021 10:22 12 KB JEscott to previous | to last
28 26-Nov-2021 10:22 9 KB JEscott to previous | to last
27 26-Nov-2021 10:22 9 KB JEscott to previous | to last
26 26-Nov-2021 10:22 8 KB JEscott to previous | to last
25 26-Nov-2021 10:22 8 KB JEscott to previous | to last
24 26-Nov-2021 10:22 8 KB JEscott to previous | to last
23 26-Nov-2021 10:22 8 KB JEscott to previous | to last
22 26-Nov-2021 10:22 7 KB JMyers to previous | to last
21 26-Nov-2021 10:22 7 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
DISTRIBUTION DEFAULTING LOGIC
DISTRIBUTION DEFAULTING LOGIC

Version management

Difference between version and

At line 3 changed one line
This section explains the Distribution Defaulting Logic within the application.
This section explains the Distribution Defaulting Logic within ePersonality.
At line 9 changed one line
It is important to note that the distribution will default in AFTER the record has been saved. The distribution is stored on a separate table that has special processing logic for its defaulting. The distribution that defaults in depends on what fields are changed and what is on the other tables (Position/Job/Department). In short the distribution cannot take place until the data has been confirmed via a save.
Detailed GL processing will be described in Payroll Advanced manual.
At line 11 changed one line
A change has been recently made to the position distribution logic so that the position’s distribution will no longer be removed if the associated job does not have a distribution defined.
!!Department
The department distribution mask will initially be empty or you may use the distribution format found on the G/L Company (IDGC) form.
If the user does not change it, then any segment value will be valid because of the wild cards.
At line 13 removed 3 lines
!!Distribution Logic for Departments ([IDDP])
The department distribution mask will initially be empty or you may use the distribution format found on the G/L Company ([IDGC]) form. If the user does not change it, then any segment value will be valid because of the wild cards.
At line 16 added 2 lines
If the financial cost for this department should be charged to a specific cost centre, then you may fill in the segment for that cost centre.
If you do supply some of the digits, the distribution mask will be validated according to the validation rules established in the G/L Segments form.
At line 18 changed one line
If the financial cost for this department should be charged to a specific cost center, then you may fill in the segment for that cost center.
!!Job
Normally, there is only one distribution code for a job and the distribution is only partially specified.
At line 20 changed one line
If you do supply some of the digits, the distribution mask will be validated according to the validation rules established in the G/L Segments form ([IDGS]).
However, it is possible to have multiple distribution codes for a job and to have the distribution fully specified.
Jobs may also have more than one associated distribution code with a specified split.
At line 22 changed 2 lines
!!Distribution Defaulting on Jobs ([IDJB])
Normally, there is only one distribution code for a job and the distribution is only partially specified. However, it is possible to have multiple distribution codes for a job and to have the distribution fully specified. Jobs may also have more than one associated distribution code with a specified split.
When you first create the job, the distribution code will be empty. You can enter the code manually with the assistance of the distribution editor. The editor will show the distribution format defined for the GL Company in the Define GL Segments (IDGS) screen.
At line 25 changed one line
When you first create the job, the distribution code will be empty. You can enter the code manually with the assistance of the distribution editor. The editor will show the distribution format defined for the GL Company in the Define GL Segments ([IDGS]) screen.
When a date sensitive change is made to the job, the existing associated distribution is cloned and attached to the newly effective job record. The user must then make any changes to the distribution tab manually, if applicable.
At line 27 changed one line
When a [date sensitive|DATE SENSITIVE] change is made to the job and has been saved, the existing associated distribution is cloned and attached to the newly effective job record. The user must then make any changes to the distribution tab manually, if applicable.
Each distribution code (full or partial) entered on a job will be validated according to the validation rules established in the G/L Segments form.
Normally, there is only one distribution code for a position and the distribution is fully specified. However, it is possible to have multiple distribution codes for a position and to have the distribution partially specified.
At line 29 changed 3 lines
Each distribution code (full or partial) entered on a job will be validated according to the validation rules established in the G/L Segments form ([IDGS]).
!!Distribution Defaulting on Positions ([IDPS])
Normally, there is only one distribution code for a position and the distribution is fully specified. However, it is possible to have multiple distribution codes for a position and to have the distribution partially specified. Position may also have more than one associated distribution code with a specified split.
Position may also have more than one associated distribution code with a specified split. When a new position is created, if there is a committed or saved distribution record associated with the related job then it is copied to the position. The distribution mask is then obtained from
the department and superimposed on each distribution code. The user may manually change the position distribution as they wish.
At line 33 changed one line
When a new position is created and saved, if there is a committed or saved distribution record associated with the related job then it is copied to the position. The distribution mask is then obtained from the department and superimposed on each distribution code. The user may manually change the position distribution as they wish.
When a date sensitive change is made to the position (without a job or department change), the existing associated distribution is cloned and attached to the newly effective position record. The user must then make any changes to the distribution tab manually, if applicable.
When a date sensitive change is made to the position and there is a job change (with or without a department change), the distribution for the position is thrown away and the distribution record associated with the related job is then copied to the position. The distribution mask is then obtained from the department and superimposed on each distribution code. The user may manually change the position distribution as they wish. This occurs only when there are saved or committed job distribution records.
At line 35 changed one line
When a date sensitive change is made to the position (without a job or department change) and the change has been saved, the existing associated distribution is cloned and attached to the newly effective position record. The user must then make any changes to the distribution tab manually, if applicable.
When a date sensitive change is made to the position and there is a department change (without a job change), the distribution mask for the department is obtained from the department and superimposed on each cloned position distribution code. The user may manually change the position distribution as they wish.
At line 37 changed one line
When a date sensitive change is made to the position and there is a job change (with or without a department change), once the change has been saved the distribution for the position is thrown away and the distribution record associated with the related job is then copied to the position. The distribution mask is then obtained from the department and superimposed on each distribution code. The user may manually change the position distribution as they wish. This occurs only when there are saved or committed job distribution records. Distributions on positions will no longer be removed when a change is made to the position record if there are no distributions located on the Job.
Each distribution code (full or partial) entered on a position will be validated according to the validation rules established in the G/L Segments form.
At line 39 removed 2 lines
When a date sensitive change is made to the position and there is a department change (without a job change), the distribution mask for the department is obtained from the department and superimposed on each cloned position distribution code after the change has been saved. The user may manually change the position distribution as they wish. Each distribution code (full or partial) entered on a position will be validated according to the validation rules established in the G/L Segments form ([IDGS]).
At line 43 changed 2 lines
!!Distribution Defaulting on Assignments ([IEAS])
Normally, there is only one distribution code with an assignment and the distribution is fully specified. e.g. EE 19803 9764-23-515 However, it is possible to have multiple distribution codes on an assignment and to have the distribution partially specified. Assignments may also have more than one associated distribution code with a specified split.
!!Assignment
Normally, there is only one distribution code with an assignment and the distribution is fully specified.
e.g. EE 19803 9764-23-515
At line 46 changed one line
In [IEAS] when there is a new assignment or an assignment change, before the save is performed a message will be displayed above the distribution table stating defaulting will occur after a save. This message is to remind users that they will only see the changed distribution AFTER the record has been saved.
However, it is possible to have multiple distribution codes on an assignment and to have the distribution partially specified.
Assignments may also have more than one associated distribution code with a specified split. The handling of the distribution code defaulting logic on an assignment depends on whether a position code is being used.
At line 48 removed 2 lines
The handling of the distribution code defaulting logic on an assignment depends on whether a position code is being used.
At line 51 changed one line
When a new assignment is created and saved (through Maintain Assignment Records - [IEAS] or Establish Personnel Profiles - [IEHR]), if there are distribution records associated with the specified position, the distributions are copied from the position to the assignment. The user may manually change the assignment distribution as they wish.
When a new assignment is created (through Maintain Assignment Records - IEAS or Establish Personnel Profiles - IEHR), if there are distribution records associated with the specified position, the distributions are copied from the position to the assignment. The user may
manually change the assignment distribution as they wish.
At line 53 changed one line
When a date sensitive change is made to an assignment (without a position change) and has been saved, the existing associated distribution is cloned and attached to the newly effective assignment record. The user must then make any changes to the Distribution tab manually, if applicable.
When a date sensitive change is made to an assignment (without a position change), the existing associated distribution is cloned and attached to the newly effective assignment record. The user must then make any changes to the Distribution tab manually, if applicable.
At line 55 changed one line
When a date sensitive change is made to an assignment and there is a position change and the change has been saved, the distribution for the assignment is discarded and the distribution record associated with the related position is copied to the assignment. The user must then make any changes to the Distribution tab manually, if applicable.
When a date sensitive change is made to an assignment and there is a position change, the distribution for the assignment is discarded and the distribution record associated with the related position is copied to the assignment. The user must then make any changes to the Distribution tab manually, if applicable.
At line 58 changed one line
When a new assignment is created (through Maintain Assignment Records - [IEAS] or Establish Personnel Profiles - [IEHR]), if there are distribution records associated with the related job then it is copied to the assignment. The distribution mask is then obtained from the department and superimposed on each distribution code. The user must then make any changes to the Distribution tab manually, if applicable.
When a new assignment is created (through Maintain Assignment Records - IEAS or Establish Personnel Profiles - IEHR), if there are distribution records associated with the related job then it is copied to the assignment. The distribution mask is then obtained from the department and
superimposed on each distribution code. The user must then make any changes to the Distribution tab manually, if applicable.
At line 66 changed one line
Each distribution code (full or partial) entered on an assignment will be validated according to the validation rules established in the G/L Segments form ([IDGS]).
Each distribution code (full or partial) entered on an assignment will be validated according to the validation rules established in the G/L Segments form.
At line 70 removed 3 lines
-----
!!!PERSONNEL ACTIONS AND DISTRIBUTION LOGIC
Personnel records may be changed through the use of a [Personnel Action (PA)|PERSONNEL ACTION], these changes may result in a distribution change. Distribution defaulting may occur as a result of a PA; however, the defaulting will only occur once the PA has been PROCESSED.
At line 74 removed 23 lines
!!Personnel Actions
Personnel Actions are supported in both the Professional world and in Self Service and yet they use different types of screens to generate and process PAs. The Professional system uses ‘P’ type screens such as [PEAS], [PEPR] and [PEID]. The Self Service system uses screens such as [WMEPR] and [WMETR].
Depending on the form definition some P type screens will show distribution changes, [PEAS] for example. This is due to the PA type that has been defined for [PEAS] including the [P2K_CM_DISTRIBUTIONS] table. Also, the [PEAS] form definition was defined with the [P2K_CM_DISTRIBUTIONS] table and column.
Screens such as [WMEPR] and [PEPR] will NOT show old and new values for distribution changes in a PA since neither of these forms include the [P2K_CM_DISTRIBUTIONS] table in their definition, nor do their associated [PA Types|PA_TYPE_CODE].
!!Distribution Defaulting with PAs
Distribution defaulting will occur when distributions are included in the Personnel Action Type ([ISPY]) and the distribution columns are included in the PA form.
The newly defaulted values will display in BOLD in Professional and BURNT ORANGE in Self Service. If the text color changes to either of these it means there are PA changes created. These changes are listed in the details of the PA which is viewable in the Maintain Personnel Actions ([ISPA]) form.
Forms that do not include the distribution table will NOT show the user the expected defaulted values. The defaulted distribution will ONLY be seen once the [PA|PERSONNEL ACTION] has been processed. Reports or screens showing new and old values will NOT show the defaulting changes such as [ISPA] or [RSPA]. For these types of screens defaulting will occur during the run of [USPPA] or when the PA is manually processed via an action button.
!!Effective Date Splits and Distribution Defaulting
When a PA has been initiated and the new values are applied to a form they are displayed as bold as explained above. This is done to show the user what the data will look like after the PA has been processed. This is also done for distributions however there is a small difference. Screens which include distributions eg: [PEAS], a PA is created causing a PA generated effective date split. This scenario will show the new distributions as normally expected via PAs with all newly defaulted records and all columns showing in BOLD.
When the PA does NOT cause an effective date split the distributions changes will show along side the existing distributions since this is multi-row display.
----
![Notes|Edit:Internal.DISTRIBUTION+DEFAULTING+LOGIC]
[{InsertPage page='Internal.DISTRIBUTION+DEFAULTING+LOGIC' default='Click to create a new notes page'}]
This page (revision-31) was last changed on 26-Nov-2021 10:22 by jmyersTop