Search Results split_date




Overview
Explore in AI Chat

Overview

OZF_CLAIMS_V is a reporting and integration view owned by the APPS schema in Oracle Trade Management (OZF), part of the Oracle E-Business Suite 12.1.1 and 12.2.2 code lines. It presents a denormalized, user-facing projection of customer claims — the deduction and accrual requests that channel customers and internal users raise against promotional, rebate, and funds activity in Trade Management. The view is a foundational access point for both inquiry screens and programmatic consumers: Oracle's own Claim and Deduction workbench pages, concurrent-program extracts, and third-party integrations typically read claim data through OZF_CLAIMS_V rather than the base OZF_CLAIMS table, because the view resolves the foreign keys that the base table stores only as IDs. In particular, lookup meanings, claim type names, user status names, party names, and account numbers are pre-joined, so a query returns business-meaningful text instead of code values. The view is listed as VALID and is a supported, documented object in the ETRM 12.2.2 data model.

Underlying Base Objects

The view is defined over one driving base table and six supporting objects in the OZF and HZ schemas:

The join is driven from OZF_CLAIMS with outer joins to the descriptive objects, preserving claims whose lookup or type values are null.

Key Columns

The most operationally significant columns include CLAIM_ID (unique claim identifier), CLAIM_NUMBER (the user-visible sequence), CLAIM_CLASS with its decoded MEANING, CLAIM_TYPE_ID and the resolved type NAME, CLAIM_DATE and DUE_DATE, and STATUS_CODE alongside USER_STATUS_ID and its NAME. Financial columns include AMOUNT, AMOUNT_REMAINING, AMOUNT_ADJUSTED, AMOUNT_SETTLED, ACCTD_AMOUNT, ACCTD_AMOUNT_REMAINING, CURRENCY_CODE, and EXCHANGE_RATE with its type and date. Customer context is provided by CUST_ACCOUNT_ID, PARTY_NAME, ACCOUNT_NUMBER, bill-to and ship-to site IDs, SALES_REP_ID, CONTACT_ID, and BROKER_ID. Hierarchy and lineage columns — ROOT_CLAIM_ID, DUPLICATE_CLAIM_ID, SPLIT_FROM_CLAIM_ID, SPLIT_DATE, SOURCE_OBJECT_ID, SOURCE_OBJECT_CLASS, RECEIPT_ID, and RECEIPT_NUMBER — trace how a claim originated, whether it duplicates or splits from another claim, and the root of its claim tree. The 15 ATTRIBUTE and DEDUCTION_ATTRIBUTE columns carry flexfield data, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) support auditing.

Common Use Cases and Queries

Typical scenarios are claim workbench inquiries, deduction aging and settlement analyses, and reconciliation of claims back to their originating order or receipt. The user search term root_claim_id reflects the common need to navigate the claim hierarchy — for example, retrieving all child, duplicate, or split claims descended from a parent claim.

  • Claims belonging to a given root: SELECT claim_id, claim_number, claim_class, status_code, amount, currency_code FROM ozf_claims_v WHERE root_claim_id = :p_root_claim_id ORDER BY claim_date;
  • A root and its descendants combined: SELECT claim_id, claim_number, root_claim_id, split_from_claim_id FROM ozf_claims_v WHERE claim_id = :p_root_claim_id OR root_claim_id = :p_root_claim_id;
  • Open deductions by customer: SELECT claim_number, party_name, account_number, amount_remaining, due_date FROM ozf_claims_v WHERE status_code = :p_open_status AND cust_account_id = :p_cust_account_id;
  • Split lineage: SELECT claim_number, split_from_claim_id, split_date, original_claim_date FROM ozf_claims_v WHERE split_from_claim_id IS NOT NULL;

Because the view decodes lookups and joins customer master data, it is directly usable in BI Publisher reports, OAF inquiries, and interface extracts without additional joins, though joins to OZF_CLAIMS_LINES or OZF_CLAIM_ACTIVITIES are required for line-level and workflow detail.