Results for “exchange_variance_account_id”

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

Overview

RCV_PARAMETERS is the organization-level receiving controls table in Oracle E-Business Suite, owned by the PO (Purchasing) schema and surfaced within the Receiving and Purchasing modules. Each row in this table defines the receiving policies, tolerances, defaults, and behavior flags that govern how receipts are processed, validated, and accounted for within a single inventory organization. Because receiving behavior in EBS is configured per organization rather than globally, RCV_PARAMETERS acts as the central configuration repository that the receiving transaction engine consults whenever a receipt, return, or correction is entered.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table is keyed by ORGANIZATION_ID and carries descriptive, context-dependent attributes (tolerances, exception codes, account references, and flags) rather than representing an independent business entity or a many-to-many association. It therefore behaves much like a satellite attached to the organization dimension, holding the receiving-specific descriptive and control attributes for each organization.

Key Information Stored

The table contains 61 documented columns in ETRM 12.2.2. The surrogate primary key is defined by RCV_PARAMETERS_PK on ORGANIZATION_ID, and a unique index RCV_PARAMETERS_U1 also exists on ORGANIZATION_ID, making the organization identifier the effective business key. The most operationally significant columns include:

• ORGANIZATION_ID — primary and business key; one receiving configuration row per inventory organization.
• QTY_RCV_TOLERANCE and QTY_RCV_EXCEPTION_CODE — quantity over-receipt tolerance and the action taken when the tolerance is breached.
• ENFORCE_SHIP_TO_LOCATION_CODE — controls whether receipt must match the ship-to location on the originating document.
• DAYS_EARLY_RECEIPT_ALLOWED and DAYS_LATE_RECEIPT_ALLOWED — date-window tolerances relative to the scheduled date.
• RECEIPT_DAYS_EXCEPTION_CODE — exception handling when the days tolerance is exceeded.
• RECEIVING_ROUTING_ID — foreign key to RCV_ROUTING_HEADERS, determining the routing used during receipt processing.
• ALLOW_SUBSTITUTE_RECEIPTS_FLAG, ALLOW_UNORDERED_RECEIPTS_FLAG, and ALLOW_EXPRESS_DELIVERY_FLAG — flags governing permitted receipt types.
• BLIND_RECEIVING_FLAG — whether quantities and items are hidden from the receiver at entry.
• RECEIVING_ACCOUNT_ID, CLEARING_ACCOUNT_ID, and the related variance accounts (INV_VARIANCE_ACCOUNT_ID, EXCHANGE_VARIANCE_ACCOUNT_ID, TAX_VARIANCE_ACCOUNT_ID, LCM_ACCOUNT_ID) — accounting references applied to receiving transactions.
• USER_DEFINED_RECEIPT_NUM_CODE, MANUAL_RECEIPT_NUM_TYPE, and NEXT_RECEIPT_NUM — receipt numbering rules and sequence control.
• ALLOW_CASCADE_TRANSACTIONS and PRE_RECEIVE — flags enabling cascading transactions and pre-receiving behavior.
• RECEIPT_ASN_EXISTS_CODE — handling when an advance shipment notice already exists.

Standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, and related) and twenty GLOBAL_ATTRIBUTE flexfields plus GLOBAL_ATTRIBUTE_CATEGORY are also present for extensibility, and the concurrent program columns (REQUEST_ID, PROGRAM_ID) track the last programmatic update.

Common Use Cases and Queries

Receiving administrators and support analysts commonly query this table to validate why a receipt was rejected, to compare receiving policies across organizations, or to audit tolerances prior to a configuration migration. A typical lookup returns the key tolerances and flags for a given organization:

• SELECT organization_id, qty_rcv_tolerance, qty_rcv_exception_code, days_early_receipt_allowed, days_late_receipt_allowed, blind_receiving_flag, allow_unordered_receipts_flag FROM rcv_parameters WHERE organization_id = :org_id;
• Reporting across organizations to identify inconsistent tolerances: SELECT organization_id, qty_rcv_tolerance, receiving_routing_id FROM rcv_parameters ORDER BY organization_id;
• Auditing account assignments: SELECT organization_id, receiving_account_id, clearing_account_id, inv_variance_account_id FROM rcv_parameters WHERE receiving_account_id IS NULL;
• Tracing the routing configuration by joining to RCV_ROUTING_HEADERS on receiving_routing_id.

These queries support month-end reconciliation, receipt-exception analysis, new-organization setup verification, and pre-upgrade impact assessments.

Related Objects

RCV_PARAMETERS is referenced and depended upon by several core objects in the Receiving and Purchasing flow. The documented foreign key links RECEIVING_ROUTING_ID to RCV_ROUTING_HEADERS, making that table the primary parent reference. Other significant related objects include:

• RCV_ROUTING_HEADERS — joined on RCV_PARAMETERS.RECEIVING_ROUTING_ID = RCV_ROUTING_HEADERS.ROUTING_HEADER_ID; defines receipt routing rules.
• RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS — receipt and transaction tables whose processing behavior is governed by these parameters.
• RCV_RECEIVING_TRANSACTIONS / receiving interfaces — consume tolerance and routing settings during transaction validation.
• HR_ALL_ORGANIZATION_UNITS and ORG_ORGANIZATION_DEFINITIONS — provide the organization context for ORGANIZATION_ID.
• PO_HEADERS_ALL / PO_LINES_ALL — purchasing documents whose receipts are validated against these controls.
• RCV_PARAMETERS_API and the Receiving open interface — the PL/SQL interfaces used to create or update receiving parameter records programmatically.

Together these objects form the configuration and transactional backbone that enforces consistent receiving behavior across each inventory organization in Oracle EBS 12.1.1 and 12.2.2.