Results for “tx_txrp_cls”

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

Overview

TX_TXRP_CLS is a reference table in the Oracle E-Business Suite Process Manufacturing Logistics (GML) schema that stores tax reporting class definitions. Tax reporting classes are used to categorize taxable transactions for statutory reporting and tax authority submissions. In releases 12.1.1 and 12.2.2, this object is owned by GML and carries VALID status in the ETRM data dictionary, indicating it is an active, supported component of the tax reporting infrastructure rather than a deprecated artifact.

The table functions as a controlled vocabulary of reporting classifications. Each row defines one tax reporting class and the descriptive text associated with it. Downstream tax authority master records and tax drivers reference these class codes to group transactions into the categories required by local fiscal authorities. Because the table holds descriptive reference data rather than transactional events, the heuristic Data Vault classification supplied in the metadata identifies it as satellite-leaning. Practically, this means TX_TXRP_CLS behaves as a descriptive companion to the core tax authority entity, and a Data Vault model would most naturally attach it as a satellite or a small reference dimension keyed by the reporting class.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

• TAXRPT_CLASS — the reporting class code. It is the single column of the unique index TX_TXRP_CLS_PK, making it both the primary key and the sole business-key candidate. It is the value propagated to dependent tables.
• TAXRPT_DESC — the human-readable description of the reporting class, used on reports and in LOVs.
• TEXT_CODE — a foreign key to TX_TEXT_HDR, linking the reporting class to a stored text template or message definition.
• TRANS_CNT — a transaction counter column, typically used for concurrency or population tracking.
• DELETE_MARK — soft-delete flag; rows are logically inactivated rather than physically removed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS auditing columns recording insert and update context.

The primary key is a natural business key rather than a generated surrogate; there is no separately documented surrogate identifier. Any integration or extension should therefore treat TAXRPT_CLASS as the stable join key.

Common Use Cases and Queries

Typical usage centers on populating reporting-class LOVs, validating tax authority master setup, and producing statutory extracts. A standard lookup of active classes is:

• SELECT taxrpt_class, taxrpt_desc FROM gml.tx_txrp_cls WHERE delete_mark = 0 ORDER BY taxrpt_class;
• Joining to the tax authority master to list authorities by class:
  SELECT a.taxrpt_class, c.taxrpt_desc, a.* FROM gml.tx_taxa_mst a, gml.tx_txrp_cls c WHERE a.taxrpt_class = c.taxrpt_class AND c.delete_mark = 0;
• Resolving the associated text template:
  SELECT c.taxrpt_class, t.* FROM gml.tx_txrp_cls c, gml.tx_text_hdr t WHERE c.text_code = t.text_code;
• Setup validation, identifying tax authorities whose reporting class has no valid definition or has been soft-deleted.

Because the table is small and slowly changing, it is commonly extracted whole into reporting or data-warehouse layers as a reference dimension.

Related Objects

Two foreign key relationships are documented in the ETRM metadata:

• TX_TEXT_HDR — referenced by TX_TXRP_CLS.TEXT_CODE; supplies the text or message definition attached to a reporting class.
• TX_TAXA_MST — references this table through TX_TAXA_MST.TAXRPT_CLASS; the tax authority master depends on TX_TXRP_CLS for its reporting classification.
• TX_TXRP_CLS_PK — the unique index enforcing uniqueness of TAXRPT_CLASS and driving lookups.

Because the documented relationship set is narrow, TX_TXRP_CLS sits near the edge of the tax reporting sub-model. Its principal dependents are the tax authority master records that consume the class code, while its only outbound dependency is the text header. When modeling or extending the GML tax reporting schema, TX_TXRP_CLS should be treated as a low-volume reference table whose integrity directly governs the validity of tax authority setup and the accuracy of downstream statutory reporting.