Results for “exempt_desc”

8 results




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

Overview

TX_TXRE_CDS is a reference (setup) table in the Oracle EBS GML — Process Manufacturing Logistics product family. It stores Tax Exemption Reason Codes, providing the controlled vocabulary that qualifies why a given transaction, customer, or shipment is exempt from tax. In the EBS tax determination flow, the reason code is a descriptive classification attached to the exemption logic rather than the tax calculation itself; it is consumed by tax reporting, exemption certificate validation, and audit-oriented inquiries.

From the documented relationship data, the table carries a heuristic Data Vault classification of satellite-leaning. This reflects the fact that TX_TXRE_CDS depends on a parent for descriptive context (via the TEXT_CODE foreign key to TX_TEXT_HDR) while itself holding descriptive attributes and audit/ETL bookkeeping columns. In Data Vault terms this is best modeled as a satellite attached to a parent hub/link, not as an independent hub. The classification is a modeling suggestion, not a mandated physical design.

Key Information Stored

The table has 10 documented columns in the ETRM 12.2.2 physical schema, owned by GML. The most significant are:

  • EXEMPT_REASCODE — the single-column primary key (TX_TXRE_CDS_PK) and the business-key candidate for the exemption reason. This is the value referenced throughout tax exemption logic.
  • EXEMPT_DESC — the human-readable description of the exemption reason, used in lookups, LOVs, and reporting labels.
  • TEXT_CODE — foreign key to TX_TEXT_HDR. This links the reason code to its extended text/notes record, so long-form explanation or legal language is stored centrally rather than duplicated per code.
  • TRANS_CNT — a transaction counter column, typically used to track or sequence activity associated with the exemption reason code.
  • DELETE_MARK — soft-delete indicator; rows are logically deactivated rather than physically removed, preserving referential history.
  • CREATION_DATE, CREATED_BY — audit columns recording when and by whom the reason code was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the login session responsible for it.

EXEMPT_REASCODE is the surrogate/primary key; no separate multi-column unique index beyond TX_TXRE_CDS_PK is documented, so EXEMPT_REASCODE also serves as the business-key candidate.

Common Use Cases and Queries

Typical scenarios include populating exemption reason LOVs, reconciling exemption certificates to transactional data, and audit reporting on which reason codes are active. Because DELETE_MARK is present, all queries should filter on it.

  • Active reason codes for a lookup:
    SELECT EXEMPT_REASCODE, EXEMPT_DESC FROM GML.TX_TXRE_CDS WHERE DELETE_MARK = 'N';
  • Reason code with its linked text notes:
    SELECT r.EXEMPT_REASCODE, r.EXEMPT_DESC, h.* FROM GML.TX_TXRE_CDS r LEFT JOIN GML.TX_TEXT_HDR h ON r.TEXT_CODE = h.TEXT_CODE;
  • Audit / change tracking by user:
    SELECT EXEMPT_REASCODE, EXEMPT_DESC, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GML.TX_TXRE_CDS ORDER BY LAST_UPDATE_DATE DESC;

Reporting uses include exemption-reason frequency analysis (via TRANS_CNT), setup completeness checks, and data-quality reviews for codes lacking TEXT_CODE or EXEMPT_DESC.

Related Objects

  • TX_TEXT_HDR — the parent of the only documented foreign key: TX_TXRE_CDS.TEXT_CODE → TX_TEXT_HDR.TEXT_CODE. Join here to retrieve extended descriptions and notes.
  • TX_TXRE_CDS_PK — the primary key constraint/index on EXEMPT_REASCODE, used for uniqueness enforcement and lookups.
  • Tax exemption and transaction tables (within the TX/GML tax model) that reference EXEMPT_REASCODE to classify exempt lines — these depend on TX_TXRE_CDS as a validation source.
  • Tax setup and reporting views in the GML/tax schema that join reason codes to tax headers for exemption reporting.
  • Standard EBS who-column audit trails (FND_USER via CREATED_BY/LAST_UPDATED_BY) for user attribution.