Results for “result_type_code”

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

Overview

ZX_SIM_PROCESS_RESULTS_VL is a validation-level (VL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the FND – Application Object Library product and is classified as a VIEW with VALID status. The view exposes the output of the tax simulation engine in Oracle E-Business Tax (ZX), presenting the results produced when tax rules are evaluated against simulated transaction conditions. Its role is primarily reporting and integration: it surfaces internal simulation result rows in a denormalized, human-readable form by joining lookup descriptions for condition groups and tax statuses, allowing downstream reporting tools, concurrent programs, and diagnostic queries to consume simulation output without reconstructing multiple joins. The VL suffix indicates the view carries a translation/validation layer for descriptive columns, which is standard for views intended for user-facing or localized reporting.

Underlying Base Objects

The view is defined over three documented base objects. The driving object is ZX_SIM_PROCESS_RESULTS, referenced through a synonym, which is the transactional store of simulated tax rule evaluation results. Descriptive attributes are resolved through two additional views: ZX_CONDITION_GROUPS_VL supplies the condition group name, and ZX_STATUS_VL supplies the tax status name. The join is an outer join on both descriptive views, meaning simulation result rows are retained even when no matching condition group or tax status description exists. This structure mirrors the pattern used throughout the ZX schema, where a _VL or _V view supplements a base _ALL table with translated or validated descriptive columns. The view text confirms the outer-join syntax against both descriptive views using the (+) operator, consistent with Oracle 11g-era SQL that remains valid in 12.2.2.

Key Columns

The view exposes identifier, descriptive, and audit columns that characterize each simulation result.

• SIM_RESULT_ID — primary key of the underlying simulation result row.
• CONDITION_GROUP_CODE / CONDITION_GROUP_NAME — the condition group evaluated, with its resolved descriptive name.
• SIM_TAX_RULE_ID — the simulated tax rule that produced the result.
• PRIORITY — evaluation priority applied when the rule was processed.
• RESULT_TYPE_CODE — the type of result returned by the simulation.
• TAX_STATUS_CODE / TAX_STATUS_NAME — the resulting tax status, with resolved description.
• NUMERIC_RESULT / ALPHANUMERIC_RESULT — typed result values returned by the rule.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID — concurrent program context identifying the process that generated the result.

Common Use Cases and Queries

The view supports troubleshooting tax rule simulation runs, verifying which rules fired under given conditions, and building reports over simulation output. A typical query filters by condition group and orders by priority to reproduce evaluation order:

• SELECT sim_result_id, condition_group_name, priority, result_type_code, tax_status_name, numeric_result, alphanumeric_result FROM zx_sim_process_results_vl WHERE condition_group_code = :p_group ORDER BY priority;
• SELECT request_id, sim_tax_rule_id, tax_status_code, alphanumeric_result FROM zx_sim_process_results_vl WHERE request_id = :p_request_id;
• SELECT condition_group_name, COUNT(*) FROM zx_sim_process_results_vl GROUP BY condition_group_name;

Because the view is read-only and built on base simulation data, it is safe for ad-hoc reporting, but write operations must target the underlying ZX_SIM_PROCESS_RESULTS table. Access should be governed through standard APPS responsibility and menu grants.