Results for “group_cd”

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

Overview

IGS_RU_NRG_GROUP_CD is a reference (lookup) table within the Oracle E-Business Suite IGS – Student System product family. Its documented description is "Named rule group code," indicating that it stores the set of named rule groups used by the student system's rules engine to categorize and organize business rules. Rows in this table define the valid group codes to which individual named rules are assigned.

The object is documented as obsolete and is explicitly noted as "Not implemented in this database" in the ETRM 12.1.1 metadata. This is a significant caveat: in many 12.1.1 and 12.2.2 environments the table will either not exist or be empty, because the IGS rules functionality has been superseded or de-supported. Any integration or report that references IGS_RU_NRG_GROUP_CD should be validated against the target instance before being relied upon.

From a dimensional modeling perspective, the supplied heuristic Data Vault classification is hub-leaning. This suggests treating GROUP_CD as a durable business key that anchors the table as a hub, with descriptive attributes such as DESCRIPTION carried on a satellite. The classification is a modeling suggestion only and does not imply that Oracle implements Data Vault constructs.

Key Information Stored

The table is documented with seven physical columns and a single unique index. The principal columns are:

• GROUP_CD — the business identifier for the rule group. It is the sole column of the unique index IGS_RU_NRG_GROUP_CD_U1 and is therefore the strongest business-key candidate, as well as the single column comprising the primary key constraint IGS_RU_NGC_PK.
• DESCRIPTION — the human-readable name or explanation of the rule group, used in list-of-values displays and reports.
• CREATED_BY, CREATION_DATE — standard Oracle EBS WHO columns recording the user and timestamp of row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns capturing the most recent modification and the login that performed it.

Notably, the documented primary key constraint IGS_RU_NGC_PK is defined on the natural business key GROUP_CD rather than on a system-generated surrogate. No independent surrogate ID column appears in the documented column list, so GROUP_CD serves simultaneously as the primary key and the business key. The remaining six columns are descriptive or audit-related.

Common Use Cases and Queries

The most common use is decoding GROUP_CD values obtained from the dependent table into meaningful descriptions for reporting. A typical pattern joins the group code table to its dependent rule table:

• Listing all defined rule groups: SELECT GROUP_CD, DESCRIPTION FROM IGS_RU_NRG_GROUP_CD ORDER BY GROUP_CD;
• Joining to named rules to retrieve rules by group: SELECT g.GROUP_CD, g.DESCRIPTION, r.* FROM IGS_RU_NRG_GROUP_CD g, IGS_RU_NAMED_RULE_GR r WHERE g.GROUP_CD = r.GROUP_CD;
• Looking up a specific group by its unique key: SELECT DESCRIPTION FROM IGS_RU_NRG_GROUP_CD WHERE GROUP_CD = :group_cd;
• Orphan detection — identifying rule rows whose group code has no definition: querying IGS_RU_NAMED_RULE_GR with a NOT EXISTS against this table.
• Audit reporting on WHO columns to determine when group definitions were created or last maintained.

Because the object is documented as obsolete and unimplemented, these patterns should be preceded by an existence and row-count check, and results should be treated as reference data rather than transactional data.

Related Objects

The FK metadata identifies one dependent relationship, but it is the primary consumer of this table:

• IGS_RU_NAMED_RULE_GR — the named rule table, joined on IGS_RU_NAMED_RULE_GR.GROUP_CD = IGS_RU_NRG_GROUP_CD.GROUP_CD. This is the child table that references the group code as a foreign key, indicating that named rules are grouped under this code.
• IGS_RU_NGC_PK — the primary key constraint on GROUP_CD, and IGS_RU_NRG_GROUP_CD_U1 the matching unique index; both are relevant when validating load order and duplicate handling.
• Other IGS_RU_* objects — the naming convention (IGS_RU_ prefix for the Rules Engine) suggests sibling reference and rule-definition tables that share the GROUP_CD concept, though only the named-rule relationship is documented in the supplied metadata.
• Rules engine APIs and concurrent programs — rule evaluation routines that accept a group code parameter are the functional consumers of this reference data.

Given the obsolete status, downstream objects referencing IGS_RU_NRG_GROUP_CD should be reviewed for decommissioning or migration to a supported rules framework.