Search Results jai_cmn_rg_pla_trxs_pk




Overview
Explore in AI Chat

Overview

The JAI_CMN_RG_PLA_TRXS table is a core data repository within the JA (Asia/Pacific Localizations) product of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary function is to store detailed transaction-level information for the PLA (Payment of Levy Account) Register. The PLA Register is a critical component for managing tax-related payments and credits, specifically for statutory levies applicable in certain Asia/Pacific jurisdictions. This table serves as the central transactional ledger for PLA activities, enabling compliance reporting, audit trails, and reconciliation of levy payments against purchases and other eligible transactions.

Key Information Stored

The table's structure is designed to capture the full context of a PLA transaction. Its primary key (JAI_CMN_RG_PLA_TRXS_PK) is the system-generated REGISTER_ID. A unique key (JAI_CMN_RG_PLA_TRXS_UK1) enforces business rule integrity across the ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, and SLNO (serial number) columns. While a full column list is not provided in the excerpt, the foreign key relationships indicate it stores essential identifiers including the INVENTORY_ITEM_ID, FIN_YEAR, CHARGE_ACCOUNT_ID (a GL code combination), VENDOR_ID, VENDOR_SITE_ID, BANK_BRANCH_ID, and ROUNDING_ID. These fields collectively define the "who, what, when, and where" of each PLA transaction—the legal entity, location, financial year, item, supplier, accounting charge account, bank details, and any applied rounding rules.

Common Use Cases and Queries

This table is central to generating statutory PLA register reports required for tax authorities, which summarize levy credits and payments for a given financial year and location. It is also queried for internal reconciliation, such as matching PLA credits against general ledger accounts or verifying vendor payment details. Common SQL patterns involve joining to its related master tables to translate IDs into meaningful names. For example, a query to list PLA transactions for a specific organization and financial year would typically join to HR_LOCATIONS_ALL for the location name, HZ_PARTIES for the vendor name, and GL_CODE_COMBINATIONS for the account segment values.

SELECT pla.register_id,
       pla.slno,
       loc.location_code,
       party.party_name vendor_name,
       cc.concatenated_segments charge_account
  FROM jai_cmn_rg_pla_trxs pla,
       hr_locations_all loc,
       hz_parties party,
       gl_code_combinations cc
 WHERE pla.organization_id = :p_org_id
   AND pla.fin_year = :p_fin_year
   AND pla.location_id = loc.location_id
   AND pla.vendor_id = party.party_id
   AND pla.charge_account_id = cc.code_combination_id;

Related Objects

The table maintains strict referential integrity with numerous master and transactional tables across EBS modules, as documented by its foreign keys:

  • JAI_INV_ITM_SETUPS: Links to item master setup (JOIN ON INVENTORY_ITEM_ID, ORGANIZATION_ID).
  • JAI_CMN_FIN_YEARS: Validates the financial year (JOIN ON ORGANIZATION_ID, FIN_YEAR).
  • GL_CODE_COMBINATIONS: Validates the general ledger charge account (JOIN ON CHARGE_ACCOUNT_ID).
  • HR_LOCATIONS_ALL: Validates the inventory organization location (JOIN ON LOCATION_ID).
  • HZ_PARTIES: Validates the trading partner/vendor (JOIN ON VENDOR_ID).
  • HZ_PARTY_SITES: Validates the specific vendor site (JOIN ON VENDOR_SITE_ID).
  • CE_BANK_ACCT_USES_ALL: Links to the bank account used (JOIN ON BANK_BRANCH_ID).
  • JAI_CMN_RG_ROUND_HDRS: Links to rounding rules (JOIN ON ROUNDING_ID).
  • JAI_CMN_RG_PLA_CMP_DTLS: A child table likely storing component or breakdown details (JOIN ON REGISTER_ID).