Results for “source_tax_line_id”

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

Overview

ZX_LINES_DET_FACTORS is a transaction-line detail table owned by the ZX schema within the Oracle E-Business Tax (E-Business Tax / EBTax) module. It stores transaction-related attributes used for tax calculation and reporting, with each row representing a single transaction line belonging to a specific event class. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the working store of "determinant factors" — the party, site, product, location, and document attributes that the tax determination engine evaluates against tax configuration rules to arrive at an applicable tax regime, tax, tax status, and rate. The table carries 349 documented columns and is populated during tax calculation from the source transaction systems (Receivables, Payables, Purchasing, and others) and, in 12.2.x, through the tax partner and migrated-partner flows.

The heuristic Data Vault classification mined from the foreign-key structure is link. This is consistent with its nature as an associative structure: it connects a transaction identity to the various parties, sites, locations, products, and profiles that participate in taxation. The classification is offered as a modeling suggestion rather than a physical design constraint; the physical table itself is a wide, single-level denormalized record keyed by transaction identifiers.

Key Information Stored

The primary key, ZX_LINES_DET_FACTORS_PK, is the composite surrogate identity (APPLICATION_ID, EVENT_CLASS_CODE, ENTITY_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE, ICX_SESSION_ID). A second unique index, ZX_LINES_DET_FACTORS_U2, uses EVENT_CLASS_MAPPING_ID with the transaction and session keys. These business-key candidates distinguish rows by owning application, event class, entity, transaction, line, level type, and session, which is important because the same transaction line can be recalculated across sessions and event classes over time.

The most significant columns include:

• APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE — identify the source application, entity, and event class/type mapping the line belongs to.
• TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE — the source transaction header and line references and the level at which tax applies.
• LEDGER_ID — the ledger whose tax configuration governs calculation.
• TRX_DATE, TRX_LINE_GL_DATE, TRX_CURRENCY_CODE, TRX_LINE_CURRENCY_CODE — transaction dating and currency context for rate and conversion determination.
• SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID, BILL_TO_LOCATION_ID, BILL_FROM_LOCATION_ID, POA_LOCATION_ID, POO_LOCATION_ID — the location factors that drive place-of-supply, place-of-acquisition, and situs rules; these columns are the direct link to the HR_LOCATIONS_ALL table.
• SHIP_TO_PARTY_TAX_PROF_ID, SHIP_FROM_PARTY_TAX_PROF_ID, BILL_TO_PARTY_TAX_PROF_ID and the corresponding SITE_TAX_PROF_ID columns — references into the ZX party tax profile, supplying registration and configuration populations.
• PRODUCT_ID, PRODUCT_FISC_CLASSIFICATION, USER_DEFINED_FISC_CLASS, PRODUCT_CODE, LINE_AMT, ASSESSABLE_VALUE — product and amount factors used to evaluate exemptions and taxable basis.
• HISTORICAL_FLAG, HISTORICAL_TAX_CODE_ID — indicate whether the line is historical (pre-migration) and its legacy tax code reference.
• TAX_CALCULATION_DONE_FLAG, TAX_PROCESSING_COMPLETED_FLAG, CTRL_TOTAL_LINE_TX_AMT — processing status and control totals for the line.

Common Use Cases and Queries

Typical uses include diagnosing why a particular tax was or was not applied, reconciling tax reporting by place of supply, and auditing the determinant factors persisted for a transaction line.

• Retrieve all factor rows for a transaction line, filtering by application, entity, transaction, and line.
• Join to HR_LOCATIONS_ALL on SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID, BILL_TO_LOCATION_ID, or BILL_FROM_LOCATION_ID to resolve location codes against the tax result.
• Join to ZX_PARTY_TAX_PROFILE on the party tax profile columns to inspect registration numbers used in determination.
• Filter on HISTORICAL_FLAG = 'Y' to isolate pre-migration partner records, or on TAX_CALCULATION_DONE_FLAG to identify lines awaiting recalculation.

A representative pattern resolves ship-to location detail for a given transaction:

SELECT d.TRX_ID, d.TRX_LINE_ID, d.SHIP_TO_LOCATION_ID,
       l.location_code, l.address_line_1, l.city
FROM   zx.zx_lines_det_factors d,
       hr.hr_locations_all l
WHERE  d.application_id    = :application_id
AND    d.entity_code       = :entity_code
AND    d.event_class_code  = :event_class_code
AND    d.trx_id            = :trx_id
AND    l.location_id(+)    = d.ship_to_location_id;

Related Objects

The most significant related objects, based on the documented foreign keys, are:

• HR_LOCATIONS_ALL — referenced by SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID, BILL_TO_LOCATION_ID, BILL_FROM_LOCATION_ID, POA_LOCATION_ID, POO_LOCATION_ID, and INTERNAL_ORG_LOCATION_ID.
• HZ_LOCATIONS — the trading community location counterpart for the same location columns.
• ZX_PARTY_TAX_PROFILE — referenced by the ship-to, ship-from, bill-to, POA, POO, paying, owning HQ, trading HQ, merchant, and headquarters establishment party/site tax profile columns.
• ZX_EVNT_CLS_MAPPINGS / ZX_EVNT_TYP_MAPPINGS — link event class and event type to the transaction through EVENT_CLASS_MAPPING_ID, APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE.
• AR_VAT_TAX_ALL_B and AP_TAX_CODES_ALL — legacy tax code references via HISTORICAL_TAX_CODE_ID.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL — third-party bill-to and ship-to account and site references.
• ZX_LINES — related through SOURCE_TAX_LINE_ID, supplying calculated tax line results.
• FND_CURRENCIES, FND_DOCUMENT_SEQUENCES, GL_CODE_COMBINATIONS, FV_LEGAL_ENTITIES, and PER_ESTABLISHMENTS — referenced by TRX_CURRENCY_CODE, DOC_SEQ_ID, ACCOUNT_CCID, LEGAL_ENTITY_ID, and ESTABLISHMENT_ID respectively.