Results for “rcv_routing_headers”

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

Overview

RCV_ROUTING_HEADERS is a compatibility view owned by the APPS schema within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the Purchasing (PO) product family but is primarily consumed by the Receiving (RCV) module. The object is documented as VALID and is a view rather than a physical table, meaning it does not store data independently — it projects rows from the Oracle Application Object Library (FND) lookup infrastructure. Its stated purpose is to expose receiving routing types, supplying the receiving sub-ledger with a list of valid routing header definitions (for example, standard, direct, or inspection-based receipt routing) that govern how inbound shipments flow through receipt and inspection processing.

Within the Oracle EBS reporting and integration landscape, RCV_ROUTING_HEADERS functions as a lookup abstraction layer. Rather than maintaining a dedicated routing header table for this narrow purpose, the application derives the data from the generic FND_LOOKUP_VALUES repository. This design allows routing types to be administered centrally through the Application Developer responsibility while remaining available to receiving-related views, concurrent programs, and inbound interfaces.

Underlying Base Objects

The documented base object referenced by this view is FND_LOOKUP_VALUES, accessed through the APPS synonym. The view text filters that repository for a single lookup type, RCV_ROUTING_HEADERS, together with three additional predicates: LANGUAGE = USERENV('LANG'), VIEW_APPLICATION_ID = 0, and SECURITY_GROUP_ID = 0. The LANGUAGE predicate ensures the description and meaning values are returned in the session's active language. The VIEW_APPLICATION_ID and SECURITY_GROUP_ID predicates restrict the result set to rows belonging to the shared, non-application-specific view layer, filtering out application-owned lookup entries. The net effect is that RCV_ROUTING_HEADERS presents only the enabled, translatable lookup values that define receiving routing types for the current session language.

Because the view inherits its columns from FND_LOOKUP_VALUES, its LAST_UPDATE_DATE, CREATED_BY, and related audit columns reflect the last change made to the underlying lookup row rather than to any receiving transaction.

Key Columns

• ROUTING_HEADER_ID — Derived as TO_NUMBER(LOOKUP_CODE) from the lookup row. This numeric identifier is the effective primary key exposed by the view and is used to join routing headers to routing detail and receiving transaction data.
• ROUTING_NAME — Maps to the MEANING column of the lookup, providing the user-facing name of the routing type.
• DESCRIPTION — Carries the lookup DESCRIPTION column, offering supplementary narrative for the routing type.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard FND descriptive flexfield columns. In the context of this lookup, these fields may hold implementation-specific supplementary attributes configured by the customer.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN record creation and modification metadata for the underlying lookup row. Note that the view text aliases LAST_UPDATED_BY while the documented column list shows LAST_UPDATED_LOGIN; both trace back to the FND audit trail.

Common Use Cases and Queries

The most frequent use is to populate or validate routing header references in receiving reports and interfaces. A typical query lists all available routing types in the current language:

SELECT ROUTING_HEADER_ID, ROUTING_NAME, DESCRIPTION FROM APPS.RCV_ROUTING_HEADERS ORDER BY ROUTING_HEADER_ID;

A second common pattern joins the view to receiving transaction tables to resolve the routing identifier captured on a receipt into a readable name. Because ROUTING_HEADER_ID is produced by a numeric conversion of LOOKUP_CODE, this join requires the lookup codes to be strictly numeric; implementations that depart from this convention should account for conversion errors. Finally, integration developers frequently extract the view's contents to synchronize routing definitions with external warehouse or WMS systems, using ROUTING_HEADER_ID as the stable cross-reference key and LAST_UPDATE_DATE for incremental delta extracts.