Search Results ozf_claim_types_vl




Overview
Explore in AI Chat

Overview

The OZF_CLAIM_TYPES_VL view is a translated (VL) dictionary view within the Oracle Trade Management (OZF) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It is owned by the APPS schema and reports a status of VALID. The view presents the language-dependent descriptive attributes of claim types — the NAME and DESCRIPTION of each claim type — joined to the operational and accounting attributes defined for that claim type. Claim types are the master reference data used throughout Trade Management to classify accruals, deductions, promotional claims, and related settlement activities.

Because Oracle EBS stores translatable seed and user-defined data in a combination of a base (_B) table and a translation (_TL) table, a _VL view is the standard mechanism for exposing both in a single queryable object. The _VL view allows forms, reports, concurrent programs, and integrations to retrieve the correct translated name and description for the session language without requiring the developer to write the join manually. In this respect OZF_CLAIM_TYPES_VL behaves like other Oracle Applications _VL views and is generally treated as the primary read interface for claim type metadata, while base tables are reserved for DML.

Underlying Base Objects

The documented ETRM metadata lists two referenced base objects: OZF_CLAIM_TYPES (a synonym) and OZF_CLAIM_TYPES_ALL_TL (a synonym). The view text shows the actual join pattern used: the translation table OZF_CLAIM_TYPES_ALL_TL (aliased T) is joined to the base table OZF_CLAIM_TYPES_ALL_B (aliased B). The synonym OZF_CLAIM_TYPES resolves to the base table within the APPS schema.

The join is driven by CLAIM_TYPE_ID, with an additional multi-org predicate on ORG_ID applied via NVL(ORG_ID, -99) on both sides. A further predicate restricts the translation row to the effective operating unit derived from USERENV('CLIENT_INFO'), and finally T.LANGUAGE = USERENV('LANG') ensures only the session-language translation is returned. This structure confirms the view is an operating-unit-aware, language-filtered projection rather than a simple synonym.

Key Columns

The view exposes the full set of base-table columns together with the translated attributes. The most significant are listed below.

  • CLAIM_TYPE_ID — primary identifier of the claim type; the join key between the base and translation tables.
  • NAME and DESCRIPTION — the translated descriptive values sourced from OZF_CLAIM_TYPES_ALL_TL.
  • LANGUAGE and SOURCE_LANG — the installed language of the returned translation and the source language of the record.
  • CLAIM_CLASS — classifies the claim type (for example accrual, deduction, or promotional categories).
  • SET_OF_BOOKS_ID — the ledger associated with accounting entries generated for the claim type.
  • POST_TO_GL_FLAG — indicates whether the claim type posts accounting entries to the General Ledger.
  • START_DATE and END_DATE — the effective date range during which the claim type is active.
  • CREATION_SIGN — controls the sign convention applied when creating claim or accrual amounts.
  • GL_ID_DED_ADJ, GL_ID_DED_ADJ_CLEARING, GL_ID_DED_CLEARING, and GL_ID_ACCR_PROMO_LIAB — foreign keys to the accounting flexfield combinations used for deduction, clearing, adjustment, and accrual liability postings.
  • TRANSACTION_TYPE and ADJUSTMENT_TYPE — further classification values used by downstream claim processing.
  • Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER — audit and optimistic locking attributes.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns available for customer extensions.
  • ROW_ID — the row identifier from the base table, exposed for tools that require a ROWID-style key.

Common Use Cases and Queries

The view is commonly used to populate LOVs (lists of values) on claim entry forms, to drive claim type lookups in custom reports, and to validate claim type identifiers in inbound integrations. Because the view already restricts to the correct language and operating unit, it is the preferred source for read-only claim type metadata.

A simple lookup of active claim types for the session operating unit:

  • SELECT claim_type_id, name, claim_class, post_to_gl_flag
  • FROM ozf_claim_types_vl
  • WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date, TRUNC(SYSDATE))
  • AND NVL(end_date, TRUNC(SYSDATE))
  • ORDER BY name;

Retrieving accounting configuration for a specific claim type:

  • SELECT name, set_of_books_id, post_to_gl_flag, creation_sign,
  • gl_id_ded_adj, gl_id_ded_clearing
  • FROM ozf_claim_types_vl
  • WHERE claim_type_id = :p_claim_type_id;

Joining the view to claim and accrual facts to report accrual liability by claim type:

  • SELECT ct.name, SUM(a.amount) accrual_amount
  • FROM ozf_claim_types_vl ct, ozf_accruals a
  • WHERE ct.claim_type_id = a.claim_type_id
  • GROUP BY ct.name;

Because the view filters on USERENV('LANG') and the client-info operating unit, developers should confirm that the reporting session initializes the client information appropriately, particularly in concurrent programs and web ADI integrations, to avoid returning no rows or rows for the wrong operating unit.