Results for “total_budget”

33 results




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

Overview

OZF_FUND_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OZF - Trade Management product family, which provides the funds, accrual, and settlement infrastructure used to plan, budget, and reimburse trade promotion activities. The view consolidates the descriptive, financial, and accrual attributes of a trade management fund into a single denormalized row, resolving the fund record against its category, internal owner, and user-defined status. Because it is a view rather than a base table, it exposes no storage of its own; it is a read-only projection intended for inquiry screens, concurrent reports, and downstream integration extracts. Its status is VALID, indicating the underlying definition compiles cleanly against the documented base objects.

Underlying Base Objects

The documented view metadata identifies four referenced base objects, all of which are themselves views in the APPS schema:

  • OZF_FUNDS_ALL_VL — the primary source, aliased twice in the view text (A and E) so that a fund and its parent fund can be joined within the same row. This object supplies the operational fund columns such as fund number, type, usage, dates, budget, and amounts.
  • AMS_CATEGORIES_VL (aliased F) — supplies CATEGORY_NAME for the fund's category identifier.
  • AMS_JTF_RS_EMP_V (aliased D) — a resource/employee view supplying the owner's FULL_NAME and EMAIL.
  • AMS_USER_STATUSES_VL (aliased AUS) — supplies the user-defined status NAME that corresponds to USER_STATUS_ID.

The view text joins these objects on their respective key columns (USER_STATUS_ID, CATEGORY_ID, OWNER, and PARENT_FUND_ID), producing a flattened result set rather than normalized relational output. Because every source is a view, runtime performance depends on the definitions below them, notably the fund base tables and their organization security predicates.

Key Columns

The projection exposes a broad set of columns that can be grouped functionally:

Common Use Cases and Queries

The view is typically used to report fund balances, to validate accrual setup, and to feed external budgeting or analytics systems. A typical balance inquiry filters by organization and active status:

  • SELECT fund_number, short_name, budget_amount_tc, available_amount, committed_amt, earned_amt, paid_amt FROM ozf_fund_details_v WHERE org_id = :p_org_id AND status_code = 'ACTIVE';
  • SELECT fund_id, fund_number, available_amount, holback_amt FROM ozf_fund_details_v WHERE fund_id = :p_fund_id;
  • SELECT category_name, fund_type, SUM(original_budget) FROM ozf_fund_details_v GROUP BY category_name, fund_type;

Because the view does not itself enforce organization-level security beyond the predicates inherited from OZF_FUNDS_ALL_VL, callers should supply the appropriate ORG_ID or rely on the underlying MOAC (Multi-Org Access Control) view logic. All fund references such as PARENT_FUND_ID, PLAN_ID, and USER_STATUS_ID should be joined back to their respective entities when descriptive context beyond the flattened columns is required.