Results for “gl_je_source”

50+ results




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

Overview

IGI_IAC_BOOK_CONTROLS_V is an APPS-owned view within the Oracle E-Business Suite product IGI — Public Sector Financials International. It presents asset book control configuration that drives the IGI Intragovernmental Asset Clearing (IAC) processes, including depreciation, revaluation, and transactional journal generation. The view exposes the GL journal source and journal categories configured for each depreciation book, along with an organization identifier used to segregate setup data by operating unit or organization. Its primary role is to provide a secure, MOAC-filtered reporting and integration layer over the underlying book controls table so that users and concurrent programs only see the book controls relevant to their current organization context. Because it surfaces GL_JE_SOURCE, the view is commonly encountered when users investigate how IGI assigns journal sources to asset-related accounting entries, particularly when searching for "gl_je_source" references in the IGI setup. The view is documented as VALID in ETRM and is available in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the synonym IGI_IAC_BOOK_CONTROLS, which resolves to the base book controls table. The documented referenced base objects are IGI_IAC_BOOK_CONTROLS (SYNONYM) and FA_BOOK_CONTROLS_SEC (SYNONYM). FA_BOOK_CONTROLS_SEC is the Assets security-enabled book controls object, indicating that book-level security is enforced in the IGI asset book configuration. The view selects directly from IGI_IAC_BOOK_CONTROLS and applies a WHERE clause based on the ORGANIZATION_ID:

  • NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTR(USERENV('CLIENT_INFO'),1,10))),-99)) equals the same expression derived from the client information.

This predicate implements the multi-org access control filter, comparing the row's ORG_ID to the organization derived from the session's CLIENT_INFO. Rows with a NULL ORG_ID are treated as global and are matched when the session organization also resolves to NULL.

Key Columns

  • ROW_ID — The ROWID of the underlying book controls record, used as a unique row identifier.
  • BOOK_TYPE_CODE — The asset book (depreciation book) identifier to which the controls apply.
  • GL_JE_SOURCE — The General Ledger journal source assigned to IGI IAC accounting entries for the book. This column is the key reference for users searching on "gl_je_source".
  • JE_IAC_DEPRN_CATEGORY — The journal category used for IAC depreciation entries.
  • JE_IAC_REVAL_CATEGORY — The journal category used for IAC revaluation entries.
  • JE_IAC_TXN_CATEGORY — The journal category used for IAC transactional entries.
  • PERIOD_NUM_FOR_CATCHUP — The period number used for catch-up processing within the IGI IAC logic.
  • ORG_ID — The organization (operating unit) that owns the book control setup row; drives MOAC filtering.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses include verifying the GL journal source and journal categories configured for each IGI asset book, troubleshooting journal creation in GL, and auditing book control setup across organizations. Because the view enforces ORG_ID filtering, query results depend on the session's organization context.

To list book controls and their journal source configuration:

  • SELECT book_type_code, gl_je_source, org_id FROM igi_iac_book_controls_v ORDER BY book_type_code;

To retrieve journal categories for a specific book:

  • SELECT book_type_code, gl_je_source, je_iac_deprn_category, je_iac_reval_category, je_iac_txn_category FROM igi_iac_book_controls_v WHERE book_type_code = :book;

To find all books using a particular GL journal source:

  • SELECT book_type_code, org_id FROM igi_iac_book_controls_v WHERE gl_je_source = :source;

Results are constrained by the organization filter embedded in the view, so users must be positioned in the appropriate operating unit to see the corresponding setup rows.