Results for “ce_801_eft_reconciled_v”

50+ results




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

Overview

The CE_801_EFT_RECONCILED_V view is a Cash Management (CE) object owned by the APPS schema. It is documented as presenting reconciled payroll payments for unreconciling, meaning it exposes the set of Oracle Payroll EFT (Electronic Funds Transfer) payments that have already been matched to a bank statement line and may subsequently require reversal or unreconciliation. This view serves as the bridge between Oracle Payroll payment data and Oracle Cash Management bank reconciliation data, allowing the reconciliation process to identify payments that flow through bank statements.

In the Oracle EBS 12.1.1 / 12.2.2 architecture, it is a query-only view that presents a union of payment attributes drawn from Payroll tables (payment actions, pre-payments, organization payment methods) and Cash Management tables (statement headers, statement lines, reconciliations). It is used primarily by reconciliation-related logic and reporting that must recognize Payroll-originated EFT payments already reflected on a bank statement. Because it is STATUS = VALID, it is a live, supported object, and it is frequently referenced by the Payroll-to-Cash-Management unreconciliation workflow.

Underlying Base Objects

The view's documented base objects span both the Payroll (PAY) and Cash Management (CE) schemas, accessed by APPS via synonyms:

The view joins these objects on identifiers such as ASSIGNMENT_ACTION_ID, PRE_PAYMENT_ID, BANK_ACCOUNT_ID, and STATEMENT_LINE_ID, aligning each reconciled Payroll payment with its corresponding bank statement line and reconciliation record. Calls to PAY_CE_RECONCILIATION_PKG.PAYMENT_TRANSACTION_INFO resolve transaction dates, concatenated identifiers, and transaction groups at runtime.

Key Columns

  • ROWID — the underlying row identifier from PAY_CE_RECONCILED_PAYMENTS.
  • STATEMENT_LINE_ID / BANK_ACCOUNT_ID — the bank statement line and bank account tied to the reconciliation.
  • ASSIGNMENT_ACTION_ID / SERIAL_NUMBER — links back to the specific payroll payment/assignment action.
  • CURRENCY_CODE / "FUNCTIONAL"/"BANK"/"FOREIGN" — a DECODE that classifies the payment currency relative to the set of books and bank account currency.
  • Effective amount columns — DECODE logic selects the functional, bank, or foreign amount depending on currency and reconciliation status.
  • CLEARED_AMOUNT / CLEARED_BASE_AMOUNT / CLEARED_DATE — mirrored from PCRP.STATUS_CODE, distinguishing cleared ('C') versus void ('V') payments.
  • TRANSACTION_DATE / CONCATENATED_IDENTIFIERS / TRANSACTION_GROUP — computed via PAY_CE_RECONCILIATION_PKG for transaction-group reporting.
  • SL.STATE and lookup MEANING columns — statement line state and descriptive lookups for payment/status types.

Common Use Cases and Queries

Typical uses include investigating why a Payroll EFT payment remains reconciled, generating a listing of cleared versus void payments, and supporting unreconciliation by identifying which statement lines still reference a payment.

SELECT serial_number, bank_account_id, statement_line_id,
       currency_code, cleared_amount, cleared_date, status_code
FROM   ce_801_eft_reconciled_v
WHERE  status_code = 'C';

To locate payments by bank account for a reconciliation review:

SELECT bank_account_id, statement_line_id, serial_number,
       cleared_amount, state
FROM   ce_801_eft_reconciled_v
WHERE  bank_account_id = :p_bank_account_id
ORDER BY cleared_date;

Because the view derives amounts and transaction groups dynamically through PAY_CE_RECONCILIATION_PKG, queries should be filtered (for example, by bank account, status, or date) to avoid costly package executions across the full result set. All access should be performed as an APPS or CE-responsibility user with appropriate Cash Management security profiles applied.