Maintenance Requirement Combo Of Master Config. Position For A Sub-config Not Calculated Correctly (Doc ID 1511027.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.
AHLVPOSB.pls
AHL_MC_PATH_POSITION_PVT
ahl_mc_path_positions
ahl_applicable_instances
Map_instance_to_positions

Symptoms

ACTUAL BEHAVIOR
When the Maintenance Requirement (MR) Effectivity is combination of Master Configuration Position for a Sub-config that is associated to Unit Config that is associated to the Product Classification (PC) node, and not to a MC node, the MR's Affected Item list displays items that are not actually calculated by the Unit Maintenance Plan (UMP).


EXPECTED BEHAVIOR
The desired outcome is that you could select the MC position, even if it is a sub-node and if it is associated to a parent node, it would follow the effectivity to its parent configuration. This way, you could have the effectivity for sub-configs in the PC structure, regardless of their installation status, without maintaining multiple effectivity rows to handle multiple scenarios.


STEPS
After running BUE successfully, they made changes in the effectivities .. then change the MC Position references before re-running the UMP program.  Now, the Maintenance Plan was calculated against the items that were shown in the Affected Items list.

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