Search Results rcv_parameters

Overview

The RCV_PARAMETERS table is a core setup and control table within the Oracle E-Business Suite Purchasing (PO) module. It stores organization-level parameters that govern the default behavior and rules for the receiving process. Each row in this table defines the receiving configuration for a specific inventory organization, acting as a central control point for how receipts, inspections, and deliveries are processed. Its existence is critical for the operational flow of the Receiving and Inventory modules, ensuring that transactions adhere to the defined business policies for material handling.

Key Information Stored

The table's primary key is ORGANIZATION_ID, establishing a one-to-one relationship with each operational inventory organization. Key columns include RECEIVING_ROUTING_ID, which links to the RCV_ROUTING_HEADERS table to define the default routing (e.g., Direct Delivery, Inspection Required) for receipts. Other significant parameters typically stored in this table control settings such as whether to allow substitute receipts, enforce receipt date against the purchase order date, default tolerances for over and under receipts, and whether to enable lot and serial number control at receipt. These settings provide the foundational rules that the receiving transaction forms and underlying processing logic enforce.

Common Use Cases and Queries

A primary use case is validating or reporting on the receiving setup across an enterprise. For instance, identifying all organizations configured for mandatory inspection routing to assess process bottlenecks. A common diagnostic query retrieves the basic receiving parameters for a specific organization to verify configuration. Sample SQL patterns include joining with ORG_ORGANIZATION_DEFINITIONS for organization names and with RCV_ROUTING_HEADERS to decode the routing name.

• Sample Query: SELECT org.organization_code, rp.* FROM rcv_parameters rp, org_organization_definitions org WHERE rp.organization_id = org.organization_id ORDER BY org.organization_code;
• Reporting Use Case: Generating a compliance report showing which organizations have not enforced receipt date rules, which may be critical for financial period close.

Related Objects

The RCV_PARAMETERS table has defined relationships with several key objects, primarily through foreign key constraints. As documented, a critical foreign key exists on the RECEIVING_ROUTING_ID column, referencing the RCV_ROUTING_HEADERS table. This relationship ensures that the default routing specified in the parameters is a valid, predefined routing method. The table is also heavily referenced by various Receiving transaction forms, concurrent programs, and underlying PL/SQL package logic (e.g., within PO and INV modules) that read its parameters to control application behavior. While not listed in the provided metadata, it is commonly joined with MTL_PARAMETERS for a complete view of an organization's inventory and receiving setup.

• Foreign Key Relationship: RCV_PARAMETERS.RECEIVING_ROUTING_ID references RCV_ROUTING_HEADERS.
• Primary Key: ORGANIZATION_ID (links to ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_ID).