Search Results gl_suspense_accounts




Overview
Explore in AI Chat

Overview

GL_SUSPENSE_ACCOUNTS is a General Ledger configuration table in Oracle EBS 12.1.1 and 12.2.2 that stores additional suspense accounts mapped to specific journal source and category combinations. Whereas the standard suspense account is defined at the ledger level, this table allows organizations to override or supplement that default on a finer granularity — per source, per category, or per source/category pair. When Journal Import encounters an unbalanced or invalid journal line whose natural account cannot be derived, it routes the residual amount to the appropriate suspense account resolved from this table. Under the heuristic Data Vault classification mined from its foreign-key structure, GL_SUSPENSE_ACCOUNTS models as a link table: it relates a ledger, a code combination, and a journal source/category pair rather than acting as an independent hub or a descriptive satellite.

Key Information Stored

The table's structure centers on a composite key that identifies which suspense account applies to a given processing context.

The primary key GL_SUSPENSE_ACCOUNTS_PK is a surrogate-style composite over CODE_COMBINATION_ID, LEDGER_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME. The business-key candidate is the unique index GL_SUSPENSE_ACCOUNTS_U1 over LEDGER_ID, JE_SOURCE_NAME, and JE_CATEGORY_NAME, which enforces that only one suspense account may be defined per ledger/source/category combination. This distinction matters: the U1 index is the true uniqueness constraint governing configuration behavior, while the PK includes the account to guarantee physical row identity.

Common Use Cases and Queries

Typical scenarios include diagnosing why an imported journal landed in a particular suspense account, auditing suspense account configuration across ledgers, and migrating or comparing setups between environments.

  • Resolving the suspense account for a given source/category: SELECT code_combination_id FROM gl_suspense_accounts WHERE ledger_id = :p_ledger AND je_source_name = :p_source AND je_category_name = :p_category;
  • Listing all suspense overrides for a ledger by joining to GL_CODE_COMBINATIONS to display the concatenated account segments.
  • Auditing configuration completeness by outer-joining source/category combinations to detect where no explicit suspense account exists and the ledger default applies.
  • Setup migration queries comparing rows across two LEDGER_ID values or databases.

Related Objects

  • GL_LEDGERS — joined via GL_SUSPENSE_ACCOUNTS.LEDGER_ID to identify the owning ledger and its default suspense account.
  • GL_CODE_COMBINATIONS — joined via GL_SUSPENSE_ACCOUNTS.CODE_COMBINATION_ID to render the suspense account's segment values.
  • GL_JE_SOURCES and GL_JE_CATEGORIES — validate JE_SOURCE_NAME and JE_CATEGORY_NAME.
  • GL_JE_HEADERS and GL_JE_LINES — the imported journals whose suspense postings this configuration governs.
  • GL_IMPORT_REFERENCES — traces Journal Import processing to the originating source rows.
  • GL_JE_BATCHES — the batch context in which suspense-generating imports are grouped.

No public API writes directly to GL_SUSPENSE_ACCOUNTS; it is maintained through the General Ledger setup forms and read by the Journal Import concurrent program.