Search Results igs_fi_posting_int




Overview

The IGS_FI_POSTING_INT view is a multi-organization secured reporting object within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to filter records from the underlying multi-org table IGS_FI_POSTING_INT_ALL so that a querying session sees only the posting interface rows that belong to the organization currently established in the session context. The view resides in the APPS schema and carries a VALID status in ETRM for both 12.1.1 and 12.2.2.

Functionally, the view exposes financial posting interface data — the staging records used to move student financial transactions into the General Ledger. Because the underlying _ALL table stores rows for every operating unit, the view applies a row-level security predicate based on ORG_ID and the USERENV('CLIENT_INFO') value, ensuring that a user querying the view only retrieves postings relevant to the active organization. This makes the view suitable for reporting, reconciliation, and integration routines that must respect multi-org boundaries.

Underlying Base Objects

The view is defined directly over a single documented base table: IGS_FI_POSTING_INT_ALL. No other base objects are documented. The defining predicate is:

  • A SELECT of the full column list from IGS_FI_POSTING_INT_ALL.
  • A WHERE clause comparing NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) against itself, which resolves the operating unit from the session's client information and restricts the result set accordingly.

The _ALL table is the base multi-org table, while the view is the organization-filtered variant typically consumed by forms, concurrent programs, and custom reports. Because no joins are documented, the view is a straight projection with a security predicate rather than a denormalized join view.

Key Columns

The view exposes the following documented columns, which describe each financial posting interface record:

Common Use Cases and Queries

Typical uses include reconciling student financial postings prior to GL transfer, auditing unsuccessful or unprocessed interface rows by STATUS, and building organization-specific extracts that must honor multi-org security. A sample query is:

  • SELECT POSTING_ID, BATCH_NAME, ACCOUNTING_DATE, CURRENCY_CD, AMOUNT, STATUS, ORG_ID FROM APPS.IGS_FI_POSTING_INT WHERE STATUS = 'NEW' ORDER BY ACCOUNTING_DATE;
  • SELECT ORG_ID, COUNT(*), SUM(AMOUNT) FROM APPS.IGS_FI_POSTING_INT GROUP BY ORG_ID;

Because the view enforces the multi-org predicate, results automatically reflect the caller's operating unit context, making it the preferred access path over querying IGS_FI_POSTING_INT_ALL directly.