Results for “reqd_for_application_flag”

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

Overview

The IGF_AP_LI_TODO_INTS table is an interface (staging) table within the IGF – Financial Aid product of Oracle E-Business Suite, documented in ETRM as a VALID table owned by the IGF schema. Its described purpose is to act as the interface table for To Do items, meaning it holds inbound records that are loaded and subsequently processed by Financial Aid concurrent programs before being promoted into the application's operational To Do structures. In EBS 12.1.1 and 12.2.2 the object retains the same physical definition in the IGF schema.

From a Data Vault modeling perspective, the ETRM metadata classifies this table heuristically as satellite-leaning. This suggests the table is best modeled as descriptive, attribute-bearing content attached to a parent business key, rather than as an independent hub of business entities or a pure link resolving many-to-many relationships. Practically, this reflects its role as a transient staging construct whose rows carry descriptive detail keyed to a batch and a person.

Key Information Stored

The table comprises 26 documented columns. The single-column primary key is TDINT_ID, enforced by the unique index IGF_AP_LI_TODO_INTS_PK. Because there is only one documented unique index, TDINT_ID serves both as the surrogate primary key and the sole documented business-key candidate; note that it is a generated identifier and not a natural business key.

The most significant columns are:

• TDINT_ID – Surrogate primary key uniquely identifying each interface To Do record.
• BATCH_NUM – Foreign key to IGF_AP_LI_BAT_INTS, grouping records into a load batch.
• PERSON_NUMBER – Identifies the person (student/applicant) to whom the To Do item belongs.
• CI_ALTERNATE_CODE – Alternate identifier used for cross-referencing the person or constituent.
• ITEM_CODE – Code identifying the type of To Do item being interfaced.
• ITEM_ADD_DATE – Date the To Do item was added.
• ITEM_STATUS_CODE and ITEM_STATUS_DATE – Current status of the To Do item and the date that status was set.
• CORSP_DATE and CORSP_COUNT_NUM – Correspondence date and count associated with the item.
• MAX_ATTEMPT_NUM and FREQ_ATTEMPT_NUM – Attempt limits and frequency control for repeated processing.
• REQD_FOR_APPLICATION_FLAG – Indicates whether the item is required for application completion.
• INACTIVE_FLAG – Marks the record as inactive.
• IMPORT_STATUS_TYPE and IMPORT_RECORD_TYPE – Control the import lifecycle of the interface row.
• RELATIONSHIP_CD – Relationship code qualifying the person context.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present.

Common Use Cases and Queries

Typical usage centers on monitoring inbound To Do loads and diagnosing rejected or pending interface rows. A frequent pattern joins the interface table to its batch parent and filters on import status:

• Batch reconciliation: SELECT b.BATCH_NUM, COUNT(*) FROM IGF.IGF_AP_LI_TODO_INTS t, IGF.IGF_AP_LI_BAT_INTS b WHERE t.BATCH_NUM = b.BATCH_NUM GROUP BY b.BATCH_NUM.
• Pending-item reporting: filter on IMPORT_STATUS_TYPE to surface rows not yet promoted.
• Per-person To Do listing: query by PERSON_NUMBER joined to status and date columns.
• Correspondence auditing: examine CORSP_DATE and CORSP_COUNT_NUM against MAX_ATTEMPT_NUM.

Related Objects

• IGF_AP_LI_BAT_INTS – Parent batch table; joined on BATCH_NUM.
• IGF_AP_LI_TODO_INTS_PK – The primary key index on TDINT_ID.

Additional dependencies are primarily the Financial Aid import concurrent programs and the operational To Do tables into which validated rows are loaded, though these are not enumerated in the supplied metadata.