Step dependency is Changed on a Routing with Version Control On and No New Version of the Routing is Created
(Doc ID 2487966.1)
Last updated on DECEMBER 13, 2021
Applies to:
Oracle Process Manufacturing Product Development - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Other Issues
ACTUAL BEHAVIOR
--------------------------------
Able to change a Routing with version control set but no new version is created
Within a Routing that has a status of Approved for General Use, when the users navigate to the Step Dependencies screen, they are able to change the Dependencies without a new version being required even though Routing version control is set on
EXPECTED BEHAVIOR
-----------------------
Would expect a new version of the Routing to be created.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use Process Engineer responsibility
2. Click on Process Routings form
3. Create a routing with 2 steps and Save. Change status to Approved for General Use
4. Query up routing created and navigate to Step Dependencies
5. Change a step dependency and Save
6. Note new version of routing is NOT created.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use routings version control when changing step dependencies on a routing.
Cause
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
Symptoms |
Cause |
Solution |
References |