Results for “cb_trx_type_id”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OZF_CLAIM_TYPES_ALL_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OZF – Trade Management product family and exposes the translatable and non-translatable attributes of claim types used throughout Oracle Trade Management, the module that manages promotional accruals, deductions, claims, and settlement activity for trade promotion programs. The "ALL" in the name indicates that the view spans multiple operating units (ORG_ID), and the "VL" suffix indicates that it joins a translation table so that the NAME and DESCRIPTION columns are returned in the session's active language, as determined by USERENV('LANG').

From a reporting and integration standpoint, this view is the standard, language-aware entry point for querying claim type definitions. Because it resolves translation automatically, it is preferred over the underlying _B and _TL tables for OBIEE reports, BI Publisher data templates, custom concurrent programs, and inbound/outbound interfaces that reference claim types by name. It is also relevant to accounting configuration, since each claim type row carries the GL accounts and the POST_TO_GL_FLAG that govern whether claim transactions are posted to the General Ledger.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

The two tables are joined on CLAIM_TYPE_ID, with an additional NVL-based comparison, NVL(B.ORG_ID, -99) = NVL(T.ORG_ID, -99), which matches rows even when ORG_ID is null. The translation row is filtered by T.LANGUAGE = USERENV('LANG') so that only the session-language translation is returned. B.ROWID is exposed as ROW_ID, providing an addressing handle for the base row.

Key Columns

Common Use Cases and Queries

A frequent requirement is identifying which claim types are configured to post to the General Ledger, typically during accounting reconciliation or before enabling a new promotion. The following query uses the searched column:

  • SELECT claim_type_id, name, org_id, set_of_books_id, post_to_gl_flag FROM ozf_claim_types_all_vl WHERE post_to_gl_flag = 'Y' ORDER BY name;
  • SELECT claim_type_id, name, gl_id_accr_promo_liab, gl_id_ded_clearing FROM ozf_claim_types_all_vl WHERE org_id = :p_org_id;
  • SELECT claim_type_id, name, description FROM ozf_claim_types_all_vl WHERE claim_class = :p_class AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
  • SELECT post_to_gl_flag, COUNT(*) FROM ozf_claim_types_all_vl GROUP BY post_to_gl_flag;

The final query is useful as a validation check when migrating configuration between environments. Because the view filters on USERENV('LANG'), reports requiring a specific language should set the session language before querying, or alternatively query OZF_CLAIM_TYPES_ALL_TL directly with an explicit LANGUAGE predicate.