Results for “routing_no”

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

Overview

PMIBV_ROUTING_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the Process Manufacturing Intelligence (PMI) product family. Its documented purpose is to serve as a List of Values (LOV) view for routing records. Routings in Oracle Process Manufacturing define the sequence of operations and resources required to manufacture a product, and this view exposes a compact, denormalized projection of that data specifically shaped for LOV consumption.

In Oracle EBS 12.1.1 and 12.2.2, the view is registered as VALID and is intended for form-based and concurrent-program LOV usage rather than as a general-purpose reporting entity. Because it is defined WITH READ ONLY, no DML is permitted against it; inserts, updates, and deletes must target the underlying base object. Its role is therefore presentation and lookup: it supplies the routing number, description, and class values that populate selection fields in process manufacturing forms and related inquiry pages.

Underlying Base Objects

The view is defined by a single SELECT statement against one documented base object:

• FM_ROUT_HDR — the routing header table, referenced through a SYNONYM in the APPS schema.

The view definition is documented as follows:

SELECT ROUTING_NO, ROUTING_DESC, ROUTING_CLASS
FROM FM_ROUT_HDR
WITH READ ONLY

Because it is a single-table view with no joins, filters, or WHERE clause, the row count and cardinality of PMIBV_ROUTING_LOV_V mirror FM_ROUT_HDR exactly. Every routing header record is returned, subject to the standard APPS schema synonym resolution. There is no organization or security filter embedded in the view text; any restriction by operating unit, organization, or responsibility is applied by the consuming form or query, not by the view itself. This is a relevant consideration when integrating the view into custom reports, since the full set of routing headers will be visible to any user or process with SELECT privilege on the view.

Key Columns

The view exposes three columns, each mapped directly from the routing header table:

• ROUTING_NO — the routing number, the primary human-readable identifier for a routing. This is the value typically returned to the calling field when an LOV selection is made.
• ROUTING_DESC — the descriptive text associated with the routing. This is the column most commonly displayed as the visible LOV entry, and it is the term matched by the user search "routing_desc."
• ROUTING_CLASS — the routing class, used to categorize routings. In process manufacturing, this value supports grouping of routings by type or purpose and is frequently used as an additional LOV filter criterion.

No additional attributes such as organization, version, or status are exposed. Where such detail is required, the base table FM_ROUT_HDR or a broader routing view must be queried directly.

Common Use Cases and Queries

The principal use case is populating routing selection fields in Oracle Process Manufacturing forms, where the LOV displays ROUTING_DESC and returns ROUTING_NO. Custom inquiries, reports, and integrations that need a lightweight routing lookup frequently query the view for the same purpose.

• Retrieve all routings: SELECT ROUTING_NO, ROUTING_DESC, ROUTING_CLASS FROM APPS.PMIBV_ROUTING_LOV_V;
• Filter by description: SELECT ROUTING_NO, ROUTING_DESC FROM APPS.PMIBV_ROUTING_LOV_V WHERE UPPER(ROUTING_DESC) LIKE UPPER(:p_search||'%');
• Filter by class: SELECT ROUTING_NO, ROUTING_DESC FROM APPS.PMIBV_ROUTING_LOV_V WHERE ROUTING_CLASS = :p_class;
• Resolve a code from description: SELECT ROUTING_NO FROM APPS.PMIBV_ROUTING_LOV_V WHERE ROUTING_DESC = :p_desc;

Because the view is read-only and unfiltered, queries should apply their own WHERE predicates and validate that returning every routing header is acceptable for the intended audience.