Results for “jl_zz_ar_tx_rules_all”

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

Overview

JL_ZZ_AR_TX_RULES_ALL is a transaction table within the JL (Latin America Localizations) product of Oracle E-Business Suite, documented as "Latin Tax Rules Information." It resides in the JL schema and stores the rule definitions that govern how Latin American tax engines—most notably the EBS Tax (E-Business Tax / Oracle Financials for Latin America) determination logic—set the tax behavior applied to Receivables transactions. Each row represents an individual tax rule that is evaluated during tax derivation and calculation for a given operating unit, allowing localized statutory requirements (such as Argentine, Brazilian, Chilean, or Mexican tax treatment) to be expressed declaratively rather than in code.

The table is a key configuration object: it links a tax rule to a tax category, a contributor type, and a Receivables transaction type, and it is scoped by ORG_ID. Because the columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN, the table is fully audit-enabled and follows standard EBS WHO-column conventions. The supplied relationship metadata identifies CUST_TRX_TYPE_ID as a foreign-key reference into RA_CUST_TRX_TYPES_ALL and provides two unique indexes (JL_ZZ_AR_TX_RULES_U1 and JL_ZZ_AR_TX_RULES_U2), making the table a business-key-constrained configuration entity rather than a pure transactional fact. Heuristically, the FK structure suggests a satellite-leaning Data Vault classification, since it references a master dimension (transaction types) while carrying its own descriptive attributes.

Key Information Stored

The table contains 14 documented columns. The surrogate primary key is RULE_ID, enforced by JL_ZZ_AR_TX_RULES_ALL_PK. RULE_ID uniquely identifies each rule and is also part of the U2 unique index (RULE_ID, ORG_ID), which enforces that a rule identifier is unique within an operating unit. The U1 unique index (TAX_RULE_LEVEL, TAX_CATEGORY_ID, CONTRIBUTOR_TYPE, CUST_TRX_TYPE_ID, PRIORITY, ORG_ID) defines the true business key: a tax rule level cannot repeat for the same combination of tax category, contributor type, transaction type, priority, and operating unit.

• RULE_ID — surrogate primary key identifying the tax rule row.
• RULE — the rule value or code that drives the tax determination outcome.
• TAX_RULE_LEVEL — the level at which the rule applies; part of the U1 business key.
• TAX_CATEGORY_ID — identifies the tax category the rule is associated with.
• CONTRIBUTOR_TYPE — the type of tax contributor (for example, a statutory or internal party) the rule targets.
• CUST_TRX_TYPE_ID — foreign key to RA_CUST_TRX_TYPES_ALL, restricting the rule to a specific transaction type.
• PRIORITY — evaluation sequence or precedence among competing rules.
• ORG_ID — the operating unit (multi-org partitioning) to which the rule belongs.
• DESCRIPTION — free-text explanation of the rule's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns tracking who created and last modified the record and when.

Common Use Cases and Queries

Typical usage centers on tax configuration review and Receivables tax troubleshooting. Analysts query the table to confirm which rule is picked up for a given tax category and transaction type, and to reconcile the priority ordering when duplicate outcomes appear. Because ORG_ID is part of both unique indexes, most production queries filter by operating unit.

Sample pattern to inspect rules for a transaction type and category:

• SELECT rule_id, tax_rule_level, rule, tax_category_id, contributor_type, cust_trx_type_id, priority, description FROM jl_zz_ar_tx_rules_all WHERE org_id = :org_id AND cust_trx_type_id = :trx_type_id ORDER BY priority;
• SELECT a.rule_id, a.rule, b.name FROM jl_zz_ar_tx_rules_all a, ra_cust_trx_types_all b WHERE a.cust_trx_type_id = b.cust_trx_type_id AND a.org_id = :org_id;
• Audit query using WHO columns: joining LAST_UPDATED_BY to FND_USER to identify who last changed a rule.

Reporting use cases include generating a matrix of rules by category, contributor type, and priority; validating that every active transaction type has at least one rule; and detecting gaps in the U1 business key before configuration migration between instances.

Related Objects

The following objects are the most significant dependencies and reference points for JL_ZZ_AR_TX_RULES_ALL.

• RA_CUST_TRX_TYPES_ALL — referenced via CUST_TRX_TYPE_ID; the transaction type dimension that constrains each rule.
• JL_ZZ_AR_TX_RULES_ALL_PK — the primary-key constraint on RULE_ID.
• JL_ZZ_AR_TX_RULES_U1 and JL_ZZ_AR_TX_RULES_U2 — unique indexes defining business-key and org-level uniqueness.
• JL_ZZ_AR_TX_CATEGORIES / tax category definition objects — supply the TAX_CATEGORY_ID referenced by the rule.
• FND_USER — joined through LAST_UPDATED_BY and CREATED_BY for audit reporting.
• ZX / E-Business Tax configuration objects — the tax determination framework that consumes these localized rule definitions during calculation.
• AR / Receivables transaction tables — downstream consumers where the applied tax rule influences invoicing and tax reporting.