Search Results igs_fi_bill_pln_crd_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_FI_BILL_PLN_CRD_PKG package body is a server-side PL/SQL API within the Oracle E-Business Suite Student Systems (IGS) product family. It provides the programmatic foundation for managing records in the IGS_FI_BILL_PLN_CRD entity, which supports the billing plan credit functionality used by higher-education institutions. Billing plans in Oracle Student Financials allow charges and credits to be distributed across scheduled installments, and this package encapsulates the DML operations, locking logic, foreign-key resolution, and validation needed to maintain the integrity of billing plan credit rows. The package status is VALID, confirming it is a compiled, deployable object in the APPS schema. It is classified under the ETRM metadata as API classification "OTHER," indicating it is a supporting maintenance API rather than a primary public business interface. The package is referenced by five other database objects, reflecting its role as a shared building block for billing and disbursement processing.

Key Procedures and Functions

The documented package exposes eleven procedures and functions, all centered on row-level maintenance and referential lookups for the IGS_FI_BILL_PLN_CRD table.

  • INSERT_ROW — Inserts a new billing plan credit record into the underlying table, populating the columns required for a valid row and applying WHO-column defaults.
  • LOCK_ROW — Acquires a row-level lock (typically via a SELECT FOR UPDATE pattern) to serialize concurrent modifications on a specific billing plan credit row.
  • UPDATE_ROW — Applies changes to an existing billing plan credit record, including the tracking of the last-updated audit columns.
  • ADD_ROW — Higher-level convenience routine that performs the combined validation and insertion path, invoking the appropriate checks before the row is persisted.
  • DELETE_ROW — Removes a billing plan credit record from the table after enforcing any applicable delete-eligibility rules.
  • GET_PK_FOR_VALIDATION — Resolves the primary key of the billing plan credit row so that downstream validation logic can operate on a uniquely identified record.
  • GET_FK_IGS_FI_BILL — Resolves the foreign key that links a billing plan credit to its parent bill record, enabling the package to enforce the bill-to-credit relationship.
  • GET_FK_IGF_AW_FUND_MAST — Resolves the foreign key referencing the award fund master, connecting the credit to the funding source used to settle the charge.
  • GET_FK_IGS_CA_INST — Resolves the foreign key to the institution (calendar/institution) entity, ensuring the credit is scoped to the correct academic institution.
  • GET_FK_IGF_AW_AWD_DISB — Resolves the foreign key to the award disbursement record, tying the credit to a specific disbursement event in the financial aid lifecycle.
  • BEFORE_DML — Central pre-DML hook that performs shared validation and defaulting for both insert and update operations before the row is written.

Tables Accessed

The package operates against the single documented base table IGS_FI_BILL_PLN_CRD, accessed through the APPS synonym APPS.IGS_FI_BILL_PLN_CRD. This table stores the billing plan credit records that associate a credit amount with a bill, a funding source, an institution, and an award disbursement. All DML activities — inserts, updates, deletes, and locking reads — target this table. Foreign-key resolution functions additionally query the parent entities referenced by the credit rows, namely the bill, award fund master, institution, and award disbursement records, to validate that each foreign key points to a legitimate parent before the credit row is committed. No other base tables are documented as being directly maintained by this package.

Usage Notes

The package is typically invoked from Oracle Forms-based billing plan maintenance screens, from concurrent programs that process billing plan credits in batch, and from custom PL/SQL code that needs to create or amend billing plan credit records. Because it is referenced by five other database objects, it functions as a shared internal API within the Student Financials and financial aid modules; callers should rely on it rather than issuing direct DML against IGS_FI_BILL_PLN_CRD. The package depends on APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, IGS_GE_MSG_STACK, IGS_FI_BILL_PKG, IGS_CA_INST_PKG, IGF_AW_AWD_DISB_PKG, and IGF_AW_FUND_MAST_PKG for error handling, WHO-column population, message resolution, and cross-entity validation. The behavior and signatures are consistent across Oracle EBS 12.1.1 and 12.2.2, as the IGS schema did not undergo structural change between these releases. Customizations should call the documented routines and honor the BEFORE_DML validation path to preserve data integrity.