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:
- Identity and hierarchy: FUND_ID, PARENT_FUND_ID, FUND_NUMBER, HIERARCHY_ID, ORG_ID, and BUSINESS_UNIT_ID.
- Classification: CATEGORY_ID, CATEGORY_NAME, FUND_TYPE, FUND_USAGE, STATUS_CODE, USER_STATUS_ID, and the resolved user status NAME.
- Validity and ownership: START_DATE_ACTIVE, END_DATE_ACTIVE, OWNER, FULL_NAME, EMAIL, and SHORT_NAME.
- Budgets and balances: BUDGET_AMOUNT_TC, BUDGET_AMOUNT_FC, ORIGINAL_BUDGET, HOLDBACK_AMT, TRANSFERED_IN_AMT, TRANSFERED_OUT_AMT, AVAILABLE_AMOUNT, and DISTRIBUTED_AMOUNT. Two computed expressions return the usable budget net of holdbacks and transfers, and the gross budget including transfers, respectively.
- Fund lifecycle amounts: PLANNED_AMT, COMMITTED_AMT, EARNED_AMT, and PAID_AMT, which track a fund from commitment through settlement.
- Accrual configuration: ACCRUAL_METHOD, ACCRUAL_OPERAND, ACCRUAL_RATE, ACCRUAL_BASIS, ACCRUAL_UOM, ACCRUAL_CAP, ACCRUAL_PHASE, ACCRUAL_QUANTITY, and ACCRUAL_DISCOUNT_LEVEL.
- Accounting and DFF: ACCRUED_LIABLE_ACCOUNT, DED_ADJUSTMENT_ACCOUNT, LIABILITY_FLAG, LIABLE_ACCNT_SEGMENTS, ADJUSTMENT_ACCNT_SEGMENTS, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15.
- Planning and audit: PLAN_TYPE, PLAN_ID, PLAN_TYPE, TASK_ID, DEPARTMENT_ID, COUNTRY_ID, THRESHOLD_ID, CUSTOM_SETUP_ID, plus standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER.
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.
-
View: OZF_FUND_DETAILS_V 12.2.2
APPS.OZF_FUND_DETAILS_V·↳ AMS_CATEGORIES_VL·↳ AMS_JTF_RS_EMP_V·↳ AMS_USER_STATUSES_VL·Explore OZF module →
-
View: OZF_FUND_DETAILS_V 12.1.1
APPS.OZF_FUND_DETAILS_V·↳ AMS_CATEGORIES_VL·↳ AMS_JTF_RS_EMP_V·↳ AMS_USER_STATUSES_VL·Explore OZF module →
-
VIEW: BIM.BIM_R_FUND_DIMSUM# 12.2.2
-
VIEW: BIM.BIM_R_FUND_DIMSUM# 12.2.2
-
TABLE: BIM.BIM_R_FUND_DIMSUM 12.2.2
-
TABLE: BIM.BIM_R_FUND_DIMSUM 12.1.1
-
View: OZF_FUND_REQUESTS_V 12.1.1
Fund request tracking table.
APPS.OZF_FUND_REQUESTS_V·↳ OZF_FUND_DETAILS_V·↳ OZF_FUND_REQUESTS·Explore OZF module →
-
View: OZF_FUND_REQUESTS_V 12.2.2
Fund request tracking table.
APPS.OZF_FUND_REQUESTS_V·↳ OZF_FUND_DETAILS_V·↳ OZF_FUND_REQUESTS·Explore OZF module →
-
eTRM - OZF Tables and Views 12.2.2
OZF_XREF_MAP table created for SIebel TPM Integration
-
eTRM - OZF Tables and Views 12.1.1
Table to store the Market eligibilty for a Offer Worksheet