Results for “adjustment_type_id”

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

Overview

OZF_FUNDS_UTILIZED_ALL_B is the base table in the Oracle E-Business Suite Trade Management (OZF) module that stores fund utilization details across the 12.1.1 and 12.2.2 releases. It records how accrued or budgeted trade promotion funds are consumed against plans, components, claims, and transactions, making it a central transactional object for accrual accounting, fund consumption tracking, and settlement processing within Trade Management.

The table resides in the OZF schema and is fully partitioned to support multi-org and multi-currency operations. Its primary key, OZF_FUNDS_UTILIZED_ALL_B_PK, is defined on UTILIZATION_ID, and a unique index, OZF_FUNDS_UTILIZED_ALL_B_U1, also exists on UTILIZATION_ID. The _B suffix indicates this is a base (non-translated) table; the corresponding translated table OZF_FUNDS_UTILIZED_ALL_TL holds language-specific descriptive attributes keyed by UTILIZATION_ID.

Based on the documented foreign key structure, the Data Vault classification for this object is hub-leaning. UTILIZATION_ID behaves as a durable business key with numerous dependent references, suggesting it functions as a hub entity whose surrounding details could be modeled as satellites or links in a dimensional or Data Vault implementation.

Key Information Stored

The most significant columns in this table fall into several logical groups:

• UTILIZATION_ID — Surrogate primary key and unique business-key candidate; identifies each fund utilization record.
• UTILIZATION_TYPE, FUND_ID, PLAN_TYPE, PLAN_ID — Describe the nature of the utilization and link it to the parent fund and plan.
• COMPONENT_TYPE, COMPONENT_ID, OBJECT_TYPE, OBJECT_ID — Identify the promotional component and the transaction object against which funds were utilized.
• ORDER_ID, INVOICE_ID, ORDER_LINE_ID, GL_DATE — Tie utilization to specific order and invoice transactions and the general ledger accounting date.
• AMOUNT, ACCTD_AMOUNT, CURRENCY_CODE — Capture the transaction amount, its accounted (functional currency) value, and the transaction currency.
• EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, EXCHANGE_RATE — Provide currency conversion context for multi-currency accruals.
• AMOUNT_REMAINING, ACCTD_AMOUNT_REMAINING, PLAN_CURR_AMOUNT, PLAN_CURR_AMOUNT_REMAINING — Track remaining balances at transaction and plan currency levels.
• GL_POSTED_FLAG — Indicates whether the utilization has been posted to the general ledger.
• ORG_ID, SECURITY_GROUP_ID — Enforce multi-org and security group access controls.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Provide descriptive flexfield storage for client-specific extensions.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns maintained by the EBS framework.

Common Use Cases and Queries

Typical reporting scenarios include fund consumption by plan, outstanding utilization balances, and GL posting status. A sample query to review utilization amounts against remaining balances follows:

• SELECT u.utilization_id, u.fund_id, u.plan_id, u.amount, u.amount_remaining, u.currency_code, u.gl_posted_flag FROM ozf.ozf_funds_utilized_all_b u WHERE u.org_id = :org_id AND u.gl_posted_flag = 'N';

Joining to HZ_CUST_ACCOUNTS through CUST_ACCOUNT_ID provides customer attribution for utilization reporting, while joining to JAI_FA_AST_YEARS through YEAR_ID supports fiscal period analysis. Aggregate queries are commonly built to sum AMOUNT and ACCTD_AMOUNT grouped by PLAN_ID, UTILIZATION_TYPE, or GL_DATE for accrual reconciliation. Because OZF_FUNDS_PAID_ALL and OZF_CLAIM_LINES_UTIL_ALL reference UTILIZATION_ID, reporting on payment and claim consumption against utilization records is also a frequent requirement.

Related Objects

This table participates in an extensive relationship network. The most significant related objects include:

• OZF_FUNDS_PAID_ALL — References UTILIZATION_ID and records payments against utilized funds.
• OZF_CLAIM_LINES_UTIL_ALL, OZF_CLAIM_LINES_ALL, OZF_CLAIM_LINES_HIST_ALL, OZF_CLAIM_LINES_INT_ALL — Claim line tables linking claims to specific utilizations.
• OZF_FUNDS_UTILIZED_ALL_TL — Translated table containing language-specific descriptive data.
• OZF_SD_BATCH_LINES_ALL — Batch settlement lines referencing utilization records.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for access control.
• HZ_CUST_ACCOUNTS — Referenced via CUST_ACCOUNT_ID for customer attribution.
• FND_DM_PRODUCTS — Referenced via PRODUCT_ID for product-level fund tracking.
• JAI_FA_AST_YEARS — Referenced via YEAR_ID for fiscal year context.

Together these objects support the complete Trade Management fund lifecycle from accrual through claim, payment, and general ledger posting.