Results for “zx_rules_b”

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

Overview

ZX_RULES_B is the base (non-translated) definition table for tax rules within the E-Business Tax (ZX) product of Oracle E-Business Suite. It stores the rules used to determine the outcome of the multiple tax determination processes — regime determination, tax determination, tax rate determination, tax recovery, and tax calculation. Each row represents a single rule scoped to a specific tax, a configuration owner, and a tax determination process, identified by the surrogate primary key TAX_RULE_ID through the ZX_RULES_B_PK index.

The table is registered in the ZX schema with 33 documented columns and is marked VALID in the 12.1.1 / 12.2.2 data dictionary. Because it carries the descriptive rule headers, effective-dating attributes, and foreign-key associations that define the rule semantics, while subordinate tables hold the rule conditions and results, its FK structure is satellite-leaning under Data Vault modeling heuristics. In other words, it behaves less like an independent hub or link and more like a descriptive satellite keyed to tax rule identity.

Key Information Stored

The most operationally significant columns in ZX_RULES_B are those that identify, scope, and control the rule:

• TAX_RULE_ID — surrogate primary key and the unique identifier referenced by all dependent tables.
• TAX_RULE_CODE — user-facing rule identifier used in setup and reporting.
• TAX and TAX_REGIME_CODE — the tax and regime to which the rule belongs; TAX_REGIME_CODE joins to ZX_REGIMES_B.
• CONTENT_OWNER_ID — the configuration owner (party) that owns the rule; joins to ZX_PARTY_TAX_PROFILE.
• TAX_EVENT_CLASS_CODE — the event class triggering the rule; joins to ZX_EVENT_CLASSES_B.
• EVENT_CLASS_MAPPING_ID — links to ZX_EVNT_CLS_MAPPINGS for event class configuration.
• SERVICE_TYPE_CODE and APPLICATION_ID — determine the owning application and service context; APPLICATION_ID joins to FND_APPLICATION.
• DET_FACTOR_TEMPL_CODE — identifies the determining factor template; joins to ZX_DET_FACTOR_TEMPL_B.
• TAX_LAW_REF_CODE, GEOGRAPHY_TYPE, and GEOGRAPHY_ID — capture tax law and geography scoping.
• PRIORITY — controls rule precedence when multiple rules qualify.
• EFFECTIVE_FROM / EFFECTIVE_TO — date-range validity of the rule.
• ENABLED_FLAG, RECORD_TYPE_CODE, RECOVERY_TYPE_CODE — enablement and record classification.

The unique index ZX_RULES_B_U2 — over TAX_REGIME_CODE, TAX, CONTENT_OWNER_ID, SERVICE_TYPE_CODE, EFFECTIVE_FROM, RECOVERY_TYPE_CODE, TAX_RULE_CODE, and PRIORITY — is the practical business-key candidate.

Common Use Cases and Queries

Typical uses include auditing rule configuration, diagnosing tax determination failures, and reconciling rules used in calculation results. A common query joins the rule header to its translations and regime:

• Listing enabled rules for a tax and configuration owner within an effective date window.
• Identifying all rules bound to a determining factor template or event class mapping.
• Reconciling rules referenced in the ZX_PROCESS_RESULTS table to confirm which rules fired during a transaction.
• Reporting on priority conflicts where multiple rules share the same regime, tax, owner, and effective date.

Sample pattern: SELECT r.tax_rule_id, r.tax_rule_code, r.tax, r.priority FROM zx.zx_rules_b r WHERE r.enabled_flag='Y' AND SYSDATE BETWEEN r.effective_from AND NVL(r.effective_to, SYSDATE+1); Additional columns can be pulled from ZX_RULES_TL for the translated rule name.

Related Objects

The following objects are most directly coupled to ZX_RULES_B through the documented referential relationships:

• ZX_PROCESS_RESULTS — references ZX_RULES_B.TAX_RULE_ID; records the rules applied during tax processing.
• ZX_RULES_TL — references ZX_RULES_B.TAX_RULE_ID; stores translated rule names and descriptions.
• ZX_REGIMES_B — joined via TAX_REGIME_CODE.
• ZX_EVENT_CLASSES_B — joined via TAX_EVENT_CLASS_CODE.
• ZX_DET_FACTOR_TEMPL_B — joined via DET_FACTOR_TEMPL_CODE.
• ZX_PARTY_TAX_PROFILE — joined via CONTENT_OWNER_ID.
• ZX_EVNT_CLS_MAPPINGS — joined via EVENT_CLASS_MAPPING_ID.
• FND_APPLICATION — joined via APPLICATION_ID.