Search Results history_event_date




Overview
Explore in AI Chat

Overview

OZF_CLAIMS_HISTORY_ALL is a Trade Management (OZF) table that stores claim header history records within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to retain historical snapshots of claim headers, allowing the application to preserve the state of a claim at each significant lifecycle event (creation, approval, settlement, splitting, and so on) without overwriting the live claim record held in OZF_CLAIMS_ALL. The table is owned by the OZF schema and is reported as VALID.

The table is implemented as an auditable, multi-organization–aware entity. It carries the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program context columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE), an ORG_ID for multi-org isolation, a SECURITY_GROUP_ID, and OBJECT_VERSION_NUMBER for optimistic locking. A heuristic Data Vault classification of this object is satellite-leaning: the primary key CLAIM_HISTORY_ID identifies individual history rows, and the foreign key CLAIM_ID back to OZF_CLAIMS_ALL behaves much like a parent key to which this table attaches descriptive, time-stamped attributes.

Key Information Stored

The table is documented with 150 columns. The most operationally significant are:

Common Use Cases and Queries

The primary use case is historical claim reporting: reconstructing the state of a claim at a given event or point in time for reconciliation, dispute tracking, and audit. A typical query joins the history table to the current claim header:

SELECT h.CLAIM_ID, h.CLAIM_NUMBER, h.HISTORY_EVENT, h.HISTORY_EVENT_DATE, h.STATUS_CODE, h.AMOUNT_REMAINING FROM OZF.OZF_CLAIMS_HISTORY_ALL h WHERE h.CLAIM_ID = :claim_id ORDER BY h.HISTORY_EVENT_DATE;

Because the table is partitioned by ORG_ID, operational queries should filter on ORG_ID and, where set-based security applies, on SECURITY_GROUP_ID. Settlement and aging reports frequently aggregate AMOUNT_SETTLED, AMOUNT_REMAINING, and ACCTD_AMOUNT_REMAINING grouped by STATUS_CODE, CURRENCY_CODE, or SALES_REP_ID. Lineage analysis for split or grouped claims uses SPLIT_FROM_CLAIM_ID, ROOT_CLAIM_ID, and GROUP_CLAIM_ID to trace a claim's ancestry, and the table pairs with OZF_CLAIM_LINES_HIST_ALL to produce a complete historical view of header plus lines. APPROVED_FLAG, APPROVED_DATE, SETTLED_DATE, and PAYMENT_STATUS support approval cycle-time and collection performance metrics.

Related Objects

These relationships make OZF_CLAIMS_HISTORY_ALL a central satellite in the Trade Management claims model, integrating customer, collections, document sequencing, and order context around each captured claim event.