Results for “applied_to_trx_line_id”

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

Overview

The JG_ZZ_VAT_TRX_DETAILS table, owned by the JG schema (Regional Localizations), is a core staging and reporting table within the Oracle E-Business Suite Value Added Tax (VAT) reporting framework. It contains Accounts Payable (AP), Accounts Receivable (AR), and General Ledger (GL) transactions that have been selected for VAT reporting purposes. The table serves as the central repository of taxable transaction line detail used to populate VAT returns, reconciliation reports, and statutory tax submissions across localized jurisdictions.

Functionally, this table acts as the intersection between transactional sub-ledger data and tax reporting structures. Each row represents a single VAT-relevant transaction line captured from AP invoices, AR transactions, or GL journal entries, enriched with tax rate, tax amount, trading partner, and reporting metadata required for regulatory filings.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as hub-leaning, based on its foreign-key structure. This heuristic suggests the table behaves primarily as a hub — a central, uniquely-identified entity keyed on a business surrogate (VAT_TRANSACTION_ID) — with multiple satellite-style descriptive attributes attached. In practice, the table also carries link semantics, since it references numerous dimension and transaction entities (establishments, tax lines, receipts classes, products, and so forth).

Key Information Stored

The table contains 233 documented columns, reflecting its role as a wide, denormalized reporting feeder. The most significant columns include:

• VAT_TRANSACTION_ID — The surrogate primary key (JG_ZZ_VAT_TRX_DETAILS_PK) and the unique business key (also enforced by unique index JG_ZZ_VAT_TRX_DETAILS_U1). Uniquely identifies each VAT transaction record.
• REPORTING_STATUS_ID — Foreign key to JG_ZZ_VAT_REP_STATUS; tracks the life-cycle state of the record within the VAT reporting process.
• LEDGER_ID / LEDGER_NAME — Identifies the ledger from which the transaction was extracted, essential for multi-ledger reporting.
• TRX_ID / TRX_NUMBER / TRX_LINE_ID — The originating transaction identifier, document number, and line identifier, providing traceability back to the source sub-ledger transaction.
• TRX_DATE / TRX_DUE_DATE — The transaction and due dates used for period-based VAT reporting.
• TRX_CURRENCY_CODE / FUNCTIONAL_CURRENCY_CODE — Transaction and functional currency codes, supporting dual-currency VAT calculations.
• TAXABLE_AMT / TAX_AMT — The taxable base and calculated tax amount in transaction currency, with functional-currency equivalents (TAXABLE_AMT_FUNCL_CURR, TAX_AMT_FUNCL_CURR).
• TAX_RATE_CODE / TAX_RATE — The tax rate code and percentage applied to the transaction line.
• TAX_LINE_ID — Foreign key to ZX_LINES; links directly to the E-Business Tax engine's tax determination record.
• TAX_REGIME_CODE / TAX_JURISDICTION_CODE — Identifies the tax regime and jurisdiction governing the reporting obligation.
• MERCHANT_PARTY_NAME / MERCHANT_PARTY_TAX_REG_NUMBER — Trading partner identity and tax registration details required for VAT invoicing.
• ESTABLISHMENT_ID — Foreign key to PER_ESTABLISHMENTS, indicating the legal establishment responsible for the transaction.
• SELECTION_PROCESS_ID / FINAL_REPORTING_ID — Control identifiers linking the row to the selection run and its final reporting batch.

Common Use Cases and Queries

The table is typically queried during VAT return preparation, reconciliation, and audit. Common patterns include:

• Extract VAT transactions by reporting period and ledger: filtering on TRX_DATE, LEDGER_ID, and REPORTING_STATUS_ID to produce the data set for a periodic VAT return.
• Reconcile tax amounts between E-Business Tax and the reported figures: joining JG_ZZ_VAT_TRX_DETAILS to ZX_LINES on TAX_LINE_ID and comparing TAX_AMT with the underlying tax line values.
• Identify unreported or pending transactions: querying rows where REPORTING_STATUS_ID indicates a non-finalized state.
• Trading partner and registration analysis: aggregating by MERCHANT_PARTY_TAX_REG_NUMBER, TAX_REGIME_CODE, and TAX_JURISDICTION_CODE for statutory cross-checks.
• Box allocation reporting: joining to JG_ZZ_VAT_BOX_ALLOCS on VAT_TRANSACTION_ID to map transactions to VAT return boxes.

A representative pattern for a period extract might filter on LEDGER_ID, a date range on TRX_DATE, and a join to JG_ZZ_VAT_REP_STATUS on REPORTING_STATUS_ID to return only rows in a completed reporting state.

Related Objects

• JG_ZZ_VAT_REP_STATUS — Referenced via REPORTING_STATUS_ID; defines the reporting status codes applied to each transaction.
• JG_ZZ_VAT_BOX_ALLOCS — References this table via VAT_TRANSACTION_ID; maps each VAT transaction to one or more return boxes.
• ZX_LINES — Referenced via TAX_LINE_ID; the E-Business Tax engine's tax line record.
• PER_ESTABLISHMENTS — Referenced via ESTABLISHMENT_ID; identifies the reporting legal establishment.
• ZX_STATUS_B — Referenced via TAX_STATUS_ID; supplies tax status definitions.
• CN_TRX_LINES_ALL — Referenced via TRX_LINE_ID; the source transaction line for receivables and related transactions.
• AR_RECEIPT_CLASSES — Referenced via RECEIPT_CLASS_ID; identifies receipt classification for AR cash receipt transactions.
• FND_DM_PRODUCTS / IGI_EXP_TRX_TYPE / GL_MGT_SEG_UPGRADE_H — Referenced via PRODUCT_ID, TRX_TYPE_ID, and CHART_OF_ACCOUNTS_ID respectively, supplying product, transaction type, and chart of accounts context.

Together these relationships confirm the table's role as a central VAT reporting hub that consolidates detail from AP, AR, GL, and the E-Business Tax engine into a single, auditable reporting structure.