Search Results igs_fi_invln_int_all




Overview
Explore in AI Chat

Overview

The IGS_FI_INVLN_INT_ALL table is an interface table within the Oracle E-Business Suite Student System (IGS), which is noted as obsolete. Its primary role is to serve as a staging area for invoice line data generated by the system's invoice processing engine. As an interface table, it acts as an intermediary data store, holding transactional information that is typically processed, validated, and then transferred to other core application tables. The "ALL" suffix indicates it is a multi-organization enabled table, capable of storing data partitioned by the operating unit. The provided metadata explicitly states it is "Not implemented in this database," suggesting it may represent a defined but unused object in a specific instance or a standard component not deployed in all implementations.

Key Information Stored

The table's structure is designed to capture the granular details of individual invoice lines. The primary identifier is the system-generated INVOICE_LINES_ID. Each line is also uniquely associated with a specific invoice via the composite key of INVOICE_ID and LINE_NUMBER, ensuring line items are correctly sequenced per invoice. Key transactional columns would typically include amounts, quantities, and descriptions for the charged item. Furthermore, the table holds critical accounting references, such as REV_ACCOUNT_CD (revenue account code) and REC_ACCOUNT_CD (receivable account code), linking the invoice line to the General Ledger. It also stores academic context via UNIT_TYPE_ID and UNIT_LEVEL, connecting financial charges to specific course units or academic levels.

Common Use Cases and Queries

The primary use case involves batch invoice generation and subsequent data integration. A background process would populate this table, after which a separate posting or interface program would validate the records and transfer them to permanent transactional tables. Common queries would focus on identifying unprocessed interface records for error resolution or audit purposes. For instance, a support analyst might run a query to find invoice lines for a specific invoice that have failed to post, or a developer might extract a sample for testing the invoice interface.

  • Identifying unprocessed invoice lines for a specific invoice: SELECT * FROM IGS_FI_INVLN_INT_ALL WHERE INVOICE_ID = :p_invoice_id AND POSTING_ID IS NULL;
  • Summarizing interface data by account code: SELECT REV_ACCOUNT_CD, COUNT(*), SUM(AMOUNT) FROM IGS_FI_INVLN_INT_ALL WHERE CREATION_DATE > SYSDATE-1 GROUP BY REV_ACCOUNT_CD;

Related Objects

Based on the documented foreign key relationships, IGS_FI_INVLN_INT_ALL is centrally connected to several key tables in the Student and Financials modules.

  • IGS_FI_POSTING_INT_ALL: Linked via POSTING_ID, this relationship connects the invoice line to its corresponding batch posting record in the interface.
  • IGS_FI_ACC_ALL: Linked via both REV_ACCOUNT_CD and REC_ACCOUNT_CD, defining the revenue and receivable accounting flexfields for the charge.
  • IGS_PS_UNIT_TYPE_LVL and IGS_PS_UNIT_LEVEL_ALL: Linked via UNIT_TYPE_ID and UNIT_LEVEL, respectively, providing the academic context for the chargeable item.
  • IGS_FI_APPLICATIONS: The foreign key from IGS_FI_APPLICATIONS.APPLIED_INVOICE_LINES_ID points back to this table, indicating that payments (applications) can be applied against specific invoice lines staged here.