Search Results rrs_site_uses




Overview
Explore in AI Chat

Overview

RRS_SITE_USES is a table owned by the RRS schema within the Oracle E-Business Suite Site Management module (RRS). It stores the individual use assignments that apply to a site record, allowing a single site to carry multiple functional roles — such as billing, shipping, receiving, or payment — without duplicating the underlying site definition. In Oracle EBS 12.1.1 and 12.2.2 this pattern mirrors the classic party-site model, where a site is a physical or logical location and site uses enumerate the operational purposes for which that location may be referenced. The table is a core supporting structure for downstream transactional and setup flows that validate whether a given site may be used for a particular activity.

Based on the foreign-key structure mined from the ETRM 12.2.2 metadata, the heuristic Data Vault classification is satellite-leaning. The table carries descriptive and state attributes (status, primary flag, audit columns) that describe a parent site entity, which is consistent with satellite behaviour rather than a pure hub or link. This classification should be treated as a modeling suggestion only.

Key Information Stored

The physical schema documents 11 columns. The most significant are listed below.

  • SITE_USE_ID — surrogate primary key, constrained by RRS_SITE_USES_PK and additionally by unique index RRS_SITE_USES_U1. This is the row-level identifier used by downstream foreign keys.
  • SITE_ID — foreign key to the parent site record; the primary join column for retrieving all uses belonging to a site.
  • SITE_USE_TYPE_CODE — the business classification of the use (for example, a billing or shipping role). Together with SITE_ID it forms the unique index RRS_SITE_USES_U2, making it a business-key candidate that guarantees one row per site/use-type combination.
  • STATUS_CODE — the lifecycle state of the use, typically controlling whether the use is active or inactive.
  • IS_PRIMARY_FLAG — flags the primary use for a site, used where a site must nominate a default role.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the ADF/BC4J framework for concurrent update control.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing who created and last changed the record.

Common Use Cases and Queries

Typical scenarios include validating that a site may be used for an activity, reporting active uses per site, and resolving the primary use for a location. A common query pattern is:

  • Retrieving all active uses for a site:
    SELECT su.site_use_id, su.site_use_type_code, su.status_code, su.is_primary_flag FROM rrs_site_uses su WHERE su.site_id = :site_id AND su.status_code = 'A';
  • Locating the primary use:
    SELECT site_use_id FROM rrs_site_uses WHERE site_id = :site_id AND is_primary_flag = 'Y';
  • Identifying sites that hold a specific use type:
    SELECT site_id FROM rrs_site_uses WHERE site_use_type_code = :use_type AND status_code = 'A';

Reporting typically joins RRS_SITE_USES to the parent site table to present site name alongside use type, and filters on STATUS_CODE to exclude retired uses.

Related Objects

  • RRS_SITE_USES (parent site record) — the FK on RRS_SITE_USES.SITE_ID links each use to its owning site; joins are performed on SITE_ID.
  • RRS_SITE_USES_PK — primary-key constraint indexed on SITE_USE_ID, referenced by dependent child tables.
  • RRS_SITE_USES_U1 — unique index on SITE_USE_ID.
  • RRS_SITE_USES_U2 — unique business-key index on (SITE_ID, SITE_USE_TYPE_CODE), enforcing uniqueness of a use per site.
  • The parent RRS site table referenced through SITE_ID, which supplies the site definition this table decorates.