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

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

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
20 26-Nov-2021 10:22 4 KB kparrott to previous
19 26-Nov-2021 10:22 4 KB jaiken to previous | to last
18 26-Nov-2021 10:22 4 KB jmyers to previous | to last APPROVAL_WIP_REC ==> APPROVAL_WIP_REC(System_Preference)
17 26-Nov-2021 10:22 4 KB JEscott to previous | to last
16 26-Nov-2021 10:22 3 KB JMyers to previous | to last
15 26-Nov-2021 10:22 3 KB JMyers to previous | to last
14 26-Nov-2021 10:22 3 KB JMyers to previous | to last
13 26-Nov-2021 10:22 3 KB RForbes to previous | to last
12 26-Nov-2021 10:22 3 KB RForbes to previous | to last
11 26-Nov-2021 10:22 3 KB RForbes to previous | to last
10 26-Nov-2021 10:22 3 KB RForbes to previous | to last Internal.UDAP ==> UDAP
9 26-Nov-2021 10:22 3 KB Sheena Mathew to previous | to last
8 26-Nov-2021 10:22 3 KB Sheena Mathew to previous | to last
7 26-Nov-2021 10:22 3 KB Sheena Mathew to previous | to last
6 26-Nov-2021 10:22 3 KB Sheena Mathew to previous | to last
5 26-Nov-2021 10:22 3 KB Sheena Mathew to previous | to last
4 26-Nov-2021 10:22 2 KB Sheena Mathew to previous | to last
3 26-Nov-2021 10:22 2 KB Sheena Mathew to previous | to last
2 26-Nov-2021 10:22 2 KB Sheena Mathew to previous | to last
1 26-Nov-2021 10:22 22 bytes RForbes to last

Page References

Incoming links Outgoing links
UDAP
UDAP

Version management

Difference between version and

At line 1 changed one line
[{TableOfContents }]
__UDAP – UPDATE APPROVAL RECORDS__\\
At line 3 changed one line
!!!MAINTAIN APPROVAL RECORDS
The new function ‘UDAP-Update Approval Records’ was developed to apply any changes made to approvers that are tied to an outstanding approval record (i.e. status equals: ‘Ready To Be Approved or Approval in Progress). For example, if an approver was terminated or on a leave of absence and a designate was identified, then UDAP could be run to update any outstanding approval records with the designate, so that they can be completed by the designate.
At line 5 changed 5 lines
The function ‘UDAP-Update Approval Records’ was developed to apply any changes made to approvers that are tied to an outstanding approval record (i.e. status equals: ‘Ready To Be Approved or Approval in Progress). The records will be up to date with start and end dates of approval process, designated approvers etc.
For example, if an approver was terminated or on a leave of absence and a designate was identified, then UDAP could be run to update any outstanding approval records with the designate, so that they can be completed by the designate.
The UDAP process ''__should be scheduled to run each night__'' so that changes made at various times during the day are picked up ''__or it could be run on demand __''(if required) when changes are made to the approvers on [IDAP].
The UDAP process ''__should be scheduled to run each __''night so that changes made at various times during the day are picked up ''__or it could be run on demand __''(if required) when changes are made to the approvers on IDAP.
At line 11 removed 3 lines
----
!!Additional Considerations
* If an approval process is set up with an Approver type of ‘Specified Person’ and the individual identified is no longer the approver, then the approval process will need to be manually updated to indicate the new person.
At line 15 changed one line
* UDAP will not update the approver stamped on records that have been already approved.\\ \\For example, if Sheila McAdams is set up as an approver in [IDAP] and has already approved a number of records prior to going on leave AND a designate (Shelly Woodruff) has been assigned, UDAP will update all outstanding/open approval records and assign Shelly Woodruff as the approver.\\ \\For those records that have already been approved, Sheila McAdams remains as the one who approved the record. Again, UDAP will only update ‘outstanding approvals’ and not ones that have already been approved.
__Additional Considerations:__\\
* If an approval process is set up with an Approver Type of ‘Specified Person’ and the individual identified is no longer the approver, then the approval process will need to be manually updated to indicate the new person
At line 17 changed one line
* If designate approvers are defined via [IEDA], the system will automatically replace any approval records in [IDAP] with the designate. UDAP does not need to be run in this situation. However, if the designate is specified with a future start date the [UDAP] will need to be run on that specific date in order for the system to generate the designate's approval records for any outstanding approval records that may exist prior to that date.
* UDAP will not update the approver stamped on records that have been already approved. For example, if Sheila McAdams is set up as an approver in IDAP and has already approved a number of records prior to going on leave AND a designate (Shelly Woodruff) has been assigned, UDAP will update all outstanding/open approval records and assign Shelly Woodruff as the approver. For those records that have already been approved, Sheila McAdams remains as the one who approved the record. Again, UDAP will only update ‘outstanding approvals’ and not ones that have already been approved.
At line 19 changed one line
* If an approver terminates (with a termination date less than or equal to the current date) and UDAP is run, any approval records that they belonged to will be removed from [IDAP]. If the terminated employee's position has been filled (assuming that the approver type is 'Position Manager') and UDAP is run, an approval record will be created for the new employee.
* If designate approvers are defined via IEDA, the system will automatically replace any approval records in IDAP with the designate. UDAP does not need to be run in this situation.
At line 21 changed one line
* If an employee is set up as an approver and they’re terminated with a future effective date, UDAP will not update the approval records until the termination date has passed. Once the termination date has passed, any/all approval records that the employee was associated to are removed from [IDAP]. If a new employee is hired into the position that the old employee held and UDAP is run, the approval records that qualify will be updated with the new employee.
* If an employee is set up as an approver and they’re terminated with a future effective date, UDAP will not update the approval records until the termination date has passed. Once the termination date has passed, any/all approval records that the employee was associated to are removed from IDAP. If a new employee is hired into the position that the old employee held and UDAP is run, the approval records that qualify will be updated with the new employee.
At line 23 changed one line
* With respect to time sheet approvals, if a time sheet that was put into a multi-level approval process and was canceled prior to receiving final approval, any outstanding approval records will be removed from [IDAP] and the status of any records that had been approved will be changed from ‘Approved’ to ‘Approval Historic’.
* With respect to timesheet approvals: If a timesheet that was put into a multi-level approval process and prior to receiving final approval, the timesheet was cancelled, any outstanding approval records will be removed from IDAP and the status of any records that had been approved will be changed from ‘Approved’ to ‘Approval Historic’
At line 25 changed one line
* If the preference [APPROVAL_WIP_REC(System_Preference)] is used for [Personnel Actions|PERSONNEL ACTION] and the PAs are generated via an SQL process such as [USSC] or [USMC] the [UDAP] must be run to generate the Future Approval records for the unsubmitted PAs. If the PAs are generated using a JAVA process such as any of the P% screens in Professional or Self Service PA screens the system will automatically create the Future Approval records.
__UDAP - Report Filters __\\
At line 27 changed 17 lines
* When the UDAP is run, the report will now print the approval processes, all the approval records inserted and the total number of records.
\\
----
!!Report Prameters__
|| __Report Parameters __||
|Exception Level|Mandatory, LOV available\\Users may increase the level of logging done from exception to user, legislation,\\usercalc, program or utility levels.
|User Comments|Optional, Text\\This field holds the user-supplied comment which will appear in the header of all pages of the report.
!!Report Filters__
|| __Report Filters __||
| Processes|Optional,Multiple selections, LOV available\\Users can select specific approval processes (e.g. client defined code). If selected, UDAP will only update changes to the approval processes selected.
|Approval Types|Optional,Multiple selections, LOV available\\Users can select specific approval types (i.e. Time sheets, Personnel Actions, etc.) to apply changes to. If selected, UDAP will update all approval processes associated to the approval type selected.
----
![Notes|Edit:Internal.UDAP]
[{InsertPage page='Internal.UDAP' default='Click to create a new notes page'}]
|| Report Filters ||
| __Processes__ | Users can select specific approval processes (e.g. client defined code). If selected, UDAP will only update changes to the approval processes selected. Multiple approval processes can be selected.
|__ Approval Types __| Users can select specific approval types (i.e. Timesheets, Personnel Actions, etc…) to apply changes to. If selected, UDAP will update all approval processes associated to the approval type selected. Multiple approval types can be selected.
This page (revision-20) was last changed on 26-Nov-2021 10:22 by kparrottTop