Results for “regime_id”

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

Overview

The APPS.JAI_RGM_STL_BALANCES_V view is a reporting and inquiry object delivered with the Oracle E-Business Suite JA – Asia/Pacific Localizations product family. Its name associates it with the Regional General Manager (RGM) settlements functionality used by Asia/Pacific tax regimes, where a settlement represents a periodic reconciliation of tax balances accumulated against a registered tax type. The view consolidates settlement balance lines into a single row per settlement, regime, and tax type, and it exposes the aggregate debit, credit, and credit-utilized figures calculated from the underlying balance table.

In the context of the ETRM object catalog for Release 12.1.1 and 12.2.2, the view is classified as a VALID view owned by the APPS schema. Because it is a view rather than a table, it carries no independent storage; it is a read-only projection intended for reporting, inquiry pages, and integration extracts that need settlement balance totals already grouped and ordered. The CREDIT_UTILIZED column, which is the term most frequently searched for against this object, is the summation of the credit amount applied or consumed against the balances of a given tax type within a settlement.

Underlying Base Objects

The view is defined over three documented base objects, all of which are referenced as synonyms in the APPS schema:

• JAI_RGM_STL_BALANCES (JRSL) – The primary balance detail source. Provides SETTLEMENT_ID, TAX_TYPE, DEBIT_BALANCE, CREDIT_BALANCE, and CREDIT_UTILIZED.
• JAI_RGM_SETTLEMENTS (JRS) – The settlement header. Supplies SETTLEMENT_ID and joins the balance lines to a specific settlement and its REGIME_ID.
• JAI_RGM_REGISTRATIONS (JRR) – The registration master for the regime. Restricts the result set to registration rows whose REGISTRATION_TYPE is 'TAX_TYPES' and validates that the balance TAX_TYPE equals the registration ATTRIBUTE_CODE.

The join path is: balance lines to settlement on SETTLEMENT_ID; settlement to registration on REGIME_ID; and balance lines to registration on TAX_TYPE = ATTRIBUTE_CODE. Rows are grouped by settlement, regime, tax type, and the registration ATTRIBUTE_SEQUENCE, with the final ordering driven by ATTRIBUTE_SEQUENCE so that tax types appear in their configured sequence.

Key Columns

• SETTLEMENT_ID – Identifier of the settlement to which the aggregated balances belong.
• REGIME_ID – Identifier of the tax regime associated with the settlement and its registration.
• TAX_TYPE – The tax type (registration attribute code) for which balances are summarized.
• DEBIT – Sum of DEBIT_BALANCE across the matching balance lines.
• CREDIT – Sum of CREDIT_BALANCE across the matching balance lines.
• CREDIT_UTILIZED – Sum of CREDIT_UTILIZED, representing the credit amount consumed against the tax type balances within the settlement.

Because the aggregation uses SUM without a DECODE or NVL guard, a tax type with no balance lines will not appear, and the numeric columns reflect only rows present in JAI_RGM_STL_BALANCES.

Common Use Cases and Queries

Typical uses include settlement balance inquiry, reconciliation between tax credit generated and credit utilized, and integration extracts that feed downstream reporting or filing processes. A representative query retrieving credit utilization for a settlement is:

• SELECT settlement_id, regime_id, tax_type, debit, credit, credit_utilized FROM apps.jai_rgm_stl_balances_v WHERE settlement_id = :p_settlement_id ORDER BY tax_type;
• SELECT tax_type, SUM(credit_utilized) FROM apps.jai_rgm_stl_balances_v WHERE regime_id = :p_regime_id GROUP BY tax_type;
• SELECT settlement_id, credit - credit_utilized remaining_credit FROM apps.jai_rgm_stl_balances_v;

These queries are read-only and inherit the security and performance characteristics of the base RGM tables; appropriate indexes on the settlement, regime, and tax type columns of the underlying tables support efficient access.