Results for “okl_cure_payments_v”

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

Overview

OKL_CURE_PAYMENTS_V is a reporting view within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its documented purpose is to store and expose payments made against a report so that reconciliation can be performed. The view presents a denormalized, translation-aware projection of the underlying payment records, combining header-level payment data with language-specific descriptive text. This design allows reconciliation users, concurrent programs, and integration interfaces to consume payment information through a single logical object rather than joining the base tables directly.

The view is relevant to Oracle EBS 12.1.1 and 12.2.2 environments. The ETRM metadata notes that the object is "Not implemented in this database," and no referenced base objects or owning schema were documented, which means the view may not be deployed in every instance. Where it does exist, it functions as a read-oriented surface for reconciliation reporting rather than a transactional entry point.

Underlying Base Objects

Although the ETRM "referenced base objects" field is empty, the view text itself documents two base objects: OKL_CURE_PAYMENTS_B and OKL_CURE_PAYMENTS_TL. These follow the standard EBS multi-language (MLS) pattern in which a "_B" table holds transactional, language-independent data and a "_TL" table stores translated descriptive columns such as COMMENTS. The view joins the two on CURE_PAYMENT_ID and filters the translation table by CPYT.LANGUAGE = USERENV('LANG'), so each query returns only the row in the caller's session language. ROW_ID is projected from CPYB.ROWID, providing a unique row identifier for the base record.

Key Columns

• CURE_PAYMENT_ID — Primary identifier for the payment record and the join key between the _B and _TL tables.
• PAYMENT_REFERENCE_NUMBER — The payment reference supplied against the report; the column most commonly used to trace and match payments during reconciliation.
• PAYMENT_TYPE — Classifies the nature of the payment recorded against the report.
• PAYMENT_DATE — Date on which the payment was made or recorded.
• AMOUNT — Monetary value of the payment.
• COMMENTS — Language-specific descriptive text drawn from the _TL table.
• ORG_ID — Operating unit identifier, supporting Multi-Org–restricted access.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the process that created or last updated the row.
• OBJECT_VERSION_NUMBER — Optimistic locking version, indicating the row is maintained through the EBS framework.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SOURCE_LANG, LANGUAGE, SFWT_FLAG — Standard EBS descriptive flexfield, WHO, and MLS audit columns.

Common Use Cases and Queries

Typical usage centers on reconciling payments to a report and looking up a payment by its reference number. A basic query filters on the reference:

• SELECT cure_payment_id, payment_type, payment_reference_number, payment_date, amount FROM okl_cure_payments_v WHERE payment_reference_number = :ref;
• SELECT payment_reference_number, amount, payment_date FROM okl_cure_payments_v WHERE org_id = :org AND payment_date BETWEEN :from_date AND :to_date;

These queries support payment tracing, reconciliation summaries, and integration extracts. Because the view already resolves the language join, callers need not join the _TL table themselves, and Multi-Org security is inherited from ORG_ID. Analysts verifying availability should confirm deployment in the target instance, since the metadata records the view as not implemented in the documented database.