ERS 9.2: Assignment Schedule Set in Pending Approval Status When Dates Are Changed, Even When AssignmentDateApproval Process Definition Should Not Be Triggered, Leaving PS_PROJ_TEAM_SCHED Record
(Doc ID 2992523.1)
Last updated on DECEMBER 17, 2023
Applies to:PeopleSoft Enterprise FIN Resource Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The AssignmentDateApproval Process Definition has been configured so that only Assignments having a Category of 'Billable External', (Record Field PS_RS_ASSIGNMENT.TASK_TYPE = 'BE'), will require approvals if any Scheduled Date (Start or End Date of the Assignment) is modified. Any other Categories, (Billable Internal, Non-Billable External, etc...), will skip such workflow altogether. However, whenever a non 'Billable External' Assignment gets its Start Date or End Date field values modified, while no workflow is triggered, the Schedule Details section gets stuck into a 'Pending Approval' status.
As workflow has not been triggered, no Approver can review/approve this transaction, and an out-of-synch problem is generated when the START_DT and END_DT Fields no longer store the same values on Records PS_RS_ASSIGNMENT (where Dates are updated correctly), and PS_PROJ_TEAM_SCHED (where the modified Field is not updated as it should).
1.- Log into the FSCM Online Application as a System Administrator
2.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Resource Management > Setup RM BU Options
3.- Open Set ID SHARE, and ensure the following settings are enabled:
- Use Approval Workflow Engine = Y
- Date Change Approval Process ID = AssignmentDateApproval
4.- Navigate to: Enterprise Components > Approvals > Approvals > Approval Process Setup
5.- Open Process Definition AssignmentDateApproval
6.- At the Criteria set up of Header, Path, and Step levels, define the below condition:
- Criteria Type = User Entered
- All Criteria Needed to Satisfy = N
- Record = RS_ASSIGNMENT
- Field Name = TASK_TYPE
- Criteria Operator = Equals
- Value = BE
7.- Log into the FSCM Online Application as a Staffing User
8.- Navigate to: Resource Management > Assign Resource
9.- Create a new Resource Assignment for an Employee, Business Unit, Project, and date range, ensuring that the Category is 'Billable Internal'
10.- Query Record PS_RS_ASSIGNMENT for the new Assignment ID created, and confirm that Field TASK_YPE = 'BI'
11.- Navigate to: Resource Management > Maintain Schedules > Review Resource Monthly Schedule
12.- Open the Schedule of the Employee at hand, and confirm that the dates entered in the Assignment have been updated accordingly
13.- Navigate to: Resource Management > Assign Resource
14.- Open the Assignment ID transaction previously created
15.- Proceed now to change the current values on the Start Date and/or End Date
16.- Save the changes
17.- Go back to the Assignment search component
18.- Open again the Assignment transaction
19.- PROBLEM: Confirm that in the Schedule Detail Dates section, there is now a 'Detail Status: Pending Approval'
20.- Query Record PS_RS_ASSIGNMENT for the transaction at hand, and confirm that Fields START_DT and END_DT are correctly updated
21.- PROBLEM: Query Record PS_PROJ_TEAM_SCHED for the transaction at hand, and confirm that Fields START_DT and END_DT have NOT been updated accordingly, and still store the old values
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the problem.
The affected Assignment will no longer be able to get further updated, or processed, as its Assignment Detail Status is set to 'Pending Approval', but workflow has not routed the transaction to any Approver User. The 'Pending Approval' status cannot be changed online either.
A date change has been done on such Assignment, but because its Category has been defined as 'Billable Internal', workflow would not be required, and the Assignment Detail Status should remain as approved/assigned.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document