Results for “igs_fi_bill_pln_crd_u1”

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

Overview

The IGS_FI_BILL_PLN_CRD table resides in the IGS schema and belongs to the IGS — Student System product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the planned credit records associated with a particular bill extract. In practical terms, each row represents an anticipated credit — typically a disbursement against an award — that is expected to be applied against a student bill during the extract process. The table therefore serves as the planning bridge between financial aid award disbursement schedules and the billing engine.

Its role is transactional rather than setup-oriented: records are created and updated as part of the bill extract workflow, capturing the timing and monetary value of credits expected to offset charges. Where a search for igf_aw_awd_disb_all surfaces this table, the connection is direct: the award disbursement schedule is the source of the planned credit detail.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is best modelled as a link. Its identity is defined by the combination of BILL_ID, AWARD_ID, and DISB_NUM, which together associate a bill with a specific award disbursement — a classic many-to-many association resolved by an intersection entity. The remaining measure and date columns behave as link-level descriptive attributes.

Key Information Stored

The documented physical schema contains 18 columns. The most significant are:

• BILL_ID — identifies the bill extract to which the planned credit applies; part of the primary key and a foreign key to IGS_FI_BILL_ALL.
• AWARD_ID — identifies the financial aid award supplying the credit; part of the primary key and a foreign key to IGF_AW_AWD_DISB_ALL.
• DISB_NUM — the disbursement sequence number within the award; part of the primary key and paired with AWARD_ID in the reference to IGF_AW_AWD_DISB_ALL.
• PLN_CREDIT_AMOUNT — the monetary value of the planned credit.
• PLN_CREDIT_DATE — the date on which the planned credit is expected to take effect.
• FUND_ID — the funding source; foreign key to IGF_AW_FUND_MAST_ALL.
• FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER — together identify the fee calendar instance and calendar sequence to which the credit relates, referencing IGS_CA_INST_ALL.
• BILL_DESC — descriptive text for the planned credit line.
• Standard WHO and 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 capture audit and concurrent program context.

The surrogate primary key is IGS_FI_BILL_PLN_CRD_PK, defined over BILL_ID, AWARD_ID, and DISB_NUM. The unique index IGS_FI_BILL_PLN_CRD_U1 is documented on the identical column set, confirming that this three-part combination is the business-key candidate as well as the physical key.

Common Use Cases and Queries

Typical uses include reconciling planned credits against actual disbursements, reporting anticipated aid for a billing period, and verifying that every award disbursement has a corresponding planned credit line on the correct bill.

• Listing all planned credits for a bill:

  SELECT b.BILL_ID, b.AWARD_ID, b.DISB_NUM,
         b.PLN_CREDIT_DATE, b.PLN_CREDIT_AMOUNT
  FROM   IGS_FI_BILL_PLN_CRD b
  WHERE  b.BILL_ID = :bill_id;

• Joining to the disbursement schedule to compare planned credits with the award disbursement detail:

  SELECT p.BILL_ID, p.AWARD_ID, p.DISB_NUM,
         p.PLN_CREDIT_AMOUNT, d.DISB_AMOUNT
  FROM   IGS_FI_BILL_PLN_CRD p,
         IGF_AW_AWD_DISB_ALL d
  WHERE  p.AWARD_ID = d.AWARD_ID
  AND    p.DISB_NUM = d.DISB_NUM;

• Aggregating planned credits by funding source:

  SELECT FUND_ID,
         SUM(PLN_CREDIT_AMOUNT) total_planned
  FROM   IGS_FI_BILL_PLN_CRD
  GROUP  BY FUND_ID;

Concurrent program context is available through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID, which is useful when auditing which extract run produced or modified a given planned credit record.

Related Objects

The following objects are the most significant dependencies, grounded in the documented foreign keys:

• IGS_FI_BILL_ALL — referenced via BILL_ID; the parent bill header for the planned credits.
• IGF_AW_AWD_DISB_ALL — referenced via AWARD_ID and DISB_NUM; the award disbursement schedule that supplies the credit.
• IGF_AW_FUND_MAST_ALL — referenced via FUND_ID; the funding master defining the source of funds.
• IGS_CA_INST_ALL — referenced via FEE_CAL_TYPE and FEE_CI_SEQUENCE_NUMBER; the calendar instance governing fee timing.
• IGS_FI_BILL_PLN_CRD_PK and IGS_FI_BILL_PLN_CRD_U1 — the primary key constraint and unique index enforcing uniqueness of the bill, award, and disbursement combination.

Because the table behaves as a link in Data Vault terms, any reporting model that joins bills to award disbursements should treat IGS_FI_BILL_PLN_CRD as the association point, with PLN_CREDIT_AMOUNT and PLN_CREDIT_DATE carried as descriptive attributes of that association.