Search Results ozf_claim_types

Overview

APPS.OZF_CLAIM_TYPES_VL is a translatable ("_VL") reporting and integration view within the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / OZF) schema. It presents the definitional attributes of claim types — the configurable categories used to classify and drive the processing of trade promotion claims, deductions, and accruals. The view combines the organization-level transactional definition of a claim type with its language-specific descriptive text, resolving translated name and description values according to the current session language.

Because it consolidates descriptive columns from the translation table with the operational columns from the base definition table, the view is the standard reference point for concurrent programs, forms, OAF pages, and external integrations that require a language-aware list of claim types. In Oracle EBS 12.1.1 and 12.2.2 it is owned by APPS and is exposed to application code and reporting tools such as Oracle Reports, BI Publisher, and ad hoc SQL.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed to the view through APPS synonyms:

• OZF_CLAIM_TYPES — the organization-level definition table (aliased B in the view text), holding the identifying, accounting, and processing configuration for each claim type.
• OZF_CLAIM_TYPES_ALL_TL — the translation table (aliased T), holding the language-specific NAME and DESCRIPTION for each claim type.

The view joins the two on CLAIM_TYPE_ID and ORG_ID, with the additional predicate T.LANGUAGE = userenv('LANG') so that only the row matching the session language is returned. This multilanguage (ML) pattern is standard in EBS: the _TL table stores one row per installed language, while the _VL view filters to the caller's language, preventing duplicate rows in query output. The view therefore behaves as a 1:1 projection of OZF_CLAIM_TYPES enriched with translated text.

Key Columns

• CLAIM_TYPE_ID, ORG_ID — primary identifier and operating unit context for the claim type.
• NAME, DESCRIPTION — language-specific descriptive text sourced from the translation table.
• CLAIM_CLASS, CREATED_FROM — classification of the claim type and its origin.
• SET_OF_BOOKS_ID, POST_TO_GL_FLAG — accounting book reference and whether accounting entries are posted to the General Ledger.
• GL_ID_DED_ADJ, GL_ID_DED_ADJ_CLEARING, GL_ID_DED_CLEARING, GL_ID_ACCR_PROMO_LIAB, GL_BALANCING_FLEX_VALUE — General Ledger account references used to derive accounting for deductions, clearing, accruals, and balances.
• TRANSACTION_TYPE, ADJUSTMENT_TYPE, CM_TRX_TYPE_ID, DM_TRX_TYPE_ID, CB_TRX_TYPE_ID, WO_REC_TRX_ID, NEG_WO_REC_TRX_ID, ADJ_REC_TRX_ID, ORDER_TYPE_ID — processing configuration linking the claim type to order management transaction types and adjustment/order types.
• START_DATE, END_DATE — effective dating for the claim type.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for customer-specific extensions.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — standard WHO/audit and concurrent program columns.

Common Use Cases and Queries

Typical uses include listing valid claim types for a given operating unit, validating configuration before claim processing, and driving accounting derivation reports. A common query is:

• SELECT CLAIM_TYPE_ID, NAME, CLAIM_CLASS, POST_TO_GL_FLAG FROM APPS.OZF_CLAIM_TYPES_VL WHERE ORG_ID = :org_id;
• SELECT CLAIM_TYPE_ID, NAME, SET_OF_BOOKS_ID, GL_ID_ACCR_PROMO_LIAB FROM APPS.OZF_CLAIM_TYPES_VL ORDER BY NAME;

Because the view enforces the session-language predicate, reports automatically display the claim type name in the runtime language. Note that translated NAME and DESCRIPTION return only rows where a translation exists for the active language; fallback to a base language is not provided by this view, which is a consideration when building multilingual reports.