Results for “ci_alternate_code”

50+ results




Overview
Explore in AI Chat

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

Overview

IGF_AW_LI_HOLD_INTS is a legacy data import interface table within the IGF (Financial Aid) product family of Oracle E-Business Suite. Its documented description is "Award Disbursement Holds Interface Table for Legacy Data Import." The table serves as a staging area into which externally sourced award disbursement hold records are loaded before being validated and transferred into the operational financial aid award and disbursement structures. Because IGF is recorded as obsolete and the object is documented as "Not implemented in this database," the table exists in the ETRM 12.1.1 physical schema (owner IGF, 13 columns) but is not expected to be present or populated in a standard 12.1.1 or 12.2.2 installation.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. No foreign key relationships were mined from the schema, so the table can be treated as an independent staging construct rather than a modeled hub, link, or satellite. Its composite primary key, rather than a single surrogate identifier, reflects its nature as an import landing table keyed by the combination of business identifiers arriving from the source system.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are the five that form the primary key, IGF_AW_LI_HOLD_INTS_PK, which also serves as the sole unique index and therefore the business-key candidate: CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM, and HOLD_CODE. No separate surrogate primary key column is documented; identity is derived entirely from this composite business key.

  • CI_ALTERNATE_CODE — an alternate identifying code for the person or customer record, used as the first element of the composite key.
  • PERSON_NUMBER — the person-level identifier for the award recipient whose disbursement is subject to the hold.
  • AWARD_NUMBER_TXT — the award number in textual form, identifying the award to which the disbursement belongs.
  • DISBURSEMENT_NUM — the disbursement sequence number within the award.
  • HOLD_CODE — the code classifying the hold applied to the disbursement; this is the term most commonly used to search and filter this table.
  • HOLD_DATE and RELEASE_DATE — the effective dates on which the hold was applied and, where applicable, released.
  • RELEASE_REASON_TXT — free-text explanation for the release of the hold.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who inserted the interface row, when, and the most recent modification and login context.

Common Use Cases and Queries

The principal use case is bulk import of historical award disbursement holds during conversion or migration, followed by reconciliation and error reporting. Typical validation queries confirm that incoming HOLD_CODE values are valid and that key combinations are unique before transfer to operational tables. For example, a duplicate detection query:

  • SELECT CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM, HOLD_CODE, COUNT(*) FROM IGF_AW_LI_HOLD_INTS GROUP BY CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM, HOLD_CODE HAVING COUNT(*) > 1;
  • SELECT HOLD_CODE, COUNT(*) FROM IGF_AW_LI_HOLD_INTS GROUP BY HOLD_CODE ORDER BY 2 DESC;
  • SELECT * FROM IGF_AW_LI_HOLD_INTS WHERE HOLD_CODE = :hold_code AND RELEASE_DATE IS NULL;

Reporting typically focuses on open versus released holds by analyzing RELEASE_DATE and RELEASE_REASON_TXT, and on load freshness by examining CREATION_DATE against the migration window.

Related Objects

Because the metadata heuristically classifies this object as standalone and no foreign keys were mined, related objects must be inferred from naming conventions and the interface's purpose. The composite key columns imply join or lookup relationships to the following:

  • IGF_AW_AWARDS and its disbursement tables, joined on award and person identifiers corresponding to PERSON_NUMBER and AWARD_NUMBER_TXT.
  • IGF_AW_DISBURSEMENTS, joined on the award number and DISBURSEMENT_NUM.
  • Hold code validation/definition tables within the IGF or shared reference schemas, joined on HOLD_CODE.
  • Person/party tables (for example, PER_ALL_PEOPLE_F or the IGF person staging structures) joined on PERSON_NUMBER.
  • Other IGF_AW_LI_* interface tables, which follow the same legacy import naming pattern and share the CI_ALTERNATE_CODE and PERSON_NUMBER conventions.

Administrators should verify object existence and column definitions in the target environment, since the table is documented as not implemented and IGF is marked obsolete in the current release.