Results for “trx_line_currency_conv_rate”

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

Overview

ZX_TRANSACTION_LINES_GT is a Global Temporary Table (GTT) owned by the ZX schema within Oracle E-Business Tax (E-Business Tax / ETRM). It is documented as VALID in Oracle EBS 12.1.1 and 12.2.2 and serves a single, deliberately narrow purpose: to pass transaction line information into the tax calculation engine. Because it is a GTT, its rows are private to a session and are typically purged on commit or at session end, making it a transient staging structure rather than a persistent transaction store.

In the E-Business Tax architecture, the calling application (for example, Payables, Receivables, Purchasing, or Order Management) populates this table with the line-level attributes required for tax determination — parties, places of supply, product fiscal classification, amounts, and reference documents. The tax engine (ZX) reads those rows, applies configuration from the Tax Configuration Owner, and returns calculated results. The table therefore acts as the inbound contract between source applications and the tax engine.

Under a heuristic Data Vault classification, ZX_TRANSACTION_LINES_GT is modeled as standalone. It does not behave as a hub, link, or satellite; it is a transient staging object whose keys are meaningful only for the duration of a single tax calculation call rather than as durable business entities. This classification is a modeling suggestion derived from its lack of dependent relationships, not a formal Data Vault designation.

Key Information Stored

The documented physical schema for 12.2.2 contains 292 columns. The following are the most functionally significant groupings.

• Business key / unique index ZX_TRANSACTION_LINES_GT_U1: APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, TRX_ID, TRX_LINE_ID, TRX_LEVEL_TYPE. This composite uniquely identifies a transaction line within the context of a source application and event class. Note that the table does not expose a separate surrogate primary key column in the documented metadata; the unique index columns serve as the identifying key.
• Transaction identity: TRX_ID, TRX_LINE_ID, TRX_LINE_NUMBER, TRX_LINE_TYPE, TRX_LINE_DATE, TRX_SHIPPING_DATE, TRX_RECEIPT_DATE, TRX_LINE_GL_DATE.
• Classification and defaulting: LINE_CLASS, TRX_BUSINESS_CATEGORY, LINE_INTENDED_USE, USER_DEFINED_FISC_CLASS, PRODUCT_FISC_CLASSIFICATION, INPUT_TAX_CLASSIFICATION_CODE, OUTPUT_TAX_CLASSIFICATION_CODE.
• Amounts and quantities: LINE_AMT, TRX_LINE_QUANTITY, UNIT_PRICE, CASH_DISCOUNT, VOLUME_DISCOUNT, TRADING_DISCOUNT, TRANSFER_CHARGE, TRANSPORTATION_CHARGE, INSURANCE_CHARGE, OTHER_CHARGE, ASSESSABLE_VALUE, CTRL_TOTAL_LINE_TX_AMT, LINE_AMT_INCLUDES_TAX_FLAG.
• Product context: PRODUCT_ID, PRODUCT_CODE, PRODUCT_TYPE, PRODUCT_CATEGORY, PRODUCT_ORG_ID, UOM_CODE.
• Parties and locations: SHIP_TO_PARTY_ID, SHIP_FROM_PARTY_ID, BILL_TO_PARTY_ID, BILL_FROM_PARTY_ID, MERCHANT_PARTY_ID, POA_PARTY_ID, POO_PARTY_ID, and the corresponding SITE_ID and LOCATION_ID columns, plus the many *_TAX_PROF_ID party tax profile references.
• Cross-document references: REF_DOC_TRX_ID / REF_DOC_LINE_ID (with user keys), APPLIED_FROM_TRX_ID / APPLIED_FROM_LINE_ID, APPLIED_TO_TRX_ID / APPLIED_TO_TRX_LINE_ID, and ADJUSTED_DOC_TRX_ID / ADJUSTED_DOC_LINE_ID.
• Source traceability: SOURCE_APPLICATION_ID, SOURCE_ENTITY_CODE, SOURCE_EVENT_CLASS_CODE, SOURCE_TRX_ID, SOURCE_LINE_ID, SOURCE_TAX_LINE_ID.
• Currency: TRX_LINE_CURRENCY_CODE, TRX_LINE_CURRENCY_CONV_RATE, TRX_LINE_CURRENCY_CONV_DATE, TRX_LINE_CURRENCY_CONV_TYPE.
• Date and control: TAX_DATE, TAX_DETERMINE_DATE, TAX_POINT_DATE, HISTORICAL_FLAG, EXEMPTION_CONTROL_FLAG, EXEMPT_REASON_CODE.
• Generic extension: NUMERIC1–NUMERIC10, CHAR1–CHAR10, DATE1–DATE10, and GLOBAL_ATTRIBUTE1 with GLOBAL_ATTRIBUTE_CATEGORY.
• Interface support: INTERFACE_ENTITY_CODE, INTERFACE_LINE_ID.

Common Use Cases and Queries

Because the table is a GTT, useful inspection is limited to a session that has just populated it, or to diagnostic scenarios where a committing GTT variant retains rows. Typical uses include:

• Debugging tax determination: capturing the exact line attributes presented to the tax engine before calculation, to confirm that party, product, and date inputs were correct.
• Reconciliation: comparing the inbound LINE_AMT against calculated totals for a specific TRX_ID.
• Source traceability: tracing interfaces that use INTERFACE_ENTITY_CODE and INTERFACE_LINE_ID back to upstream records.
• Cross-reference analysis: examining applied-from, applied-to, and adjusted document chains for credit and adjustment transactions.

A representative query pattern follows:

• SELECT application_id, entity_code, event_class_code, trx_id, trx_line_id, line_amt, trx_line_currency_code FROM zx_transaction_lines_gt WHERE trx_id = :trx_id ORDER BY trx_line_number;
• For joined reporting, the line may be joined to CN_TRX_LINES_ALL on TRX_LINE_ID, or to reference documents using REF_DOC_TRX_ID / REF_DOC_LINE_ID, to associate engine input with the persisted transaction line.
• Because rows are session-scoped, queries should be executed in the same session that populated the table, or by schema owners with privileges to view GTT data during diagnosis.

Related Objects

The metadata documents three foreign key relationships and several implicit dependencies. The most significant related objects are:

• CN_TRX_LINES_ALL — referenced via ZX_TRANSACTION_LINES_GT.TRX_LINE_ID; the persisted source transaction line.
• FND_DM_PRODUCTS — referenced via PRODUCT_ID; supplies product context for tax determination.
• IGI_DOS_TRX_SOURCES — referenced via SOURCE_TRX_ID; provides source document origin information.
• ZX_LINES / ZX_LINES_DET_FACTORS — downstream structures where calculated tax lines and detail factors are stored after the engine processes the input.
• ZX_TRANSACTION_HEADERS_GT — the companion header-level GTT passed alongside the line table for the same calculation call.
• ZX_PARTY_TAX_PROFILE / ZX_LOCATION_TAX_PROFILE — resolve the many *_TAX_PROF_ID and *_SITE_TAX_PROF_ID references to party and site tax profiles.
• ZX_API_INPUT_PARAMETERS and the ZX tax calculation API (e.g., ZX_API_PUB) — programmatic entry points that populate and invoke processing of this GTT.

Together these objects provide the input, calculation, and output context in which ZX_TRANSACTION_LINES_GT functions as the transient line-level interface into E-Business Tax.