Search Results RCV_ROUTING_HEADERS




Overview
Explore in AI Chat

Overview

The RCV_ROUTING_HEADERS view is a critical reference data object within the Oracle E-Business Suite Purchasing (PO) module. It serves as a standardized interface for querying the valid receiving routing types available in the system. The view is built directly upon the Oracle Applications Foundation (FND) table FND_LOOKUP_VALUES, which is the central repository for all lookup codes. Its primary role is to provide a clean, application-specific representation of routing types—such as Standard, Direct, or Inspection—which govern the workflow for receiving purchased items into inventory. This view ensures that all queries for routing information are language-sensitive and adhere to the standard security model, making it the preferred source for this data in reports, forms, and program logic.

Key Information Stored

The view presents a transformed subset of columns from the underlying FND_LOOKUP_VALUES table. The most significant columns include ROUTING_HEADER_ID, which is the numeric conversion of the LOOKUP_CODE and serves as the primary identifier for a routing type. The ROUTING_NAME column contains the translated, user-friendly meaning of the routing (e.g., "Standard Receiving"). Standard Oracle audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) track the object's history. The view also exposes fifteen descriptive flexfield attribute columns (ATTRIBUTE1-15) and an ATTRIBUTE_CATEGORY for custom extensions, along with a DESCRIPTION column for further detail. The view's WHERE clause filters specifically for the 'RCV_ROUTING_HEADERS' lookup type, the user's session language, and a standard security context.

Common Use Cases and Queries

This view is predominantly used in reporting and data validation scenarios related to the receiving process. A common use case is to generate a list of all active routing types for a setup or configuration report. Another frequent application is joining this view to transactional tables like RCV_SHIPMENT_HEADERS or PO_HEADERS_ALL to display the routing name alongside shipment data in operational or analytical reports. For instance, a query to list all receipts with their routing type would typically join on the routing identifier. Developers also reference this view within PL/SQL code to validate routing inputs or to populate list of values (LOVs) in custom forms. A basic query to retrieve all routings would be: SELECT routing_header_id, routing_name, description FROM apps.rcv_routing_headers ORDER BY routing_name;

Related Objects

The RCV_ROUTING_HEADERS view is intrinsically linked to the FND_LOOKUP_VALUES base table. Its primary relationship within the Purchasing schema is to transactional tables that store a ROUTING_HEADER_ID. The most direct link is typically to the RCV_SHIPMENT_HEADERS table, where the ROUTING_HEADER_ID column defines the routing for a specific receipt. It may also relate to purchasing document lines or supplier site settings that define default receiving instructions. The view itself does not define database foreign keys, but the ROUTING_HEADER_ID it provides is the logical foreign key value used throughout the receiving sub-module. Key joins are made on the condition rcv_shipment_headers.routing_header_id = rcv_routing_headers.routing_header_id.