Results for “journal_line_number”

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

Overview

CEBV_STMTRECON is a Business View owned by the APPS schema within the Cash Management (CE) product family of Oracle E-Business Suite. It is delivered in a VALID state and is defined as a view rather than a base table, meaning it does not store data itself but projects and reshapes rows from its underlying reconciliation objects at query time. Its name follows the Cash Management naming convention for statement reconciliation (CEBV = Cash Management Business View, STMTRECON = Statement Reconciliation).

The view surfaces reconciliation activity recorded against bank statement lines, exposing each reconciliation record together with a lookup-derived meaning column that translates the YES/NO auto-reconciliation flag into a display value. Its central purpose is to provide a denormalized, reference-type-aware picture of how statement lines were matched — to journal lines, payments, or receipts. Because the view unions these three reference types into a common column layout, downstream reporting, reconciliation inquiry, and integration consumers can query a single object instead of branching across reference types themselves.

Users searching for the term "journal_line_number" commonly encounter this view because its journal-entry reconciliation rows (REFERENCE_TYPE = 'JE_LINE') are the carrier of the journal line reference. It is relevant in both 12.1.1 and 12.2.2, where the definition is stable.

Underlying Base Objects

The documented base objects referenced by CEBV_STMTRECON are:

• CE_STATEMENT_RECONCILS_ALL (referenced as a SYNONYM) — the principal source of reconciliation rows, providing statement line identifiers, reference type and identifier, journal entry header, amounts, organization, and audit columns.
• CE_LOOKUPS (VIEW) — used to resolve the auto-reconciliation indicator, restricted to LOOKUP_TYPE = 'YES/NO' joined on LOOKUP_CODE = AUTO_RECONCILED_FLAG.

The view text consists of four UNION ALL branches over CE_STATEMENT_RECONCILS_ALL, filtered by CURRENT_RECORD_FLAG = 'Y', STATUS_FLAG = 'M', and the security predicate on ORG_ID. Each branch is constrained to one REFERENCE_TYPE — 'JE_LINE', 'PAYMENT', 'RECEIPT', and (in the truncated remainder) a fourth reference type — routing the applicable REFERENCE_ID value into position-specific TO_NUMBER(NULL) placeholder columns. This positional shifting is what allows dissimilar reference types to share one column signature.

Key Columns

• STATEMENT_LINE_ID — identifier of the bank statement line being reconciled.
• REFERENCE_TYPE — denotes what the line was matched to (JE_LINE, PAYMENT, RECEIPT, etc.).
• REFERENCE_ID — the primary identifier of the matched entity; for journal entries this supports journal line identification, which is why "journal_line_number" searches resolve here.
• JE_HEADER_ID — journal entry header reference for JE_LINE rows.
• MEANING — decoded YES/NO text for the auto-reconciled flag via CE_LOOKUPS.
• AMOUNT — reconciled amount of the statement line.
• ORG_ID — operating unit, used for data security.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical use cases include statement reconciliation inquiry reports, audit extracts of auto-reconciled versus manually reconciled lines, and integration feeds that require a uniform reconciliation record across reference types. A representative query filtering journal-line reconciliations by operating unit is:

• SELECT STATEMENT_LINE_ID, REFERENCE_TYPE, REFERENCE_ID, JE_HEADER_ID, AMOUNT, MEANING, ORG_ID FROM APPS.CEBV_STMTRECON WHERE REFERENCE_TYPE = 'JE_LINE' AND ORG_ID = :p_org_id;
• SELECT REFERENCE_TYPE, COUNT(*), SUM(AMOUNT) FROM APPS.CEBV_STMTRECON WHERE MEANING = 'Yes' GROUP BY REFERENCE_TYPE;

Because the view is defined over CE_STATEMENT_RECONCILS_ALL with the CURRENT_RECORD_FLAG and STATUS_FLAG filters built in, callers should not re-apply those predicates; they should instead bind ORG_ID for multi-org security and use REFERENCE_TYPE to constrain the result set.