Results for “object_currency”

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

Overview

OZF_FUND_CHECKBOOK_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Trade Management (OZF) product family. It consolidates funding and budget consumption activity across campaigns and offers, presenting fund checkbook data as a unified set of rows suitable for inquiry screens and concurrent-program extracts. The view was introduced to support the Trade Management "checkbook" concept, where marketers draw against approved budgets for campaigns, offers, and events and require a single ledger-style presentation of approved, pending, and actual consumption.

In EBS 12.1.1 and 12.2.2 the view remains a read-only reporting object; it holds no physical storage and inherits the row-level security of its underlying AMS and OZF objects. Because it is defined with a UNION ALL, it exposes a de-normalized shape that maps readily onto Oracle Discoverer worksheets, BI Publisher reports, and custom OAF pages. The search term component_type_code is relevant because the view explicitly projects this attribute for budget-consumption rows.

Underlying Base Objects

The view text defines the projection over AMS_CAMPAIGNS_VL (aliased A) joined to AMS_ACT_BUDGETS (aliased ACT1). The documented metadata additionally lists AMS_CAMPAIGN_SCHEDULES_VL, AMS_DELIVERABLES_VL, AMS_EVENT_HEADERS_VL, AMS_EVENT_OFFERS_VL, OZF_ACT_BUDGETS, OZF_ACT_OFFERS, OZF_FUNDS_ALL_B, OZF_OFFERS, OZF_FUND_ADJUSTMENT_PVT, and QP_LIST_HEADERS_VL as referenced base objects, reflecting the full UNION ALL expansion that draws consumption from schedules, offers, events, and deliverables.

The join predicate is driven by DECODE logic on TRANSFER_TYPE: for 'REQUEST' rows the budget-used-by identifier is the campaign, while for other transfer types the budget-source identifier is used. The second filter restricts to ARC_ACT_BUDGET_USED_BY = 'CAMP' and excludes rows where the source and used-by types are identical. Status is restricted to 'APPROVED' and 'PENDING'.

Key Columns

• CAMPAIGN_NAME / CAMPAIGN_ID — identifies the campaign against which funds are consumed.
• BUDGET_SOURCE_ID / BUDGET_SOURCE_TYPE — the originating fund or budget account.
• ACT_BUDGET_USED_BY_ID / ARC_ACT_BUDGET_USED_BY — the consuming campaign or object, depending on transfer type.
• APPROVED_AMOUNT — sign-adjusted (negated for non-request transfers) to represent drawdown.
• REQUEST_AMOUNT — populated only for rows with STATUS_CODE = 'PENDING'.
• COMPONENT_TYPE, COMPONENT_NUMBER, COMPONENT_TYPE_CODE, COMPONENT_NAME — explicitly projected as NULL in the budget union, providing a consistent column shape across the unions for component-driven consumption rows sourced from offers, deliverables, and events. component_type_code therefore classifies the type of budget component consumed (for example offer, deliverable, or event), enabling attribution reporting.
• PARENT_SOURCE_ID / PARENT_SRC_CURR / PARENT_SRC_APPRVD_AMT — carry parent funding context, sign-adjusted like APPROVED_AMOUNT.
• REQUEST_CURRENCY, STATUS_CODE, TRANSFER_TYPE — currency, approval state, and the request-versus-transfer discriminator.
• OWNER_USER_ID, SOURCE_CODE, CUSTOM_SETUP_ID — ownership and setup metadata.
• ACTUAL_EXEC_START_DATE / ACTUAL_EXEC_END_DATE — execution window of the campaign.

Common Use Cases and Queries

Typical uses include checkbook drill-down reports, fund utilization dashboards, and reconciliation extracts that compare approved versus consumed amounts by campaign.

Total approved consumption by campaign:

SELECT campaign_name, SUM(approved_amount)
FROM ozf_fund_checkbook_v
WHERE status_code = 'APPROVED'
GROUP BY campaign_name;

Pending requests requiring approval:

SELECT campaign_name, request_amount, request_currency
FROM ozf_fund_checkbook_v
WHERE status_code = 'PENDING';

Attribution by component type:

SELECT component_type_code, SUM(approved_amount)
FROM ozf_fund_checkbook_v
WHERE component_type_code IS NOT NULL
GROUP BY component_type_code;

Because NULL placeholders maintain a stable column list, the view is safe to consume in generic report templates that must span both fund-level and component-level consumption rows.