Search Results ra_site_uses_u1

Overview

AR.RA_SITE_USES_ALL is the Oracle Receivables (AR) transactional table that stores customer site use records — the business-purpose instances of a customer address. While AR.RA_ADDRESSES_ALL holds the physical address itself, RA_SITE_USES_ALL records how that address is used by the customer, for example as a Bill-To, Ship-To, Statement-To, Dunning-To, or Deliver-To location. Each row represents one such usage and carries the operational, financial, and tax attributes that govern transactions flowing through that site. In EBS 12.1.1 and 12.2.2, it is a core hub object for order-to-cash flows, referenced heavily by Order Management, Shipping, Payments, and Receivables modules.

The _ALL suffix indicates a multi-org (Operating Unit) aware table, controlled through the ORG_ID column. The heuristic Data Vault classification is hub-leaning: the table is centered on a stable business key (SITE_USE_ID) with many outbound and inbound foreign keys, but also carries descriptive and operational attributes that behave satellite-like. In practice it is best modeled as a hub with associated satellites for financial, shipping, and tax attributes. The table is owned by the AR schema and stored in tablespace APPS_TS_TX_DATA.

Key Information Stored

The documented schema contains 114 columns. The most significant are:

• SITE_USE_ID (NUMBER 15) — the surrogate primary key, enforced by RA_SITE_USES_PK and the unique index RA_SITE_USES_U1. This is the column users search for when querying ra_site_uses_u1.
• ADDRESS_ID — foreign key to RA_ADDRESSES_ALL, linking the site use to its physical address.
• SITE_USE_CODE — the business purpose (BILL_TO, SHIP_TO, STATEMENT, DUNNING, etc.).
• PRIMARY_FLAG — Y/N indicator of whether this site is the primary one for its use code.
• STATUS — site use status flag based on the CODE_STATUS lookup.
• CONTACT_ID — the primary contact associated with the site use.
• BILL_TO_SITE_USE_ID — self-referencing foreign key pointing to the related Bill-To site use.
• PAYMENT_TERM_ID — foreign key to RA_TERMS_B; drives due-date and aging calculations.
• TERRITORY_ID and PRIMARY_SALESREP_ID — sales territory and representative assignment.
• TAX_CODE, TAX_CLASSIFICATION, TAX_EXEMPT, and related tax columns — determine tax treatment of transactions.
• ORDER_TYPE_ID, PRICE_LIST_ID, WAREHOUSE_ID, SHIP_VIA, FREIGHT_TERM — order management defaults.
• ORG_ID — the Operating Unit that owns the row.
• Standard WHO and 20 GLOBAL_ATTRIBUTE descriptive flexfield columns.

The business-key candidate documented by unique index is SITE_USE_ID; two non-unique indexes support address-based and concurrent-program access.

Common Use Cases and Queries

Typical scenarios include retrieving all ship-to sites for a customer, validating a Bill-To before invoice creation, and reporting on tax-exempt sites. A common join pattern is:

• Joining RA_SITE_USES_ALL to RA_ADDRESSES_ALL on ADDRESS_ID to obtain street, city, and country details.
• Joining to RA_CUSTOMERS via the customer's address/site relationships to produce a customer-site listing.
• Filtering by SITE_USE_CODE = 'SHIP_TO' and PRIMARY_FLAG = 'Y' to isolate primary ship-to sites.
• Using BILL_TO_SITE_USE_ID to resolve the bill-to for a given ship-to.

Sample pattern:

SELECT su.site_use_id, su.site_use_code, su.primary_flag, a.address1, a.city
FROM ra_site_uses_all su, ra_addresses_all a
WHERE su.address_id = a.address_id
AND su.org_id = :org_id
AND su.site_use_code = 'SHIP_TO';

Reporting use cases include customer master extracts, tax-exemption audits, credit and collection reporting (via the Dunning-To and Statement-To sites), and data migration validation where ORIG_SYSTEM_REFERENCE is used to map legacy identifiers.

Related Objects

The table participates in a dense relationship network. The most significant related objects are:

• RA_ADDRESSES_ALL — joined on ADDRESS_ID; holds the physical address.
• RA_CUSTOMERS — references RA_SITE_USES_ALL via DUNNING_SITE_USE_ID and STATEMENT_SITE_USE_ID.
• RA_TERMS_B — joined on PAYMENT_TERM_ID; supplies payment terms.
• SO_HEADERS_ALL — references this table through INVOICE_TO_SITE_USE_ID and SHIP_TO_SITE_USE_ID.
• SO_LINES_ALL — references SHIP_TO_SITE_USE_ID.
• WSH_DELIVERIES — references ULTIMATE_SHIP_TO_ID and INTERMEDIATE_SHIP_TO_ID.
• PN_PAYMENT_ITEMS_ALL and PN_PAYMENT_TERMS_ALL — reference CUSTOMER_SITE_USE_ID for payment processing.
• AR_CUSTOMER_PROFILES — references SITE_USE_ID, holding profile-class values per site.
• MTL_INTERCOMPANY_PARAMETERS — references CUSTOMER_SITE_ID for intercompany flows.
• RA_SITE_USES_ALL self-reference — via BILL_TO_SITE_USE_ID.

Because this is documented Oracle internal data, direct DML should be avoided; changes should flow through supported Receivables APIs such as the Customer Interface or the Trading Community Architecture (TCA) APIs.