Search Results currency_code_fc




Overview
Explore in AI Chat

Overview

OZF_FUNDS is an APPS-owned, VALID view within the Oracle Trade Management (OZF) module, which forms part of the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. The view exposes the logical trade fund record as maintained by the Trade Management Funds functionality. Trade funds represent accrual-based and budget-based promotional or trade spend instruments through which organizations plan, distribute, accrue against, and settle liabilities owed to customers, partners, or internal trading units. The view is a secured (organization-filtered) projection rather than a physical table, and it is intended to be consumed by Oracle Forms, OAF pages, concurrent programs, reports, and external integrations rather than written to directly.

The user search term "budget_amount_tc" identifies a column of particular importance in this view. BUDGET_AMOUNT_TC stores the budgeted fund amount expressed in the transaction currency (TC), complementing BUDGET_AMOUNT_FC, which holds the same budget amount in the functional currency (FC) of the associated set of books. Together these columns underpin fund utilisation reporting, available-versus-budget comparisons, and the calculation of amounts available for distribution.

Underlying Base Objects

Per the ETRM 12.2.2 documented metadata, OZF_FUNDS is defined over a single base object: the synonym OZF_FUNDS_ALL_B, which in turn resolves to the underlying Trade Management fund base table that carries the org-specific fund records. The view selects from this base object and applies a row-level organization security predicate. This predicate derives the operating unit (ORG_ID) from the session's CLIENT_INFO through USERENV, extracts the first ten characters, and compares it against the ORG_ID column of the base record, treating a blank prefix character as NULL and defaulting unmatched values to -99. The effect is that a session only sees funds belonging to the operating unit described in its client information, which enforces multi-org data segregation at the view layer.

Because OZF_FUNDS is a view, it inherits the column definitions, constraints, and business meaning of OZF_FUNDS_ALL_B while adding the security filter and the ROWID projection. All fifty-plus database columns of the base object, including the WHO audit columns, descriptive flexfield attributes ATTRIBUTE1 through ATTRIBUTE15, and ATTRIBUTE_CATEGORY, are surfaced unchanged.

Key Columns

Common Use Cases and Queries

The view is typically queried to reconcile budgets, trace available balances, and feed downstream reports. A basic lookup by fund number is shown below.

  • Budget versus availability: SELECT fund_id, fund_number, budget_amount_tc, currency_code_tc, available_amount, distributed_amount FROM ozf_funds WHERE fund_number = :p_fund_number;
  • Budgeted spend by status: SELECT status_code, SUM(budget_amount_tc) FROM ozf_funds GROUP BY status_code;
  • Hierarchy rollup: SELECT hierarchy_id, hierarchy_level, SUM(budget_amount_tc) FROM ozf_funds WHERE hierarchy_id = :p_hierarchy GROUP BY hierarchy_id, hierarchy_level;
  • Accrual exposure: SELECT fund_number, accrued_liable_account, earned_amt, paid_amt FROM ozf_funds WHERE liability_flag = 'Y';

Because the view enforces ORG_ID security from CLIENT_INFO, integrations must establish the correct operating unit context before querying OZF_FUNDS; otherwise the predicate defaults ORG_ID to -99 and returns no rows. Analysts comparing BUDGET_AMOUNT_TC against AVAILABLE_AMOUNT and DISTRIBUTED_AMOUNT obtain the standard measure of fund utilisation in transaction currency, while BUDGET_AMOUNT_FC supports general ledger reconciliation.