Results for “reverse_charge_flag”

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

Overview

JAI_RGM_BALANCE_T is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores debit and credit balances for every organization and location, segmented by tax type. The table supports India localization tax reporting requirements, including excise, VAT, service tax, and related regime-based tax processing governed by the JAI_RGM_DEFINITIONS setup.

From a Data Vault modeling perspective, this object is heuristically classified as a link table. Its structure joins multiple business entities — regime, organization, location, and concurrent program context — while also carrying measurable transactional facts such as debit and credit amounts. This dual nature (relationship plus measure) is typical of link-satellite hybrids in the localization tax domain.

Key Information Stored

The table contains 23 documented columns. The most operationally significant are:

• REGIME_ID — Foreign key to JAI_RGM_DEFINITIONS; identifies the tax regime under which the balance is recorded.
• PARTY_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS; the organization or business unit whose balance is tracked.
• PARTY_TYPE — Distinguishes the party category associated with the balance record.
• LOCATION_ID — Foreign key to HR_LOCATIONS_ALL; the physical location for which the balance applies.
• TAX_TYPE — The specific tax classification (for example, excise or VAT) driving the balance.
• DEBIT_AMT and CREDIT_AMT — The core financial measures representing debit and credit balances.
• PLA_BALANCE — The balance maintained under the PLA (Personal Ledger Account) mechanism used in Indian excise accounting.
• CREDIT_UTILIZED — Tracks the portion of available credit that has been consumed.
• REVERSE_CHARGE_FLAG — Indicates whether the transaction falls under reverse charge provisions.
• SERVICE_TYPE_CODE — Categorizes the service type for service tax reporting.
• BALANCE_DATE — The accounting date to which the balance pertains.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_LOGIN_ID — Concurrent program context columns linking each row to the batch or report that generated it.

No surrogate primary key column is explicitly documented in the metadata. The table relies on composite business-key combinations involving REGIME_ID, PARTY_ID, LOCATION_ID, TAX_TYPE, and BALANCE_DATE to uniquely identify a balance record within the localization context. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) are present for concurrency control and change tracking.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include querying outstanding debit or credit balances per organization, location, and tax type for a given period. A representative pattern is:

• Balance reconciliation by regime: sum DEBIT_AMT and CREDIT_AMT grouped by REGIME_ID and TAX_TYPE for a specified BALANCE_DATE range.
• PLA register reporting: filter on PLA_BALANCE and CREDIT_UTILIZED to produce the excise PLA register required for statutory filing.
• Organization-level drill-down: join PARTY_ID to HR_ALL_ORGANIZATION_UNITS and LOCATION_ID to HR_LOCATIONS_ALL to present balances with descriptive names.
• Batch traceability: join REQUEST_ID to FND_CONCURRENT_REQUESTS to trace which concurrent program run populated a set of balance rows.

Reverse charge analysis can be performed by filtering REVERSE_CHARGE_FLAG, and service tax analysis by filtering SERVICE_TYPE_CODE.

Related Objects

The following tables are directly referenced through foreign keys and are the most significant for joins and integrity:

• JAI_RGM_DEFINITIONS on REGIME_ID — defines the tax regime master.
• HR_ALL_ORGANIZATION_UNITS on PARTY_ID — organization or business unit master.
• HR_LOCATIONS_ALL on LOCATION_ID — location master.
• FND_CONCURRENT_REQUESTS on REQUEST_ID — concurrent request audit trail.
• FND_CONCURRENT_PROGRAMS on PROGRAM_APPLICATION_ID and PROGRAM_ID — program definition.
• FND_LOGINS on PROGRAM_LOGIN_ID — user login session context.

These relationships confirm that JAI_RGM_BALANCE_T acts as a linking entity between localization tax setup, HR organizational structures, and concurrent processing infrastructure, supporting the full auditability required for Indian tax compliance reporting.