Results for “bombv_eco_revised_components”

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

Overview

The BOMBV_ECO_REVISED_COMPONENTS view is a read-only reporting object owned by the APPS schema within the Bills of Material (BOM) module of Oracle E-Business Suite. It exposes engineering change order (ECO) revised bill of material component data in a flattened, presentation-ready format, joining component-level attributes against bill, item, and organization context. The view is documented as "Retrofitted," indicating it was carried forward from earlier EBS releases into 12.1.1 and 12.2.2 with minimal structural change. Its role is to support ECO review, component effectivity reporting, and integration extracts where revised component structures must be examined without navigating the full BOM schema.

Users frequently search this object in connection with the planning_percent attribute. In the view definition this is satisfied by the column PLANNING_PERCENT, which maps to the base column CO.PLANNING_FACTOR on BOM_INVENTORY_COMPONENTS.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following documented base objects:

• BOM_INVENTORY_COMPONENTS (VIEW) — aliased as CO; supplies the component rows, effectivity dates, quantities, planning factor, supply attributes, and flag columns.
• BOM_BILL_OF_MATERIALS (VIEW) — aliased as BI; supplies bill header context, including alternate designator and organization.
• MTL_SYSTEM_ITEMS (SYNONYM) — aliased as PA/item references for organization code and item identification.
• MTL_PARAMETERS (SYNONYM) — organization-level parameters.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — aliased as AL; provides the organization name.
• FND_GLOBAL (PACKAGE) — supplies session context such as the current user and responsibility.

The pseudo-columns prefixed with _KF: and _LA: are Oracle EBS descriptive flexfield and value-set translation constructs (Key Flexfield and Lookup Attribute tokens) that resolve display values at runtime for the consuming form or report.

Key Columns

• PLANNING_PERCENT — derived from PLANNING_FACTOR; the planning percentage applied to a component, controlling how much of the component quantity is included in planning calculations.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — component effectivity window.
• OPERATION_SEQUENCE_NUMBER — routing operation to which the component is assigned.
• PER_ASSEMBLY_QUANTITY — component quantity per assembly.
• PROJECTED_YIELD — component yield factor.
• MINIMUM_ALLOWED_QUANTITY / MAXIMUM_ALLOWED_QUANTITY — quantity range limits.
• ORGANIZATION_CODE, ORGANIZATION_NAME, ALTERNATE_BOM_CODE, ITEM_SEQUENCE_NUMBER — structural context.
• ECO_IMPLEMENTATION_DATE, COMMENTS, UPDATED_ON, CREATED_ON — ECO audit information.
• Boolean flag columns (e.g., INCLUDE_IN_COST_ROLLUP, CHECK_ATP, REQUIRED_FOR_REVENUE) resolved via MFG_LOOKUPS.

Common Use Cases and Queries

Typical usage centers on auditing revised components during ECO implementation and verifying planning percentages.

• Listing all revised components for an organization with their planning percentages:

SELECT organization_code, item_sequence_number, planning_percent, per_assembly_quantity
FROM   apps.bombv_eco_revised_components
WHERE  organization_code = :org;

• Filtering components whose planning percentage is below full inclusion:

SELECT bill_sequence_id, component_sequence_id, planning_percent
FROM   apps.bombv_eco_revised_components
WHERE  planning_percent < 100;

• Retrieving effectivity and ECO dates for change-impact review, joining bill_sequence_id and component_sequence_id back to base BOM tables where write-side detail is required.

Because the view is read-only and built on component views rather than writable tables, it should be used strictly for query and reporting; all maintenance of planning percent values is performed through the Bills of Material forms against the underlying base tables.