Results for “igs_fi_invln_int_all”

50+ results




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

Overview

The IGS_FI_INVLN_INT_ALL table is an interface staging table within the Oracle E-Business Suite Student System (IGS) module. Its documented purpose is to store invoice line data generated by the invoice process. As an interface table, it acts as a transient holding area where line-level invoice records are written, validated, and subsequently consumed by downstream processing routines — most notably posting logic that moves financial data into the general ledger and receivables layers.

The module is classified in the ETRM metadata as IGS – Student System (Obsolete), and the table is explicitly documented as "Not implemented in this database" for the reference environment. Practitioners working on legacy 12.1.1 and 12.2.2 instances where IGS was originally licensed should therefore confirm physical existence and column-level definition against their own data dictionary rather than assume availability.

From a dimensional modeling perspective, the mined Data Vault classification is satellite-leaning. This is a modeling suggestion: the table carries descriptive, transactional attributes (amounts, charge elements, accounting codes) attached to invoice-line keys, which is consistent with satellite behavior rather than a hub or link. Its two unique indexes — IGS_FI_INVLN_INT_ALL_U1 on INVOICE_LINES_ID and IGS_FI_INVLN_INT_ALL_U2 on (INVOICE_ID, LINE_NUMBER) — reinforce that the row grain is one invoice line.

Key Information Stored

The table is documented with 63 columns in the 12.1.1 physical schema. The most operationally significant are listed below.

Common Use Cases and Queries

Typical usage centers on reconciliation of staged invoice lines against processed postings rather than direct transaction entry.

  • Identifying lines that failed validation: SELECT INVOICE_ID, LINE_NUMBER, ERROR_STRING FROM IGS_FI_INVLN_INT_ALL WHERE ERROR_STRING IS NOT NULL;
  • Retrieving all lines for a given invoice using the unique business key: SELECT * FROM IGS_FI_INVLN_INT_ALL WHERE INVOICE_ID = :p_invoice ORDER BY LINE_NUMBER;
  • Summing amounts by accounting code for revenue analysis: SELECT REV_ACCOUNT_CD, SUM(AMOUNT) FROM IGS_FI_INVLN_INT_ALL GROUP BY REV_ACCOUNT_CD;
  • Checking posting progress by comparing GL_DATE against GL_POSTED_DATE to find unposted lines.
  • Joining to IGS_FI_POSTING_INT_ALL on POSTING_ID to trace a line into its posting batch.

Related Objects

The documented foreign keys define the primary dependencies of this table.