Results for “zx_service_type_codes”

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

Overview

APPS.ZX_SIM_RULE_RESULTS_V is a reporting view in the Oracle E-Business Suite (EBS) E-Business Tax (ETRM) module, available in Release 12.1.1 and 12.2.2. It exposes the outcome of tax rule simulation, presenting the evaluated results of tax determination for a given configuration set. Its name reflects its purpose: it surfaces simulated rule results (SIM_RULE_RESULTS) in a denormalized, human-readable form.

The view plays a central role in the Tax Simulator and in any downstream reporting or integration that needs to explain how ETRM arrived at a particular tax outcome. Rather than returning raw rule identifiers, it resolves codes to descriptive names — tax regime names, tax full names, tax rule names, condition group names, and detail factor template names. This makes it suitable for diagnostics, regression testing of tax setups during implementations, audit reporting, and analytical extracts where a flattened result set is preferred over normalized transactional tables. Users searching on "df_template_name" are typically looking for the detail factor template description associated with a simulated result, which this view exposes as DF_TEMPLATE_NAME.

Underlying Base Objects

The view is owned by APPS and is defined over a set of ETRM base objects, joining transactional simulation results with configuration lookups and descriptive views:

• ZX_PROCESS_RESULTS (synonym) — the primary source of simulated process outcome rows, supplying result identifiers, process ordering, and status/rate result values.
• ZX_CONDITION_GROUPS_VL — supplies condition group codes and translated names (CONDITION_GROUP_CODE, CONDITION_GROUP_NAME).
• ZX_DET_FACTOR_TEMPL_VL — supplies detail factor template code and name (DF_TEMPLATE_CODE, DF_TEMPLATE_NAME).
• ZX_REGIMES_VL — supplies tax regime code and name (TAX_REGIME_CODE, TAX_REGIME_NAME).
• ZX_RULES_VL — supplies tax rule code and name (TAX_RULE_CODE, TAX_RULE_NAME).
• ZX_TAXES_VL — supplies tax code and full name (TAX, TAX_FULL_NAME).
• FND_LOOKUPS — resolves lookup-based display values.
• FND_GLOBAL (package) — used to derive session context such as the current user.

All configuration views are ETRM "_VL" views, meaning they expose translated (multi-language) descriptions. The view is not referenced by any database object, so it is a terminal read-only reporting object.

Key Columns

• PROCESS_ORDER and RESULT_ID — sequencing and unique identifier for each simulated result row.
• CONDITION_GROUP_CODE / CONDITION_GROUP_NAME and GROUP_PRIORITY — the condition group evaluated and its ordering.
• TAX_STATUS_CODE — the tax status associated with the result.
• RESULT, STATUS_RESULT, RATE_RESULT — the evaluated outcome, status determination, and rate determination respectively.
• TAX_REGIME_CODE / TAX_REGIME_NAME, TAX / TAX_FULL_NAME, TAX_RULE_CODE / TAX_RULE_NAME — codes and translated names for the regime, tax, and rule.
• PROCESS_CODE / PROCESS_NAME and RULE_PRIORITY — the tax process applied and the rule precedence.
• RECOVERY_TYPE_CODE — the recovery type where applicable.
• DF_TEMPLATE_CODE / DF_TEMPLATE_NAME — the detail factor template code and its descriptive name, a common search target.

Common Use Cases and Queries

The view is most often used to review simulated tax determination, to explain which detail factor template influenced a result, and to build extracts for validation.

Basic retrieval, using the documented query text:

• SELECT PROCESS_ORDER, RESULT_ID, CONDITION_GROUP_CODE, DF_TEMPLATE_CODE, DF_TEMPLATE_NAME, TAX_REGIME_NAME, TAX_FULL_NAME, TAX_RULE_NAME, RATE_RESULT, STATUS_RESULT FROM APPS.ZX_SIM_RULE_RESULTS_V ORDER BY PROCESS_ORDER;

Filtering by detail factor template name:

• SELECT RESULT_ID, TAX_RULE_NAME, DF_TEMPLATE_NAME, RATE_RESULT FROM APPS.ZX_SIM_RULE_RESULTS_V WHERE DF_TEMPLATE_NAME IS NOT NULL;

Grouping to review outcomes by regime and rule:

• SELECT TAX_REGIME_NAME, TAX_RULE_NAME, COUNT(*) FROM APPS.ZX_SIM_RULE_RESULTS_V GROUP BY TAX_REGIME_NAME, TAX_RULE_NAME;

Typical scenarios include verifying a configuration change before promotion, reconciling simulator output against expected tax, and supporting audits that require the full chain from condition group through rule to detail factor template.