Results for “name_cd”

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

Overview

The IGS_RU_TURIN_RULE_GR table belongs to the Oracle E-Business Suite IGS product family, historically designated as the Student System module and now classified as obsolete in the ETRM 12.1.1 and 12.2.2 reference documentation. The object is described as a "Turing Rule Group," indicating that it stored configuration groupings for rules applied within the legacy Turing engine used by the Student System for academic record processing and admissions-related decision logic. In modern deployments the table is documented as "Not implemented in this database," meaning most current installations will not carry it, and it appears only in upgrade-path or historical schema listings.

From a dimensional modeling standpoint, the Data Vault classification mined heuristically from the foreign key structure is link. This suggests the table functions as an associative entity that resolves a relationship between a Turing rule group definition and a broader IGS_RU_GROUP construct, rather than acting as a standalone descriptive hub or as a satellite capturing time-variant attributes.

Key Information Stored

The physical schema documented for 12.1.1 identifies the owner as IGS with nine columns and a composite primary key. Among the most significant columns:

• GROUP_CD — Part of the composite primary key; identifies the Turing rule group to which a rule belongs.
• NAME_CD — The second component of the composite primary key; names the specific rule association within a group.
• DESCRIPTION — Free-text description of the rule group entry, used for administrative clarity.
• RUG_SEQUENCE_NUMBER — A foreign key referencing IGS_RU_GROUP, tying the rule grouping to a specific record in the RU group structure.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and concurrency information.

The surrogate-style primary key is IGS_RU_TRG_PK covering (GROUP_CD, NAME_CD). The same two columns form the unique index IGS_RU_TURIN_RULE_GR_PK, so they serve simultaneously as the business-key candidate and the physical uniqueness constraint.

Common Use Cases and Queries

Because the table is obsolete, practical use cases center on historical data migration, upgrade validation, and audit investigation. A common query joins the table to IGS_RU_GROUP to enumerate rules associated with a given RU group sequence:

SELECT t.GROUP_CD, t.NAME_CD, t.DESCRIPTION, g.* FROM IGS_RU_TURIN_RULE_GR t, IGS_RU_GROUP g WHERE t.RUG_SEQUENCE_NUMBER = g.RUG_SEQUENCE_NUMBER;

Another recurring pattern checks for orphaned rule groupings by finding rows whose RUG_SEQUENCE_NUMBER has no parent in IGS_RU_GROUP. Reporting use cases typically extract the GROUP_CD/NAME_CD pairs to document legacy Turing rule configuration before decommissioning the Student System components.

Related Objects

The FK metadata identifies the following primary relationships:

• IGS_RU_TRG_GROUP_CD — Referenced through IGS_RU_TURIN_RULE_GR.GROUP_CD; supplies the group code master list.
• IGS_RU_GROUP — Referenced through IGS_RU_TURIN_RULE_GR.RUG_SEQUENCE_NUMBER; provides the RU group parent record.

Additional related IGS objects commonly consulted alongside this table include the Turing rule detail tables and the Student System group definitions that share the same RU sequencing lineage. Joins should always be driven through GROUP_CD, NAME_CD, and RUG_SEQUENCE_NUMBER to preserve referential integrity with the documented parent tables.