Results for “je_line”

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

Overview

The APPS.CE_STATEMENT_RECONCILIATIONS view is a security-enabled reporting layer over cash management statement reconciliation data in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes rows from the CE_STATEMENT_RECONCILS_ALL table that the current responsibility is authorized to see, applying multi-org and legal entity access rules at query time. The view is defined in the APPS schema and is referenced by Oracle Cash Management reconciliation windows, Oracle Payments integration, and reconciliation reporting. Because it enforces row-level security through CE_SECURITY_PROFILES_V, direct queries against the underlying table may return data outside the caller's access scope, whereas this view does not. The view also handles a specific exception for reference types JE_LINE, ROI_LINE, and STATEMENT, ensuring journal-line and reconciliation-line references remain visible regardless of the organization filter. The user search term "je_line" corresponds directly to one of these special reference types, making this view the primary access path for correlating Cash Management bank statement lines with Oracle General Ledger journal lines.

Underlying Base Objects

The principal base object is CE_STATEMENT_RECONCILS_ALL, accessed through the synonym CE_STATEMENT_RECONCILS_ALL. This table stores reconciliation matches between bank statement lines and the transactions applied against them, including journal entry references. The view's WHERE clause references CE_SECURITY_PROFILES_V, a security profile view used to resolve the operating units, business groups, and legal entities assigned to the current user. Documented supporting packages include FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS, which supply organization context, security profile configuration, and user access resolution during view evaluation. The view text exposes CSR.ROWID, which permits update-capable behavior in some Oracle Forms contexts even though the view is primarily used for query and reporting.

Key Columns

• STATEMENT_LINE_ID — Identifier of the bank statement line being reconciled.
• REFERENCE_TYPE — Classification of the matched source; values include JE_LINE, ROI_LINE, and STATEMENT.
• REFERENCE_ID — The identifier of the referenced transaction; for JE_LINE it maps to the journal line.
• JE_HEADER_ID — General Ledger journal header associated with the reconciliation entry.
• ORG_ID — Operating unit that owns the reconciliation record.
• LEGAL_ENTITY_ID — Legal entity used in the security predicate.
• AMOUNT — Reconciled amount for the matched line.
• STATUS_FLAG, ACTION_FLAG, CURRENT_RECORD_FLAG, AUTO_RECONCILED_FLAG — State indicators describing reconciliation status and processing history.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context for the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.
• ROWID — Physical row identifier used for DML and row-level operations.

Common Use Cases and Queries

Typical usage includes reconciliation reporting, GL-to-bank analysis, and integration extracts that must respect operating unit security. The most common pattern filters on REFERENCE_TYPE = 'JE_LINE' to isolate general ledger journal line matches.

• Extracting journal-line reconciliations for a specific operating unit: SELECT statement_line_id, reference_id, je_header_id, amount FROM apps.ce_statement_reconciliations WHERE org_id = :p_org_id AND reference_type = 'JE_LINE';
• Auditing auto-reconciled records: SELECT statement_line_id, status_flag, amount FROM apps.ce_statement_reconciliations WHERE auto_reconciled_flag = 'Y' AND current_record_flag = 'Y';
• Reviewing unmatched or reversed entries by status: SELECT statement_line_id, reference_type, status_flag FROM apps.ce_statement_reconciliations WHERE status_flag IN ('U','R');
• Joining to journal sources to trace accounting entries related to a bank statement line during reconciliation research.

Because the view applies CE_SECURITY_PROFILES_V predicates, results automatically reflect the responsibility's organization and legal entity assignments, and queries should not add redundant MO_GLOBAL initialization filters unless required by downstream logic.