Results for “excise_duty_amount”

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

Overview

JAI_CMN_RG_I_TRXS is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). It stores the information required for the RG 1 Register, a statutory quantity register used for excise and regulatory reporting in India. Unlike a value-based ledger, this object acts as a quantity register, capturing manufactured, packed, issued, and balance quantities alongside the corresponding excise duty components for each recorded transaction.

The table is defined with 61 columns and two unique indexes. JAI_CMN_RG_I_TRXS_PK on REGISTER_ID serves as the primary key, while JAI_CMN_RG_I_TRXS_UK1 covering ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, INVENTORY_ITEM_ID, and SLNO enforces the natural business key of the register.

The Data Vault classification inferred from the foreign key structure is that of a link. This is a reasonable modeling suggestion: the table predominantly associates independent business entities — organizations, items, locations, customers, vendors, and accounts — through foreign keys, with the transactional quantities and duty amounts acting as the descriptive payload. Analysts designing a warehouse layer can treat the FK targets as hubs and dimension candidates, and this object as the link that connects them.

Key Information Stored

Among the 61 columns, the following carry the greatest functional weight:

• REGISTER_ID — surrogate primary key; the technical identity of each register line.
• ORGANIZATION_ID, LOCATION_ID, FIN_YEAR, INVENTORY_ITEM_ID, SLNO — the business key combination enforced by UK1. Together they identify a register entry for a specific item, inventory organization, location, fiscal year, and serial number.
• TRANSACTION_DATE, TRANSACTION_TYPE, ISSUE_TYPE — classify and date when the movement or production event occurred.
• MANUFACTURED_QTY, MANUFACTURED_PACKED_QTY, MANUFACTURED_LOOSE_QTY — the quantities produced, segmented by packed and loose form.
• BALANCE_PACKED, BALANCE_LOOSE — the residual register balance carried after the transaction.
• EXCISE_DUTY_AMOUNT, BASIC_ED, ADDITIONAL_ED, OTHER_ED, CESS_AMT, SH_CESS_AMT — the duty and cess amounts applicable to the line.
• CHARGE_ACCOUNT_ID — the GL account charged, linked to GL_CODE_COMBINATIONS.
• VENDOR_ID, CUSTOMER_ID — trading partners referenced through HZ_PARTIES.
• POSTED_FLAG, MASTER_FLAG — control flags governing posting status and master-records handling.

Common Use Cases and Queries

The primary use case is statutory RG 1 reporting, where quantities manufactured, received, issued, and held in balance are extracted for a fiscal year. A second use case is reconciliation of duty liability against GL accounts, and a third is audit verification of item-level movements by location and organization.

A typical reporting pattern retrieves register lines for an organization and fiscal year:

• SELECT register_id, inventory_item_id, transaction_date, transaction_type, manufactured_qty, balance_packed, balance_loose FROM jai_cmn_rg_i_trxs WHERE organization_id = :org AND fin_year = :year ORDER BY slno;
• Joining to gl_code_combinations on charge_account_id produces account-level excise summaries.
• Joining to hz_parties on customer_id or vendor_id supports party-wise movement analysis.

Report writers should filter on posted_flag where only finalized entries are required, and should use the UK1 columns in the predicate to exploit the unique index.

Related Objects

Foreign keys define the principal relationships. The most significant referenced objects are:

• JAI_INV_ITM_SETUPS — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID; supplies item-level localization setup.
• JAI_CMN_FIN_YEARS — joined on ORGANIZATION_ID and FIN_YEAR; defines the fiscal calendar.
• GL_CODE_COMBINATIONS — joined on CHARGE_ACCOUNT_ID for account validation and reporting.
• HR_LOCATIONS_ALL — joined on LOCATION_ID.
• HZ_PARTIES — joined on VENDOR_ID and CUSTOMER_ID.
• HZ_PARTY_SITES — joined on VENDOR_SITE_ID and CUSTOMER_SITE_ID.
• OP_BILL_LAD — joined on BOL_ID, linking register lines to bill-of-lading documentation.

These relationships confirm the table's role as a transactional link connecting item, organization, location, party, and accounting dimensions for regulatory excise register maintenance.