Search Results zx_fc_codes_vl




Overview
Explore in AI Chat

Overview

The ZX_FC_CODES_VL view is a translation-enabled (VL, or "view language") database object owned by the APPS schema in Oracle E-Business Suite. It is catalogued under the FND — Application Object Library product/module within ETRM and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The view presents fiscal classification code definitions used by the E-Business Tax (EBTax) and related tax determination infrastructure, exposing the descriptive classification name alongside the operational classification attributes.

Because it is a VL view — a multilingual, translation-enabled view — it collapses the base (business) table and its translation table into a single logical source. The WHERE clause filters the translation table to only the row matching the session language, so consumers of the view always see the classification name in the language of the current session rather than all installed languages. This makes the view suitable for user-facing reports, list-of-values (LOV) definitions, and integration extracts where a single, session-appropriate name is required.

Underlying Base Objects

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

  • ZX_FC_CODES_B — the base (non-translated) table holding the operational fiscal classification code data, including identifiers, codes, types, dates, and audit columns. It supplies the majority of the columns in the view.
  • ZX_FC_CODES_TL — the translation table holding the language-specific classification name, keyed by CLASSIFICATION_ID and LANGUAGE.

The join is performed on CLASSIFICATION_ID, with the translation table restricted by T.LANGUAGE = USERENV('LANG'). The view also exposes B.ROWID as ROW_ID, which is a common EBS VL pattern that supports row identification for certain framework operations.

Key Columns

The column list is drawn primarily from ZX_FC_CODES_B, supplemented by one column from ZX_FC_CODES_TL:

Common Use Cases and Queries

Typical scenarios include building fiscal classification LOVs, generating tax setup reports, and extracting classification definitions for integration or reconciliation. Because the view provides the translated name, it simplifies reporting that would otherwise require an explicit join to the TL table.

Example — list active classifications with names:

SELECT classification_id, classification_code, classification_name, classification_type_code, country_code, effective_from, effective_to FROM zx_fc_codes_vl WHERE SYSDATE BETWEEN NVL(effective_from, SYSDATE) AND NVL(effective_to, SYSDATE + 1) ORDER BY classification_name;

Example — resolve a code to its name and parent:

SELECT classification_code, classification_name, parent_classification_code, classification_type_code FROM zx_fc_codes_vl WHERE classification_code = :code;

When joins to translation-specific logic are required regardless of session language, query ZX_FC_CODES_B and ZX_FC_CODES_TL directly; for session-language reporting and LOVs, ZX_FC_CODES_VL is the preferred access path. Restricting by classification_type_code and country_code typically improves selectivity on large extracts.