Results for “igs_sc_per_attr_vals”

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

Overview

The IGS_SC_PER_ATTR_VALS table resides in the IGS (Student System) schema and forms part of the Oracle E-Business Suite security infrastructure for higher-education institutions. Its documented purpose is to hold security attribute information for a person — that is, the specific values assigned to a given person for each configured security attribute. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the intersection between individual party records and the attribute definitions used by the Student System's security model, enabling attribute-based access control over student and person data.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure and composite primary key suggest this object behaves as a link table. It connects two business entities — a person (via PERSON_ID) and a security attribute definition (via USER_ATTRIB_ID) — and carries the resolved attribute value (USER_ATTRIB_VALUE) as part of its unique key. It is not a pure hub, since it holds no independent business key of its own, and not a satellite, since it references multiple parents.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• PERSON_ID — Identifies the person (party) whose security attribute is being recorded. This is a foreign key to IGS_PE_HZ_PARTIES and part of the composite primary key.
• USER_ATTRIB_ID — Identifies the security attribute definition being applied. This is a foreign key to IGS_SC_USR_ATTRIBS and part of the composite primary key.
• USER_ATTRIB_VALUE — The actual value assigned to the person for the given attribute. This column is also part of the composite primary key, meaning a person may hold multiple distinct values for the same attribute.
• CREATION_DATE, CREATED_BY — Standard Oracle EBS audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login session responsible for it.

The primary key is defined by the unique index IGS_SC_PER_ATTR_VALS_PK over (PERSON_ID, USER_ATTRIB_ID, USER_ATTRIB_VALUE). There is no separate surrogate key column documented; the composite business key itself serves as the unique identifier. The inclusion of USER_ATTRIB_VALUE in the key means the table supports multiple concurrent values per person-attribute pairing, which is important for multi-valued security attributes.

Common Use Cases and Queries

Typical usage centers on resolving which security attribute values apply to a given person, and conversely, which persons share a given attribute value for population-based security rules.

• Listing all security attributes for a person:

  SELECT USER_ATTRIB_ID, USER_ATTRIB_VALUE
  FROM   IGS_SC_PER_ATTR_VALS
  WHERE  PERSON_ID = :person_id;

• Finding all persons holding a specific attribute value:

  SELECT PERSON_ID
  FROM   IGS_SC_PER_ATTR_VALS
  WHERE  USER_ATTRIB_ID = :attrib_id
  AND    USER_ATTRIB_VALUE = :value;

• Join to the attribute definition to obtain descriptive names:

  SELECT a.PERSON_ID, u.ATTRIB_NAME, a.USER_ATTRIB_VALUE
  FROM   IGS_SC_PER_ATTR_VALS a,
         IGS_SC_USR_ATTRIBS u
  WHERE  a.USER_ATTRIB_ID = u.USER_ATTRIB_ID
  AND    a.PERSON_ID = :person_id;

These queries are commonly embedded in security-rule resolution logic, personalized dashboards, and administrative reports validating attribute coverage across a student population. Because the table is keyed on person and attribute, partition-aware or indexed access on PERSON_ID is essential for performance in high-volume institutions.

Related Objects

• IGS_PE_HZ_PARTIES — Parent table for PERSON_ID, providing the person/party identity record.
• IGS_SC_USR_ATTRIBS — Parent table for USER_ATTRIB_ID, defining the available security attributes and their metadata.
• IGS_SC_PER_ATTR_VALS_PK — The primary key unique index enforcing uniqueness of (PERSON_ID, USER_ATTRIB_ID, USER_ATTRIB_VALUE).
• IGS_SC_USR_ATTRIBS and related security configuration tables — Together with this table, they form the Student System attribute-based security model.
• HZ_PARTIES / HZ_PERSON_PROFILES — Underlying Trading Community Architecture entities reached through IGS_PE_HZ_PARTIES joins, useful when reporting person demographics alongside security attributes.

Because the metadata documents only two foreign keys, related-object analysis beyond IGS_PE_HZ_PARTIES and IGS_SC_USR_ATTRIBS should be validated against the specific 12.1.1 or 12.2.2 instance, as views and public APIs layered over the security model may vary by patch level.