Search Results ahl_mc_relationships_v




Overview
Explore in AI Chat

Overview

AHL_MC_RELATIONSHIPS_V is an APPS-owned database view in the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul (CMRO). It exposes the node-level details of a Master Configuration, with the descriptive lookup columns resolved to their human-readable meanings. A Master Configuration defines a hierarchical bill-of-material style structure for a complex asset or assembly, and each row in the underlying AHL_MC_RELATIONSHIPS table represents a relationship (node position) within that structure. The view enriches those raw node records by resolving the position reference and position necessity codes against FND_LOOKUP_VALUES_VL and by joining item group details from AHL_ITEM_GROUPS_V.

The view is primarily consumed for reporting, inquiry screens, and integration extracts, where users need to see decoded descriptions rather than raw lookup codes. Because the lookup joins are outer joins, rows are still returned even when a code has no matching lookup entry, which keeps the view tolerant of incomplete or historical lookup configuration.

Underlying Base Objects

The documented base objects referenced by the view are:

The join conditions are: FPRC.LOOKUP_TYPE = 'AHL_POSITION_REFERENCE' matching POSITION_REF_CODE, FPNC.LOOKUP_TYPE = 'AHL_POSITION_NECESSITY' matching POSITION_NECESSITY_CODE, and MCR.ITEM_GROUP_ID = IGV.ITEM_GROUP_ID. The lookup joins are outer joins (+), and the item group join is also outer.

Key Columns

Common Use Cases and Queries

A frequent scenario is retrieving the descriptive attributes of every node in a configuration, including the item group description. For example, to find nodes by group description:

  • Filter on GROUP_DESC using a LIKE predicate to locate configurations containing a particular item group.
  • Join MC_HEADER_ID to the Master Configuration header to report the full structure.
  • Order by PARENT_RELATIONSHIP_ID and DISPLAY_ORDER to reproduce the hierarchy.

Sample SQL:

SELECT mc_header_id, relationship_id, parent_relationship_id,
       position_key, group_name, group_desc,
       position_ref_meaning, position_necessity_meaning,
       uom_code, quantity, display_order
 FROM apps.ahl_mc_relationships_v
 WHERE group_desc LIKE '%<search_term>%'
       AND NVL(active_end_date, SYSDATE + 1) > SYSDATE
 ORDER BY mc_header_id, parent_relationship_id, display_order;

Because the view already decodes lookups and joins item groups, it eliminates the need to write the underlying three-way join in ad hoc reports, making it the preferred source for Master Configuration node reporting and integration extracts.