Results for “base_amount”

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

Overview

TX_TAXA_DTL is a table in the GML (Process Manufacturing Logistics) schema of Oracle E-Business Suite, implemented in both 12.1.1 and 12.2.2. Its documented purpose is to store tax rates for a tax authority, defined at the granularity of an item and/or a charge class. In practical terms, it functions as the rate-detail layer beneath the tax authority header, holding the effective-dated rates, thresholds, and classification assignments that determine how tax is calculated against inventory charges and invoiced amounts.

The table's role in EBS is to connect three master concepts: a tax authority (via TAXAUTH_ID), input or charge tax classifications (via ICTAX_CLASS and CHGTAX_CLASS), and a text or note reference (via TEXT_CODE). Downstream, it is consumed by OP_INVC_CHG, the invoice charge table, which carries TAXRATE_ID as a foreign key, indicating that the rate records defined here are resolved during invoice charge processing.

Under a Data Vault modeling heuristic derived from the documented foreign key structure, TX_TAXA_DTL is satellite-leaning. That classification is a modeling suggestion rather than a physical property: the table is richly attributed with rates, amounts, and dates that describe changing state, while its business key is anchored in a referenced parent. It is not presented as a hub, since it does not stand alone as a core business key registry.

Key Information Stored

The table is documented with 20 columns. The most significant include:

• TAXRATE_ID — the surrogate primary key, enforced by index TX_TAXA_DTL_PK. This is the value referenced by dependent invoice charge rows.
• TAXAUTH_ID — foreign key to TX_TAXA_MST, identifying the tax authority that owns the rate.
• EFFECTIVE_DATE and END_DATE — the effective dating window during which the rate applies.
• ICTAX_CLASS and CHGTAX_CLASS — tax classifications for item and charge respectively, referencing IC_TAXN_CLS and OP_CHRG_CLS.
• BASE_RATE and BASE_AMOUNT — the base percentage rate and the base amount to which it applies.
• FLATTAX_AMOUNT — a fixed tax amount where flat taxation applies.
• MAXTAX_AMOUNT and EXCESS_RATE — the cap on tax and the rate applied to amounts exceeding the cap.
• TAX_CATEGORY_ID — a categorization reference for the rate record.
• TEXT_CODE — foreign key to TX_TEXT_HDR, linking explanatory text.
• TRANS_CNT and DELETE_MARK — the transaction count used for concurrency control and the soft-delete indicator.

The surrogate key is TAXRATE_ID. The documented business-key candidate is the unique index TX_TAXA_DTL_U1, spanning TAXAUTH_ID, EFFECTIVE_DATE, ICTAX_CLASS, and CHGTAX_CLASS. This confirms that a tax authority may hold only one active rate definition per effective date, item tax class, and charge tax class combination. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

Typical scenarios center on rate resolution and audit. A frequent query retrieves the rate applicable to a given authority and classification pair on a specific date, filtering between EFFECTIVE_DATE and END_DATE and using DELETE_MARK to exclude retired rows:

• Point-in-time rate lookup by TAXAUTH_ID, ICTAX_CLASS, and CHGTAX_CLASS.
• Rate history reporting to reconstruct which rate applied to a historical invoice charge.
• Validation of overlapping effective-date ranges within a tax authority, exploiting the TX_TAXA_DTL_U1 business key.
• Reconciliation of OP_INVC_CHG records back to their governing rate via TAXRATE_ID.
• Reporting on capped taxation using MAXTAX_AMOUNT and EXCESS_RATE for high-value invoice analysis.

Related Objects

The documented foreign key relationships establish the following dependencies:

• TX_TAXA_MST — parent authority table, joined on TAXAUTH_ID.
• IC_TAXN_CLS — item tax classification, joined on ICTAX_CLASS.
• OP_CHRG_CLS — charge classification, joined on CHGTAX_CLASS.
• TX_TEXT_HDR — text header, joined on TEXT_CODE.
• OP_INVC_CHG — invoice charge table referencing this table through TAXRATE_ID.

Together these relationships place TX_TAXA_DTL at the intersection of tax authority setup, classification master data, and invoice charge processing within Process Manufacturing Logistics.