Search Results jai_ap_rgm_payments




Overview
Explore in AI Chat

Overview

The JAI_AP_RGM_PAYMENTS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves a specific regulatory function by storing transactional records for payments made to the Tax Collected at Source (TCS) authority. This table is essential for compliance in jurisdictions where TCS regulations are enforced, as it provides an auditable link between internal settlement processes, actual payment instruments (checks), and the external tax authorities and banking institutions involved in the remittance process.

Key Information Stored

While the full column list is not detailed in the provided metadata, the documented foreign key relationships define the critical data entities stored. The primary identifier is the PAYMENT_ID. Each record fundamentally links a specific TCS settlement (via SETTLEMENT_ID) to the actual payment instrument issued, typically an AP check (via CHECK_ID). Furthermore, the table stores key party identifiers: the specific TAX_AUTHORITY_ID and its TAX_AUTHORITY_SITE_ID that received the payment, and the BANK_BRANCH_ID representing the financial institution involved. This structure ensures every TCS payment can be traced from the internal liability through to the external payee and payment method.

Common Use Cases and Queries

This table is central to reconciliation and reporting for TCS compliance. Common operational and audit scenarios include tracing payment history for a specific TCS settlement, verifying payments made to a particular tax authority within a period, and reconciling Accounts Payable check registers with TCS remittances. A typical query would join to related tables to produce a detailed payment register.

Sample Query Pattern:
SELECT p.payment_id,
s.settlement_number,
c.check_number,
hz_party.party_name tax_authority_name,
p.payment_date,
c.amount check_amount
FROM ja.jai_ap_rgm_payments p,
ja.jai_rgm_settlements s,
ap.ap_checks_all c,
hz.hz_parties hz_party
WHERE p.settlement_id = s.settlement_id
AND p.check_id = c.check_id
AND p.tax_authority_id = hz_party.party_id
AND TRUNC(p.payment_date) BETWEEN :p_start_date AND :p_end_date;

Related Objects

The JAI_AP_RGM_PAYMENTS table sits at the intersection of localization-specific tax data and core EBS financials, as evidenced by its foreign key relationships.

  • JAI_RGM_SETTLEMENTS: Links to the source TCS liability settlement (via JAI_AP_RGM_PAYMENTS.SETTLEMENT_ID).
  • AP_CHECKS_ALL: Links to the core Payables payment instrument used (via JAI_AP_RGM_PAYMENTS.CHECK_ID).
  • HZ_PARTIES (Multiple Relationships): References the Trading Community Architecture (TCA) registry to identify the tax authority party (TAX_AUTHORITY_ID), its specific site (TAX_AUTHORITY_SITE_ID), and the bank branch (BANK_BRANCH_ID).

These relationships are critical for generating compliant reports that merge localized tax data with standard EBS financial and party information.