Search Results jai_rgm_manual_trxs




Overview
Explore in AI Chat

Overview

The JAI_RGM_MANUAL_TRXS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the primary repository for manually entered tax transactions, specifically for Service Tax and Value-Added Tax (VAT) regimes. This table is essential in jurisdictions where automated transaction capture is insufficient or where corrections and adjustments to tax records must be manually recorded. Its existence underscores the localization requirements for complex tax reporting and compliance in the Asia/Pacific region, acting as a critical bridge between manual tax accounting entries and the standardized EBS tax and trading community architecture.

Key Information Stored

The table's primary key is the TRANSACTION_NUMBER, which uniquely identifies each manual tax entry. The structure is designed to integrate with the EBS Trading Community Model (TCM). Key foreign key columns link the manual transaction to established master data: REGIME_ORG_ID references the JAI_RGM_PARTIES table to associate the transaction with a specific tax regime and organization; PARTY_ID links to HZ_PARTIES to identify the legal entity or customer/vendor involved; and PARTY_SITE_ID references HZ_PARTY_SITES to pinpoint the specific location or site of the party for accurate tax jurisdiction determination. While the provided metadata does not list all columns, the table logically stores details such as transaction date, tax type (Service Tax/VAT), taxable amount, tax amount, tax rate, period information, and a description of the manual adjustment.

Common Use Cases and Queries

This table is primarily used for compliance reporting and audit trails. A common use case is generating statutory reports for Service Tax or VAT authorities that require a consolidated view of all tax liabilities, including those recorded outside standard transaction flows (e.g., manual journal adjustments for prior period errors). Finance teams may query this table to reconcile manually posted tax entries with general ledger accounts. A typical reporting query would join this table to its related master data tables to enrich transaction records with party names and addresses.

Sample Query Pattern:
SELECT m.transaction_number, m.transaction_date, p.party_name, r.regime_code, m.tax_amount
FROM jai_rgm_manual_trxs m,
    hz_parties p,
    jai_rgm_parties r
WHERE m.party_id = p.party_id
AND m.regime_org_id = r.regime_org_id
AND m.transaction_date BETWEEN :p_start_date AND :p_end_date;

Related Objects

The JAI_RGM_MANUAL_TRXS table has defined foreign key relationships with several master data tables, ensuring referential integrity and enabling data validation. The documented relationships are:

  • JAI_RGM_PARTIES: Linked via JAI_RGM_MANUAL_TRXS.REGIME_ORG_ID = JAI_RGM_PARTIES.REGIME_ORG_ID. This joins the transaction to the specific tax regime definition and organization.
  • HZ_PARTIES: Linked via JAI_RGM_MANUAL_TRXS.PARTY_ID = HZ_PARTIES.PARTY_ID. This joins the transaction to the master trading community record (customer, supplier, or legal entity).
  • HZ_PARTY_SITES: Linked via JAI_RGM_MANUAL_TRXS.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID. This joins the transaction to the specific address or site of the party, which is crucial for determining applicable tax jurisdiction and rates.

As the source table for manual tax data, it is likely referenced by various localization-specific reports, interfaces, and potentially by the JAI_RGM (Regime) application programming interfaces (APIs) for data validation and processing.