Search Results ship_to_cust_acct_id




Overview

AR.AR_RDR_PARAMETERS_GT is a global temporary table owned by the Oracle Receivables (AR) schema. It functions as a transient staging structure used by the Receivables data-parameter resolution process, most commonly associated with Revenue Data Recording (RDR) and related transaction parameter derivation workflows. As a global temporary table, its contents are session-scoped: the current session can see only the rows it inserted, and other concurrent sessions cannot access them. The table carries a data duration of SYS$TRANSACTION, meaning rows persist only until the transaction completes, after which Oracle automatically removes the data. This design makes the table suitable for short-lived intermediate processing rather than persistent storage.

From a Data Vault modeling perspective, the mined relationship metadata suggests a heuristic classification of standalone. The table is not identified as a hub, link, or satellite, but it does carry several foreign-key-style references to core master and transaction tables. This classification should be treated as a modeling suggestion only; in practice the table behaves as an ephemeral parameter collection point populated by PL/SQL processing logic.

Key Information Stored

The documented physical schema in ETRM 12.2.2 defines 23 columns. The table does not expose an explicit surrogate primary key in the documented metadata; SOURCE_LINE_ID appears first in the column list and is the most likely candidate for a source line identifier, though no unique index is documented. The most significant columns include:

Common Use Cases and Queries

This table is typically populated and consumed by Receivables concurrent programs and PL/SQL packages during transaction creation, import, or revenue recognition processing. Because it is a global temporary table scoped to the session and transaction, direct reporting against it is generally limited to diagnostic and debugging scenarios. A common pattern is to join the staged parameters back to the referenced master tables to validate ship-to resolution:

SELECT g.SOURCE_LINE_ID, g.SHIP_TO_CUST_ACCT_ID, g.SHIP_TO_SITE_USE_ID, hca.account_number
FROM AR.AR_RDR_PARAMETERS_GT g
JOIN HZ_CUST_ACCOUNTS hca ON hca.cust_account_id = g.SHIP_TO_CUST_ACCT_ID;

Other practical uses include verifying that profile class and transaction type parameters resolve correctly, auditing memo line associations, and troubleshooting ship-to site use mismatches in import failures. Queries should be run within the originating session, since other sessions cannot observe the temporary rows.

Related Objects

The table's documented foreign key relationships point to several core Receivables and Trading Community objects:

  • HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID; provides customer account master data.
  • HZ_CUST_ACCT_SITES_ALL — joined on CUST_ACCT_SITE_ID; provides account site details.
  • HZ_CUST_PROFILE_CLASSES — joined on PROFILE_CLASS_ID; provides profile class definitions.
  • RA_CUST_TRX_TYPES_ALL — joined on CUST_TRX_TYPE_ID; provides transaction type definitions.
  • AR_MEMO_LINES_ALL_B — joined on MEMO_LINE_ID; provides memo line information.
  • AR_RDR_PARAMETERS_GT (APPS synonym) — the APPS-level synonym through which the table is typically accessed.

Together these references position the table as a transient parameter workspace within the broader Receivables data model, with the SHIP_TO_CUST_ACCT_ID and SHIP_TO_SITE_USE_ID columns serving as the primary linkage for ship-to address resolution.