Results for “taxloc_from”

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

Overview

GML.TX_TOFR_ASC is a Tax configuration table owned by the Process Manufacturing Logistics (GML) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the pairing of tax locations, defining which ship-from location corresponds to which ship-to location for tax determination purposes. The table functions as a cross-reference registry that validates and constrains the directional flow of tax location combinations used by the ETRM (E-Business Tax) engine during transactional processing.

Under a heuristic Data Vault classification mined from its foreign key structure, this object leans toward a satellite role. It carries descriptive attributes and audit columns attached to a primary business key (TAXLOC_ID), while its foreign keys point outward to reference hubs such as TX_TLOC_CDS and TX_TEXT_HDR. Modelers should treat this as a suggestion rather than a prescriptive design; the table is best understood as a transactional configuration entity with both descriptive and relational characteristics.

Key Information Stored

The table contains 11 documented columns. The most operationally significant are:

• TAXLOC_ID — The surrogate primary key (TX_TOFR_ASC_PK), uniquely identifying each ship-from/ship-to pairing record.
• TAXLOC_FROM — Foreign key to TX_TLOC_CDS; identifies the originating (ship-from) tax location.
• TAXLOC_TO — Foreign key to TX_TLOC_CDS; identifies the destination (ship-to) tax location.
• TEXT_CODE — Foreign key to TX_TEXT_HDR; links the pairing to textual/descriptive metadata used in tax configuration.
• IN_USE — Status flag indicating whether the pairing is active for tax determination.
• DELETE_MARK — Soft-delete indicator, standard in EBS multi-org aware tables; a value of 1 marks the row logically removed.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the record and when.

The unique index TX_TOFR_ASC_U1 on (TAXLOC_TO, TAXLOC_FROM) is the business-key candidate: it enforces that any given ship-from/ship-to direction pair occurs only once, preventing duplicate tax-location combinations. Note the column ordering in the unique index, which matters for index-driven query performance.

Common Use Cases and Queries

Typical scenarios include validating whether a given ship-from/ship-to pairing is legally configured for tax calculation, troubleshooting tax determination failures during order entry or shipping, and reporting on active tax location pairings.

A representative query retrieving all active pairings:

SELECT t.taxloc_id,
       f.taxloc_code  AS from_loc,
       t2.taxloc_code AS to_loc
FROM   gml.tx_tofr_asc t,
       gml.tx_tloc_cds f,
       gml.tx_tloc_cds t2
WHERE  t.taxloc_from = f.taxloc_code
AND    t.taxloc_to   = t2.taxloc_code
AND    t.in_use      = 'Y'
AND    NVL(t.delete_mark,0) = 0;

A lookup by direction:

SELECT taxloc_id, text_code
FROM   gml.tx_tofr_asc
WHERE  taxloc_from = :p_from
AND    taxloc_to   = :p_to
AND    NVL(delete_mark,0) = 0;

Reporting use cases include auditing which location pairs reference a particular TEXT_CODE (join to TX_TEXT_HDR), and identifying stale configurations via LAST_UPDATE_DATE.

Related Objects

The following objects are most significant to TX_TOFR_ASC:

• TX_TLOC_CDS — Referenced twice, via TAXLOC_FROM and TAXLOC_TO; provides the tax location codes.
• TX_TEXT_HDR — Referenced via TEXT_CODE; supplies textual metadata for the pairing.
• TX_TLOC_ASC — A child table referencing TX_TOFR_ASC via TAXLOC_ID; holds additional tax location association records.

Because TX_TLOC_ASC depends on the parent record, deletion or logical removal of a TX_TOFR_ASC row must respect that child relationship. Together these objects form the core tax location configuration cluster within GML/ETRM.