Results for “ra_site_uses”

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

Overview

RA_SITE_USES is a Receivables (AR) module view in Oracle EBS 12.1.1 and 12.2.2 that presents site use information associated with customers, addresses, and tax attributes. Within Oracle Receivables, a "site use" represents the specific business purpose assigned to a customer address — for example, Bill-To, Ship-To, or Statement-To — and RA_SITE_USES consolidates these records together with tax-related, financial, freight, and descriptive flexfield attributes.

The view plays a significant role in reporting and integration because it exposes both operational site use data and tax configuration fields such as TAX_CODE, TAX_CLASSIFICATION, TAX_EXEMPT, and TAX_EXEMPT_REASON_CODE on a single flattened structure. This makes RA_SITE_USES particularly useful for reporting on tax treatment by customer site, auditing exemption usage, and supporting downstream integrations that need customer address context joined with tax classification information.

Underlying Base Objects

According to the documented ETRM metadata for this object, no base objects are explicitly documented, and the referenced base objects field is listed as "none documented." The Implementation/DBA Data likewise indicates that the object is "Not implemented in this database," meaning the view is not physically deployed in the instance from which the metadata was captured.

In functional terms, RA_SITE_USES is understood to be defined over the RA_SITE_USES_ALL base table (with the standard _ALL naming convention supporting multi-organization data), which stores customer site use records for Receivables. The ORG_ID column exposed by the view reflects this multi-org orientation. Because the ETRM metadata does not document the exact view definition, the column list rather than a formal base-object mapping is the authoritative reference for how RA_SITE_USES relates to its underlying tables.

Key Columns

The view exposes a broad set of columns that can be grouped as follows:

• Tax attributes: TAX_CODE, TAX_CLASSIFICATION, TAX_EXEMPT, TAX_EXEMPT_NUM, TAX_EXEMPT_REASON_CODE, TAX_REFERENCE, TAX_HEADER_LEVEL_FLAG, TAX_ROUNDING_RULE, and the GL_ID_TAX accounting reference.
• Site use identity: SITE_USE_ID, SITE_USE_CODE, ADDRESS_ID, LOCATION, PRIMARY_FLAG, STATUS, CONTACT_ID, ORG_ID, and BILL_TO_SITE_USE_ID.
• Shipping and order defaults: SHIP_PARTIAL, SHIP_VIA, FOB_POINT, FREIGHT_TERM, WAREHOUSE_ID, ORDER_TYPE_ID, PRICE_LIST_ID, and TERRITORY_ID.
• Financial and accounting: PAYMENT_TERM_ID, GL_ID_REC, GL_ID_REV, GL_ID_FREIGHT, GL_ID_CLEARING, GL_ID_UNBILLED, GL_ID_UNEARNED, and FINCHRG_RECEIVABLES_TRX_ID.
• Accrual tracking: LAST_ACCRUE_CHARGE_DATE, SECOND_LAST_ACCRUE_CHARGE_DATE, LAST_UNACCRUE_CHARGE_DATE, SECOND_LAST_UNACCRUE_CHRG_DATE.
• Descriptive flexfields: ATTRIBUTE_CATEGORY through ATTRIBUTE25, plus GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–20.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

A frequent scenario is identifying the tax classification and exemption status for each customer site, which supports tax reporting and compliance review.

Sample query — tax classification by site use:

SELECT SITE_USE_ID, SITE_USE_CODE, ADDRESS_ID, TAX_CODE, TAX_CLASSIFICATION, TAX_EXEMPT, TAX_EXEMPT_NUM
FROM RA_SITE_USES
WHERE TAX_CLASSIFICATION IS NOT NULL;

Sample query — exempt sites by organization:

SELECT ORG_ID, SITE_USE_ID, TAX_EXEMPT_REASON_CODE, TAX_EXEMPT_NUM
FROM RA_SITE_USES
WHERE TAX_EXEMPT = 'Y'
ORDER BY ORG_ID, SITE_USE_ID;

Sample query — active primary bill-to sites with payment terms:

SELECT SITE_USE_ID, PRIMARY_FLAG, STATUS, PAYMENT_TERM_ID, CONTACT_ID
FROM RA_SITE_USES
WHERE SITE_USE_CODE = 'BILL_TO'
AND PRIMARY_FLAG = 'Y'
AND STATUS = 'A';

Because the ETRM metadata records no documented base objects and marks the view as not implemented in the captured database, analysts should confirm column availability and multi-org filtering against their specific 12.1.1 or 12.2.2 instance before relying on RA_SITE_USES in production queries.