Results for “cr_gl_code_ccid”

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

Overview

IGS_FI_APPLICATIONS_V is a reporting view belonging to the IGS — Student System product family in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The IGS schema historically supported the Oracle Student System financials integration, specifically the application of payments and credits against student invoices and fee charges. Within this schema, the base table IGS_FI_APPLICATIONS stores the transactional linkage between an invoice and a credit (payment, adjustment, or waiver), while IGS_FI_INV_INT stores the corresponding invoice interface records.

The view IGS_FI_APPLICATIONS_V joins these two objects to present a flattened, denormalized picture of each payment application alongside its related invoice attributes. Its role in reporting and integration is to expose application-level amounts and invoice context in a single queryable structure, avoiding the need for report authors and interface programs to code the join themselves.

The ETRM documentation for this object carries the designation "No Longer Used" and the implementation note "Not implemented in this database," indicating the view is obsolete in current releases and generally absent from fresh 12.2.2 installations. Consequently, any reference to it should be treated as legacy.

Underlying Base Objects

The view is defined over two documented base objects:

• IGS_FI_APPLICATIONS APPL — the primary source of application records, supplying the application identifier, application type, credit references, apply date, account codes, GL code combinations, posting identifiers, and standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID).
• IGS_FI_INV_INT INV — the invoice interface source, supplying invoice number, fee type, invoice amount due, fee calendar type, fee calendar instance sequence number, and invoice description.

The two are joined on APPL.INVOICE_ID = INV.INVOICE_ID. A key characteristic of the view text is its reliance on a PL/SQL function, IGS_FI_GEN_007.GET_SUM_APPL_AMNT(APPL.APPLICATION_ID), to derive the AMOUNT_APPLIED column at runtime rather than storing it. The ETRM metadata records no referenced base objects beyond these two tables.

Key Columns

Notable columns exposed by the view include:

• APPLICATION_ID — unique identifier for the payment/credit application record; used as the input to the amount-summing function.
• APPLICATION_TYPE — classifies the application (for example, payment, adjustment, or waiver).
• INVOICE_ID / INVOICE_NUMBER — linkage and human-readable reference to the invoice being settled.
• CREDIT_ID / CREDIT_ACTIVITY_ID — identifiers for the credit transaction or activity applied.
• AMOUNT_APPLIED — computed amount applied, returned by IGS_FI_GEN_007.GET_SUM_APPL_AMNT.
• APPLY_DATE — the date the application was made.
• FEE_TYPE, FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER — fee categorization and calendar context for the invoice.
• BALANCE_DUE — the outstanding invoice amount; this is the column most commonly queried when searching for "balance_due" and corresponds to the invoice's amount still payable after applications.
• DR_ACCOUNT_CD / CR_ACCOUNT_CD / DR_GL_CODE_CCID / CR_GL_CODE_CCID — accounting distribution for the application.
• GL_DATE / GL_POSTED_DATE / POSTING_ID / POSTING_CONTROL_ID — general ledger posting state and control references.

Common Use Cases and Queries

Historically, this view supported student accounts receivable reporting: identifying outstanding balances, tracing which credits settled which invoices, and reconciling GL postings. A representative query follows.

• Listing open balances by invoice:
  SELECT invoice_number, application_id, amount_applied, balance_due
FROM igs_fi_applications_v
WHERE balance_due > 0;
• Summarizing amounts applied per invoice:
  SELECT invoice_number, SUM(amount_applied) total_applied
FROM igs_fi_applications_v
GROUP BY invoice_number;
• Auditing GL posting status:
  SELECT application_id, gl_date, gl_posted_date
FROM igs_fi_applications_v
WHERE gl_posted_date IS NULL;

Because the object is documented as obsolete and not implemented, these patterns apply only to legacy environments that retain the IGS views; on current 12.2.2 instances the view should be treated as unavailable.