Results for “rule_priority”

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

Overview

The ZX_SIM_RULE_RESULTS_V view in the APPS schema provides a consolidated, read-only projection of rule evaluation results produced by the Oracle E-Business Tax (EBS Tax / ETRM) engine. The name prefix "SIM" indicates that the view is designed to surface the outcome of tax rule simulations — the deterministic evaluation performed by the tax engine's service types such as Direct Rate, Place of Supply, Applicable Taxes, Tax Registration, Tax Status, Tax Rate, Taxable Basis, and Tax Amount Calculation. In Oracle EBS 12.1.1 and 12.2.2 it exposes the same rule-evaluation scaffold used by the Tax Simulator and Calculator diagnostics, allowing a technical consultant to interrogate the effective condition groups, priorities, and result values that the engine resolved for a given transaction scenario.

Because the view is owned by APPS and catalogued under FND - Application Object Library, it is registered as a public application view and is available for reporting and integration without additional grants to the underlying ZX tables. It is not a base entity and should never be DML-ed; it is a query surface used for investigation, diagnostics, and exception reporting.

Underlying Base Objects

The view is a UNION ALL of two SELECT blocks over the following documented base objects:

• ZX_PROCESS_RESULTS (SYNONYM) — the driving transaction-level table holding each evaluated rule's result, status result, and rate result.
• ZX_RULES_VL (VIEW) — the tax rule definitions, supplying service type, rule code, priority, recovery type, and determinant factor template code.
• ZX_DET_FACTOR_TEMPL_VL (VIEW) — determinant factor templates referenced by each rule.
• ZX_CONDITION_GROUPS_VL (VIEW) — condition group code and name for each result row.
• ZX_REGIMES_VL, ZX_TAXES_VL (VIEWs) — tax regime and tax metadata, including the applicability, status, rate, place-of-supply, direct-rate, taxable-basis, tax-calc, and registration-type rule flags.
• FND_LOOKUPS (VIEW) — the ZX_SERVICE_TYPE_CODES lookup used to resolve process code to its meaning.
• FND_GLOBAL (PACKAGE) — used to resolve the current application/user context.

Joins are performed on TAX_RULE_ID, CONDITION_GROUP_ID, DET_FACTOR_TEMPL_CODE, SERVICE_TYPE_CODE, TAX, and TAX_REGIME_CODE. The second UNION ALL branch injects a synthetic "DEFAULT" place-of-supply row with RESULT_ID -9998.

Key Columns

• PROCESS_CODE / PROCESS_NAME — service type code and its lookup meaning, returned as the first column with an explicit DECODE ordering 1–8 (otherwise 10).
• RESULT_ID — identifier of the process result.
• CONDITION_GROUP_CODE / CONDITION_GROUP_NAME — condition group that qualified the rule.
• GROUP_PRIORITY — this is the alias for PR.PRIORITY in ZX_PROCESS_RESULTS, i.e. the priority of the qualifying process result. This is the column the user searched for under "group_priority".
• RULE_PRIORITY — alias for RU.PRIORITY from ZX_RULES_VL, the priority of the rule itself; distinct from GROUP_PRIORITY.
• RESULT — coalesced ALPHANUMERIC_RESULT, NUMERIC_RESULT, or RESULT_API.
• STATUS_RESULT / RATE_RESULT — specialised result values for tax status and tax rate service types.
• TAX_REGIME_CODE / TAX_REGIME_NAME, TAX / TAX_FULL_NAME, TAX_RULE_CODE / TAX_RULE_NAME — tax identity columns.
• RECOVERY_TYPE_CODE, DF_TEMPLATE_CODE / DF_TEMPLATE_NAME — recovery and determinant factor template attributes.

Common Use Cases and Queries

Typical use is diagnosis of why a transaction received a particular tax outcome, and audit of condition-group precedence.

SELECT process_code, process_name, condition_group_code,
       group_priority, result
FROM   apps.zx_sim_rule_results_v
WHERE  tax_regime_code = :regime
AND    tax               = :tax
ORDER  BY process_code, group_priority;

SELECT group_priority, rule_priority, tax_rule_code, result
FROM   apps.zx_sim_rule_results_v
WHERE  result_id = :result_id
ORDER  BY group_priority;

The first query lists all evaluated processes and the winning condition groups; the second inspects a single result and its duplicate priority candidates, which is useful when rule precedence is suspected of producing an unexpected tax.