Results for “igf_ap_todo_all”

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

Overview

The IGF_AP_TODO_ALL table resides in the IGF schema and belongs to the Financial Aid (IGF) product family within Oracle E-Business Suite. According to the Enterprise Technical Reference Model (ETRM) metadata, the object is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2, meaning it is retained for backward compatibility but is no longer actively populated or referenced by current application logic. The table carries a primary key constraint named IGF_AP_TODO_ALL_PK on the TODO_ID column.

The heuristic Data Vault classification mined from the foreign key structure is standalone. In Data Vault modeling terms, this suggests the object does not behave as a conventional hub, link, or satellite with clearly defined parent relationships; it should instead be modeled as an isolated entity with no external join dependencies. This classification reinforces the observation that the table's relationships to other EBS objects are not formally documented and that it functions as a self-contained legacy structure.

Key Information Stored

The table contains 37 documented columns. The most significant of these are:

• TODO_ID — the surrogate primary key (IGF_AP_TODO_ALL_PK) and also the sole business-key candidate via the unique index IGF_AP_TODO_ALL_U1.
• PERSON_ID — identifies the person (typically a student or applicant) to whom the to-do item relates.
• ACAD_CI_CAL_TYPE and ACAD_CI_SEQUENCE_NUMBER — the academic calendar type and sequence context for the to-do item.
• AWD_CI_CAL_TYPE and AWD_CI_SEQUENCE_NUMBER — the award calendar type and sequence context.
• TODO_TYPE and TODO_SUB_TYPE — classify the category of the outstanding action.
• LOGICAL_DELETE — a soft-delete flag commonly used to retire records without physical removal.
• KEY1 through KEY8 — generic attribute slots used to store contextual lookup values.
• OLD_VALUE1 through OLD_VALUE5 and NEW_VALUE1 through NEW_VALUE5 — paired audit fields capturing before/after values for tracked changes.
• ORG_ID — the multi-org operating unit identifier, enabling row-level security across organizations.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the process that created or last modified the row.

The generic KEY, OLD_VALUE, and NEW_VALUE columns indicate the table was designed as a flexible staging or audit construct rather than a rigid master-data entity.

Common Use Cases and Queries

Because the table is documented as obsolete, direct querying is uncommon in live production reporting. Queries are typically limited to historical data migrations, archival extracts, and patch/upgrade validation exercises.

A basic inspection of active records would resemble:

• SELECT TODO_ID, PERSON_ID, TODO_TYPE, TODO_SUB_TYPE FROM IGF.IGF_AP_TODO_ALL WHERE LOGICAL_DELETE IS NULL;
• A change-audit extract joining old and new values: SELECT TODO_ID, OLD_VALUE1, NEW_VALUE1 FROM IGF.IGF_AP_TODO_ALL WHERE OLD_VALUE1 IS NOT NULL;
• An organization-scoped count: SELECT ORG_ID, COUNT(*) FROM IGF.IGF_AP_TODO_ALL GROUP BY ORG_ID;
• A concurrent-program provenance check: SELECT REQUEST_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE FROM IGF.IGF_AP_TODO_ALL ORDER BY PROGRAM_UPDATE_DATE DESC;

These patterns are useful when auditing historical financial-aid to-do activity or tracing how a particular concurrent request populated records. No current functional flow is expected to insert new rows.

Related Objects

The FK relationship metadata classifies IGF_AP_TODO_ALL as standalone, so no documented parent or child foreign keys exist. The following objects are the most plausible associational counterparts based on column semantics:

• PER_ALL_PEOPLE_F — joined on IGF_AP_TODO_ALL.PERSON_ID = PER_ALL_PEOPLE_F.PERSON_ID to resolve person details.
• IGF_AP_TODO_TYPES (or equivalent lookup) — resolved via TODO_TYPE and TODO_SUB_TYPE.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the originating concurrent process.
• FND_APPLICATION — joined on PROGRAM_APPLICATION_ID to identify the owning application.
• FND_PROGRAM — joined on PROGRAM_ID to identify the concurrent program.
• HR_ALL_ORGANIZATION_UNITS — joined on ORG_ID for operating unit context.

These joins are inferential; because the object is deprecated, dependency analysis should confirm whether any surviving view or PL/SQL package still references it before relying on them.