Wrong Counter Reading When Using Past-Dated Removal Date in a Sub-Configuration (with Patch 18157486:R12.AHL.B) (Doc ID 1919458.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
When performing a past dated removal of an on wing Sub-configuration (Engine #2) Sub-Configuration (Accessory Section Module) the following behavior were observed (Note Engine #1 Accessory Section Module was not removed)

Engine #2 - Accessory Section Module Counters update correctly; Accessory Section Module Children update correctly
Engine #1 – Accessory Section Module Counters are not updated (as expected); Accessory Section Module Children are updated the same as the Children from Engine #2 Accessory Section Module (totally unexpected).



EXPECTED BEHAVIOR
This is not only totally unexpected but also totally unacceptable as Counters are being updated to Item Instances that should not be updated.


STEPS
Responsibility – Complex MRO User
Execution>Production Planning>Work Orders
Select Visit Number or Work Order Number
Click Go
Select Perform Part Removal/Install
Click Go
Unit Configuration Part Changes Screen Opens
Remove Engine #2 Accessory Section Module Item Instance using Past Dated Removal Date and Other Removal Data
Click Remove Button

Responsibility – Complex MRO User
Configuration Management>Unit Configuration>Search Product
Advanced Item Instance Search Screen Opens
Select Item Instance
Click Search
Select Counters
Click Go
Item Instance Details Screen Opens


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