When Adding a Non Resource Management Resource/Employee As a Team Member to a Project, Workflow Is Trigger As If The Resource/Employee Is A Resource Management Resource.

(Doc ID 2324338.1)

Last updated on NOVEMBER 03, 2017

Applies to:

PeopleSoft Enterprise FIN Program Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Functionality

ACTUAL BEHAVIOR
---------------
Resource Management Workflow Triggers for Non Resource Management Workflow emplids in Program Mgmt

We have resource management, program management, proposal management, project costing and Contracts installed.

There are two issues:
a) IF a new resource is added on program management and the resource is not established in resource management, workflow is still being triggered.
b) We only changed the date and on the resource management BU options (page 1 screenshot), date change workflow was turned off. Still, date change workflow triggered under “Schedule Changes Pending Approval” grid when we changed the start date from 6/1/06 to 6/1/17.
 

EXPECTED BEHAVIOR
-----------------------
The schedule changes for a non RM resource should be in committed state as no specific approvals are required in RM as the resource is not an RM resource

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Program Management and Resource Management turned on in the installation Options
2. Resource Management Options has

Under Assignment Approval Required - "Resource Manager Approval Required" checked and
Under Date Change Approval Required - "Resource Manager Approval Required" UNCHECKED

3. KU0047 is not established as a resource in Resource Management in Demo
4. Now Assign this employee to a Project in demo, US004/000000000000165
5. Save. The resource is commited.
6. Now change either start or end date and save. The Resource status goes to "Requested"

Issue 1 : Based on the set up date changes does not require resource manager approvals. So this change should keep the resource assignment in a committed state
Issue 2 : The resource KU0047 is not established as a resource and hence the validation should not be checked for date changes and should leave the resource assignment in committed state.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms