Search Results zx_lines_det_factors

Overview

The ZX_LINES_DET_FACTORS table is a core data repository within the Oracle E-Business Tax (ZX) module for Oracle EBS releases 12.1.1 and 12.2.2. It functions as the central table for storing granular, transaction-level attributes that are critical for the determination, calculation, and subsequent reporting of taxes. As documented, each row corresponds to a single transaction line associated with a specific event class, capturing the detailed context necessary for the tax engine to apply the correct rules. Its role is pivotal in the tax determination process, serving as the primary source of transactional facts against which tax regimes, rates, and rules are evaluated.

Key Information Stored

The table's primary key structure highlights its fundamental design, uniquely identifying a transaction line through a combination of identifiers: APPLICATION_ID, EVENT_CLASS_CODE, ENTITY_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, and ICX_SESSION_ID. Beyond these keys, the table stores a wide array of determinant attributes. These include party and location information (e.g., SHIP_TO_LOCATION_ID, BILL_THIRD_PTY_ACCT_ID), financial context (TRX_CURRENCY_CODE, LEDGER_ID), organizational data (INTERNAL_ORGANIZATION_ID), and references to historical or manual tax codes (HISTORICAL_TAX_CODE_ID). The extensive foreign key relationships indicate it holds IDs that link to master data in Customer (HZ), Subledger (AP, AR), Human Resources (HR), and General Ledger (FND) tables.

Common Use Cases and Queries

This table is primarily accessed for tax inquiry, audit reporting, and troubleshooting tax determination issues. A common use case involves tracing the specific attributes that led to a calculated tax line on a transaction. For example, to analyze tax determinants for a specific invoice line, a query would join to ZX_LINES (which holds the calculated tax results) using the primary key columns. Another critical reporting use case is verifying the sourcing of location or party data used in tax determination, which is essential for compliance audits. A sample query pattern to retrieve determinant details for a transaction would be:

• SELECT * FROM ZX_LINES_DET_FACTORS WHERE APPLICATION_ID = 222 /* OE */ AND ENTITY_CODE = 'TRANSACTIONS' AND TRX_ID = <ORDER_HEADER_ID>;

Technical consultants also query this table to diagnose mismatches in expected versus applied tax rates by examining the stored ship-to, bill-to, and product category values.

Related Objects

The table maintains integral relationships with numerous core EBS objects, as evidenced by its foreign key constraints. Key documented relationships include:

• ZX_LINES: The primary child table, where calculated tax results are stored, joined via the primary key columns.
• HZ_CUST_ACCOUNTS / HZ_CUST_ACCT_SITES_ALL: For bill-to and ship-to third-party account and site information (e.g., BILL_THIRD_PTY_ACCT_ID, SHIP_THIRD_PTY_ACCT_SITE_ID).
• HR_LOCATIONS_ALL: For ship-to and ship-from location details (SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID).
• AP_TAX_CODES_ALL / AR_VAT_TAX_ALL_B: For historical or manually entered tax code references (HISTORICAL_TAX_CODE_ID).
• ZX_EVNT_CLS_MAPPINGS / ZX_EVNT_TYP_MAPPINGS: For tax event class and type mapping definitions.
• FND_CURRENCIES, FND_DOCUMENT_SEQUENCES, HR_ALL_ORGANIZATION_UNITS: For transactional currency, document sequencing, and internal organization context.