Search Results promise_date

Overview

OKL_PROMISE_TO_PAYS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It presents the contents of the OKL_PROMISE_TO_PAYS base table in a denormalized, read-optimized form suitable for external queries, concurrent program outputs, and integrations. Promise-to-pay records capture a lessee's or obligor's commitment to remit a specific amount on a specific date, typically arising during collections or delinquency management workflows. Because ETRM treats the source table as an operational entity, the view serves as the standard read interface, insulating downstream consumers from direct dependency on the underlying table's physical structure while still exposing the full complement of business and descriptive attributes. The view is documented in ETRM 12.2.2 metadata; the "Not implemented in this database" note in the source excerpt indicates that the object may not exist in every environment, depending on whether the OKL collections-related schema components have been applied. The absence of an owner in the documented metadata means qualified references should always include the OKL schema prefix (for example, OKL.OKL_PROMISE_TO_PAYS_V) in cross-schema queries.

Underlying Base Objects

The view is defined over a single documented base object: OKL_PROMISE_TO_PAYS, aliased PTPB in the view text. The SELECT list is an explicit column enumeration rather than a wildcard, which is a deliberate design choice that stabilizes the view's column order and lets Oracle invalidate the view if the table's structure changes. Each row carries the base table's ROWID exposed as ROW_ID, providing a stable physical locator that can be used for joins back to the table in update scenarios. The view also carries the full standard WHO columns and the multi-organization ORG_ID column, indicating that the base table is organization-partitioned under Multi-Org (or MOAC) security. No additional tables, synonyms, or joined objects are documented as contributing to the view definition.

Key Columns

• ID — Primary surrogate key of the promise-to-pay record, used to relate it to downstream transactions or correspondence.
• PROMISE_DATE — The date on which the obligated party has committed to make payment. This is the column most frequently targeted by users searching for "promise_date" and the driving field in most aging and follow-up reports.
• PROMISED_AMOUNT — The amount the party has agreed to pay on the promise date.
• ADJUSTED_AMOUNT — The amount after any adjustments applied to the promise.
• PAYMENT_RECEIVED_DATE — The date the promised payment was actually received; a null value against a past PROMISE_DATE indicates an unmet commitment.
• CHEQUE_NUMBER — Instrument reference where payment is made by cheque.
• XPT_CODE, PPS_CODE, PYM_CODE, CAC_ID — Foreign references to the associated party, promise source, payment method, and contract or customer account context.
• SEQUENCE_NUMBER — Ordering of promise records within the parent transaction.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OKL framework.
• ORG_ID — Operating unit identifier enforcing Multi-Org access control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments holding client-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context for records created or updated by batch processes.
• ROW_ID — The base table ROWID exposed as a character column.

Common Use Cases and Queries

Typical uses include collections follow-up reporting, promise-versus-actual performance tracking, cash forecasting, and reconciliation interfaces. Because the view is thin, queries perform comparably to queries against the base table and can be filtered, grouped, and joined freely.

Listing open promises through a cutoff date:

• SELECT id, xpt_code, promised_amount, promise_date, payment_received_date FROM okl.okl_promise_to_pays_v WHERE org_id = :p_org_id AND payment_received_date IS NULL AND promise_date <= :p_cutoff_date ORDER BY promise_date;

Aggregating promised amounts by month for forecasting:

• SELECT TRUNC(promise_date,'MM') promise_month, SUM(promised_amount) total_promised FROM okl.okl_promise_to_pays_v WHERE org_id = :p_org_id GROUP BY TRUNC(promise_date,'MM') ORDER BY promise_month;

Comparing commitments fulfilled on time against those that slipped:

• SELECT id, promise_date, payment_received_date, promised_amount, adjusted_amount FROM okl.okl_promise_to_pays_v WHERE org_id = :p_org_id AND payment_received_date IS NOT NULL AND payment_received_date > promise_date;

These patterns support both ad hoc reporting through BI Publisher or SQL*Plus and embedded integration logic, always with ORG_ID constrained where Multi-Org security applies.