Results for “pending_from_ecn”

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

Overview

The BOM_OPERATIONAL_ROUTINGS_ERV view is a denormalized reporting and integration interface owned by the APPS schema in Oracle E-Business Suite. It belongs to the Bills of Material (BOM) product family and exposes operational routing header information for manufactured assemblies. The suffix "ERV" denotes an "Entity Relationship View," a naming convention Oracle uses for read-only views intended to supply join-ready data to reports, interfaces, and downstream applications without requiring consumers to reconstruct the underlying relational model.

This view flattens a routing record together with its owning organization, the routed assembly item, the routing revision, the completion subinventory, the completion locator, the production line, and, where applicable, a common (product family) item. Because it resolves these relationships internally, it is well suited to concurrent program extracts, custom reports, and integration feeds that require routing context in a single result set. It remains VALID in both 12.1.1 and 12.2.2.

Underlying Base Objects

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

• BOM_OPERATIONAL_ROUTINGS (synonym) — the driving routing header table, aliased BOR, supplying routing sequence, alternate designator, priority, CTP and CFM flags, attributes, and WHO columns.
• MTL_SYSTEM_ITEMS_VL (view) — joined twice: once as the routed assembly item (ITEMS) and once as the common product family item (ITEMS2).
• MTL_PARAMETERS (synonym) — source of the inventory organization code.
• HR_ALL_ORGANIZATION_UNITS_TL (synonym) — source of the organization name.
• MTL_RTG_ITEM_REVISIONS (synonym) — provides the routing process revision.
• MTL_SECONDARY_INVENTORIES (synonym) — joined with an outer (+) operator on completion subinventory.
• MTL_ITEM_LOCATIONS_KFV (view) — supplies the concatenated completion locator.
• WIP_LINES (synonym) — supplies the line code, outer-joined on LINE_ID.
• MTL_ITEM_FLEXFIELDS (view) — supplies the concatenated flexfield item number.

Most joins to the routing header are outer joins, meaning a routing record is returned even when the assembly, revision, subinventory, locator, or line is missing.

Key Columns

• ASSEMBLY_ITEM_ID, ORGANIZATION_ID, ROUTING_SEQUENCE_ID — the primary identifying keys for the routing header.
• ORGANIZATION_CODE / NAME — inventory organization code and organization unit name.
• CONCATENATED_SEGMENTS (item), DESCRIPTION, PRIMARY_UOM_CODE — the routed assembly and its attributes.
• PRODUCT_FAMILY_ITEM_ID — the product family item identifier, the column most relevant to product-family analysis.
• COMMON_ITEM, COMMON_ITEM_DESCRIPTION, COMMON_ASSEMBLY_ITEM_ID, COMMON_ROUTING_SEQUENCE_ID — common routing / product family associations.
• ALTERNATE_ROUTING_DESIGNATOR, PROCESS_REVISION, PRIORITY, ROUTING_TYPE, CFM_ROUTING_FLAG — routing classification.
• COMPLETION_SUBINVENTORY, LOCATOR, COMPLETION_LOCATOR_ID, SUB_LOCATOR_CONTROL, SERIALIZATION_START_OP — completion and locator control data.
• LINE_CODE, MIXED_MODEL_MAP_FLAG, CTP_FLAG, TOTAL_PRODUCT_CYCLE_TIME — line and planning attributes.
• ITEM_NUMBER (flexfield) and the standard WHO columns and ATTRIBUTE1–15.

Common Use Cases and Queries

Typical uses include product-family routing extracts, routing master reports, and integration to planning or MES systems. A representative query:

• List routings with their product family for an organization: SELECT organization_code, concatenated_segments, product_family_item_id, alternate_routing_designator, priority FROM bom_operational_routings_erv WHERE organization_code = :org ORDER BY concatenated_segments, priority;
• Return common/product-family item descriptions: SELECT concatenated_segments, common_item, common_item_description FROM bom_operational_routings_erv WHERE common_assembly_item_id IS NOT NULL;
• Extract completion and line detail: SELECT concatenated_segments, completion_subinventory, locator, line_code FROM bom_operational_routings_erv WHERE organization_id = :org_id;
• Filter by routing type or CTP flag: SELECT concatenated_segments, routing_type, ctp_flag FROM bom_operational_routings_erv WHERE organization_id = :org_id AND ctp_flag = 1;

Because all joins are resolved internally and most are outer joins, the view is convenient for reporting but should be filtered by ORGANIZATION_ID for performance on large item masters.