Search Results rrs_sites_b




Overview
Explore in AI Chat

Overview

RRS_SITES_B is the foundational base table within the RRS (Site Management) product module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the master descriptive and administrative information for sites operated, owned, licensed, or otherwise managed by an enterprise. In the context of ETRM-based site operations, a "site" represents a physical or logical business location — such as a retail outlet, convenience store, fuel station, terminal, or operator premises — that participates in periodic reporting, inventory reconciliation, and volume accountability processes.

The table resides in the RRS schema, is documented with 22 columns, and carries a VALID status. Its primary key is RRS_SITES_B_PK1 on SITE_ID, supported by two unique indexes: RRS_SITES_B_U1 (SITE_ID) and RRS_SITES_B_U2 (SITE_IDENTIFICATION_NUMBER). The metadata's heuristic Data Vault classification places this object as standalone with no mined foreign-key relationships, which suggests it functions as a hub-like entity anchored on its own business key rather than as a dependent satellite or associative link. The "_B" suffix follows Oracle EBS convention for base tables, implying a corresponding translation ("_TL") table may exist for multi-language descriptive attributes, though no such object is documented in the provided metadata.

Key Information Stored

Among the 22 documented columns, the following are the most significant for functional and integration purposes:

  • SITE_ID — The surrogate primary key, sourced from the sequence supporting RRS_SITES_B_PK1. It is the internal, system-generated identifier used by all foreign-key references from child tables.
  • SITE_IDENTIFICATION_NUMBER — The externally meaningful business key, enforced by unique index RRS_SITES_B_U2. This is the human-readable site number or code that users reference in forms and reports.
  • SITE_TYPE_CODE — Classifies the site (for example, retail, terminal, operator, or warehouse), driving downstream business rules.
  • SITE_STATUS_CODE — Tracks the lifecycle state of the site (active, inactive, closed, pending), used by validation and reporting logic.
  • BRANDNAME_CODE — Associates the site with a brand or trading identity, relevant in multi-brand retail networks.
  • CALENDAR_CODE — Links the site to the reporting calendar that governs its period-close and reporting cycles.
  • LOCATION_ID — References the HR or inventory location that describes the physical address and geography.
  • SITE_PARTY_ID, PARTY_SITE_ID, LE_PARTY_ID — Trading Community Architecture (TCA) party references identifying the operating party, the party-site relationship, and the legal entity party respectively.
  • PROPERTY_LOCATION_ID — Distinguishes the physical property location from the operating location.
  • TEMPLATE_COUNTRY, IS_TEMPLATE_FLAG — Support site template creation, allowing a country-specific template to seed new site records.
  • ORGANIZATION_ID — The multi-org (Operating Unit) discriminator, critical for row-level security and data segregation in multi-org deployments.
  • START_DATE, END_DATE — Date-range effective dating for the site relationship.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework.
  • Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Audit trail metadata maintained automatically.

Common Use Cases and Queries

Typical scenarios include listing active sites for a given operating unit, joining site attributes to transaction or reporting data, and deriving reconciliation populations by calendar and brand.

Sample query — active sites with type and brand:

  • SELECT SITE_ID, SITE_IDENTIFICATION_NUMBER, SITE_TYPE_CODE, SITE_STATUS_CODE, BRANDNAME_CODE FROM RRS_SITES_B WHERE SITE_STATUS_CODE = 'ACTIVE' AND ORGANIZATION_ID = :org_id;

Sample query — lookup by business key:

  • SELECT * FROM RRS_SITES_B WHERE SITE_IDENTIFICATION_NUMBER = :site_num;

Sample query — sites tied to a specific reporting calendar and date-effective at a point in time:

  • SELECT SITE_ID, SITE_IDENTIFICATION_NUMBER FROM RRS_SITES_B WHERE CALENDAR_CODE = :cal AND :asof BETWEEN START_DATE AND NVL(END_DATE, :asof+1);

Reporting uses include site master extracts, site hierarchy reconciliations, and validating that downstream transactions reference a valid, active site before period close.

Related Objects

Because the mined FK structure classifies RRS_SITES_B as standalone, no inbound or outbound foreign keys were documented. The following relationships are inferred from the column semantics and standard RRS/EBS patterns:

  • RRS_SITE_RELATIONSHIPS — Associates sites to one another; joins on SITE_ID.
  • RRS_SITE_ASSIGNMENTS — Maps sites to users, teams, or responsibility-owning entities; joins on SITE_ID.
  • RRS_DOWNLOAD / transaction/staging tables — Operational volume data reported per site; join on SITE_ID.
  • HR_LOCATIONS_ALL (PER_ locations) — Source of address and geographic detail; join on LOCATION_ID.
  • HZ_PARTIES / HZ_CUST_ACCOUNTS — TCA party records behind SITE_PARTY_ID, PARTY_SITE_ID, and LE_PARTY_ID.
  • FND_LOOKUPS — Provides the valid values for SITE_TYPE_CODE, SITE_STATUS_CODE, and BRANDNAME_CODE.
  • ORG_ORGANIZATION_DEFINITIONS — Supplies the operating unit context referenced by ORGANIZATION_ID.

Any extract or interface touching site master data should key on SITE_ID internally and reconcile to SITE_IDENTIFICATION_NUMBER for user-facing output.