Results for “ozf_claim_adjustments_all”

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

Overview

OZF_CLAIM_ADJUSTMENTS_ALL is a Trade Management (OZF) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores adjustments applied against a claim amount. Whenever a trade promotion claim is settled, disputed, or reconciled at an amount other than its original value, the delta is recorded here as an adjustment line. The table therefore acts as the financial audit trail for claim modifications, capturing the magnitude, direction, reason, and currency context of each adjustment so that the original claim record in OZF_CLAIMS_ALL remains an immutable statement of the claimed amount.

The table is owned by the OZF schema and is validated in the ETRM data dictionary with 38 documented columns. Its _ALL suffix indicates it is a multi-organization (MLS/multi-org) enabled table, with ORG_ID and SECURITY_GROUP_ID present to partition data by operating unit and by security group. The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning: the table carries descriptive, time-stamped attributes that describe and quantify changes to a parent claim entity, rather than representing an independent business entity or a pure many-to-many association.

Key Information Stored

The primary key is OZF_CLAIM_ADJUSTMENTS_ALL_PK, defined on ADJUSTMENT_ID, a system-generated surrogate key. The principal business-key candidate is the combination of CLAIM_ID with ADJUSTMENT_TYPE and the surrounding business attributes; CLAIM_ID is a foreign key to OZF_CLAIMS_ALL and identifies the claim being adjusted. The most significant columns are:

• ADJUSTMENT_ID — surrogate primary key, unique per adjustment line.
• CLAIM_ID — foreign key to OZF_CLAIMS_ALL; the claim to which the adjustment applies.
• ADJUSTMENT_TYPE — classifies the nature of the adjustment (for example accrual, settlement, write-off, or reconciliation variance).
• AMOUNT_ADJUSTED — the monetary value of the adjustment, the core quantitative fact of the row.
• CURRENCY_CODE — currency in which AMOUNT_ADJUSTED is denominated.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE — conversion context when the claim and adjustment currencies differ.
• COMMENTS — free-text justification or approver note.
• ORG_ID — operating unit that owns the adjustment; drives multi-org security.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used for data security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking for concurrent updates through the OAF/Forms UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO-column audit trail.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context, identifying the batch that created or last updated the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard flexfield extension block for customer-specific data.
• CREATED_FROM — indicates the originating source (UI, API, or concurrent process).

Common Use Cases and Queries

The primary reporting use case is reconciliation of claim liability: summing adjustments per claim to derive the net settled amount. A representative query joins adjustments to their parent claim and filters by operating unit:

• SELECT c.claim_id, c.claim_number, SUM(a.amount_adjusted) net_adjustment FROM ozf_claim_adjustments_all a, ozf_claims_all c WHERE a.claim_id = c.claim_id AND a.org_id = :org_id GROUP BY c.claim_id, c.claim_number;
• Audit and control queries select adjustments where PROGRAM_ID or REQUEST_ID is populated to trace batch-originated changes.
• Currency-exposure reporting groups by CURRENCY_CODE and EXCHANGE_RATE_TYPE to identify adjustments requiring revaluation.
• Adjustment-type analysis aggregates AMOUNT_ADJUSTED by ADJUSTMENT_TYPE for accrual-versus-settlement trending.
• Exception reporting isolates rows where COMMENTS is null or where EXCHANGE_RATE is missing for a foreign-currency adjustment, flagging data-quality gaps.

Because the table is MLS-enabled, every query should constrain ORG_ID to respect multi-org access and to avoid double counting across operating units.

Related Objects

The dominant relationship is the foreign key from OZF_CLAIM_ADJUSTMENTS_ALL.CLAIM_ID to OZF_CLAIMS_ALL, the master claim table. This is the join used in virtually all reporting and is the parent that defines the adjustment's business context. The second documented foreign key, SECURITY_GROUP_ID to FND_SECURITY_GROUPS, links the row to the security framework that governs which users may view it. Related objects include the claim lines and claim history tables within the OZF schema that decompose OZF_CLAIMS_ALL, the Trade Management concurrent programs referenced through PROGRAM_ID and REQUEST_ID, and the standard FND audit and multi-org views built over the base table. The OZF_CLAIM_ADJUSTMENTS_ALL_PK unique index and the CLAIM_ID foreign-key index are the principal access paths for application and reporting queries.