Results for “taxloc_code”

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

Overview

TX_TLOC_CDS is a Process Manufacturing Logistics (GML) master/reference table in Oracle E-Business Suite that stores Tax Location Codes. It resides in the GML schema and carries a status of VALID in both 12.1.1 and 12.2.2. The table functions as the central definition point for tax jurisdictions or locations used by ordering, warehousing, customer, and organization entities across the OPM/GML product family. Its TAXLOC_CODE is reused as a foreign key by many downstream tables, making it a de facto master reference for tax determination.

From a Data Vault modeling perspective, the heuristic classification is hub-leaning. The single-column unique index TX_TLOC_CDS_PK on TAXLOC_CODE indicates a stable business key, and the table primarily acts as a hub of tax location identities. Descriptive and audit attributes (TAXLOC_DESC, CREATION_DATE, LAST_UPDATE_DATE, etc.) behave like satellite attributes, but they are co-located in the same physical table.

Key Information Stored

• TAXLOC_CODE — the business key and the column that constitutes the primary key TX_TLOC_CDS_PK. It is the value referenced by all downstream foreign keys.
• TAXLOC_DESC — descriptive name/text of the tax location, used in reports and lookups.
• TEXT_CODE — foreign key to TX_TEXT_HDR, linking the tax location to a text/comment header record.
• TRANS_CNT — transaction counter, typically used for optimistic locking or change tracking in OPM tables.
• DELETE_MARK — soft-delete flag indicating logical removal without physical deletion.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit who/when columns.

Note that while TX_TLOC_CDS_PK is the surrogate/unique index, TAXLOC_CODE itself is the documented unique business-key candidate. No separate numeric surrogate column is documented; the business key and unique index coincide.

Common Use Cases and Queries

Typical scenarios include validating tax location codes during order entry, resolving a tax location for warehouse or customer masters, and reporting tax location coverage across organizations. A frequent pattern is joining the hub to its referencing entity tables:

• Resolve a warehouse's tax location: SELECT t.TAXLOC_CODE, t.TAXLOC_DESC FROM GML.TX_TLOC_CDS t JOIN GML.IC_WHSE_MST w ON w.TAXLOC_CODE = t.TAXLOC_CODE;
• Find customers assigned to a given tax location: SELECT c.* FROM GML.OP_CUST_MST c WHERE c.TAXLOC_CODE = :taxloc_code;
• Identify tax transfer rules referencing a location: SELECT * FROM GML.TX_TOFR_ASC WHERE TAXLOC_FROM = :taxloc OR TAXLOC_TO = :taxloc;
• List organizations bound to a tax location: SELECT * FROM GML.SY_ORGN_MST WHERE TAXLOC_CODE = :taxloc_code;
• Detect only active codes: filter on DELETE_MARK IS NULL OR DELETE_MARK = 0.

Related Objects

• TX_TEXT_HDR — referenced by TX_TLOC_CDS.TEXT_CODE; supplies descriptive text.
• IC_WHSE_MST — warehouse master referencing TX_TLOC_CDS.TAXLOC_CODE.
• OP_CUST_MST — customer master referencing TAXLOC_CODE.
• OP_CUST_MST_OPM — OPM variant of customer master referencing TAXLOC_CODE.
• SY_ORGN_MST and SY_ORGN_MST_B — organization masters referencing TAXLOC_CODE.
• TX_TOFR_ASC — tax transfer association table referencing TAXLOC_FROM and TAXLOC_TO, both pointing to TX_TLOC_CDS.

These relationships confirm TX_TLOC_CDS as a shared tax location hub serving warehousing, customer, and organization domains within Process Manufacturing Logistics.