Results for “value_set”

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

Overview

ZX_DETERMINING_FACTORS_VL is a linguistic (MLS) view owned by the APPS schema in Oracle E-Business Suite, residing in the FND – Application Object Library product grouping. It exposes the translation view for E-Business Tax (E-Business Tax / ZX) determining factors, which are the configurable inputs the tax engine evaluates when it decides whether and how a tax applies to a transaction line. The VL suffix indicates that the view combines the base, language-independent definition rows with their language-specific translated attributes for the session language, resolved through USERENV('LANG').

The view is the primary reporting and integration access point for determining factor setup. Because it presents both descriptive text (name and description) and the full configuration flags and codes, it is used in tax configuration reports, data migration validation scripts, integration extracts that replicate tax setup across environments, and diagnostic queries that investigate why a particular determining factor is or is not being applied during tax calculation.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over two base objects, both referenced through APPS synonyms:

• ZX_DETERMINING_FACTORS_B — the base table holding the language-independent row for each determining factor, including all functional codes, flags, data types, value sets, and audit columns.
• ZX_DET_FACTORS_TL — the translation table holding language-specific values, principally DETERMINING_FACTOR_NAME and DETERMINING_FACTOR_DESC.

The join is performed on DETERMINING_FACTOR_ID, with the translation side restricted to the runtime language via T.LANGUAGE = USERENV('LANG'). The view therefore returns exactly one combined row per determining factor, presented in the user's session language. The user search term "zx_determining_factors_b" corresponds precisely to the base table alias B in this definition, which is the table of record for the setup.

Key Columns

• DETERMINING_FACTOR_ID — the primary key and join key between the base and translation rows.
• DETERMINING_FACTOR_CODE — the internal code used by the tax engine to identify the factor.
• DETERMINING_FACTOR_NAME / DETERMINING_FACTOR_DESC — the translated name and description from ZX_DET_FACTORS_TL.
• DETERMINING_FACTOR_CLASS_CODE — classifies the factor (for example, a regime-to-rate flow classification).
• VALUE_SET, DATA_TYPE_CODE, RECORD_TYPE_CODE — define the value domain and the type of data a factor accepts.
• TAX_FUNCTION_CODE / TAX_PARAMETER_CODE — link the factor to the tax function and parameter it feeds.
• TAX_CALCULATION_FLAG, TAX_SUMMARIZATION_FLAG, TAX_RULES_FLAG, TAXABLE_BASIS_FLAG, TAX_REGIME_DET_FLAG — flags indicating the tax processes in which the factor participates.
• INTERNAL_FLAG / RECORD_ONLY_FLAG — indicate whether the factor is Oracle-internal or record-only.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID.

Common Use Cases and Queries

The view is queried to list all configured determining factors with user-facing names, to validate that a factor required by a tax rule exists and is enabled for the correct process, and to support migrations that compare factor setups between instances. A typical listing query is:

SELECT determining_factor_id, determining_factor_code, determining_factor_name, determining_factor_class_code, data_type_code, value_set FROM zx_determining_factors_vl ORDER BY determining_factor_name;

A second common pattern filters by class or by participation flag, for example retrieving only factors that drive tax calculation:

SELECT determining_factor_code, determining_factor_name FROM zx_determining_factors_vl WHERE tax_calculation_flag = 'Y' AND determining_factor_class_code = :p_class;

When translation is not required, or when it is necessary to see all languages, the underlying ZX_DET_FACTORS_TL and ZX_DETERMINING_FACTORS_B tables are queried directly, since the VL view deliberately restricts the translation join to the current environment language.