Quality Mass Search And Replace Copies Start Date from Original Specification Validity Rule Instead of Setting Start Date of New Spec VR to Current Date (Doc ID 2113389.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Process Manufacturing Product Development - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Quality Management Specification Validity Rules

ACTUAL BEHAVIOR
---------------
Patch 20028902 fixed an issue in which when creating a new spec validity rule using Mass Search and Replace, the start date on the new VR was set to the start date of the original VR instead of sysdate.

Customer has now applied patch 21356477, and this has broken again.

It appears that patch 21207935 undid the changes made in patch 20028902. Patch 21207935 was to correct a problem in which the validity rule API always set the start date to sysdate, regardless of what was passed in. It looks like the fix for 20028902 was what caused that problem.

EXPECTED BEHAVIOR
-----------------------
This needs to be fixed in such a way that the validity rule API respects the start date passed in, and that Mass Search and Replace passes in sysdate as the start date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set revision control on specs to Optional or On
2. Use Mass Search and Replace to update a spec
3. When asked whether to create a new version, answer yes

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, VR start date implies that it was valid in the past when in fact it was not.

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