Results for “jai_cmn_rg_comp_dtls”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JAI_CMN_RG_COMP_DTLS is a transactional detail table owned by the JA schema and delivered as part of the Asia/Pacific Localizations (JA) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the detailed balances of each excise component for every RG23A/C record. In the Indian excise regime, RG23A and RG23C registers track duty-paid balances for inputs and capital goods respectively, and each register entry can be decomposed into multiple excise components such as Basic Excise Duty, Additional Excise Duty, and Other Excise Duty. This table preserves opening, debit, credit, and closing balances for each component, for each inventory item, organization, and financial year.

From a Data Vault modeling perspective (a heuristic classification mined from its foreign key structure), this object is best treated as a link table: it associates inventory items, organizations, locations, financial years, and RG23A/C register transactions into a single intersection carrying its own descriptive measures. The component balances behave as satellite attributes of that link, since they change over time and are stamped with creation and update audit columns.

Key Information Stored

The table is keyed by the surrogate primary key EXCISE_COMP_DTL_ID (unique index JAI_CMN_RG_COMP_DTLS_PK). No separate business-key unique index is documented; the business identity is effectively the combination of ORGANIZATION_ID, INVENTORY_ITEM_ID, FIN_YEAR, REGISTER_ID, and SLNO, which form the foreign-key grain of the record.

• ORGANIZATION_ID, INVENTORY_ITEM_ID, LOCATION_ID — identify the owning inventory organization, item, and physical location for the component balance.
• FIN_YEAR, REGISTER_ID, REGISTER_TYPE, SLNO — the financial year, the parent RG23A/C register reference, the register classification, and the serial sequence of the entry.
• BASIC_OPENING_BALANCE, ADDITIONAL_OPENING_BALANCE, OTHER_OPENING_BALANCE — carried-forward opening balances per excise component.
• CR_BASIC_ED, CR_ADDITIONAL_ED, CR_OTHER_ED — credit (utilisation) amounts posted during the period per component.
• DR_BASIC_ED, DR_ADDITIONAL_ED, DR_OTHER_ED — debit (accrual) amounts posted during the period per component.
• BASIC_CLOSING_BALANCE, ADDITIONAL_CLOSING_BALANCE, OTHER_CLOSING_BALANCE — resulting closing balances per component.
• TRANSACTION_DATE — the effective date of the component movement.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic-locking columns.

Common Use Cases and Queries

Typical reporting centers on per-item, per-year excise component reconciliation. A representative query retrieves closing balances for a financial year and organization:

• SELECT inventory_item_id, register_id, register_type, basic_closing_balance, additional_closing_balance, other_closing_balance FROM ja.jai_cmn_rg_comp_dtls WHERE organization_id = :org_id AND fin_year = :fin_year;
• Reconciling RG23A/C closing balances against the parent register transaction rows joined on REGISTER_ID.
• Audit verification that closing balance equals opening balance plus debits minus credits for each component.
• Feeding excise return reports and statutory registers by aggregating components per item and period.

Related Objects

The documented foreign keys anchor this table to the following significant objects:

• JAI_CMN_RG_23AC_II_TRXS — joined on REGISTER_ID; the parent RG23A/C transaction record.
• JAI_INV_ITM_SETUPS — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; item-level excise setup.
• JAI_CMN_FIN_YEARS — joined on ORGANIZATION_ID and FIN_YEAR; defines the financial period.
• HR_LOCATIONS_ALL — joined on LOCATION_ID; supplies the location for the register entry.