Search Results ozf_claims




Overview
Explore in AI Chat

Overview

The APPS.OZF_FUNDS_PAID view is a reporting and integration object within the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / ETRM) module. It consolidates fund utilization activity against customer claims, presenting a unified picture of funds that have been applied, accrued, or paid in relation to trade promotion and channel-funds claim processing. Unlike a base table, this view is a denormalized join designed for query convenience: it merges fund utilization records with their associated claim headers, claim lines, and customer account details, so that reporting tools and interface programs can retrieve payment-oriented fund data without manually joining four separate objects.

In EBS 12.1.1 and 12.2.2 the view is owned by the APPS schema and is built on public synonyms pointing to the underlying ETRM tables. Because it is a view rather than a stored table, it carries no independent data; all values are derived at query time from the referenced base objects. Its most common role is to support funds-paid analysis, claim reconciliation reporting, and custom extracts that need claim-to-fund linkage.

Underlying Base Objects

The documented referenced base objects are all synonyms resolved through APPS:

  • OZF_FUNDS_UTILIZED_ALL_B — the primary driver, holding the fund utilization record (the umbrella record that ties a fund to its usage).
  • OZF_CLAIM_LINES — the claim line detail, joined to the utilization via utilization_id in an outer-join ((+)) direction, meaning utilizations can appear even where no claim line exists.
  • OZF_CLAIMS — the claim header, joined to claim lines by claim_id.
  • HZ_CUST_ACCOUNTS — the Trading Community Architecture (TCA) customer account, joined by cust_account_id to supply the account name.

Note that the outer-join is applied on the utilization-to-claim-line relationship, while the claim-line-to-claim and claim-to-account joins are inner joins. Only claim-linked utilizations therefore appear in a fully populated row.

Key Columns

  • utilization_id, fund_id, plan_type, plan_id, component_type, component_id, object_type — the fund utilization context identifying which fund at which plan level was drawn against.
  • claim_number, claim_date, claim_id, claim_line_id — the claim identification and its line detail.
  • currency_code — from the claim line, indicating the currency of the amount.
  • account_name — the customer account name from HZ_CUST_ACCOUNTS.
  • payment_method — the settlement method recorded on the claim.
  • amount — the claim line amount, representing the value of the funds involved.

Common Use Cases and Queries

Typical uses include reconciling accrued versus settled funds, reporting by customer account, and extracting fund-paid totals by currency or plan. Because the user search context is ozf_claims, this view is especially relevant when answering "how much has been paid to a customer against a claim?"

Sample query returning paid funds per claim:

SELECT claim_number,
       account_name,
       currency_code,
       payment_method,
       SUM(amount) AS total_amount
FROM   apps.ozf_funds_paid
WHERE  claim_date >= :p_from_date
GROUP  BY claim_number, account_name, currency_code, payment_method;

A second scenario traces a specific utilization back to its claim:

SELECT utilization_id, fund_id, claim_number, claim_line_id, amount
FROM   apps.ozf_funds_paid
WHERE  utilization_id = :p_utilization_id;

Because the utilization-to-claim-line join is outer, administrators should be aware that orphan utilizations may surface with null claim columns when filtering solely on claim attributes, and standard ETRM security (operating unit / responsibility) is not enforced within the view itself.