Search Results end_effectivity_date




Overview
Explore in AI Chat

Overview

APPS.BOMBV_FLOW_ROUTING_PROCESSES is a read-only Oracle EBS view that exposes flow manufacturing routing process (operation) information for assemblies configured as flow routings. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, the view serves as a reporting and integration surface over the routing definition data maintained in Oracle Bills of Material and Oracle Flow Manufacturing. Its columns carry business-facing names (for example SEQUENCE_NUMBER, START_EFFECTIVE_DATE, END_EFFECTIVITY_DATE, OPERATION_YIELD) that map directly to underlying BOM operation sequence attributes, making the view convenient for extracts, custom reports, and interface programs that need routing process details without joining the base tables manually.

The view is defined WITH READ ONLY, so it is intended strictly for query access. The trailing predicate on OP.ORGANIZATION_ID combined with the "SEC:" prefix indicates that the view is subject to Oracle's organization-level security (MOAC) filtering, meaning results are restricted to the operating units and inventory organizations the querying user is authorized to access.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

Because the view joins the routing header, its processes, the organization definition, and the item master, it consolidates data that would otherwise require a multi-table join across BOM and inventory schemas.

Key Columns

Notable columns exposed by the view include:

Common Use Cases and Queries

Typical uses include reporting active flow routing processes for an organization, extracting yield and time standards, and driving downstream interfaces. Because the END_EFFECTIVITY_DATE maps to the operation disable date, a common query filters for currently effective processes:

  • Reporting all processes for an assembly within an organization, ordered by SEQUENCE_NUMBER.
  • Identifying processes whose END_EFFECTIVITY_DATE is null or in the future (still effective).
  • Auditing yield, planning percent, and calculated versus entered time values.

Sample SQL:

SELECT sequence_number, organization_code, alternate_routing_code, description, start_effective_date, end_effectivity_date, operation_yield FROM apps.bombv_flow_routing_processes WHERE organization_code = :org AND (end_effectivity_date IS NULL OR end_effectivity_date > SYSDATE) ORDER BY sequence_number;

Results are automatically constrained by organization security, so callers need only supply the organization and any item or routing filters relevant to their report.