Results for “node_purpose_code”

18 results




Overview
Explore in AI Chat

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

Overview

RRS_SITE_GROUP_NODES_B is the base table that stores the fundamental definition of nodes within Oracle E-Business Suite's Site Management module (RRS). In the ETRM data model, a "node" represents a discrete logical or physical location element belonging to a site group — for example, a collection point, a storage location, or a hierarchical grouping member used to organize site-level operations. The table resides in the RRS schema and is valid in both Oracle EBS 12.1.1 and 12.2.2 deployments, with the documented physical schema reflecting 12.2.2 (9 columns).

The "_B" suffix indicates this is the base (language-independent) table of a translated pair. The companion table, RRS_SITE_GROUP_NODES_TL, holds the translatable descriptive attributes, while RRS_SITE_GROUP_NODES_B holds the structural and operational data shared across all languages. From a heuristic Data Vault classification perspective, this object is modeled as a standalone structure — effectively a hub-like entity keyed by its own surrogate identifier, with no documented parent foreign keys feeding into it. That classification is a modeling suggestion rather than a physical assertion, since the metadata shows the table as a source of foreign key relationships rather than a target.

Key Information Stored

The table's identity is anchored by the surrogate primary key SITE_GROUP_NODE_ID, enforced through the constraint RRS_SITE_GROUP_NODES_B_PK and the unique index RRS_SITE_GROUP_NODES_B_U1. A second unique index, RRS_SITE_GROUP_NODES_B_U2, is built on NODE_IDENTIFICATION_NUMBER, making it the primary business-key candidate — the human-recognizable identifier used to reference a node in operational and integration contexts.

  • SITE_GROUP_NODE_ID — surrogate primary key; the internal join key to all dependent and translated tables.
  • NODE_IDENTIFICATION_NUMBER — unique business identifier for the node; the externally meaningful reference value.
  • NODE_PURPOSE_CODE — classified code describing the functional purpose or role of the node within the site group.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE — audit columns capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns capturing the most recent modifying user and timestamp.
  • LAST_UPDATE_LOGIN — login/session identifier associated with the last update, useful for forensic auditing.

Notably absent are any foreign key columns pointing to a parent site group table; the documented relationship data classifies this object as standalone, and the only outbound FK relationship is to its own translation table.

Common Use Cases and Queries

Typical usage centers on resolving node identity and reporting on node inventory within a site group. A common pattern joins the base and translation tables to render a fully localized node listing:

  • Node lookup by business key: SELECT * FROM rrs.rrs_site_group_nodes_b WHERE node_identification_number = :num;
  • Localized listing: SELECT b.site_group_node_id, b.node_identification_number, b.node_purpose_code, t.description FROM rrs.rrs_site_group_nodes_b b, rrs.rrs_site_group_nodes_tl t WHERE b.site_group_node_id = t.site_group_node_id AND t.language = USERENV('LANG');
  • Audit / change tracking: filtering on LAST_UPDATE_DATE to identify nodes modified in a given period for reconciliation or SOX reporting.
  • Purpose-code analysis: grouping nodes by NODE_PURPOSE_CODE to validate configuration completeness before go-live or during data migration.
  • Concurrency diagnostics: inspecting OBJECT_VERSION_NUMBER mismatches when OAF pages raise "row has been updated by another user" errors.

Related Objects

  • RRS_SITE_GROUP_NODES_TL — translation table; joined on SITE_GROUP_NODE_ID. The documented FK is RRS_SITE_GROUP_NODES_TL.SITE_GROUP_NODE_ID referencing RRS_SITE_GROUP_NODES_B. This is the primary dependent object and the mandatory join partner for any user-facing query.
  • RRS_SITE_GROUP_NODES_B_PK — primary key constraint on SITE_GROUP_NODE_ID.
  • RRS_SITE_GROUP_NODES_B_U1 — unique index on SITE_GROUP_NODE_ID.
  • RRS_SITE_GROUP_NODES_B_U2 — unique index on NODE_IDENTIFICATION_NUMBER; the business-key enforcement point.
  • RRS Site Management concurrent programs and OAF pages — the RRS module's node maintenance UI and validation APIs consume this table as the authoritative node registry.

Because the documented Data Vault classification is standalone with no inbound foreign keys, downstream integration or reporting objects are expected to reference it through the SITE_GROUP_NODE_ID surrogate rather than through any documented parent-child constraint.