Search Results jai_cmn_rg_23d_trxs




Overview
Explore in AI Chat

Overview

The JAI_CMN_RG_23D_TRXS table is a core transactional data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a quantity register specifically designed for trading organizations. This table is central to the localization's compliance framework, serving as a detailed log to track the movement and status of inventory items for statutory reporting and tax calculation purposes. Its existence and structure are mandated by regional legal requirements, such as those in India, to maintain auditable records of goods transactions for registered dealers under specific tax regulations (like the erstwhile VAT/CST regime, often associated with Form 23D). The table acts as a bridge between standard Oracle Inventory transactions and localized regulatory reporting.

Key Information Stored

The table stores granular details for each register entry, uniquely identified by the system-generated REGISTER_ID (primary key). Its structure enforces a unique combination for a trading organization's records through a unique key on ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, INVENTORY_ITEM_ID, and SLNO (sequence number). Key columns include identifiers for the item (INVENTORY_ITEM_ID), the financial year (FIN_YEAR), and the involved parties—VENDOR_ID, CUSTOMER_ID, and their respective sites (VENDOR_SITE_ID, SHIP_TO_SITE_ID, BILL_TO_SITE_ID). It links to the core inventory transaction (GOODS_ISSUE_ID to MTL_MATERIAL_TRANSACTIONS) and holds accounting references (CHARGE_ACCOUNT_ID). The table's design ensures each entry is tied to validated master data through its extensive foreign key constraints.

Common Use Cases and Queries

The primary use case is generating statutory reports required by local tax authorities, which summarize goods received, issued, and in stock for a given trading organization and financial period. It is also queried for internal audit trails and reconciliation between financial and inventory records. Common reporting SQL patterns involve joining this table with its referenced master data tables. For example, to list all register entries for a specific organization and item in a financial year:

  • SELECT rg.*, mtt.transaction_id, msi.segment1 item_code FROM jai_cmn_rg_23d_trxs rg JOIN mtl_material_transactions mtt ON rg.goods_issue_id = mtt.transaction_id JOIN mtl_system_items_b msi ON rg.inventory_item_id = msi.inventory_item_id AND rg.organization_id = msi.organization_id WHERE rg.organization_id = :p_org_id AND rg.inventory_item_id = :p_item_id AND rg.fin_year = :p_fin_year ORDER BY rg.slno;

Another critical use case is verifying the completeness of the register by ensuring all relevant goods issues from MTL_MATERIAL_TRANSACTIONS have corresponding entries in this table, which is essential for compliance.

Related Objects

JAI_CMN_RG_23D_TRXS has a tightly integrated relationship with numerous core and localization tables. It directly references master data tables like HZ_PARTIES (for customers/vendors), HR_LOCATIONS_ALL, and MTL_MATERIAL_TRANSACTIONS. Its definition is enforced by foreign keys to localization setup tables such as JAI_CMN_FIN_YEARS and JAI_INV_ITM_SETUPS. Crucially, it is referenced by other key localization transactional tables, namely JAI_CMN_MATCH_RECEIPTS and JAI_CMN_MATCH_TAXES, via the RECEIPT_ID, indicating its role as a source for subsequent tax matching and receipt processing. This network of relationships positions it as a foundational table within the JA localization's transactional schema.