Results for “cr_basic_ed”

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

Overview

The JAI_CMN_RG_23AC_II_TRXS table is a core transactional data object within the JA – Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores RG23A and RG23C Part II details, commonly referred to as the Amount Register, which records the monetary implications of excise movements for goods held in a manufacturing or trading location under the Indian excise regime. The table resides in the JA schema and is classified as VALID in the ETRM inventory. Its primary purpose is to capture debit and credit amounts for basic excise duty, additional excise duty, additional CVD, and other tax components, cross-referenced to the Part I quantity register. Under a heuristic Data Vault classification, the table is satellite-leaning: it is dense with descriptive and measure attributes, is keyed by a surrogate primary key, and is surrounded by foreign key relationships to configuration, party, accounting, and balance hubs.

Key Information Stored

The table is uniquely identified by the surrogate primary key REGISTER_ID, enforced by JAI_CMN_RG_23AC_II_TRXS_PK. This column is a system-generated identifier and serves as the technical unique index; it is not a natural business key of the underlying excise transaction.

• REGISTER_ID_PART_I – links the amount entry to its originating Part I quantity transaction in JAI_CMN_RG_23AC_I_TRXS.
• FIN_YEAR, SLNO, RANGE_NO, DIVISION_NO – statutory financial year, serial number, range, and division identifiers printed on the RG23A/C register.
• INVENTORY_ITEM_ID, ORGANIZATION_ID – item and inventory organization to which the amount transaction belongs.
• CR_BASIC_ED, CR_ADDITIONAL_ED, CR_OTHER_ED, CR_ADDITIONAL_CVD – credit-side excise duty and CVD amounts.
• DR_BASIC_ED, DR_ADDITIONAL_ED, DR_OTHER_ED, DR_ADDITIONAL_CVD – debit-side duty amounts.
• ADDITIONAL_CVD_AMT, OTHER_TAX_CREDIT, OTHER_TAX_DEBIT – additional tax and CVD measures.
• OPENING_BALANCE, CLOSING_BALANCE – running register balances at the start and end of each transaction.
• EXCISE_INVOICE_NO, EXCISE_INVOICE_DATE, REGISTER_TYPE, TRANSACTION_DATE – statutory document references and register category.
• VENDOR_ID, CUSTOMER_ID, CHARGE_ACCOUNT_ID – party and GL accounting dimensions.
• POSTED_FLAG, MASTER_FLAG – subledger posting and master-record indicators.

Common Use Cases and Queries

Typical reporting uses include reconstructing the excise amount register for audit, reconciling open and closing balances by financial year, and tracing a Part II amount back to its Part I quantity movement. A common query joins the amount register to the quantity register on REGISTER_ID_PART_I to reconcile quantity and value. Balance reconciliation queries aggregate CR_* and DR_* columns grouped by ORGANIZATION_ID, FIN_YEAR, and REGISTER_TYPE. Utilization reports filter on POSTED_FLAG and MASTER_FLAG to separate posted entries from provisional ones. Exceptions queries compare OPENING_BALANCE to the prior period's CLOSING_BALANCE and highlight mismatches.

Related Objects

• JAI_CMN_RG_23AC_I_TRXS – joins on REGISTER_ID_PART_I / REGISTER_ID_PART_II; the Part I quantity counterpart.
• JAI_CMN_RG_PERIOD_BALS – via PERIOD_BALANCE_ID; period balance snapshots.
• JAI_CMN_RG_ROUND_HDRS – via ROUNDING_ID; rounding header linkage.
• JAI_INV_ITM_SETUPS – via INVENTORY_ITEM_ID and ORGANIZATION_ID; item/organization excise setup.
• GL_CODE_COMBINATIONS – via CHARGE_ACCOUNT_ID; GL charge account.
• HZ_PARTIES / HZ_PARTY_SITES – via VENDOR_ID, CUSTOMER_ID, CUSTOMER_SITE_ID, VENDOR_SITE_ID.
• JAI_CMN_FIN_YEARS – via ORGANIZATION_ID and FIN_YEAR; financial year definition.
• JAI_PA_DRAFT_INVOICES – references this table through EXCISE_REGISTER_ID.