Search Results igs_fi_unposted_transactions

Overview

IGS_FI_UNPOSTED_TRANSACTIONS is an APPS-owned database view in the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to display un-posted transactions in Student Finance. In practical terms, the view exposes the population of accounting entries that have been generated by Student Finance sub-ledger activity but that have not yet been transferred to the General Ledger and therefore cannot yet appear in GL balances.

The view is significant because it operates as a reconciliation and monitoring artifact rather than as a transactional table. Each row represents a single debit or credit accounting line awaiting posting. Because Student Finance transactions such as invoices, credit activities, applications of funds, and admission application requests are captured in separate base tables, the view harmonises those heterogeneous sources into a single, uniform projection of GL_DATE, account, CCID, amount, and transaction type. This makes it suitable for period-end close monitoring, posting exception analysis, and integration checks between the Student System and the Oracle General Ledger.

The user search term "posting_control_id" is central to this view. The posting control identifier is the mechanism by which Student Finance marks an accounting line as having been picked up and controlled by the posting process. Where POSTING_ID is null and POSTING_CONTROL_ID is null, the line is genuinely un-posted and is therefore surfaced by this view.

Underlying Base Objects

The documented view text shows that IGS_FI_UNPOSTED_TRANSACTIONS is defined as a UNION ALL of multiple source queries drawn from four base tables, each contributing a debit leg and a credit leg:

• IGS_FI_INVLN_INT — the invoice line interface table, filtered by POSTING_ID IS NULL, POSTING_CONTROL_ID IS NULL, an accrual accounting method condition via IGS_FI_GEN_005.FINP_GET_ACCT_METH, a non-null GL_DATE, and ERROR_ACCOUNT not equal to 'Y'.
• IGS_FI_CR_ACTIVITIES — credit activities, where GL_DATE is not null and typically both posting identifiers are null.
• IGS_FI_APPLICATIONS — fund applications, with both posting identifiers null and GL_DATE not null.
• IGS_AD_APP_REQ — admission application requests, filtered on POSTING_CONTROL_ID IS NULL and GL_POSTED_DATE IS NULL.

The view also references the server-side function IGS_FI_GEN_005.FINP_GET_ACCT_METH, which returns the accounting method and gates the invoice line interface branch on an accrual value. No other referenced base objects are documented in the ETRM metadata. Because the view contains a UNION ALL and calls a PL/SQL function, performance depends heavily on the indexes supporting the posting columns on each base table.

Key Columns

• GL_DATE — the accounting date that would be assigned to the entry if posted to GL. It determines the GL period into which the transaction falls.
• ACCOUNT_CODE — the concatenated or descriptive accounting flexfield account code, populated from REC_ACCOUNT_CD, REV_ACCOUNT_CD, DR_ACCOUNT_CD, CR_ACCOUNT_CD, CASH_ACCOUNT_CD, or the equivalent source depending on the branch.
• GL_CCID — the numeric code combination identifier corresponding to the account code, taken from the various CCID columns such as REC_GL_CCID, REV_GL_CCID, DR_GL_CCID, CR_GL_CCID, DR_GL_CODE_CCID, CR_GL_CODE_CCID, or CASH_GL_CCID.
• AMOUNT — the monetary value of the line, drawn from AMOUNT, AMOUNT_APPLIED, or FEE_AMOUNT.
• TRX_TYPE — a literal indicator of the accounting side, returned as 'DR' for debit branches and 'CR' for credit branches.

Common Use Cases and Queries

The primary use case is identifying what remains un-posted at a point in time so that the posting process can be run or investigated. A representative query totals the un-posted population by GL date:

• SELECT gl_date, trx_type, SUM(amount) FROM igs_fi_unposted_transactions GROUP BY gl_date, trx_type ORDER BY gl_date;
• SELECT account_code, gl_ccid, SUM(amount) FROM igs_fi_unposted_transactions GROUP BY account_code, gl_ccid;
• SELECT * FROM igs_fi_unposted_transactions WHERE gl_date BETWEEN :p_start AND :p_end;

These queries support period-close reconciliation, review of transactions on hold due to account errors, and confirmation that the posting control process has correctly consumed previously outstanding lines. The absence of a row for a given transaction indicates either successful posting or that a POSTING_ID or POSTING_CONTROL_ID has been assigned.