Search Results min_credit_pts




Overview
Explore in AI Chat

Overview

APPS.IGF_AW_TP_INSTMT is a multi-org view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and registered under the FND Design Data identifier IGF.IGF_AW_TP_INSTMT. It falls within the Oracle Financials product family, specifically the Financial Aid functionality associated with the IGF module. The view exposes data governing the relationship between academic time periods and installment or disbursement schedules tied to a fund or award.

As a multi-org view, IGF_AW_TP_INSTMT is designed to retrieve records only for the current operating unit, automatically filtering out data belonging to other operating units. This behavior depends on the ORG_ID column and the standard multi-org security profile option, ensuring that querying users see only the data relevant to their assigned organization. The view serves reporting, integration, and inquiry purposes, providing a read-friendly projection over the underlying staging or base table.

Underlying Base Objects

The view is defined over APPS.IGF_AW_TP_INSTMT_ALL, which holds the composite multi-org records including the ORG_ID column. The _ALL table is the base storage object; the view IGF_AW_TP_INSTMT applies the operating unit predicate to present an org-secured subset. The view also participates in a layered dependency chain: APPS.IGF_AW_TP_INSTMT is referenced by APPS.IGF_AW_TP_INSTMT_V, indicating that a further view or synonym layer exists on top of it. This pattern is common in Oracle Financials, where a base table (_ALL) is wrapped by a multi-org view and then further wrapped for specific functional views.

The referenced base objects in the documented metadata list none explicitly beyond the internal dependency on IGF_AW_TP_INSTMT_ALL. The FND Design Data entry references the obsolete artifact FA125_3160568_CS_DP1.doc, which is a legacy development document and does not affect current runtime behavior.

Key Columns

  • ROW_ID (ROWID): The physical row identifier of the underlying record.
  • FINST_ID (NUMBER): Identifier linking to the fund installment record for the award.
  • LD_CAL_TYPE and LD_SEQUENCE_NUMBER: The load calendar type and sequence number describing the period over which the installment applies.
  • FUND_ID (NUMBER): The fund or award identifier associated with the record.
  • TP_CAL_TYPE and TP_SEQUENCE_NUMBER: The time period calendar type and sequence number defining the applicable academic period.
  • TP_OFFSET_DA (VARCHAR2): Offset or date-adjustment attribute applied to the time period.
  • TP_PERCT (NUMBER): Percentage of the installment distributed to the time period.
  • MIN_CREDIT_PTS (NUMBER): The minimum credit points a student must be enrolled in for the corresponding time period to qualify for the installment or disbursement. This is the column most directly associated with the search term "min_credit_pts."
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard audit columns maintained automatically by EBS.
  • ORG_ID (NUMBER): The operating unit identifier that drives the multi-org filtering behavior of the view.

Common Use Cases and Queries

Typical use cases include validating minimum credit-point thresholds for financial-aid disbursements, reporting on installment schedules per academic period, and integrating award data into downstream reporting or analytics platforms. Because the view enforces operating unit security, queries should be run within a session whose ORG_ID profile is correctly set.

A basic query retrieving all rows for the current operating unit:

SELECT FINST_ID, FUND_ID, TP_CAL_TYPE, TP_SEQUENCE_NUMBER, TP_PERCT, MIN_CREDIT_PTS, ORG_ID FROM APPS.IGF_AW_TP_INSTMT;

A query filtering by a specific fund and reviewing minimum credit-point requirements:

SELECT FUND_ID, TP_CAL_TYPE, TP_SEQUENCE_NUMBER, MIN_CREDIT_PTS, TP_PERCT FROM APPS.IGF_AW_TP_INSTMT WHERE FUND_ID = :p_fund_id ORDER BY TP_SEQUENCE_NUMBER;

For auditing, joining to the base table IGF_AW_TP_INSTMT_ALL is unnecessary because the view already exposes all documented columns. Administrators requiring data across all operating units must query the _ALL table directly or use a responsibility whose ORG_ID security permits it. Given the dependency on IGF_AW_TP_INSTMT_V, developers should confirm which layer is referenced by their code to avoid ambiguity when the higher-level view applies additional filters.