Results for “anticipated_value_date”

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

Overview

CE_AP_FC_PAYMENTS_V is a Cash Management (CE) forecasting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as a forecasting source for Oracle Payables (AP) payment activity, providing Cash Management with the payment-level data required to project future cash outflows against bank accounts. The view consolidates payment records from AP_CHECKS_ALL with bank account usage information and supplier attributes, producing a denormalized result set that the Cash Management cash forecasting engine and related reporting components can consume directly.

Because it is a view rather than a table, CE_AP_FC_PAYMENTS_V does not store data. It is a read-only, query-time projection whose contents are always derived from the current state of the underlying Payables and Cash Management tables. This makes it suitable for real-time reporting on expected and actual payment disbursements, but it also means query cost is governed entirely by the base tables and their indexes.

Underlying Base Objects

The view is defined over a four-table join with an anti-join filter, as documented in the ETRM metadata:

• AP_CHECKS_ALL (synonym) — the primary source of payment records, supplying payment amounts, currency, status, dates, payment method, bank account usage reference, vendor site, and organization.
• CE_BANK_ACCT_USES_ALL (synonym) — provides the bank account identifier associated with each payment's cash account usage.
• PO_VENDOR_SITES_ALL (view) — supplies the supplier site, payment priority, and pay group attributes.
• PO_VENDORS (view) — supplies the supplier type lookup code.
• CE_BANK_ACCOUNTS (synonym) — referenced in a NOT EXISTS subquery to exclude netting bank accounts.
• FND_GLOBAL (package) — referenced for runtime context such as organization and user session values.

The join logic links payments to their supplier site and cash bank account usage, while the exclusion predicate removes any bank account flagged as a netting account (NETTING_ACCT_FLAG = 'Y'). Payments are included only when their status is NEGOTIABLE, CLEARED, CLEARED BUT UNACCOUNTED, RECONCILED, or RECONCILED UNACCOUNTED, or when status is ISSUED and a future payment due date exists — thereby restricting the forecast set to payments with meaningful cash flow timing.

Key Columns

• CHECK_ID / REFERENCE_ID — primary identifier of the payment record.
• BASE_AMOUNT / AMOUNT — the payment value, with cleared amounts preferred through nested NVL logic when available.
• CURRENCY_CODE — currency of the payment.
• PAYMENT_PRIORITY — supplier-site payment priority, defaulting to 99 when null.
• SUPPLIER_TYPE / PAYGROUP — supplier classification and pay group, defaulting to '-1' when unavailable.
• CLEARED_DATE / MATURITY_DATE / PAYMENT_DATE — cleared date, future payment due date, and check date respectively.
• ACTUAL_VALUE_DATE / ANTICIPATED_VALUE_DATE — value dates used to place cash flow in the forecast horizon.
• STATUS — payment status lookup code.
• BANK_ACCOUNT_ID / PAYMENT_METHOD / ORG_ID / CHECK_NUMBER — bank account, disbursement method, operating unit, and payment document number.

Common Use Cases and Queries

Typical uses include cash position forecasting by bank account, anticipated disbursement reporting by value date, and reconciliation of forecast to actual clearing.

• Payments expected to clear within a date window for a given bank account.
• Aggregate forecasted outflow by currency and payment priority.
• Supplier-level analysis of open negotiable payments.

Sample query:

SELECT bank_account_id, currency_code, SUM(amount) forecast_amount
FROM ce_ap_fc_payments_v
WHERE anticipated_value_date BETWEEN :from_date AND :to_date
AND org_id = :org_id
GROUP BY bank_account_id, currency_code;