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

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

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
40 26-Nov-2021 10:22 9 KB khiggs to previous
39 26-Nov-2021 10:22 8 KB khiggs to previous | to last
38 26-Nov-2021 10:22 8 KB khiggs to previous | to last
37 26-Nov-2021 10:22 7 KB jmyers to previous | to last
36 26-Nov-2021 10:22 7 KB JMyers to previous | to last FROM_DATE ==> FROM_DATE(Field)
35 26-Nov-2021 10:22 7 KB JMyers to previous | to last TO_DATE ==> TO_DATE(Oracle_Function)
34 26-Nov-2021 10:22 7 KB JEscott to previous | to last
33 26-Nov-2021 10:22 7 KB JMyers to previous | to last
32 26-Nov-2021 10:22 7 KB JEscott to previous | to last
31 26-Nov-2021 10:22 7 KB JEscott to previous | to last
30 26-Nov-2021 10:22 7 KB JMyers to previous | to last
29 26-Nov-2021 10:22 7 KB JMyers to previous | to last
28 26-Nov-2021 10:22 7 KB JMyers to previous | to last
27 26-Nov-2021 10:22 7 KB JMyers to previous | to last
26 26-Nov-2021 10:22 9 KB JMyers to previous | to last
25 26-Nov-2021 10:22 9 KB JMyers to previous | to last
24 26-Nov-2021 10:22 9 KB JAiken to previous | to last
23 26-Nov-2021 10:22 9 KB JEscott to previous | to last
22 26-Nov-2021 10:22 8 KB JEscott to previous | to last
21 26-Nov-2021 10:22 8 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IDAP
IDAP

Version management

Difference between version and

At line 4 changed one line
Approval Processes are used to ensure that approval is obtained for certain actions within the system. The Define Approval Processes (IDAP) form allows you to set up approval requirements for different processes within Personality.
Approval Processes are used to ensure that approval is obtained for certain actions within the system. The Approval Process (IDAP) allows you to set up approval requirements for different processes within [{$applicationname}] .
At line 6 removed one line
The definition data for the Define Approval Processes screen is stored in the [P2K_CM_APPROVAL_PROCESSES], [P2K_CM_APPROVAL_STEPS], [P2K_CM_APPROVAL_RECORDS] and [P2K_CM_APPROVERS] tables.
At line 8 changed one line
;[Approval Process|APPROVAL_PROCESS_CODE]: This field holds the unique user-defined name of the process.
;[Approval Process|APPROVAL_PROCESS_CODE]: This field holds the unique user-defined name of the process. Approval_Process_Code is a 10-character alphanumeric mandatory field you must manually enter.
;[Type|APPROVAL_TYPE]:This field identifies classifies the approval process to a specific type. Approval_Type is a mandatory field which you must fill from the user-defined lexicon [X_APPROVAL_TYPE].
;[Description|DESCRIPTION]:This field allows you to enter a brief description about the process. Description is a 50-character alphanumeric optional field you may manually enter.
;[Priority|PRIORITY]:Each Approval Process is assigned a Priority. The Priority of an approval process indicates the order that the approval processes are checked. The highest is checked first. If multiple Approval Processes exist of the same type and if multiple qualify for a given transaction, the process with the highest Priority will be used. Priority is a 5-character numeric optional field you may manually enter.
;[Where Clause|WHERE_CLAUSE_CODE]:The field allows you to select a `Where Clause' which may be used to specify conditions for selecting approval process. i.e. The `Where Clause' may restrict this process to employee time sheets where the employee is in a specific Unit or Department. By pressing the F9 key while focusing in this field, the user may create a new where clause specifically for this approval process using the 'Where Clause Creater dialog' that pops up. Where_Clause_Code from [P2K_AM_WHERE_CLAUSES] is a 10-character alphanumeric optional field you may either manually enter or select a value from the LOV(F9) provided.
;[Start Date|START_DATE] / [End Date|END_DATE]: 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 10 removed 29 lines
;[Type|APPROVAL_TYPE]:This field identifies classifies the approval process to a specific type.
%%zebra-table
|Approval Type|Table
|Disabled | N/A
|Pay Trans Batches | P2K_PR_BATCHES
|Pay Header Batches | P2K_PR_BATCHES
|Performance Reviews | P2K_SA_REVIEWS
|Personnel Actions | P2K_SA_PERSONNEL_ACTIONS
|Job Requisitions | P2K_RE_POSTINGS
|Applicant Hires | P2K_RE_APPLICATIONS
|Development Programs | P2K_CP_DEVELOPMENT_PROGRAMS
|Development Activity | P2K_CP_DEVELOMENT_ACTIVITIES
|Courses | P2K_CP_COURSES
|Class Schedules | P2K_CP_CLASS_SCHEDULES
|Training Resources | P2K_CP_TRAINING_RESOURCES
|Benefit Elections | P2K_BE_ELECTIONS
|Assessments | P2K_RE_ASSESSMENTS
|Class Registration | P2K_CP_CLASS_REGISTRATIONS
|Time Sheets | P2K_PR_TIME_SHEETS
|Leave Lines | P2K_AT_LEAVE_LINES
|Clock Entries (Authorize) | P2K_TS_CLOCK_ENTRIES
|Education | P2K_RE_EDUCATIONS
|References | P2K_RE_REFERENCES
|Work History | P2K_RE_WORK_HISTORIES
|Open Enrollment EEs | P2K_BE_OPEN_ENROLLMENT_EES
|Positions | P2K_CM_POSITIONS
|Time Sheet Entries (Authorize) | P2K_PR_TIME_SHEET_ENTRIES
%%
;[Description|DESCRIPTION]:This field allows you to enter a brief description about the process.
At line 40 changed one line
;[Maintain Approval Records|ACT_MAINTAIN_RECORDS]: This button allows the user to update any outstanding approval records with changes that have been made to the approval process. If changes are made, this button must be pressed or the function [UDAP] must be run otherwise the changes will not be picked up and processed.
__Approval Steps__
At line 42 removed 7 lines
;[Priority|PRIORITY]:Each Approval Process is assigned a Priority. The Priority of an approval process indicates the order that the approval processes are checked. The highest is checked first. If multiple Approval Processes exist of the same type and if multiple qualify for a given transaction, the process with the highest Priority will be used.
;[Where Clause|WHERE_CLAUSE_CODE]:The field allows you to select a `Where Clause' which may be used to specify conditions for selecting approval process. i.e. The `Where Clause' may restrict this process to employee time sheets where the employee is in a specific Unit or Department. By pressing the F9 key while focusing in this field, the user may create a new where clause specifically for this approval process using the 'Where Clause Creater dialog' that pops up.
;[Start Date|START_DATE] / [End Date|END_DATE]: 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.
!Approval Steps
At line 51 changed one line
;[Seq #|SEQUENCE]: The sequence number indicates the order the steps within the process will be executed.
;[Seq #|SEQUENCE]: The sequence number indicates the order the steps within the process will be executed. Sequence is a 5-character numeric mandatory field you must manually enter
;[Description|DESCRIPTION]: This field allows you to enter a brief description about the step. Description is a 50-character alphanumeric mandatory field you must manually enter.
;[Function Name|FUNCTION_NAME]: This field allows you to enter a function name which is the form to be used for approving the record. If no function is specified, the record may be approved in any form that calls the subject focus of the approval process and that calls the Approval Process logic. Function_Name from [P2K_AM_FUNCTIONS] is a 10-character alphanumeric optional field you may either manually enter or select a value from the LOV(F9) provided.
At line 53 removed 5 lines
;[Description|DESCRIPTION]: This field allows you to enter a brief description about the step.
;[Function Name|FUNCTION_NAME]: This field allows you to enter an embedded function name that can be used in self service when using the "Outstanding Approvals I need to Make" splash function. The default values that have been provided are EPTS (Time Sheets),EALR (Leave Lines), ESPA (Personnel Actions),ESRV (Performance Reviews) and EBOEEE (Open Enrollments). If no function is specified, the IDVAR should not be used as there will be no data to review. Standard screens should not be used in this field (ie, WEPTS, WMALP, WVDALR, etc.).
\\ \\
At line 59 changed 2 lines
!!Approver tab
Approvers are categorized by type as follows: Department Manager, Position Manager, Assignment Manager, Any Manager, Specified Person, etc. This tab identifies the individual who is allowed to approve the current step in the process and what approval rights they have.
!!Approvers tab
Approvers are categorized by type as follows: Department Manager, Position Manager, Assignment Manager, Any Manager, Any Manager, Specified Person, etc. This tab identifies the individual who is allowed to approve the current step in the process and what approval rights they have.
At line 29 added 17 lines
*Department Manager
**An employee who is identified on the department ([IDDP]) as the `Dept. Supervisor' or Manager- Person Code.
* Position Manager
**An employee who is identified on the position ([IDPS]) as the `Supervisor by' or Classification-Manager.
* Assignment Manager
**An employee who is identified on the assignment ([IEAS]) the employee as Service-Supervised By.
* First Manager
* User with Match
**A specific employee who is identified under Last, First.
* Manager
**Currently not supported.
* Specified Person (works with Last, First)
**A specific employee who is identified in the [IEID] form.
* Spec List of People (works with People List)
**This identifies multiple people who qualify to be approvers. Note: only People Lists that are defined through EP can only used in this selection. EP People Lists are cased on Where Clauses.
*Last Approvers Manager
* All Managers
At line 64 changed one line
;[Person|PERSON_CODE]:If the type of approver is listed as `Specified Person or User with Match', the user may select the specific person in this field using the drop down LOV.
;Person:If the type of approver is listed as `Specified Person or User with Match', the user may select the specific person in this field using the drop down LOV.
;Or People List:If the type of approver is listed as `Spec List of People', the user may select the appropriate people list code in this field using the LOV provided.
At line 66 changed one line
;[Or People List|PEOPLE_LIST_CODE]:If the type of approver is listed as `Spec List of People', you may select the appropriate people list code in this field using the LOV provided.
;[Where Clause|WHERE_CLAUSE_CODE]:The field allows you to select a `Where Clause' which may be used to specify conditions for selecting approvers. i.e. The `Where Clause' may restrict this process to approvers in a specific Unit or Department. Where_Clause_Code from [P2K_AM_WHERE_CLAUSES] is a 10-character alphanumeric optional field you may either manually enter or select a value from the LOV(F9) provided.
At line 68 changed 6 lines
;[Where Clause|WHERE_CLAUSE_CODE]:The field allows you to select a `Where Clause' which may be used to specify conditions for selecting approvers. i.e. The `Where Clause' may restrict this process to approvers in a specific unit or department.
;[From Date|FROM_DATE(Field)] / [To Date|TO_DATE(Oracle_Function)]:If there is a specific start or end to this approver's rights then these fields can control the time frame that they are active. If the approval rights for the individual are for a set time frame only, a Start and End Date may be defined.
;[Up to Approval|UP_TO_APPROVAL]: If the individual is part of a sequence of approvers, but has this toggle checked, they can by pass the other approvers and authorize the process directly. e.g. the approval process goes through the department manager, the assignment manager and the position manager. The position manager has `Up to Approval' checked. In this case, the position manager can approve the process without having to wait for the department or assignment manager's approval.
;[From Date|FROM_DATE] / [To Date|TO_DATE]:If there is a specific start or end to this approver's rights then these fields can control the time frame that they are active. If the approval rights for the individual are for a set time frame only, a Start and End Date may be defined. From_Date and To_Date are optional date fields you may manually enter or select a value from the calendar (F9).
;[Up to Approval|UP_TO_APPROVAL]: If the individual is part of a sequence of approvers, but has this toggle checked, they can by pass the other approvers and authorize the process directly. e.g. the approval process goes through the department manager, the assignment manager and the position manager. The position manager has `Up to Approval' checked. In this case, the position manager can approve the process without having to wait for the department or assignment manager's approval. UP_TO_APPROVAL is an optional toggle field.
At line 55 added 2 lines
;[Allow Decline|ALLOW_DECLINE]:The Allow Decline option gives the approver a right to decline an approval record.
;[Allow Change|ALLOW_CHANGE]:The Allow Change option has been added to the IDAP form, however it currently has no logic behind it. This will be implemented in the near future.
At line 76 removed 4 lines
;[Allow Decline|ALLOW_DECLINE]:This setting allows the approver to decline the approval entity. The option is applicable to all steps the approver is responsible for. If a decline is made the approval process is complete, no further approval notification is necessary. This option is available in the right mouse click menu . Comments as to why the decline was made may be entered if necessary.
;[Allow Change|ALLOW_CHANGE]:This setting will cause the approval entity to be editable or not during the approval. Change is allowed when the toggle is checked. Change is NOT allowed when the toggle is unchecked.
\\ \\
At line 87 removed one line
At line 89 removed one line
At line 91 removed one line
At line 93 changed one line
\\
At line 95 removed one line
At line 97 changed 7 lines
;[From Date|FROM_DATE(Field)] / [To Date|TO_DATE(Oracle_Function)]:If there is a specific start or end to this approver's rights then these fields can control the time frame that they are active. If the approval rights for the individual are for a set time frame only, a Start and End Date may be defined.
;[Specified Person|PERSON_CODE]:If the type of approver is listed as `Specified Person or User with Match', this field will identify that person.
;[Or People List|PEOPLE_LIST_CODE]:If the type of approver is listed as `Spec List of People' this field will identify that list of people.
;[From Date|FROM_DATE] / [To Date|TO_DATE]:If there is a specific start or end to this approver's rights then these fields can control the time frame that they are active. If the approval rights for the individual are for a set time frame only, a Start and End Date may be defined. From_Date and To_Date are optional date fields you may manually enter or select a value from the calendar (F9).
;[Specified Person|IDENTITY_NAME]:If the type of approver is listed as `Specified Person or User with Match', this field will identify that person.
;[Or People List|PEOPLE_LIST_CODE]:If the type of approver is listed as `Spec List of People' this field will identify that list of people. Person_List_Code from EPL_ID is a 10-character alphanumeric optional field you may either manually enter or select a value from the LOV(F9) provided.
At line 105 removed 5 lines
----
![Notes|Edit:Internal.IDAP]
[{InsertPage page='Internal.IDAP' default='Click to create a new notes page'}]
This page (revision-40) was last changed on 26-Nov-2021 10:22 by khiggsTop