Search Results tx_calc_mst_pk




Overview
Explore in AI Chat

Overview

The TX_CALC_MST table is a master data repository within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. Its primary role is to store and manage tax calculation codes, which are essential reference data for determining applicable tax rules and formulas within the manufacturing and logistics processes. As a master table, it serves as the system of record for valid tax calculation identifiers, ensuring data integrity and consistency across transactional operations that require tax computation. Its existence within the GML schema underscores its specific importance in the tax handling for process manufacturing environments, where material and product taxation can be complex.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a primary key column that uniquely identifies each tax calculation code. The most critical column is TAXCALC_CODE, which serves as the primary key (TX_CALC_MST_PK). This column holds the unique identifier for a specific tax calculation rule or method. While the full column list is not detailed in the excerpt, the presence of a foreign key relationship with the TX_TEXT_HDR table via a TEXT_CODE column strongly suggests the table also stores a reference code for descriptive, translatable text associated with each tax calculation code. This is a common pattern in EBS for storing multilingual descriptions.

Common Use Cases and Queries

The primary use case for TX_CALC_MST is to provide a validated list of tax codes for assignment to business entities and for reference during transaction processing. A common operational query would retrieve the list of active tax calculation codes for setup in a customer master record. For example, when creating or updating a customer in the Order Management (OP_CUST_MST) or Process Manufacturing Order Management (OP_CUST_MST_OPM) tables, a validated list would be sourced from TX_CALC_MST. A typical reporting or validation SQL pattern would involve joining to the text table for descriptions:

  • SELECT tc.taxcalc_code, tl.description FROM gml.tx_calc_mst tc, gml.tx_text_hdr tl WHERE tc.text_code = tl.text_code;

Another critical use case is data integrity validation, ensuring that codes referenced in customer master tables exist in the TX_CALC_MST table via the defined foreign key constraints.

Related Objects

The ETRM documentation explicitly lists several key dependencies. TX_CALC_MST is referenced by foreign key constraints from customer master tables in both the core and OPM schemas, making it central to customer tax setup:

  • OP_CUST_MST and OP_CUST_MST_OPM: These tables store customer information and reference TX_CALC_MST.TAXCALC_CODE to define the default tax calculation method for a customer.
  • TX_TEXT_HDR: This table is referenced by TX_CALC_MST (via TEXT_CODE) to store the translatable descriptive text for the tax calculation codes, following Oracle's standard multilingual architecture.

These relationships position TX_CALC_MST as a foundational reference table that links tax calculation logic to customer data and internationalized descriptions.