Search Results pln_credit_date

Overview

IGS.IGS_FI_BILL_PLN_CRD is a transactional table in the Oracle E-Business Suite 12.1.1 / 12.2.2 Financial Aid (IGS) schema that stores the planned credit records associated with a particular bill extract. In the student financial aid billing cycle, the billing process evaluates anticipated or planned disbursements of awards and constructs expected credit entries against a student bill. This table persists those expected credits so that downstream processes — invoice generation, anticipated aid tracking, and reconciliation — can reference them without recomputing the underlying planned disbursements.

The object is classified as VALID and is owned by the IGS schema under the FND Design Data designation IGS.IGS_FI_BILL_PLN_CRD, with storage in the APPS_TS_TX_DATA tablespace. Based on the heuristic Data Vault classification derived from the foreign key structure, this table is best modelled as a link: it resolves the many-to-many relationship between awards (via planned disbursements) and bills, carrying a small set of descriptive attributes such as the planned credit date and amount. Practitioners modelling an enterprise data warehouse over EBS financial aid data should treat it as a relationship (link) table rather than a descriptive satellite.

Key Information Stored

The table contains 18 documented columns. Its composite primary key, IGS_FI_BILL_PLN_CRD_PK, consists of BILL_ID, AWARD_ID, and DISB_NUM, and the same three columns also drive the unique index IGS_FI_BILL_PLN_CRD_U1 — meaning the primary key and the business-key candidate are coincident on this object, so no separate surrogate key exists.

• BILL_ID — the bill for which the planned credit record was created; joins to IGS_FI_BILL_ALL.
• AWARD_ID — the award whose planned disbursement was considered for the bill; joins to IGF_AW_AWD_DISB_ALL.
• DISB_NUM — the disbursement number of the planned disbursement record considered for the bill.
• PLN_CREDIT_DATE — the date of the planned credit record; this is the column most commonly searched, and it drives anticipated-aid reporting and aging analysis.
• PLN_CREDIT_AMOUNT — the monetary value of the planned credit applied to the bill.
• FUND_ID — the fund against which the planned disbursement was created; joins to IGF_AW_FUND_MAST_ALL.
• FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER — the fee calendar and calendar instance context for the planned credit.
• BILL_DESC — a descriptive label for the bill, carried denormalised for convenience.
• Standard WHO/concurrent columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The primary use case is reporting anticipated financial aid against a student's bill. A typical query lists planned credits by date for a given bill:

• SELECT BILL_ID, AWARD_ID, PLN_CREDIT_DATE, PLN_CREDIT_AMOUNT FROM IGS.IGS_FI_BILL_PLN_CRD WHERE BILL_ID = :bill_id ORDER BY PLN_CREDIT_DATE;
• Aggregating anticipated aid by fund and calendar period for cash-flow forecasting, joining FUND_ID to IGF_AW_FUND_MAST_ALL.
• Reconciling planned credits against actual disbursements by comparing DISB_NUM and AWARD_ID to IGF_AW_AWD_DISB_ALL records.
• Identifying stale planned credits by filtering on PLN_CREDIT_DATE relative to the current date, useful for cleanup or re-evaluation before final invoicing.

Because the table is purely insert-oriented during the bill extraction process, queries should generally be scoped by BILL_ID to exploit the unique index rather than scanning by PLN_CREDIT_DATE alone.

Related Objects

• IGS.IGS_FI_BILL_ALL — the parent bill header; joined on BILL_ID.
• IGF.IGF_AW_AWD_DISB_ALL — the planned disbursement record; joined on AWARD_ID.
• IGF.IGF_AW_FUND_MAST_ALL — the fund master; joined on FUND_ID.
• IGS.IGS_CA_INST_ALL — the calendar instance; joined on FEE_CAL_TYPE with FEE_CI_SEQUENCE_NUMBER.
• IGS.IGS_FI_BILL_PLN_CRD_U1 — the unique index supporting business-key lookups.