Results for “taxauth_id”

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

Overview

OP_TXCU_ASC is a transactional master-level table owned by the GML schema (Process Manufacturing Logistics) in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores customer tax exemption information, capturing the relationship between a customer and the tax authority that has granted an exemption, together with the exemption certificate number, status, and validity period. In OPM (Oracle Process Manufacturing) tax processing, this table acts as the authoritative source consulted when orders and invoices are evaluated to determine whether tax should be charged to a given customer.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies OP_TXCU_ASC as a link table. It resolves relationships between several independent business entities — customers, tax authorities, tax statuses, and text headers — rather than acting as a standalone hub or a descriptive satellite. A dimensional model would likely treat it as a bridge or relationship table between the customer dimension and the tax authority dimension.

Key Information Stored

The table is documented with 17 columns. The most significant are:

• CUSTTAX_ID — surrogate primary key, enforced by the OP_TXCU_ASC_PK constraint; uniquely identifies each exemption record.
• CUST_ID — foreign key to OP_CUST_MST identifying the exempt customer; part of the unique index OP_TXCU_ASC_U1.
• TAXAUTH_ID — foreign key to TX_TAXA_MST identifying the tax authority granting the exemption; part of OP_TXCU_ASC_U1.
• EXEMPTCERT_NO — the customer's exemption certificate number; part of OP_TXCU_ASC_U1 and therefore a business-key candidate alongside CUST_ID and TAXAUTH_ID.
• TAX_STATUS — foreign key to TX_TAXA_STS indicating the exemption status code.
• TEXT_CODE — foreign key to OP_TEXT_HDR linking to descriptive text.
• EXEMPT_REASCODE — reason code explaining the exemption.
• EXEMPTDATE_EXPIRE — date on which the exemption certificate expires.
• OPM_CUST_ID — alternate customer identifier used within OPM processes.
• CO_CODE — operating company or organization code.
• TRANS_CNT and DELETE_MARK — concurrency/version counter and soft-delete flag respectively.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS who/audit columns.

The distinction between the surrogate primary key (CUSTTAX_ID) and the unique business key (CUST_ID + TAXAUTH_ID + EXEMPTCERT_NO) is important for de-duplication and integration with external tax engines.

Common Use Cases and Queries

Typical uses include validating exemption certificates at order entry, producing expiry reports, and reconciling tax exemption coverage against the tax authority master. A representative query joining the customer and tax authority is:

• SELECT a.CUST_ID, a.EXEMPTCERT_NO, a.EXEMPTDATE_EXPIRE FROM OP_TXCU_ASC a WHERE a.DELETE_MARK = 0 AND a.EXEMPTDATE_EXPIRE >= SYSDATE;
• Join to OP_CUST_MST for customer names, and to TX_TAXA_MST for the authority description.
• Expiry monitoring by filtering on EXEMPTDATE_EXPIRE for upcoming renewals.
• Status analysis by grouping on TAX_STATUS joined to TX_TAXA_STS.

Related Objects

• OP_CUST_MST — joined on OP_TXCU_ASC.CUST_ID; supplies customer master data.
• TX_TAXA_MST — joined on TAXAUTH_ID; defines the tax authority.
• TX_TAXA_STS — joined on TAX_STATUS; defines valid exemption statuses.
• OP_TEXT_HDR — joined on TEXT_CODE; provides supporting text.
• OPM order entry and billing processes, which consume this table during tax determination.