Search Results jl_br_ar_tx_exc_itm_all

Overview

The table JL_BR_AR_TX_EXC_ITM_ALL is a legacy data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically designed for the JL (Latin America Localizations) product module. Its primary purpose was to store configuration data for Brazilian tax exceptions defined at the item level. This table enabled the association of specific inventory items with tax category exemptions based on defined shipping locations (ship-from and ship-to). However, as explicitly noted in the official ETRM documentation, this table is flagged as "no longer used." This status indicates it is a deprecated artifact from a previous localization implementation, likely superseded by a newer tax engine or data model. Its presence in the schema is for historical data integrity, and it should not be referenced for new development or transactional processing in current implementations.

Key Information Stored

The table's structure centers on defining a unique combination of attributes to identify a specific tax exemption rule. Its composite primary key highlights the critical dimensions of the data: the shipping parties, the item, the applicable tax category, and the rule's active period. The key columns include SHIP_FROM_CODE and SHIP_TO_SEGMENT_ID, which define the geographic or legal jurisdictions for the transaction. The INVENTORY_ITEM_ID and ORGANIZATION_ID pair uniquely identifies the specific item from the inventory master. The TAX_CATEGORY_ID references the type of tax being exempted. Finally, the END_DATE_ACTIVE column, part of the primary key, facilitates the management of rule validity, allowing for time-bound exemptions. The inclusion of ORG_ID suggests the table supports multi-organization data access (MOAC) through the _ALL suffix.

Common Use Cases and Queries

Given its deprecated status, there are no active use cases for this table in standard Oracle EBS operations. Its sole contemporary use would be for historical data analysis or during complex data migration and cleanup projects. For instance, a query might be executed to identify any remaining data that needs to be migrated to a successor system or to validate that the table is indeed empty in a production environment. A sample diagnostic query to check for any residual records would be:

• SELECT COUNT(*), org_id FROM jl_br_ar_tx_exc_itm_all GROUP BY org_id;

Technical consultants or DBAs might also query the table's foreign key relationships to understand legacy dependencies before considering its removal from the schema. No new reporting or integration should be built using this object.

Related Objects

The ETRM documentation specifies clear foreign key relationships from JL_BR_AR_TX_EXC_ITM_ALL to other core tables, illustrating its former integration points. These relationships are crucial for understanding its historical context and for performing any data cleanup.

• AR_LOCATION_VALUES_OLD: The SHIP_TO_SEGMENT_ID column references this table, linking the exemption to a customer's shipping location definition in the old Receivables location model.
• MTL_SYSTEM_ITEMS_B: The INVENTORY_ITEM_ID and ORGANIZATION_ID columns jointly reference the inventory items table, tying the exemption to a specific product.
• JL_BR_AR_TX_CATEG_ALL: The TAX_CATEGORY_ID column references this table, which defines the master list of Brazilian tax categories available within the localization.

The primary key constraint, JL_BR_AR_TX_EXC_ITM_ALL_PK, enforces uniqueness on the combination of all key columns. No relationships where other tables hold foreign keys referencing this table are documented, reinforcing its obsolete nature.