Search Results parent_sort_code




Overview
Explore in AI Chat

Overview

APPS.BOM_IMPL_INQUIRY_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as BOM.BOM_IMPL_INQUIRY_V. In Oracle EBS 12.1.1 and 12.2.2 it is classified as a view type used to simplify forms coding, and it supports the Bill of Materials implosion inquiry functionality. Implosion traverses the bill structure upward from a selected component to identify every parent assembly in which that component is used, and this view flattens the result of that traversal so that the Oracle Forms-based inquiry screen can display it without embedding complex hierarchical SQL directly in the form.

Because the view is explicitly designated as a forms-support construct, Oracle documentation warns that it is not recommended for direct querying or data manipulation and that its definition may change substantially in subsequent minor or major releases. It should therefore be treated as a read-only reporting and integration source rather than as a stable interface for data maintenance. The status of the object is VALID in the documented environment.

Underlying Base Objects

The documented referenced objects expose the view's dependency footprint across several EBS modules. BOM_GLOBALS supplies bill of materials profile and setup values, while BOM_SMALL_IMPL_TEMP is a temporary synonym that holds implosion results generated by the BOM implosion engine. FND_GLOBAL and FND_LOOKUP_VALUES provide application context such as organization and user identifiers and translated lookup meanings. HR_GENERAL, HR_ORGANIZATION_UNITS, and HR_SECURITY supply organization names and operating unit security restrictions.

Inventory master data is drawn from MTL_SYSTEM_ITEMS_B_KFV, which presents concatenated item key flexfield segments; MTL_ITEM_REVISIONS_B, which supplies revision labels; and MTL_PARAMETERS, which carries inventory organization parameters. MFG_LOOKUPS and INV_MEANING_SEL provide coded lookup descriptions, including basis type and effectivity control values. The combination of these objects means the view joins organizational, item, revision, and bill structure information into a single inquiry row per component-to-parent relationship.

Key Columns

The view returns a ROWID-based ROW_ID plus an ORGANIZATION_ID and ORGANIZATION_CODE for organization context. SEQUENCE_ID and LOWEST_ITEM_ID identify the implosion run and the starting component, while PARENT_ITEM_ID, COMPONENT_ITEM_ID, PARENT, COMPONENT_NAME, and PARENT_DESCRIPTION describe the assembly and component. CURRENT_LEVEL and SORT_CODE represent the implosion level and ordering sequence.

Bill structure attributes include COMPONENT_QUANTITY, BASIS_TYPE, COMPONENT_OP_SEQ_NUM, COMPONENT_REVISION, REVISION_LABEL, PARENT_ALTERNATE_DESIGNATOR, PARENT_ENGINEERING_BILL, CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, and IMPLEMENTED_FLAG. Effectivity fields include COMPONENT_EFFECTIVE_FROM and COMPONENT_EFFECTIVE_TO, both VARCHAR2(30), together with EFFECTIVITY_CONTROL and COMPONENT_EFFEC. Item and structure state is represented by ITEM_STATUS, ITEM_TYPE, DISABLED_FLAG, LIFECYCLE_ID, CURRENT_PHASE_ID, PARENT_UOM, and ORG_NAME.

Common Use Cases and Queries

Typical usage is component where-used analysis: identifying every parent assembly that consumes a given component within an organization, including effectivity windows.

  • Where-used listing filtered by component and organization.
  • Effectivity checks using COMPONENT_EFFECTIVE_FROM and COMPONENT_EFFECTIVE_TO.
  • Revision-level or change-notice impact analysis through COMPONENT_REVISION and CHANGE_NOTICE.
  • Engineering versus manufacturing bill comparison using PARENT_ENGINEERING_BILL.

A representative query is:

SELECT organization_code, parent, component_name, component_quantity, component_effective_from, component_effective_to FROM apps.bom_impl_inquiry_v WHERE organization_id = :org_id AND component_item_id = :component_item_id AND (component_effective_to IS NULL OR TO_DATE(component_effective_to,'DD-MON-RR') >= SYSDATE) ORDER BY current_level, sort_code;

Because the effectivity columns are stored as character strings, date comparisons require explicit TO_DATE conversion, and the END_DATE_ACTIVE predicate used in the base bill tables should be mirrored when filtering.