Results for “igs_ad”

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

Overview

The table IGS.IGS_AD_DSCP_ATTR is a transactional data object within the Oracle EBS IGS schema, which supports the Student Systems / Admissions (Advanced) product family. It stores attribute-level definitions that are associated with admission source categories, and each record binds a discrepancy rule code to a specific category and attribute name. In this way the table acts as a configuration and reference store that drives how admission discrepancies are classified and evaluated during processing.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it qualifies as a standard, VALID table identical to the shipped FND Design Data definition IGS.IGS_AD_DSCP_ATTR. Heuristic Data Vault modeling suggests a satellite-leaning classification: the table carries descriptive and configuration attributes keyed to an admission source category, making it a natural satellite hanging off a hub or link rather than an independent hub itself. This classification is a modeling suggestion only; the physical implementation remains a conventional relational table with a surrogate primary key and business-key unique constraints.

Key Information Stored

The table contains nine documented columns. The most significant are described below.

• DISCREPANCY_ATTR_ID (NUMBER 15, mandatory): the surrogate primary key of the table (IGS_AD_DSCP_ATTR_PK) and the unique identifier of the discrepancy attribute. It is also the leading column of the unique index IGS_AD_DSCP_ATTR_U1, which the user's search term referenced.
• SRC_CAT_ID (NUMBER 15): the unique identifier of the admission source category. This column is a foreign key to IGS_AD_SOURCE_CAT_ALL and forms part of the composite business-key candidate IGS_AD_DSCP_ATTR_U2.
• ATTRIBUTE_NAME (VARCHAR2 30): the attribute name applied to different categories. Together with SRC_CAT_ID it defines the unique business key IGS_AD_DSCP_ATTR_U2, ensuring no category holds the same attribute twice.
• DISCREPANCY_RULE_CD (VARCHAR2 30): the discrepancy rule code that governs how the attribute is evaluated for the category.
• Standard Who columns: LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE capture audit and concurrency information automatically maintained by the Oracle EBS framework.

The distinction between the surrogate key (DISCREPANCY_ATTR_ID) and the documented business-key candidates (the composite of SRC_CAT_ID and ATTRIBUTE_NAME) is important for integration and de-duplication logic.

Common Use Cases and Queries

Typical usage centers on admissions configuration reporting and validation. Administrators query the table to confirm which attributes exist for a given source category, and developers join it to the parent category to resolve human-readable category names. A representative pattern is:

• Retrieving attribute definitions for a category: SELECT ATTRIBUTE_NAME, DISCREPANCY_RULE_CD FROM IGS.IGS_AD_DSCP_ATTR WHERE SRC_CAT_ID = :p_cat_id;
• Joining to the source category table to label results: SELECT a.ATTRIBUTE_NAME, c.CATEGORY_NAME FROM IGS.IGS_AD_DSCP_ATTR a, IGS.IGS_AD_SOURCE_CAT_ALL c WHERE a.SRC_CAT_ID = c.SRC_CAT_ID;
• Auditing rule assignments by attribute name across categories to spot configuration gaps.

Because the table is referenced by the APPS synonym IGS_AD_DSCP_ATTR, custom reports should query the APPS layer rather than the IGS owner directly to respect the supported access path.

Related Objects

The documented dependency model identifies one direct referential relationship and the standard synonym layer.

• IGS_AD_SOURCE_CAT_ALL: the parent table referenced via the foreign key SRC_CAT_ID → IGS_AD_SOURCE_CAT_ALL; the primary join target for category resolution.
• APPS.IGS_AD_DSCP_ATTR: the APPS synonym that exposes the table to application and reporting schemas.
• IGS_AD_DSCP_ATTR_U1 and IGS_AD_DSCP_ATTR_U2: the unique indexes supporting surrogate and business-key access paths.
• Downstream discrepancy-evaluation logic and any views or APIs that consume DISCREPANCY_RULE_CD depend indirectly on this table's configuration rows.

The metadata records no outbound references beyond SRC_CAT_ID; therefore related-object analysis should focus on the source category hierarchy and the admission discrepancy rule definitions that this table connects.