Results for “okl_cure_fund_sums_all”

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

Overview

OKL_CURE_FUND_SUMS_ALL is a transactional table in the OKL (Lease and Finance Management) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The table stores funds available for refund, derived from overpayment or underpayment calculations produced by a concurrent report, and grouped at the vendor program level. In leasing operations, this object acts as the persisted output of the cure-fund computation, allowing refund balances to be reported, audited, and reconciled per vendor program rather than recomputed on demand.

From a modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This is consistent with a table whose primary identity is a single surrogate key (CURE_FUND_SUM_ID) and whose non-key columns carry descriptive and measurable attributes (BALANCE, vendor program references, audit columns) that change over time. The table does not decompose into multiple hubs and links; it behaves as a descriptive satellite attached to the cure fund and vendor concepts, so implementers building a Data Vault layer should treat it as satellite data rather than as a hub or link.

Key Information Stored

The table is owned by OKL and documents 30 columns in the ETRM 12.2.2 physical schema. The columns below carry the substantive business and technical content.

• CURE_FUND_SUM_ID — the surrogate primary key and the identifier carried into the OKL_CURE_FUND_SUMS relationship. It is the join key for downstream reporting and for the foreign key to OKL_CURE_FUND_SUMS.
• VENDOR_ID — the vendor (supplier) associated with the refund group. This is the strongest business-key candidate and is a foreign key to AP_SUPPLIERS, enabling supplier-level aggregation.
• BALANCE — the funds available for refund, derived from overpayment or underpayment amounts. This is the primary measure of the table and the value most commonly reported.
• ORG_ID — the operating unit that owns the row, supporting multi-org security and partitioned reporting.
• REQUEST_ID — the concurrent request that generated or last processed the row, used for traceability back to the report run.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — the vendor program identity and its last update timestamp, which define the grouping level referred to in the object description.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexfield (descriptive) columns, available for client-specific refund classifications.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns maintained by the application and useful for reconciliation and change tracking.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect concurrent updates.

Where unique indexes are documented, VENDOR_ID combined with the program and org attributes is the natural business-key candidate; CURE_FUND_SUM_ID remains the surrogate identifier.

Common Use Cases and Queries

The most frequent use of this table is refund reporting by supplier and vendor program. A typical pattern joins the sums to AP_SUPPLIERS to present supplier names alongside the available balance:

• Refund availability report: SELECT s.vendor_id, v.vendor_name, s.balance FROM okl.okl_cure_fund_sums_all s JOIN ap.ap_suppliers v ON v.vendor_id = s.vendor_id WHERE s.org_id = :p_org_id ORDER BY v.vendor_name;
• Reconciliation to the parent cure fund: join CURE_FUND_SUM_ID to OKL_CURE_FUND_SUMS to compare summarized refund balances against their source records and to confirm completeness of the report output.
• Concurrent request audit: filter on REQUEST_ID to inspect the rows produced by a specific run of the cure-fund report and to verify totals.
• Multi-org reporting: constrain ORG_ID to enforce operating unit security when the table is exposed through a report or an OAF page.
• Change tracking and locking analysis: use LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to identify stale or concurrently modified rows during troubleshooting.

Related Objects

The following objects are the most significant references and dependencies for OKL_CURE_FUND_SUMS_ALL, based on the documented foreign key relationships.

• AP_SUPPLIERS — referenced through OKL_CURE_FUND_SUMS_ALL.VENDOR_ID; provides the supplier identity for refund grouping and reporting.
• OKL_CURE_FUND_SUMS — parent table referenced through OKL_CURE_FUND_SUMS_ALL.CURE_FUND_SUM_ID; holds the cure-fund summary records from which these balances are derived.
• The concurrent program and report that populate the table, identified at run level through REQUEST_ID, and the vendor program definition referenced by PROGRAM_ID and PROGRAM_APPLICATION_ID.
• The standard OKL purchasing and leasing supplier views used in refund inquiries, which surface AP_SUPPLIERS data alongside these refund balances.

Together these relationships confirm that the table serves as a vendor-program-grouped refund balance store, tightly coupled to supplier data and to the parent cure fund summary.