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

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

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
69 26-Nov-2021 10:22 9 KB kparrott to previous
68 26-Nov-2021 10:22 9 KB jmyers to previous | to last APPROVAL_WIP_REC ==> APPROVAL_WIP_REC(System_Preference)
67 26-Nov-2021 10:22 9 KB JEscott to previous | to last
66 26-Nov-2021 10:22 9 KB JEscott to previous | to last
65 26-Nov-2021 10:22 9 KB JEscott to previous | to last
64 26-Nov-2021 10:22 9 KB JEscott to previous | to last
63 26-Nov-2021 10:22 9 KB JEscott to previous | to last
62 26-Nov-2021 10:22 9 KB JMyers to previous | to last
61 26-Nov-2021 10:22 9 KB JMyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 changed one line
Approval Processes are user defined on the [IDAP] form. The Approval Process definitions identify which transactions require approvals, the authorized approvers and the levels of approval required. The Approval Process begins as soon as an employee (or other person) "submits" a transaction.
The Approval Process definitions identify which transactions require approvals, the authorized approvers and the levels of approval required. The Approval Process begins as soon as an employee (or other person) "submits" a transaction.
At line 7 changed one line
!What can be approved?
!!What can be approved?
At line 25 added 3 lines
!!How to Define an Approval Process
At line 27 changed one line
Ordering processes may be achieved by adding a “Priority”. The priority will be used when the approval service is deciding which process applies to the approval entity. Processes are grouped by type and ordered from highest to lowest. Caution should be used since if left empty the ID value will be substituted. This may cause unexpected results if one of many is left empty. The suggested set up is to define a priority when multiple of the same type exist.
Approval Processes can be refined using a Where Clause. The Where Clause acts as a filter to qualify the transactions that are to be handled by the process. For example, if there is a special set of approval rules for wage changes, a Personnel Action type approval process can be set up with a where clause that restricts the process to PA’s that have a change reason of “A WAGE INCREASE”. All other types of PA’s would not qualify.
At line 29 changed one line
Processes can be refined using a WHERE CLAUSE to restrict which types will fall under the defined PROCESS. Example - a process of TYPE: Personnel Actions can have a where clause that only PA’s of type “A WAGE INCREASE” will qualify for this process defined, and such PA’s of type: “ADDRESS CHANGE” do not.
A priority may be specified to indicate the order that the approval processes are checked. The priority will be used when the approval service is deciding which process applies to the approval entity. Processes are grouped by type and ordered from highest to lowest. Caution should be used since if left empty the ID value will be substituted. This may cause unexpected results if one of many is left empty. The suggested set up is to define a priority when multiple of the same type exist.
At line 31 changed one line
A Process may have a “Start” and “End’ date where it will be considered to be “effective”. If the current approval entity’s AS_OF_DATE falls either between dates if both given, after the start if the end date is not provided or before the end date if the start date is not provided.
Approval Processes can also be defined using a start date and/or an end date where the rules are considered to be “effective”. If the current processing as of date falls within the time frame specified the approval is considered effective.
At line 36 added 9 lines
!What are Priorities?
When you have more than one Approval Process for any given Approval Type that are differentiated by using where clauses, in order to ensure that they are processed properly, they must be given a processing priority.
To get the best performance, processing should begin with the most specific (smallest) group of employees and finish with the least specific (largest) group. High priority numbers are processed first. Therefore, you want to process the most specific (smallest) Approval Process first and end with a general Approval Process that will process all remaining employees.
This accomplishes two objectives. Employees are processed in the proper order and eliminated from further processing which is more efficient. More importantly, it also prevents employees who are both part of a general group (entity) as well as a specific group (department) from getting processed and eliminated from further processing as part of general group before they get processed in their proper specific group.
Example: You have a situation where Department A has a different benefit election approval process than the rest of the company. If you set the priority for Department A’s approval process to be processed after the approval process for the rest of the company, then all employees in Department A will be processed as part of the whole company and will never be processed as Department A. However, if you set the priority to process Department A first, they will be processed correctly, eliminated from further processing, and then the rest of the company will be processed as required.
No employee in the organization will ever be processed twice for the same Approval Type. Once someone has qualified they are excluded from further processing.
At line 46 added 3 lines
!Setting up by Approval Type with Sub Types
Within the Approval Type of Personnel Actions there are many PA Types and within each PA Type there can be many Approval Processes.
Each Approval Process within each PA Type will need to follow a specific processing Priority, so can break them down into Series.
At line 50 added 11 lines
For example:
\\4000 Series: WEBEL Benefit Election Requests
\\3000 Series: WEEPP Personal Profile Change Requests
\\2000 Series: WMEPR Promotion Requests
\\1000 Series: WMETR Termination Requests
Within each series, set the processing Priority for the different sub-types, starting with the most specific, and ending with the least specific.
[Example of Approval Type with Sub Types|EXAMPLE APPROVAL WITH SUBTYPES]