Search Results jai_cmn_rg_comp_dtls




Overview
Explore in AI Chat

Overview

The JAI_CMN_RG_COMP_DTLS table is a core data repository within the Oracle E-Business Suite Asia/Pacific Localizations module (Product JA). Its primary function is to maintain granular, component-level balance information for excise registers, specifically RG23A and RG23C records, as mandated by statutory requirements in certain jurisdictions, notably India. This table operates as a detailed subsidiary ledger, tracking the quantity and value of each distinct excise component (e.g., Basic Excise Duty, Additional Duty, Special Additional Duty) associated with inventory items. Its role is critical for ensuring accurate excise accounting, compliance reporting, and the reconciliation of physical stock against registered balances for audit purposes.

Key Information Stored

The table stores transactional and balance details keyed by several identifiers. The primary key is the unique EXCISE_COMP_DTL_ID. Each record is anchored to a specific inventory item (INVENTORY_ITEM_ID) within an organization (ORGANIZATION_ID) and linked to a financial year (FIN_YEAR). The core data includes the REGISTER_ID, which identifies the specific RG23A or RG23C register, and the LOCATION_ID for geographical tracking. The table holds detailed quantities and values for each excise component, typically including fields for opening balance, received quantity, issued quantity, and closing balance. These fields enable the system to maintain a running, auditable trail for every excisable item and component.

Common Use Cases and Queries

The primary use case is generating statutory excise register reports and reconciling book balances with physical stock. Finance and compliance teams query this table to verify component-level liabilities and credits. A common reporting pattern involves joining with item and organization master data to produce register summaries. For example, to check the current balance for a specific item and component, a query might filter on the register, item, organization, and financial year. Troubleshooting often involves tracing discrepancies by comparing transaction summaries in related transaction tables (like JAI_CMN_RG_23AC_II_TRXS) against the aggregated balances stored in this detail table to identify posting errors or missing entries.

Related Objects

JAI_CMN_RG_COMP_DTLS is centrally connected to several key master and transactional tables via foreign key relationships, as documented in the ETRM:

  • JAI_INV_ITM_SETUPS: Joined via INVENTORY_ITEM_ID and ORGANIZATION_ID. This links the balance details to the localized inventory item setup defining excise attributes.
  • JAI_CMN_FIN_YEARS: Joined via ORGANIZATION_ID and FIN_YEAR. This ensures balances are maintained within the correct statutory accounting period.
  • JAI_CMN_RG_23AC_II_TRXS: Joined via REGISTER_ID. This is a critical relationship where individual excise transactions (issues, receipts) post to and update the summarized balances in the detail table.
  • HR_LOCATIONS_ALL: Joined via LOCATION_ID. This provides the physical address or warehouse location associated with the registered balance.

The primary key constraint JAI_CMN_RG_COMP_DTLS_PK ensures the uniqueness of each component detail record.