Search Results zx_ptnr_location_info_gt_pk




Overview

The ZX_PTNR_LOCATION_INFO_GT table is a global temporary table within the Oracle E-Business Tax (ZX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. Its primary role is to act as a transient data repository during the processing of tax calculations. Specifically, it stores a flattened, or denormalized, representation of location information for business partners (e.g., customers, suppliers) involved in a transaction. This temporary structure is designed for high-performance reference and lookup by the E-Business Tax engine, enabling efficient determination of applicable tax jurisdictions, rates, and rules based on the partner's geographic details. As a global temporary table, its data is session-specific and automatically purged at the end of the transaction or session, ensuring data isolation and manageability.

Key Information Stored

The table's structure is centered around linking transaction details to a partner's location hierarchy. According to the provided metadata, the primary key consists of EVENT_CLASS_MAPPING_ID, TRX_ID, TRX_LINE_ID, and TRX_LEVEL_TYPE. This composite key uniquely identifies temporary records for a specific tax event and transaction line. While the full column list is not detailed in the excerpt, typical data stored in such a table would include identifiers for the partner site, along with flattened attributes from the location hierarchy such as country, state, county, city, and postal code. The TRX_LEVEL_TYPE column indicates whether the location data is associated with a header-level or line-level transaction context, which is critical for accurate tax determination.

Common Use Cases and Queries

This table is predominantly used internally by the E-Business Tax engine and is not typically queried directly for reporting or manual updates. Its primary use case is during the real-time tax calculation process for transactions like invoices, purchase orders, or receipts. A sample query to inspect session-specific data during debugging might follow this pattern:

  • SELECT event_class_mapping_id, trx_id, trx_line_id, trx_level_type, country, state_province FROM zx_ptnr_location_info_gt WHERE trx_id = :p_trx_id ORDER BY trx_line_id;

This table facilitates scenarios where the tax engine needs to quickly evaluate multiple location-based tax rules without performing complex, multi-table joins on the transactional location tables for every calculation, thereby optimizing performance.

Related Objects

The ZX_PTNR_LOCATION_INFO_GT table is intrinsically linked to the core E-Business Tax processing framework. It is populated by tax determination logic, likely within packages such as ZX_API_PUB or ZX_TAX_EVENT_PUB, and is referenced by internal tax calculation routines. Its data originates from permanent tables storing partner and location information, including:

  • ZX_PARTY_TAX_PROFILE: Stores tax registration details for legal entities and business partners.
  • HZ_LOCATIONS and HZ_PARTY_SITES: Tables from the Trading Community Architecture (TCA) that store detailed address and location data for parties.
  • ZX_LINES_DET_FACTORS: A key table that stores tax determinants and factors, which may consume the flattened location data for rule evaluation.

The primary key constraint ZX_PTNR_LOCATION_INFO_GT_PK enforces data integrity for the temporary records within a session.