Quality Plans No Longer Default Values For Populating The Plans After CMRO RUP6 Applied (Doc ID 1568182.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Complex Maintenance, Repair & Overhaul - Version 12.1.3 and later
Information in this document applies to any platform.
QualityMrContextVO.xml
QualityMrContextVORowImpl.java
QualityResultsCollAMImpl.java

***Checked for the relevance on 3-Apr-2015***

Symptoms

On : 12.1.3.6 version, Production

Post <Patch 14642977>:R12.AHL.B, receive error using cMRO’s Data Clerk or Production Execution screens. Quality Plans no longer default values for populating the plans.

In the prior release, the QA information was captured on cMRO forms and then when the user saves the record, it would call an API to populate the quality plan information and apparently, the sql that was associated to the collection plan element, which was seeded form Oracle, would populate for the Maintenance Workorder, Maintenance Workorder Status, Maintenance Requirement, etc… Now, it does not do that.


ERROR
1. Work Order is a mandatory element but a null value was supplied. (CHAR_ID=165)
2. Work Order Status is a mandatory element but a null value was supplied. (CHAR_ID=98)


STEPS
cMRO’s Data Clerk or Production Execution screens
Quality Plans no longer default values for populating the plans



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