Results for “status_desc”

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

Overview

TX_TAXA_STS is a reference (lookup) table owned by the GML schema within the Process Manufacturing Logistics module of Oracle E-Business Suite. It stores tax status codes and their associated classification flags, providing the master list of taxability designations that downstream transaction and accounting tables consume. Because it defines valid tax status values rather than recording transactional events, it functions as a controlled vocabulary object: any process that must decide whether a material, invoice line, or cost adjustment is taxable, exempt, or export-classified resolves that decision through the codes held here. The table has 13 documented columns and is marked VALID in the ETRM 12.2.2 physical schema.

Heuristic Data Vault classification: the metadata suggests a hub-leaning classification. The presence of a single-column primary key (TX_TAXA_STS_PK on TAX_STATUS) and the absence of composite natural keys is consistent with a hub pattern — a stable, uniquely identified business concept referenced by multiple satellites and links. Under strict Data Vault modelling, descriptive attributes such as STATUS_DESC and the various indicator flags would be split into a satellite, while the referencing tables below would become links or foreign-key relationships to the hub.

Key Information Stored

The table's structure separates the business key from descriptive classification attributes and standard EBS audit columns:

• TAX_STATUS — the primary key and only documented unique index column (TX_TAXA_STS_PK). This is the business-key candidate and the value carried into child tables.
• STATUS_DESC — the human-readable description of the tax status code, used in list-of-values and reporting displays.
• EXEMPT_IND — indicator flagging whether the status represents an exempt condition.
• TAXABLE_IND — indicator flagging whether the status represents a taxable condition.
• EXPORT_IND — indicator flagging whether the status represents an export classification.
• TEXT_CODE — foreign key to TX_TEXT_HDR; links the status to configurable descriptive text.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS auditing and concurrency columns.
• TRANS_CNT — surrogate transaction counter used for change tracking.
• DELETE_MARK — soft-delete indicator; rows are logically retired rather than physically removed.

The three indicator columns (EXEMPT_IND, TAXABLE_IND, EXPORT_IND) form the substantive business content of each row, while TAX_STATUS serves as the sole documented unique key.

Common Use Cases and Queries

Typical usage centres on validating tax status codes and joining them to the operational tables that reference them. A standard listing query retrieves the active lookup set:

• SELECT TAX_STATUS, STATUS_DESC, TAXABLE_IND, EXEMPT_IND, EXPORT_IND FROM GML.TX_TAXA_STS WHERE DELETE_MARK = 0 ORDER BY TAX_STATUS;
• Resolving invoice charge classifications: SELECT c.INVOICE_CHARGE_ID, c.TAX_STATUS, s.STATUS_DESC FROM GML.OP_INVC_CHG c, GML.TX_TAXA_STS s WHERE c.TAX_STATUS = s.TAX_STATUS;
• Auditing usage/cost adjustments through OP_TXCU_ASC to determine how tax status affects costing outcomes.
• Reporting the distribution of taxable versus exempt designations across the reference set using the indicator columns.
• Identifying orphaned statuses by outer-joining the lookup to its referencing tables to find codes never consumed.

Because there is no public API documented for this lookup, it is generally maintained through the application's setup or concurrent programs, and direct DML should be avoided in favour of the supported maintenance path.

Related Objects

The documented foreign-key relationships define the object's integration points:

• TX_TEXT_HDR — referenced by TX_TAXA_STS.TEXT_CODE; supplies the descriptive text associated with a tax status.
• OP_INVC_CHG — references TX_TAXA_STS.TAX_STATUS; invoice charge lines inherit tax status from this lookup.
• OP_TXCU_ASC — references TX_TAXA_STS.TAX_STATUS; usage/cost adjustment records resolve their tax status here.

These three tables constitute the documented relationship set in the ETRM metadata. No additional views, synonyms, or PL/SQL packages are documented as depending on TX_TAXA_STS within the supplied reference, so integrators should verify runtime dependencies against the live data dictionary before extending the model.