Results for “invoice_amount”

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

Overview

The GML.TX_HIST_TAX table is an Oracle E-Business Suite repository object owned by the GML — Process Manufacturing Logistics schema (also referenced generally as Process Manufacturing). Within the EBS 12.1.1 and 12.2.2 data model, it stores a historical record of tax amounts associated with invoices, keyed by the tax authority, tax classification, and invoice identity. Its documented description states plainly that the table is not used in 11i, meaning it is a post-11i construct introduced for later releases and therefore relevant primarily to 12.1.1 and 12.2.2 environments.

From a heuristic Data Vault classification standpoint — mined from the documented foreign-key structure — TX_HIST_TAX is best modeled as a link. Its primary key composes multiple business identifiers (INVOICE_ID, TAXAUTH_ID, ICTAX_CLASS) that resolve to more than one referenced entity, specifically the invoice and the tax authority master, with an additional resolution to a tax classification reference table. This associative structure, rather than a single-subject descriptor set, supports the link interpretation as a modeling suggestion. The object status is recorded as VALID.

Key Information Stored

The table is documented with 16 physical columns. The most significant of these fall into three groups:

• INVOICE_ID — part of the composite primary key; identifies the invoice against which tax history is recorded.
• TAXAUTH_ID — part of the primary key; the tax authority responsible for the tax assessment, resolving to TX_TAXA_MST.
• ICTAX_CLASS — part of the primary key; the intercompany tax classification, resolving to IC_TAXN_CLS.
• INVOICE_DATE, PAYMENT_DATE, TAXPOINT_DATE — date attributes capturing invoice issuance, settlement, and the tax point (the moment tax liability is recognized).
• INVOICE_AMOUNT, TAXABLE_AMOUNT, TAX_AMOUNT — monetary measures representing the gross invoice value, the portion subject to tax, and the resulting tax computed.
• TAX_CATEGORY_ID — a foreign-key-style reference to the tax category classification for the line.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row and when.
• DELETE_MARK — the conventional EBS soft-delete flag; rows with a non-zero marker are logically deleted rather than physically removed.

The surrogate primary key is the unique index TX_HIST_TAX_PK, composed of (INVOICE_ID, TAXAUTH_ID, ICTAX_CLASS). There is no separate single-column surrogate documented; the business-key candidates are exactly those three columns, so the unique index and the primary key coincide.

Common Use Cases and Queries

Because the table captures historical tax amounts tied to invoices, it is most useful for tax reporting, reconciliation, and audit. A typical query joins to the tax authority master to resolve the authority name:

• Tax by authority: aggregate TAX_AMOUNT grouped by TAXAUTH_ID, joined to TX_TAXA_MST for the authority description.
• Tax point analysis: filter on TAXPOINT_DATE to report tax recognized in a given period, comparing INVOICE_DATE and PAYMENT_DATE.
• Taxable versus tax: compute the effective rate as TAX_AMOUNT / TAXABLE_AMOUNT for reconciliation against the invoice gross (INVOICE_AMOUNT).
• Audit trail: select CREATED_BY, LAST_UPDATED_BY and timestamps for change-tracking, excluding rows where DELETE_MARK is set.

A representative pattern is SELECT h.INVOICE_ID, h.TAXAUTH_ID, t.TAX_AUTHORITY_NAME, h.TAX_AMOUNT FROM GML.TX_HIST_TAX h, GML.TX_TAXA_MST t WHERE h.TAXAUTH_ID = t.TAXAUTH_ID AND h.DELETE_MARK = 0.

Related Objects

• TX_TAXA_MST — referenced by TX_HIST_TAX.TAXAUTH_ID; the tax authority master.
• IC_TAXN_CLS — referenced by TX_HIST_TAX.ICTAX_CLASS; the intercompany tax classification reference.
• TX_HIST_TAX_PK — the unique/primary index enforcing (INVOICE_ID, TAXAUTH_ID, ICTAX_CLASS).
• Invoice-related GML objects — the INVOICE_ID column implies a dependency on the process manufacturing invoice header/line structures within the GML schema.

No additional dependent views or APIs are documented in the supplied ETRM metadata; the two foreign keys above constitute the verified relationship set.