Search Results jai_cmn_rg_23d_trxs_uk1




Overview
Explore in AI Chat

Overview

JAI_CMN_RG_23D_TRXS is a transaction-level register table owned by the JA schema, delivered under the Oracle E-Business Suite Asia/Pacific Localizations module. Its documented description is "Quantity register for Trading Organizations." It records the movement of goods — receipts, issues, and adjustments — for organizations operating under the Indian excise and trading localization requirements, capturing both quantity and duty/charge information at the transaction level. It is a 69-column table in the ETRM 12.2.2 schema definition and is marked VALID, so it is an actively maintained object in the JA product lineage.

From a dimensional modeling standpoint, the mined foreign-key profile suggests a satellite-leaning classification. The table's identity is anchored almost entirely by descriptive and transactional attributes tied to parent entities — items, organizations, parties, sites, accounts, and source transactions — rather than by a self-contained hub key or a pure many-to-many resolving link. This is a heuristic suggestion only; the definitive model should follow the operational semantics of the quantity register.

Key Information Stored

The primary key is REGISTER_ID via index JAI_CMN_RG_23D_TRXS_PK, which serves as the surrogate identifier for each register row. A separate unique index, JAI_CMN_RG_23D_TRXS_UK1, spans ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, INVENTORY_ITEM_ID, and SLNO — establishing those columns as the business-key candidate that most naturally defines register uniqueness within an organization and financial year.

Common Use Cases and Queries

Because the user search context was "hz_party_sites," one primary use case is resolving the trading party site for each register row, using SHIP_TO_SITE_ID, BILL_TO_SITE_ID, or VENDOR_SITE_ID:

A representative query joining to party sites follows:

SELECT t.REGISTER_ID, t.ORGANIZATION_ID, t.FIN_YEAR, t.INVENTORY_ITEM_ID,
p.PARTY_NAME, ps.SITE_USE_CODE, t.RECEIPT_DATE, t.QUANTITY_RECEIVED
FROM JA.JAI_CMN_RG_23D_TRXS t, HZ_PARTY_SITES ps, HZ_PARTIES p
WHERE t.SHIP_TO_SITE_ID = ps.PARTY_SITE_ID
AND ps.PARTY_ID = p.PARTY_ID
AND t.ORGANIZATION_ID = :organization_id
AND t.FIN_YEAR = :fin_year;

Related Objects

The most significant related objects, based on the documented FK structure, are:

  • HZ_PARTY_SITES — joined via SHIP_TO_SITE_ID, BILL_TO_SITE_ID, and VENDOR_SITE_ID.
  • HZ_PARTIES — joined via VENDOR_ID and CUSTOMER_ID.
  • JAI_INV_ITM_SETUPS — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item setup validation.
  • JAI_CMN_FIN_YEARS — joined on ORGANIZATION_ID and FIN_YEAR.
  • MTL_MATERIAL_TRANSACTIONS — joined via GOODS_ISSUE_ID.
  • GL_CODE_COMBINATIONS — joined via CHARGE_ACCOUNT_ID.
  • HR_LOCATIONS_ALL — joined via LOCATION_ID.
  • OP_BILL_LAD — joined via BOL_ID.
  • JAI_CMN_MATCH_RECEIPTS and JAI_CMN_MATCH_TAXES — child tables referencing RECEIPT_ID back to this register.