Counter Entries And Corrections Do Not Cascade Prior To The First Part Change (Doc ID 2172361.1)

Last updated on JUNE 12, 2017

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
---------------
Prior to performing a Part Change, using a cMRO Visit and work order, counter entries and corrections cascade down the unit configuration.

However, once a part change is performed, the counter entries and corrections do not cascade, and do not tell you they are not cascading. This applies to
parts even unaffected by the parts change.

STEPS
-----------------------
Prior to performing a Part Change, using a cMRO Visit and work order, counter entries and corrections cascade down the unit configuration. However, once a part change is performed, the counter entries and corrections do not cascade, and do not tell you they are not cascading. This applies to parts even unaffected by the parts change.

Steps:
a. Parts changed
b. Counter readings entered prior to, and after part change.
c. Change to one of the readings entered prior to the part change, and change to one after the part change
The counter entry and correction functionality was introduced in cMRO patch 12.1.3.7

Changes

 Behaviour observed post 12.1.3.7 cMRO Patch.

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