Search Results jl_br_ar_tx_locn_all

Overview

The table JL_BR_AR_TX_LOCN_ALL is a historical data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the JL (Latin America Localizations) product. Its primary purpose was to store Brazilian tax location information, which was used to associate tax categories with specific shipping locations for transactional tax determination. As explicitly noted in the official documentation, this table is "no longer used" in the current system. Its presence in the database is typically for backward compatibility or data archival purposes, and it is not part of active transactional processing in standard implementations. The table is owner by the JL schema and is designed to be multi-org aware, as indicated by the inclusion of the ORG_ID column in its foreign key relationships.

Key Information Stored

The table's structure centers on defining a relationship between a shipping location and a tax category, with a validity period. The primary key is a composite of four columns: SHIP_FROM_CODE, SHIP_TO_SEGMENT_ID, TAX_CATEGORY_ID, and END_DATE_ACTIVE. This design suggests it was used to maintain a history of tax location assignments. Key columns include SHIP_FROM_CODE, which likely identifies a warehouse or inventory organization; SHIP_TO_SEGMENT_ID, a foreign key to a location value; and TAX_CATEGORY_ID, a foreign key to a defined tax category. The END_DATE_ACTIVE column indicates the table supported date-effective record tracking, allowing tax rules to be valid for specific timeframes.

Common Use Cases and Queries

Given its deprecated status, direct operational use cases are obsolete. Its primary contemporary relevance is for historical data analysis, auditing, or data migration validation. A consultant might query it to understand legacy tax configurations that were in effect during a specific period before a system upgrade or localization change. A sample analytical query would join to its related tables to reconstruct old tax rules:

SELECT locn.SHIP_FROM_CODE, locn.SHIP_TO_SEGMENT_ID, cat.TAX_CATEGORY_CODE, locn.END_DATE_ACTIVE
FROM JL.JL_BR_AR_TX_LOCN_ALL locn
JOIN JL.JL_BR_AR_TX_CATEG_ALL cat ON locn.TAX_CATEGORY_ID = cat.TAX_CATEGORY_ID
WHERE locn.ORG_ID = :org_id
AND :transaction_date BETWEEN locn.START_DATE_ACTIVE AND NVL(locn.END_DATE_ACTIVE, SYSDATE)
ORDER BY locn.END_DATE_ACTIVE DESC;

Development or upgrade scripts may also reference this table to check for the existence of legacy data before truncating or archiving it.

Related Objects

Based on the documented foreign key relationships, JL_BR_AR_TX_LOCN_ALL is integrally linked to two other tables:

• AR_LOCATION_VALUES_OLD (via JL_BR_AR_TX_LOCN_ALL.SHIP_TO_SEGMENT_ID): This relationship ties the tax location rule to a specific customer or transactional location defined in the Receivables module. The "_OLD" suffix in the table name further underscores the historical nature of this entire data model.
• JL_BR_AR_TX_CATEG_ALL (via JL_BR_AR_TX_LOCN_ALL.TAX_CATEGORY_ID): This is the master table for Brazilian tax categories. The location table references it to apply the correct tax category based on the ship-from and ship-to context.

The table's primary key (JL_BR_AR_TX_LOCN_ALL_PK) ensures uniqueness of the location-tax category combination over time. No other objects are documented as having foreign keys referencing this table, consistent with its deprecated state.