Results for “igr_is_per_all”

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

Overview

IGR_IS_PER_ALL is a staging table within the Oracle E-Business Suite Student System (IGS) product family, historically associated with the Self Service Inquiry functionality that allowed prospective students and applicants to submit and track enrollment inquiries through web-facing interfaces. The table holds staging records for the "person" entity as captured during the self-service inquiry lifecycle, providing a landing area for person-level data before it is validated, reconciled, or promoted into the operational student system tables. In EBS 12.1.1 the physical schema is owned by the IGS schema and documents 25 columns. Under the ETRM 12.2.2 reference metadata, this object is flagged as obsolete and is explicitly marked "Not implemented in this database," meaning it should be treated as a legacy artifact rather than an active runtime dependency in current installations.

From a Data Vault modeling perspective, the mined foreign key structure suggests a hub-leaning classification. The table is referenced by four child tables that each carry an INQ_PERSON_ID or PERSON_ID foreign key pointing back to it, which is characteristic of a central business entity key surrounded by dependent descriptive and transactional satellites. This heuristic makes IGR_IS_PER_ALL a candidate hub for the inquiry-person business key, with the surrounding IGR_IS_* tables acting as links and satellites.

Key Information Stored

The documented primary key is IGR_IS_PER_ALL_PK, defined on the single column INQ_PERSON_ID. This is the surrogate identifier that uniquely identifies each staging inquiry person record. There is no separate documented unique index beyond the primary key, so INQ_PERSON_ID doubles as the business-key candidate for join purposes.

The most significant descriptive columns include:

• INQ_PERSON_ID — surrogate primary key and the join anchor for all child tables.
• ORG_ID — operating unit / organization context for multi-org data segregation.
• GIVEN_NAME, MIDDLE_NAME, SURNAME — core person name components.
• PREFERRED_GIVEN_NAME — the name the inquirer prefers to be addressed by.
• TITLE, SUFFIX, PRE_NAME_ADJUNCT — name prefixes, suffixes, and salutations.
• BIRTH_DT — date of birth used for validation and matching.
• SEX, ETHNIC_ORIGIN — demographic attributes captured during inquiry.
• CITIZENSHIP1_ID, CITIZENSHIP2_ID — citizenship references (primary and secondary).
• STATUS — workflow or processing state of the staging record.
• IMP_SOURCE_TYPE_ID — identifies the import or inquiry source channel.

Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent-program audit columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present for auditability and traceability.

Common Use Cases and Queries

Because the table is marked obsolete and unimplemented, practical querying is limited to legacy reconciliation, data migration audits, and historical reporting on former self-service inquiry populations. A representative join to consolidate the inquiry person with related records follows:

• Reconcile staging persons against their inquiry records: SELECT p.inq_person_id, p.surname, i.* FROM igr_is_per_all p JOIN igr_is_inquiry i ON i.inq_person_id = p.inq_person_id;
• Audit demographic completeness: filter on NULL BIRTH_DT or missing CITIZENSHIP1_ID to assess data quality before promotion.
• Trace import provenance using IMP_SOURCE_TYPE_ID grouped with ORG_ID.
• Audit record provenance via REQUEST_ID and PROGRAM_APPLICATION_ID to identify the concurrent program that created each staging row.

Related Objects

Four dependent tables reference IGR_IS_PER_ALL through documented foreign keys, forming the surrounding inquiry data model:

• IGR_IS_ADDRESS — joins on INQ_PERSON_ID; holds address records for the staging person.
• IGR_IS_INQUIRY — joins on INQ_PERSON_ID; holds the inquiry event or request records.
• IGR_IS_RACE — joins on PERSON_ID; holds race and ethnicity detail for the person.
• IGR_IS_TEST — joins on INQ_PERSON_ID; holds test scores or admissions test data linked to the inquirer.

These four tables collectively represent the dependency footprint of IGR_IS_PER_ALL; any migration or archival activity involving this hub should sequence the child tables accordingly to preserve referential integrity.