Results for “jnl_reversal_ind”

50+ results




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

Overview

XTR_JOURNALS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the XTR (Treasury) product. It exposes the accounting journal lines generated by Treasury deal, transaction, and settlement processing, presenting them in a denormalized, read-only form suitable for extraction, reconciliation, and downstream integration with General Ledger. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. Because the underlying data is written by the Treasury accounting engine, the view functions primarily as a canonical access point for journal data without exposing callers to direct DML on the base table.

The recurring search term "suspense_gl" corresponds directly to the SUSPENSE_GL column in this view, making XTR_JOURNALS_V a common target for queries that identify Treasury journals routed to a suspense account rather than a valid, fully qualified balancing segment value.

Underlying Base Objects

The view is defined over a single documented base object: XTR_JOURNALS, accessed through a synonym. The view text is a straightforward projection with no joins, filters, or aggregation. The first column is derived as ROWID AS ROW_ID, and the remaining columns map one-to-one to their base table counterparts. No WHERE clause restricts the result set, so every row in XTR_JOURNALS is visible through the view. This simplicity means row counts are identical and no additional predicates are required for full extraction.

Key Columns

  • ROW_ID — ROWID surrogate that uniquely identifies the physical base-table row.
  • BATCH_ID — Links a group of journal lines generated by the same accounting batch.
  • DEBIT_AMOUNT / CREDIT_AMOUNT — Entered amounts for the line in the transaction currency.
  • ACCOUNTED_DR / ACCOUNTED_CR — Accounted amounts in the ledger currency.
  • CODE_COMBINATION_ID — The accounting flexfield combination to which the line is posted.
  • SUSPENSE_GL — Flag/indicator designating that the line has been directed to a suspense account, typically because a valid code combination could not be derived.
  • CANCELLED_IN_GL — Indicates the journal was cancelled in the general ledger.
  • TRANSFER_TO_EXTERNAL_GL — Indicates whether the line is destined for an external GL.
  • JNL_REVERSAL_IND — Marks entries created by journal reversal processing.
  • GL_SL_LINK_ID — Correlation identifier used to tie the Treasury line back to the GL interface or SLA entry.
  • SET_OF_BOOKS_ID — The ledger to which the journal belongs.
  • DATE_TYPE, ORIG_JOURNAL_DATE, ALT_JOURNAL_DATE — Control whether the original or alternate journal date is used for accounting.
  • CURRENCY, DEAL_NUMBER, TRANSACTION_NUMBER, SETTLEMENT_NUMBER — Business context identifying the source deal, transaction, or settlement.

Common Use Cases and Queries

Typical use cases include Treasury-to-GL reconciliation, suspense-account investigation, and period-close validation. The following queries illustrate common access patterns.

Locate all lines routed to suspense:

  • SELECT BATCH_ID, DEAL_NUMBER, CODE_COMBINATION_ID, DEBIT_AMOUNT, CREDIT_AMOUNT FROM XTR_JOURNALS_V WHERE SUSPENSE_GL IS NOT NULL;

Reconcile a batch to General Ledger:

  • SELECT BATCH_ID, SUM(ACCOUNTED_DR), SUM(ACCOUNTED_CR) FROM XTR_JOURNALS_V WHERE BATCH_ID = :p_batch GROUP BY BATCH_ID;

Review lines pending transfer or already cancelled in GL:

  • SELECT BATCH_ID, TRANSFER_TO_EXTERNAL_GL, CANCELLED_IN_GL, GL_SL_LINK_ID FROM XTR_JOURNALS_V WHERE CANCELLED_IN_GL = 'Y' OR TRANSFER_TO_EXTERNAL_GL IS NOT NULL;

Because the view performs no transformation, results mirror XTR_JOURNALS exactly, and standard Treasury and GL security applies.