Results for “merchant_party_id”

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

Overview

The ZX_TRANSACTION_LINES table resides in the ZX schema, which is owned by the Oracle E-Business Tax (E-Business Tax / ETRM) product. It is classified as a TABLE and holds a VALID status in Oracle E-Business Suite releases 12.1.1 and 12.2.2. As its ETRM description states, this table stores transaction lines entered by the user through the tax simulator.

The tax simulator is a diagnostic and configuration-validation facility within E-Business Tax that allows tax managers to model hypothetical transactions and observe how the tax determination engine will calculate taxes, without creating real receivables or payables transactions. ZX_TRANSACTION_LINES is therefore the persistent store for the simulated transaction line input that drives that engine. Each row represents a single simulated transaction line together with the tax attributes, party/location context, product context, and calculated tax results associated with it.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as standalone. In Data Vault terms it may be modeled as a satellite-like descriptive record keyed on its natural composite identifier, with limited outward dependencies; the modeling suggestion is a standalone descriptive table rather than a hub or link.

Key Information Stored

The documented physical schema for release 12.2.2 contains 117 columns. The primary key is defined by the constraint ZX_TRANSACTION_LINES_PK over the composite columns TRX_ID and TRX_LINE_ID. These two columns form the surrogate/uniquely identifying key for a simulated line, and they are the principal business-key candidates for joining and de-duplication purposes.

The 10 to 15 most significant columns fall into three groups:

• Identity and context: TRX_ID, TRX_LINE_ID, TRX_LINE_NUMBER, TRX_LEVEL_TYPE, TRX_LINE_TYPE, TRX_LINE_DATE, APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_BUSINESS_CATEGORY, LINE_INTENDED_USE.
• Amount and product attributes: LINE_AMT, TRX_LINE_QUANTITY, UNIT_PRICE, PRODUCT_ID, PRODUCT_CODE, PRODUCT_FISC_CLASSIFICATION, PRODUCT_TYPE, UOM_CODE.
• Tax determination and result: TAX_REGIME_ID, TAX_REGIME_CODE, TAX_ID, TAX, TAX_STATUS_ID, TAX_STATUS_CODE, TAX_RATE_ID, TAX_RATE_CODE, TAX_RATE, TAX_LINE_AMT, LINE_CLASS.

Foreign key relationships documented for this table include PRODUCT_ID referencing FND_DM_PRODUCTS and TAX_STATUS_ID referencing ZX_STATUS_B.

Common Use Cases and Queries

Typical usage centers on reviewing and reproducing simulator scenarios. Analysts query simulated lines to validate tax setup before it is applied to live transactions, to compare calculated tax against an expected value, and to troubleshoot rules that produced an incorrect result.

• Retrieve all simulated lines for a simulator transaction:

SELECT trx_line_number, line_amt, product_code,
       tax_regime_code, tax_rate_code, tax_line_amt
FROM   zx.zx_transaction_lines
WHERE  trx_id = :p_trx_id
ORDER BY trx_line_number;

• Report tax by regime and rate across simulator runs:

SELECT tax_regime_code, tax_rate_code, SUM(taX_line_amt) tax_total
FROM   zx.zx_transaction_lines
GROUP BY tax_regime_code, tax_rate_code;

• Join simulator lines to status and product definitions:

SELECT l.trx_line_id, s.tax_status_code, p.product_number
FROM   zx.zx_transaction_lines l,
       zx.zx_status_b s,
       fnd_dm_products p
WHERE  l.tax_status_id = s.tax_status_id
AND    l.product_id    = p.product_id;

Reporting is commonly combined with ZX_LINES and ZX_LINES_DET_FACTORS when administrators need to compare simulated outcomes against actual calculated lines, verifying that configuration changes yield the expected results.

Related Objects

The following objects are the most significant points of integration for ZX_TRANSACTION_LINES, based on the documented FK and PK relationships:

• ZX_STATUS_B — joined via TAX_STATUS_ID; supplies the tax status description and code used during simulation.
• FND_DM_PRODUCTS — joined via PRODUCT_ID; supplies product context for the simulated line.
• ZX_TRANSACTION_LINES_PK — the composite primary key constraint over TRX_ID and TRX_LINE_ID enforcing uniqueness of each simulated line.
• ZX_LINES and ZX_LINES_DET_FACTORS — the core E-Business Tax result tables; simulator output is frequently compared against these to confirm engine behavior.
• ZX_RATES_B / ZX_RATES_VL — referenced by TAX_RATE_ID and TAX_RATE_CODE to obtain rate definitions for the simulated tax.
• ZX_REGIMES_B / ZX_REGIMES_VL — referenced by TAX_REGIME_ID and TAX_REGIME_CODE for the governing tax regime.
• ZX_TAXES_B / ZX_TAXES_VL — referenced by TAX_ID and TAX for the tax itself.
• ZX_PARTY_TAX_PROFILE — provides default party tax profile settings that influence simulator defaults.

Together these objects allow the tax simulator to assemble the same attribute set the determination engine consumes for a real transaction, making ZX_TRANSACTION_LINES a faithful test harness for tax configuration in both 12.1.1 and 12.2.2.