Search Results finp_get_acct_meth




Overview
Explore in AI Chat

Overview

IGS_FI_UNPOSTED_TRANSACTIONS is a reporting and integration view in the Oracle E-Business Suite Financials product family, specifically within the Student Systems / Financial Aid (IGS) schema. It is owned by APPS and exposes general ledger-bound transactions that have been generated but not yet posted to the General Ledger. The view consolidates unposted debits and credits from several IGS transaction sources—fee invoice lines, cash receipt activities, application adjustments, and admissions application fee requests—into a single, consistent presentation of accounting entries awaiting GL posting.

Its primary role is to drive the "unposted transactions" inquiry and the downstream GL posting programs within Student Financials. Because each source row is emitted as either a debit or credit line, the view produces a classic double-entry projection. The column GL_DATE is central to this view: it is the prospective accounting date that will be written to General Ledger when the transaction is posted, and it is a mandatory filter throughout the union (each contributing SELECT enforces "GL_DATE IS NOT NULL"). Users searching for "gl_date" are typically seeking to understand how the accounting date is derived, which records are eligible for transfer to GL, and how to reconcile unposted balances by accounting period.

Underlying Base Objects

The view is defined as a UNION ALL over four base IGS tables. Each base table contributes a debit leg and a credit leg:

Eligibility across all sources requires POSTING_ID and POSTING_CONTROL_ID to be null (or GL_POSTED_DATE to be null for IGS_AD_APP_REQ), confirming the record has not been posted or submitted for posting. No additional base objects are documented, though IGS_FI_GEN_005 is referenced as a package function controlling the accounting method.

Key Columns

  • GL_DATE — the accounting date proposed for the General Ledger entry. Non-nullable within the view; rows without a GL_DATE are excluded.
  • ACCOUNT_CD columns (REC_ACCOUNT_CD, REV_ACCOUNT_CD, DR_ACCOUNT_CD, CR_ACCOUNT_CD, CASH_ACCOUNT_CD) — flexfield account codes for the debit/credit side.
  • GL_CCID columns (REC_GL_CCID, REV_GL_CCID, DR_GL_CCID, CR_GL_CCID, CASH_GL_CCID, DR_GL_CODE_CCID, CR_GL_CODE_CCID) — numeric code combination identifiers mapping to GL_CODE_COMBINATIONS.
  • AMOUNT / AMOUNT_APPLIED / FEE_AMOUNT — monetary value of the entry, mapped to a common amount position.
  • DR / CR literal — a constant indicator denoting the debit or credit nature of the row.

Common Use Cases and Queries

Typical uses include reconciliation of unposted balances, review of GL dates awaiting posting, and feeding external reporting or interfaces. Example:

  • Unposted entries by GL date: SELECT gl_date, account_cd, amount, dr_cr FROM apps.igs_fi_unposted_transactions ORDER BY gl_date;
  • Period exposure: aggregate amounts within a date range to project GL impact before posting.
  • Dr/Cr balancing check: group by GL_DATE and the 'DR'/'CR' literal to confirm debits equal credits prior to transfer to GL.

Because the view surfaces only unposted records, it is best treated as a point-in-time work queue: as the GL posting process runs and populates POSTING_ID/POSTING_CONTROL_ID, rows drop out of the view.