Search Results rg_dss_requests




Overview
Explore in AI Chat

Overview

The RG_DSS_REQUESTS table is a core data object within the Oracle E-Business Suite (EBS) Application Report Generator (RG) module. It functions as the central tracking and logging mechanism for requests related to the Financial Analyzer extract and load processes. Financial Analyzer, a component of Oracle's Enterprise Performance Management suite, relies on data extracted from the EBS General Ledger. This table records the metadata and status of each concurrent program request that extracts financial data from the GL or loads data back into it, providing a critical audit trail and enabling users to monitor the history and outcome of these integration jobs.

Key Information Stored

The table's primary identifier is the REQUEST_ID, which is the primary key for the table. The most critical foreign key is CONCURRENT_REQUEST_ID, which links each record directly to the FND_CONCURRENT_REQUESTS table, thereby integrating the Financial Analyzer process with the standard EBS concurrent manager framework for execution and status monitoring. Other essential foreign keys define the specific context of each data transfer operation: LEDGER_ID (GL_SETS_OF_BOOKS_11I) specifies the source ledger, BUDGET_VERSION_ID (GL_BUDGET_VERSIONS) and ENCUMBRANCE_TYPE_ID (GL_ENCUMBRANCE_TYPES) identify the budget or encumbrance data being processed, TEMPLATE_ID (GL_SUMMARY_TEMPLATES) points to the summary template used, and HIERARCHY_ID (RG_DSS_HIERARCHIES) references the account hierarchy definition for the extract.

Common Use Cases and Queries

A primary use case is auditing and troubleshooting Financial Analyzer data transfer jobs. System administrators and functional users frequently query this table to check the status and parameters of recent or historical extracts. A common reporting query joins RG_DSS_REQUESTS with FND_CONCURRENT_REQUESTS to get the human-readable program name and execution details.

  • Sample Query to List Recent Extracts:
    SELECT rgr.request_id, fcr.request_id AS concurrent_request_id, fcr.concurrent_program_name, fcr.argument_text, fcr.phase_code, fcr.status_code, fcr.request_date FROM rg.rg_dss_requests rgr, apps.fnd_concurrent_requests fcr WHERE rgr.concurrent_request_id = fcr.request_id ORDER BY fcr.request_date DESC;
  • Identifying Failed Requests: Users filter on the phase and status codes from the joined FND_CONCURRENT_REQUESTS table (e.g., WHERE fcr.phase_code = 'C' AND fcr.status_code = 'E') to identify failed jobs for re-submission or analysis.

Related Objects

The RG_DSS_REQUESTS table is centrally connected to several key EBS tables via documented foreign key relationships, which define its operational context.

  • FND_CONCURRENT_REQUESTS: Joined via RG_DSS_REQUESTS.CONCURRENT_REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID. This is the most critical relationship, providing execution log details.
  • GL_SETS_OF_BOOKS_11I: Joined via RG_DSS_REQUESTS.LEDGER_ID. Identifies the specific ledger from which data is extracted.
  • GL_BUDGET_VERSIONS: Joined via RG_DSS_REQUESTS.BUDGET_VERSION_ID. Specifies the budget data version for budget-related extracts.
  • GL_ENCUMBRANCE_TYPES: Joined via RG_DSS_REQUESTS.ENCUMBRANCE_TYPE_ID. Specifies the encumbrance type for encumbrance-related extracts.
  • GL_SUMMARY_TEMPLATES: Joined via RG_DSS_REQUESTS.TEMPLATE_ID. References the summary template used to define the data aggregation.
  • RG_DSS_HIERARCHIES: Joined via RG_DSS_REQUESTS.HIERARCHY_ID. References the account hierarchy used to structure the extracted financial data.