Results for “ce_statement_reconciliations”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The CE_STATEMENT_RECONCILIATIONS view is a secured reporting object in the Oracle E-Business Suite Cash Management (CE) module, owned by the APPS schema. It is a synonym-backed interface to the base table CE_STATEMENT_RECONCILS_ALL, exposing the reconciliation records that link bank statement lines to the corresponding accounting, cashflow, and statement entries matched against them during the bank reconciliation process. In Oracle EBS 12.1.1 and 12.2.2 the view is registered as VALID within the ETRM repository.
The object's primary role is to provide data security enforcement at query time. Rather than exposing all reconciliation rows to every user, the view filters records by the active operating unit, legal entity, and security profile assigned to the session. It queries CE_STATEMENT_RECONCILS_ALL and restricts the result set using CE_SECURITY_PROFILES_V, ensuring that users only see reconciliation activity belonging to organizations they are authorized to access. This makes the view suitable for custom reports, embedded analytics, and integrations that must respect Multi-Org Access Control (MOAC) and legal entity security without re-implementing that logic.
Underlying Base Objects
Per the documented ETRM metadata, CE_STATEMENT_RECONCILIATIONS is defined over the following referenced objects:
- CE_STATEMENT_RECONCILS_ALL (SYNONYM) — the base reconciliation table containing statement line matches.
- CE_SECURITY_PROFILES_V (VIEW) — provides the operating unit and legal entity IDs available to the current user session, driving the WHERE-clause filter.
- FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE (PACKAGES) — EBS foundation utilities supplying session context such as operating unit, user ID, and responsibility.
- MO_GLOBAL (PACKAGE) — the Multi-Org initialization package used to establish the current org context.
- XTR_USER_ACCESS (PACKAGE) — used for user-level access restrictions, typically involving treasury or cash management role-based security.
The view therefore inherits the column set of the base statement reconciliations table while layering on the security predicate. Any insert, update, or delete against reconciliation data must target the underlying base table, not this view.
Key Columns
The view exposes the full reconciliation structure. Important columns include:
- STATEMENT_LINE_ID — identifier of the bank statement line being reconciled.
- REFERENCE_TYPE and REFERENCE_ID — the type of object matched to the statement line (for example JE_LINE, ROI_LINE, or STATEMENT) and its primary key.
- JE_HEADER_ID — the journal entry header associated with the reconciliation, where applicable.
- ORG_ID and LEGAL_ENTITY_ID — the operating unit and legal entity used for security filtering.
- REFERENCE_STATUS, STATUS_FLAG, ACTION_FLAG, CURRENT_RECORD_FLAG, AUTO_RECONCILED_FLAG — lifecycle and state indicators describing how the reconciliation was created and whether it was automatic or manual.
- AMOUNT — the reconciled amount.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program execution context.
- ROWID — the pseudo-column identifier used for row-level addressing.
Common Use Cases and Queries
Typical scenarios include reporting on outstanding versus reconciled statement lines, auditing automatic reconciliations, and building custom cash position dashboards. Because security is enforced inside the view, simple selections require no additional org predicates.
SELECT statement_line_id,
reference_type,
reference_id,
je_header_id,
amount,
status_flag,
auto_reconciled_flag
FROM ce_statement_reconciliations
WHERE statement_line_id = :p_statement_line_id;
To review automatic reconciliation activity within a period:
SELECT csr.statement_line_id,
csr.reference_type,
csr.amount,
csr.creation_date
FROM ce_statement_reconciliations csr
WHERE csr.auto_reconciled_flag = 'Y'
AND csr.creation_date BETWEEN :p_from AND :p_to
ORDER BY csr.creation_date;
Note that the status, action, and current-record flags should be interpreted together with Cash Management reconciliation documentation, as their meaning depends on the reconciliation stage. The view is read-only by design and should be used consistently in custom code to preserve security and multi-org compliance.
-
APPS.CE_STATEMENT_RECONCILIATIONS·↳ CE_SECURITY_PROFILES_V·↳ CE_STATEMENT_RECONCILS_ALL·↳ FND_ACCESS_CONTROL_UTIL·Explore CE module →
-
APPS.CE_STATEMENT_RECONCILIATIONS·↳ CE_SECURITY_PROFILES_V·↳ CE_STATEMENT_RECONCILS_ALL·↳ FND_ACCESS_CONTROL_UTIL·Explore CE module →
-
(Release 10SC Only)
APPS.AR_RGW_CASH_MANAGEMENT_V·↳ AR_CASH_RECEIPTS·↳ AR_CASH_RECEIPT_HISTORY·↳ CE_STATEMENT_HEADERS·Explore AR module →
-
(Release 10SC Only)
APPS.AR_RGW_CASH_MANAGEMENT_V·↳ AR_CASH_RECEIPTS·↳ AR_CASH_RECEIPT_HISTORY·↳ CE_STATEMENT_HEADERS·Explore AR module →
-
View: CE_185_TRANSACTIONS_V 12.2.2
Available Treasury transactions for reconciliation via Open Interface
APPS.CE_185_TRANSACTIONS_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_BANK_BRANCHES_V·Explore CE module →
-
View: CE_185_TRANSACTIONS_V 12.1.1
Available Treasury transactions for reconciliation via Open Interface
APPS.CE_185_TRANSACTIONS_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_BANK_BRANCHES_V·Explore CE module →
-
View: AP_ENC_GL_PAY_V 12.2.2
APPS.AP_ENC_GL_PAY_V·↳ AP_CHECKS_ALL·↳ AP_ENCUMBRANCE_LINES_ALL·↳ AP_INVOICES_ALL·Explore AP module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
VIEW: APPS.AP_ENC_GL_PAY_V 12.2.2
-
VIEW: APPS.AP_ENC_GL_PAY_V 12.2.2
-
View: AP_AEL_SL_PAY_V 12.2.2
Not implemented in this database·Explore AP module →