Results for “weeks_per_year”

31 results




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

Overview

The IGS_AD_EXCURR_INT_ALL table belongs to the Oracle E-Business Suite Student System (IGS) product family and resides in the IGS schema. Its documented purpose is to store a person's extracurricular activity details prior to import into the broader Oracle EBS person data model. Because the IGS Student System was primarily deployed on the 12.1.1 code line, this table is most relevant to EBS 12.1.1 environments, though 12.2.2 installations that retain IGS content will carry the same structure.

The table functions as an inbound staging or interface object. Records are populated by external feeds, flat files, or concurrent program loads, then validated and transferred into transactional person-interest tables. The "INT" segment of the object name confirms this interface role.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table carries descriptive attributes about a person's interests alongside its own surrogate key, which is consistent with a satellite attached to a person-interest hub or link. Modelers should treat this as a suggestion rather than a fixed architectural fact.

Key Information Stored

The table is documented with 31 columns. The most significant include:

The documented key fields distinguish INTERFACE_EXCURR_ID as the surrogate PK from the person-interest linkage via DUP_PERSON_INTEREST_ID, which serves as the principal business-key candidate for matching staged data against existing records.

Common Use Cases and Queries

Typical scenarios include loading student activity data from external systems, reconciling import failures, and reporting on interest participation. A representative query joins the staging table to HZ_PERSON_INTEREST:

  • SELECT a.interface_excurr_id, a.interest_type_code, a.status, b.interest_id FROM igs.igs_ad_excurr_int_all a, hz.hz_person_interest b WHERE a.dup_person_interest_id = b.interest_id AND a.status = 'ERROR';

Error reconciliation uses ERROR_CODE and MATCH_IND to isolate rows requiring correction. Concurrent program audit queries filter on REQUEST_ID or INTERFACE_RUN_ID to trace a specific load. Reporting extracts summarize activity by INTEREST_TYPE_CODE, SPORT_INDICATOR, or LEVEL_OF_PARTICIPATION across ORG_ID partitions.

Related Objects

The most significant related objects include:

  • HZ_PERSON_INTEREST — referenced via IGS_AD_EXCURR_INT_ALL.DUP_PERSON_INTEREST_ID. This is the primary relationship documented in the FK metadata.
  • The IGS interest validation and import concurrent programs that read and consume this staging table.
  • IGS person and student staging tables (IGS_AD_* interface family) sharing the INTERFACE_ID batch key.
  • HZ_PARTIES and HZ_PERSON_PROFILES, reachable through the person-interest chain in TCA.

Because IGS_AD_EXCURR_INT_ALL is an interface object, ongoing dependencies are mainly inbound feeds and downstream import routines rather than outbound FK children.