Results for “rrs_site_groups_b”

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

Overview

RRS_SITE_GROUPS_B is the base (non-translated) table within the Oracle E-Business Suite RRS – Site Management module. It stores the master definition of site groups, which are logical collections of operating sites used to organize, segment, and govern site-related transactions, reporting, and process flows. In Oracle EBS 12.1.1 and 12.2.2, RRS supports regulatory and operational site management, including site registration, group-based reporting hierarchies, and purpose-driven site classification. The _B suffix indicates this is the primary entity table that holds the group's core attributes, typically paired with a _TL table for translated (multi-language) descriptive text where applicable.

From a data modeling perspective, the metadata's heuristic Data Vault classification for this object is standalone, meaning the mined foreign-key structure did not surface strong inbound or outbound dependencies. In Data Vault terms, this suggests the object can be modeled as a hub for the site-group business key (SITE_GROUP_ID), with its descriptive and lifecycle attributes (dates, purposes, version numbers) potentially modeled as a satellite. This is offered as a modeling suggestion rather than a certified classification.

Key Information Stored

The table contains 11 documented columns. Among the most significant are:

• SITE_GROUP_ID – The surrogate primary key, defined by the unique index RRS_SITE_GROUPS_B_U1 and constrained by the primary key RRS_SITE_GROUPS_B_PK. It uniquely identifies each site group record.
• SITE_GROUP_TYPE_CODE – A code classifying the nature or category of the site group, driving which site-association and reporting rules apply.
• GROUP_PURPOSE_CODE – A code indicating the intended purpose or functional use of the group (e.g., reporting, compliance, operational segmentation).
• START_DATE and END_DATE – The effective date range during which the site group is active, enabling date-effective querying and historical analysis.
• OBJECT_VERSION_NUMBER – An optimistic-locking/versioning column used by the EBS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO columns capturing audit and user-session information for record creation and last modification.

Two unique indexes are documented: RRS_SITE_GROUPS_B_PK and RRS_SITE_GROUPS_B_U1, both keyed on SITE_GROUP_ID. This indicates that SITE_GROUP_ID serves simultaneously as the surrogate primary key and as the sole documented business-key candidate available in the metadata.

Common Use Cases and Queries

Because the table has no documented foreign keys in the mined metadata, referencing objects are inferred from the RRS domain rather than proven through constraints. Typical use cases include:

• Active site group reporting – Querying groups effective as of the current date:

  SELECT site_group_id, site_group_type_code, group_purpose_code
FROM rrs.rrs_site_groups_b
WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

• Group type analysis – Aggregating groups by SITE_GROUP_TYPE_CODE to understand distribution across classification categories.
• Audit and change tracking – Using CREATED_BY, LAST_UPDATED_BY, and the timestamp columns to trace who defined or modified a group.
• Concurrency validation – Application logic comparing OBJECT_VERSION_NUMBER during updates to enforce optimistic locking.

Reports should honor the date-effective columns and filter on type and purpose codes to return the relevant subset of groups.

Related Objects

The documented FK metadata classifies this object as standalone, so no authoritative foreign-key relationships were mined. Based on RRS – Site Management semantics, the objects most likely to reference or depend on RRS_SITE_GROUPS_B include a translated table (RRS_SITE_GROUPS_TL, joined on SITE_GROUP_ID) and site-assignment/mapping tables linking groups to individual sites (typically joined via SITE_GROUP_ID). Public EBS views and the Site Management concurrent programs and APIs that manage site groups also depend on this base table. Where the metadata supplies no FK, joins to assignment and translation entities should be validated against the actual RRS schema before use.