Results for “inventory_master_org_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AHL_ITEM_COMP_DETAILS is a transactional detail table within the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module. It stores the individual line-level records that make up an Item Composition, specifically the Non-Tracked Items and Item Groups associated with a composition defined in the corresponding header table. In the Oracle EBS 12.1.1 and 12.2.2 data models, this table acts as the granular extension of the composition header, allowing maintenance planners to assemble bills of material-style groupings that drive MRO work order execution and material planning.

Based on the foreign key topology mined from the ETRM metadata, the table exhibits the characteristics of a link entity in a Data Vault heuristic classification. It resolves a many-to-many style relationship between the Item Composition header and both inventory items and item groups, carrying descriptive and quantitative attributes in the same structure. The table is owned by the AHL schema, is marked VALID in the data dictionary, and contains 32 documented columns.

Key Information Stored

The primary key of the table is ITEM_COMP_DETAIL_ID, defined through AHL_ITEM_COMP_DETAILS_PK. A unique index, AHL_ITEM_COMP_DETAILS_U1, also exists on this column, confirming it as the business-key candidate. The most significant columns include:

• ITEM_COMPOSITION_ID – foreign key back to the composition header; identifies the parent composition to which the detail belongs.
• INVENTORY_ITEM_ID and INVENTORY_MASTER_ORG_ID – identify the specific non-tracked inventory item and its master organization.
• ITEM_GROUP_ID – foreign key to AHL_ITEM_GROUPS_B, linking the detail to a defined item group when applicable.
• UOM_CODE – unit of measure for the detail quantity.
• QUANTITY – the required quantity of the associated item or group.
• LINK_COMP_DETL_ID – self-referencing link connecting related composition detail lines.
• EFFECTIVE_END_DATE – date on which the composition detail ceases to be effective.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security access.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard Who columns supporting concurrency and audit.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – DFF (descriptive flexfield) segments for extensible customer attributes.

Common Use Cases and Queries

This table is queried whenever MRO users need to explode an item composition into its constituent non-tracked items or item groups. A typical reporting query joins the detail to the header and to AHL_ITEM_GROUPS_B:

• Listing all details for a given composition: SELECT * FROM AHL_ITEM_COMP_DETAILS WHERE ITEM_COMPOSITION_ID = :comp_id;
• Resolving item groups: join ITEM_GROUP_ID to AHL_ITEM_GROUPS_B to obtain group names.
• Filtering effective records: apply EFFECTIVE_END_DATE IS NULL OR EFFECTIVE_END_DATE > SYSDATE.
• Security-scoped reporting: constrain by SECURITY_GROUP_ID for multi-org visibility.

Downstream uses include work definition generation, maintenance bill of material reporting, and integration extracts into planning systems.

Related Objects

Key related objects and join columns derived from the documented foreign keys include:

• AHL_ITEM_GROUPS_B – joined via ITEM_GROUP_ID.
• FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID.
• The Item Composition header table – joined via ITEM_COMPOSITION_ID.
• AHL_ITEM_COMP_DETAILS (self) – joined via LINK_COMP_DETL_ID.
• Inventory item master (MTL_SYSTEM_ITEMS_B) – implicitly joined via INVENTORY_ITEM_ID and INVENTORY_MASTER_ORG_ID.