Search Results jai_rgm_conc_requests




Overview
Explore in AI Chat

Overview

The JAI_RGM_CONC_REQUESTS table is a core data object within the JA (Asia/Pacific Localizations) product of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a central repository for tracking concurrent request information specifically related to India's Service Tax Processing. This table is integral to the localization's regulatory regime (RGM) management, acting as a bridge between the standard EBS concurrent request framework and localized tax transaction processing. Its primary role is to store metadata and status information for batches of service tax-related jobs submitted for execution, enabling audit trails, process linkage, and reporting.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships. The primary key is the BATCH_ID, which uniquely identifies each batch of service tax processing. Key foreign key columns establish critical links to other EBS entities: REQUEST_ID links to the standard FND_CONCURRENT_REQUESTS table to track the concurrent request's lifecycle (status, start/end time). REGIME_ID references JAI_RGM_DEFINITIONS to associate the batch with a specific tax regime definition. PROGRAM_APPLICATION_ID and PROGRAM_ID link to FND_CONCURRENT_PROGRAMS to identify the specific program executed. PROGRAM_LOGIN_ID references FND_LOGINS for user session context. Collectively, these columns store the who, what, and when of each service tax processing batch.

Common Use Cases and Queries

Common use cases revolve around monitoring, troubleshooting, and reconciling India Service Tax reports and processes. Support personnel frequently query this table to determine the status and outcome of a specific regulatory submission batch or to list all batches processed for a given regime within a date range. A typical diagnostic query joins with FND_CONCURRENT_REQUESTS to get detailed request status and phase/status codes.

  • Sample Query: To find details for a specific batch and its concurrent request status:
    SELECT jrc.batch_id, jrc.regime_id, fcr.request_id, fcr.phase_code, fcr.status_code, fcr.actual_start_date
    FROM jai_rgm_conc_requests jrc, fnd_concurrent_requests fcr
    WHERE jrc.request_id = fcr.request_id
    AND jrc.batch_id = :p_batch_id;
  • Reporting Use Case: Generating an audit report of all service tax processing batches submitted by a user, joining with JAI_RGM_DEFINITIONS to get the regime name and with FND_CONCURRENT_PROGRAMS for the program name.

Related Objects

The JAI_RGM_CONC_REQUESTS table is a central node in the India Service Tax schema, with documented relationships to several key tables.

  • Referenced Objects (Foreign Keys FROM JAI_RGM_CONC_REQUESTS):
    • FND_CONCURRENT_REQUESTS: Via JAI_RGM_CONC_REQUESTS.REQUEST_ID. For standard request tracking.
    • JAI_RGM_DEFINITIONS: Via JAI_RGM_CONC_REQUESTS.REGIME_ID. For regime setup details.
    • FND_CONCURRENT_PROGRAMS: Via JAI_RGM_CONC_REQUESTS.PROGRAM_APPLICATION_ID and .PROGRAM_ID. For program metadata.
    • FND_LOGINS: Via JAI_RGM_CONC_REQUESTS.PROGRAM_LOGIN_ID. For user session information.
  • Referencing Objects (Foreign Keys TO JAI_RGM_CONC_REQUESTS):
    • JAI_RGM_TRX_RECORDS: Via JAI_RGM_TRX_RECORDS.BATCH_ID. This table likely stores the detailed transaction records processed in the batch.
    • JAI_RGM_TRX_REFS: Via JAI_RGM_TRX_REFS.BATCH_ID. This table likely stores reference information for the transactions in the batch.