Results for “other_closing_balance”

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

Overview

JA.JAI_CMN_RG_PLA_CMP_DTLS is a table within the JA — Asia/Pacific Localizations product family in Oracle E-Business Suite (validated on 12.1.1 and 12.2.2). Its documented description states that it stores detailed balances of each excise component for every PLA record. In the context of the Asia/Pacific excise regime, a PLA (Personal Ledger Account) register records the statutory ledger activity for excisable goods maintained at an organization, location, inventory item, and financial year level. The JAI_CMN_RG_PLA_CMP_DTLS table decomposes the aggregate ledger balance into its individual excise duty components, providing the granular opening, debit, credit, and closing balances required for statutory reporting and reconciliation.

From a Data Vault modeling perspective, the FK structure mined in the metadata (with a single-column primary key on REGISTER_ID and multiple foreign keys pointing to parent entities such as JAI_CMN_RG_PLA_TRXS, JAI_INV_ITM_SETUPS, JAI_CMN_FIN_YEARS, and HR_LOCATIONS_ALL) suggests this table behaves primarily as a link object — a transactional association joining the PLA register transaction to its component-level balance details, rather than a pure hub or satellite. This is a heuristic classification and should be treated as a modeling suggestion.

Key Information Stored

The table contains 25 documented columns. The most significant are the organizational and inventory context columns (ORGANIZATION_ID, LOCATION_ID, INVENTORY_ITEM_ID, FIN_YEAR, REGISTER_ID, SLNO), the component balance columns, and the audit columns.

• REGISTER_ID — the surrogate primary key (JAI_CMN_RG_PLA_CMP_DTLS_PK); links back to the parent PLA transaction/register in JAI_CMN_RG_PLA_TRXS.
• ORGANIZATION_ID, LOCATION_ID, INVENTORY_ITEM_ID, FIN_YEAR, SLNO — the business-key candidate columns (documented as the unique index JAI_CMN_RG_PLA_CMP_DTLS_UK1), collectively identifying the scope of the component balance for a given organization, physical location, inventory item, financial year, and serial line number.
• BASIC_OPENING_BALANCE / ADDITIONAL_OPENING_BALANCE / OTHER_OPENING_BALANCE — opening balances per excise component classification.
• CR_BASIC_ED, CR_ADDITIONAL_ED, CR_OTHER_ED — credit-side excise duty amounts by component (basic, additional, other).
• DR_BASIC_ED, DR_ADDITIONAL_ED, DR_OTHER_ED — debit-side excise duty amounts by component.
• BASIC_CLOSING_BALANCE, ADDITIONAL_CLOSING_BALANCE, OTHER_CLOSING_BALANCE — closing balances per component, derived from the opening balance plus credits less debits.
• TRANSACTION_DATE — effective business date of the component balance entry.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic-locking columns.

The tri-partite component structure (basic / additional / other excise duty) mirrors the Indian excise duty reporting format, where duties are segregated by statute and are reported separately on statutory registers.

Common Use Cases and Queries

Typical reporting scenarios include reconciling component balances to the parent PLA register, producing excise duty utilization reports, and verifying that closing balances equal opening plus credits less debits for each component. A representative query pattern is:

• Retrieve all component balances for a specific item and financial year at a location:
  SELECT register_id, basic_opening_balance, cr_basic_ed, dr_basic_ed, basic_closing_balance FROM ja.jai_cmn_rg_pla_cmp_dtls WHERE organization_id = :org_id AND inventory_item_id = :item_id AND fin_year = :fin_year AND location_id = :loc_id;
• Join to JAI_CMN_RG_PLA_TRXS on REGISTER_ID to obtain the register transaction header details alongside the component balances.
• Reconcile aggregate closing balances against the parent register by summing the three component closing balances per register.
• Utilization analysis: compute DR_BASIC_ED - CR_BASIC_ED per period to determine net excise consumed.

Because the table is scoped by organization, location, item, and financial year, all queries should filter on those dimensions to leverage the unique index and avoid full scans.

Related Objects

The following objects are documented as directly related through FK/PK relationships and are the most significant for dependency analysis and joins:

• JAI_CMN_RG_PLA_TRXS — parent PLA transaction/register; joined on JAI_CMN_RG_PLA_CMP_DTLS.REGISTER_ID = JAI_CMN_RG_PLA_TRXS.REGISTER_ID.
• JAI_INV_ITM_SETUPS — item setup for the localized excise configuration; joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• JAI_CMN_FIN_YEARS — financial year definition; joined on ORGANIZATION_ID and FIN_YEAR.
• HR_LOCATIONS_ALL — physical location (inventory/warehouse) master; joined on LOCATION_ID.

These four parent objects provide the complete contextual anchor for each component balance row and are the primary tables to consider when designing joins, extraction queries, or reconciliation reports against JAI_CMN_RG_PLA_CMP_DTLS.