Search Results ozf_claim_lines_hist_v
Overview
OZF_CLAIM_LINES_HIST_V is an APPS-owned view in the Oracle Trade Management (OZF) module, valid in EBS 12.1.1 and 12.2.2. It exposes the historical audit trail of claim lines processed through Trade Management settlement and payment workflows. Where OZF_CLAIM_LINES holds the current state of each claim line, the underlying history table — OZF_CLAIM_LINES_HIST — captures a snapshot row for every change event, enabling point-in-time reconstruction of a claim line's lifecycle.
The view's principal reporting value lies in its denormalization of foreign-key references into business-readable values. Rather than returning raw IDs, it resolves the payee approver, the settler, and the payment method into descriptive names, making it suitable for direct use in BI Publisher reports, OBIEE/OTBI analyses, and custom concurrent programs without additional lookup joins.
Underlying Base Objects
The view is defined over four documented base objects:
OZF_CLAIM_LINES_HIST(SYNONYM) — the primary driving table, aliasedOCL, supplying all claim line history columns.OZF_SYS_PARAMETERS(SYNONYM) — aliasedOSP, joined onSET_OF_BOOKS_IDto constrain history rows to the operating ledger configured in system parameters.AMS_LOOKUPS(SYNONYM, referenced asOZF_LOOKUPS/LK_PM) — an outer join onLOOKUP_TYPE = 'AMS_PAYMENT_METHOD'that supplies the meaning of the payment method code.JTF_RS_RESOURCE_EXTNS(SYNONYM) — joined twice as outer joins (JRE1,JRE2) to resolveAPPROVED_BYandSETTLED_BYto resource source names.
The mandatory inner join to OZF_SYS_PARAMETERS means the view returns rows only when a matching system parameter record exists for the claim's set of books; all other joins are outer, so rows are never dropped when a lookup or resource reference is null.
Key Columns
CLAIM_LINE_HISTORY_ID,CLAIM_HISTORY_ID,CLAIM_ID,CLAIM_LINE_ID— primary and foreign keys linking the history row to its parent claim and line.SETTLED_DATE,SETTLED_BY— the settlement timestamp and the resource that performed settlement;SETTLED_BYis the column most directly relevant to searches for the settler identity.JRE2.SOURCE_NAME— the denormalized resource name corresponding toSETTLED_BY;JRE1.SOURCE_NAMEserves the same purpose forAPPROVED_BY.APPROVED_FLAG,APPROVED_DATE,APPROVED_BY— approval audit attributes.AMOUNT,CLAIM_CURRENCY_AMOUNT,ACCTD_AMOUNT,CURRENCY_CODE,EXCHANGE_RATE— monetary and currency details, including the accounted amount.PAYMENT_METHODand its lookupMEANING, plusPAYMENT_REFERENCE_NUMBER,VOUCHER_NUMBER, andPAYMENT_STATUS— settlement and disbursement references.VALID_FLAG,PERFORMANCE_COMPLETE_FLAG,PERFORMANCE_ATTACHED_FLAG— status indicators.ATTRIBUTE_CATEGORYthroughATTRIBUTE15andORG_ID— descriptive flexibility and multi-org partitioning.
Common Use Cases and Queries
Typical scenarios include auditing who settled a claim line and when, reconciling settlement history against payables vouchers, and reproducing approval-versus-settlement timelines. Because the view is not org-striped by default, callers should filter on ORG_ID where multi-org security applies.
To identify the settler for a given claim line:
SELECT claim_id, claim_line_id, line_number, SETTLED_DATE, SETTLED_BY, SOURCE_NAME settler_name, PAYMENT_STATUS, VOUCHER_NUMBER FROM OZF_CLAIM_LINES_HIST_V WHERE claim_line_id = :p_line_id ORDER BY SETTLED_DATE;
To list all lines settled by a specific user resource:
SELECT claim_id, claim_line_id, SETTLED_DATE, claim_currency_amount, currency_code, MEANING payment_method FROM OZF_CLAIM_LINES_HIST_V WHERE SOURCE_NAME = :p_settler AND SETTLED_DATE BETWEEN :p_from AND :p_to ORDER BY SETTLED_DATE DESC;
To summarize settlement activity per resource within an operating unit:
SELECT SOURCE_NAME settler_name, COUNT(*) settled_lines, SUM(claim_currency_amount) total_amount FROM OZF_CLAIM_LINES_HIST_V WHERE SETTLED_DATE IS NOT NULL AND org_id = :p_org_id GROUP BY SOURCE_NAME;
These queries assume the resource name uniquely identifies the settler; where duplicate resource names exist, join SETTLED_BY back to JTF_RS_RESOURCE_EXTNS on RESOURCE_ID for precise attribution.
-
View: OZF_CLAIM_LINES_HIST_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_CLAIM_LINES_HIST_V, object_name:OZF_CLAIM_LINES_HIST_V, status:VALID, product: OZF - Trade Management , implementation_dba_data: APPS.OZF_CLAIM_LINES_HIST_V ,
-
View: OZF_CLAIM_LINES_HIST_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_CLAIM_LINES_HIST_V, object_name:OZF_CLAIM_LINES_HIST_V, status:VALID, product: OZF - Trade Management , implementation_dba_data: APPS.OZF_CLAIM_LINES_HIST_V ,
-
SYNONYM: APPS.OZF_CLAIM_LINES_HIST
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OZF_CLAIM_LINES_HIST, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
SYNONYM: APPS.OZF_CLAIM_LINES_HIST
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OZF_CLAIM_LINES_HIST, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
SYNONYM: APPS.OZF_SYS_PARAMETERS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OZF_SYS_PARAMETERS, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
SYNONYM: APPS.OZF_SYS_PARAMETERS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OZF_SYS_PARAMETERS, status:VALID,
-
VIEW: APPS.OZF_LOOKUPS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_LOOKUPS, object_name:OZF_LOOKUPS, status:VALID,
-
VIEW: APPS.OZF_CLAIM_LINES_HIST_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_CLAIM_LINES_HIST_V, object_name:OZF_CLAIM_LINES_HIST_V, status:VALID,
-
VIEW: APPS.OZF_CLAIM_LINES_HIST_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_CLAIM_LINES_HIST_V, object_name:OZF_CLAIM_LINES_HIST_V, status:VALID,
-
VIEW: APPS.OZF_LOOKUPS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OZF.OZF_LOOKUPS, object_name:OZF_LOOKUPS, status:VALID,
-
SYNONYM: APPS.JTF_RS_RESOURCE_EXTNS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JTF_RS_RESOURCE_EXTNS, status:VALID,
-
SYNONYM: APPS.JTF_RS_RESOURCE_EXTNS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JTF_RS_RESOURCE_EXTNS, status:VALID,
-
eTRM - OZF Tables and Views
12.2.2
description: OZF_XREF_MAP table created for SIebel TPM Integration ,
-
eTRM - OZF Tables and Views
12.1.1
description: Table to store the Market eligibilty for a Offer Worksheet ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
eTRM - OZF Tables and Views
12.1.1
description: Table to store the Market eligibilty for a Offer Worksheet ,
-
eTRM - OZF Tables and Views
12.2.2
description: OZF_XREF_MAP table created for SIebel TPM Integration ,