Search Results deduction_attribute1

Overview

OZF_CLAIMS_HISTORY_V is an APPS-owned reporting view in the Oracle Trade Management (OZF) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It presents the denormalized claim history record set, combining the transactional columns of the OZF_CLAIMS_HISTORY table with descriptive values resolved from lookup, customer, and claim-type sources. Each row represents a point-in-time snapshot of a trade claim, captured when a history event occurs, so the view functions as an audit and analytical layer over the claims lifecycle.

The view is read-only by design. It is intended for reporting, extracts, and integration interfaces that require human-readable claim history without joining to multiple lookup and party tables. Because it exposes both the surrogate identifiers and the decoded meanings, it supports concurrent reporting and programmatic consumption.

Underlying Base Objects

The view is defined over the following documented base objects:

• OZF_CLAIMS_HISTORY (synonym) — the primary history table supplying claim snapshot columns, including SPLIT_FROM_CLAIM_ID and SPLIT_DATE.
• OZF_LOOKUPS (view) — resolves CLAIM_CLASS to its meaning via LK_CC.MEANING.
• OZF_CLAIM_TYPES_VL (view) — supplies the claim type name (CT.NAME) for CLAIM_TYPE_ID.
• AMS_USER_STATUSES_VL (view) — resolves the user-defined status name (AUS.NAME) for USER_STATUS_ID and the owner meaning (ALS.MEANING).
• HZ_CUST_ACCOUNTS (synonym) — provides ACCOUNT_NUMBER for CUST_ACCOUNT_ID.
• HZ_PARTIES (synonym) — provides PARTY_NAME for CUST_ACCOUNT_ID.
• OZF_SYS_PARAMETERS (synonym) — supplies system-level parameter context.

The joins are driven from OZF_CLAIMS_HISTORY, with outer joins to the lookup, status, claim type, and party objects so that history rows remain visible even when a descriptive value is absent.

Key Columns

The following columns are material to claim history analysis:

• CLAIM_HISTORY_ID — primary key of the history record; uniquely identifies each snapshot.
• CLAIM_ID, CLAIM_NUMBER — the operational claim being traced.
• SPLIT_FROM_CLAIM_ID, SPLIT_DATE — identify the parent claim from which this claim was split and the split date; central to split-lineage tracing.
• ROOT_CLAIM_ID, DUPLICATE_CLAIM_ID — trace original and duplicate claim relationships.
• CLAIM_CLASS, MEANING — decoded classification of the claim.
• CLAIM_TYPE_ID, NAME — claim type and its descriptive name.
• STATUS_CODE, USER_STATUS_ID, NAME — system and user-defined status values.
• HISTORY_EVENT_DATE, HISTORY_EVENT_DESCRIPTION — when and why the snapshot was written.
• CUST_ACCOUNT_ID, PARTY_NAME, ACCOUNT_NUMBER — customer identification.
• AMOUNT, AMOUNT_REMAINING, AMOUNT_ADJUSTED, AMOUNT_SETTLED, ACCTD_AMOUNT, ACCTD_AMOUNT_REMAINING — entered and accounted monetary positions.
• CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_DATE — currency conversion context.
• SOURCE_OBJECT_ID, SOURCE_OBJECT_CLASS, SOURCE_OBJECT_NUMBER — originating document reference.
• ATTRIBUTE1..15 and DEDUCTION_ATTRIBUTE1..15 — descriptive flexfield segments.

Common Use Cases and Queries

Typical usage includes claims audit reporting, lineage tracing, and reconciliation of claim amounts across history events.

• Trace all claims split from a specific parent claim:

  SELECT claim_id, claim_number, split_from_claim_id, split_date
  FROM   apps.ozf_claims_history_v
  WHERE  split_from_claim_id = :p_claim_id;

• Retrieve the history of a single claim ordered by event date:

  SELECT history_event_date, history_event_description,
         status_code, amount, amount_remaining
  FROM   apps.ozf_claims_history_v
  WHERE  claim_id = :p_claim_id
  ORDER  BY history_event_date;

• Summarize claim amounts by class and status for a period:

  SELECT meaning, status_code, COUNT(*) claims, SUM(amount) total_amount
  FROM   apps.ozf_claims_history_v
  WHERE  history_event_date BETWEEN :p_start AND :p_end
  GROUP  BY meaning, status_code;

• Reconcile customer exposure with party detail:

  SELECT party_name, account_number, claim_number, amount_remaining
  FROM   apps.ozf_claims_history_v
  WHERE  cust_account_id = :p_cust_account_id;

Because the view resolves meanings and party attributes inline, it is suited to operational dashboards and Oracle Business Intelligence extracts, provided query predicates are applied on CLAIM_ID, CLAIM_HISTORY_ID, or HISTORY_EVENT_DATE to limit the history volume.