Results for “okl_cure_fund_trans_all”

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

Overview

OKL_CURE_FUND_TRANS_ALL is a transaction table within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It stores over-payment and under-payment amounts recorded against individual cure payments, aggregated by report and grouped against a vendor program. The table functions as the accounting and reconciliation bridge between cure (credit remediation) activities and the vendor program payment cycle, allowing finance operations to track where a payment deviated from its expected amount and how that variance is attributed to a specific supplier or program.

From a data-modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. The presence of multiple foreign keys pointing to parent operational tables (cure fund transactions, cure payments, refund lines, and suppliers) combined with transactional attribute columns such as AMOUNT, FUND_TYPE, and TRANS_TYPE suggests the table behaves more as a descriptive satellite attached to those business hubs than as an independent hub or an association link. This classification should be treated as a modeling suggestion rather than a normative fact.

Key Information Stored

The table contains 34 documented columns. The most operationally significant are:

• CURE_FUND_TRANS_ID — Surrogate primary key identifying each fund transaction row; also participates as a foreign key reference back to OKL_CURE_FUND_TRANS.
• CURE_PAYMENT_ID — Foreign key to OKL_CURE_PAYMENTS_B, linking the variance entry to its originating cure payment.
• CURE_REFUND_LINE_ID — Foreign key to OKL_CURE_REFUND_LINES, tying the transaction to a specific refund line.
• VENDOR_ID — Foreign key to AP_SUPPLIERS, identifying the supplier or vendor program against which the variance is grouped.
• AMOUNT — The monetary value of the over- or under-payment.
• FUND_TYPE — Classifies the nature of the fund movement (e.g., the funding category driving the variance).
• TRANS_TYPE — Distinguishes the transaction class, such as over-payment versus under-payment.
• PROGRAM_ID and PROGRAM_APPLICATION_ID — Identify the vendor program and its application context, supporting program-level aggregation.
• PROGRAM_UPDATE_DATE — Timestamp associated with the program-side update, useful for reconciliation timing.
• ORG_ID — Multi-org operating unit identifier, essential for operating-unit-scoped reporting.
• REQUEST_ID — Links the row to the concurrent request that created it.
• OBJECT_VERSION_NUMBER — Optimistic-locking version column for concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.

The documented metadata does not explicitly identify a separate business-key unique index; CURE_FUND_TRANS_ID serves as the operational surrogate key.

Common Use Cases and Queries

Typical scenarios include reconciling cure payments to vendor programs, reporting outstanding over-/under-payments by supplier, and auditing program-level variance trends. A representative query joins the table to its supplier master and payment parent:

• Variance by vendor: SELECT t.VENDOR_ID, SUM(t.AMOUNT) FROM OKL.OKL_CURE_FUND_TRANS_ALL t WHERE t.TRANS_TYPE = :type GROUP BY t.VENDOR_ID;
• Payment detail: join CURE_PAYMENT_ID to OKL_CURE_PAYMENTS_B to surface payee and payment date alongside AMOUNT.
• Supplier enrichment: join VENDOR_ID to AP_SUPPLIERS for supplier name and site.
• Operating-unit reporting: filter by ORG_ID to scope results to a legal entity.
• Refund tracing: join CURE_REFUND_LINE_ID to OKL_CURE_REFUND_LINES to connect the variance to its refund activity.

Related Objects

The following parent objects are referenced through documented foreign keys and are the most significant related entities:

• OKL_CURE_FUND_TRANS — Parent fund transaction, joined on CURE_FUND_TRANS_ID.
• OKL_CURE_PAYMENTS_B — Cure payment base table, joined on CURE_PAYMENT_ID.
• OKL_CURE_REFUND_LINES — Refund lines, joined on CURE_REFUND_LINE_ID.
• AP_SUPPLIERS — Supplier master, joined on VENDOR_ID.

Program context is further provided through PROGRAM_ID and PROGRAM_APPLICATION_ID, which resolve to the OKL vendor program tables used during cure processing.