Results for “ozf_act_budgets”

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

Overview

OZF.OZF_ACT_BUDGETS is a Trade Management (OZF) transactional table that holds information about budget sources for a marketing activity. Each row represents a budget request, allocation, transfer, or adjustment associated with a marketing activity such as a campaign, event, deliverable, or fund. The table is the central repository for tracking how budget amounts are requested, approved, spent, and adjusted across the trade promotion lifecycle in Oracle EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the ETRM metadata classifies OZF_ACT_BUDGETS heuristically as a link table. This classification is suggested by its FK structure: the table resolves many-to-many relationships between marketing activities (campaigns, events, deliverables, funds) and the budget source or usage entities. It therefore behaves as an associative fact/link object rather than a pure hub or satellite, and this classification should be treated as a modeling suggestion rather than a physical enforcement.

Key Information Stored

The table contains 61 documented columns. The most significant are:

• ACTIVITY_BUDGET_ID — surrogate primary key (OZF_ACT_BUDGETS_PK, also unique via OZF_ACT_BUDGETS_U1); the business-key candidate for the row.
• BUDGET_SOURCE_TYPE and BUDGET_SOURCE_ID — identify where the budget originates (for example a campaign or event header).
• ACT_BUDGET_USED_BY_ID and ARC_ACT_BUDGET_USED_BY — identify the consuming activity instance.
• TRANSACTION_TYPE, TRANSFER_TYPE, REASON_CODE — classify the nature of the budget movement.
• REQUEST_AMOUNT, REQUEST_CURRENCY, SRC_CURR_REQUEST_AMT, REQUEST_DATE — capture the requested budget and its currency context.
• APPROVED_AMOUNT, APPROVED_ORIGINAL_AMOUNT, APPROVED_IN_CURRENCY, APPROVED_AMOUNT_FC, APPROVAL_DATE, APPROVER_ID — capture approval outcome and approver.
• SPENT_AMOUNT — tracks consumption against the approved budget.
• STATUS_CODE, USER_STATUS_ID, POSTED_FLAG, ADJUSTED_FLAG — workflow and posting state.
• REQUESTER_ID, OWNER_ID, CONTACT_ID, VENDOR_ID — party references for the request and ownership.
• PARENT_ACT_BUDGET_ID, PARENT_SOURCE_ID, PARENT_SRC_CURR, PARENT_SRC_APPRVD_AMT — self-referencing hierarchy for derived budgets.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER) and SECURITY_GROUP_ID for multi-org/security enforcement.

Common Use Cases and Queries

Typical reporting scenarios include budget-vs-spend analysis, approval cycle tracking, and source-to-consumption tracing. A representative query joins the table to activity headers to reconcile approved amounts:

SELECT b.activity_budget_id,
       b.budget_source_id,
       b.request_amount,
       b.approved_amount,
       b.spent_amount,
       b.status_code
FROM   ozf.ozf_act_budgets b
WHERE  b.budget_source_type = 'CAMPAIGN'
AND    b.approved_amount > 0;

Analysts also aggregate spend by activity and requester, or filter on POSTED_FLAG and ADJUSTED_FLAG to isolate adjustments that have been posted to the general ledger. Hierarchy queries can walk PARENT_ACT_BUDGET_ID to reconstruct transferred or rolled-up budgets.

Related Objects

The table participates in several foreign key relationships and is referenced by key Trade Management and Funds entities:

• AMS_CAMPAIGNS_ALL_B — referenced via both ACT_BUDGET_USED_BY_ID and BUDGET_SOURCE_ID.
• AMS_EVENT_HEADERS_ALL_B — referenced via both ACT_BUDGET_USED_BY_ID and BUDGET_SOURCE_ID.
• AMS_DELIVERABLES_ALL_B — referenced via ACT_BUDGET_USED_BY_ID.
• OZF_FUNDS_ALL_B — referenced via ACT_BUDGET_USED_BY_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.

These relationships make OZF_ACT_BUDGETS a pivotal join point for trade promotion budget reporting, bridging activity headers to the funds that finance them.