Results for “rg_dss_requests_v”

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

Overview

RG_DSS_REQUESTS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Application Report Generator (RG) product family. It presents a denormalized, read-oriented projection of balancing and reporting extraction requests stored in the RG_DSS_REQUESTS base table, enriching each request with descriptive attributes drawn from General Ledger and Application Object Library reference entities. The view is valid in both Oracle EBS 12.1.1 and 12.2.2 and is used by the GL Data Sub-System (DSS) reporting and extraction infrastructure to describe how a given balance request was configured, executed, and targeted.

Its principal role is to resolve numeric identifiers — chart of accounts structures, ledgers, budget versions, encumbrance types, hierarchies, and summary templates — into human-readable names, while decoding status and program flags used by the extraction engine. Because the view exposes CHART_OF_ACCOUNTS_NAME, it is frequently consulted by users and administrators investigating which accounting flexfield structure a request operated against, a common point of inquiry when diagnosing GL reporting output.

Underlying Base Objects

The view is defined over RG_DSS_REQUESTS as its driving table, joined to several GL and FND reference objects. The primary base and referenced objects are:

• RG_DSS_REQUESTS — the core request record, holding program type, request identifiers, status flags, file specifications, extraction and load timestamps, and seeded foreign keys.
• FND_ID_FLEX_STRUCTURES_TL — provides the translated ID_FLEX_STRUCTURE_NAME that becomes CHART_OF_ACCOUNTS_NAME, filtered to APPLICATION_ID = 101, ID_FLEX_CODE = 'GL#', and the session language.
• GL_LEDGERS — supplies NAME as LEDGER_NAME for the associated ledger.
• GL_BUDGET_VERSIONS and GL_ENCUMBRANCE_TYPES — resolve BUDGET_NAME or ENCUMBRANCE_TYPE into the derived BUDGET_ENC_NAME column via a DECODE on BALANCE_TYPE.
• RG_DSS_HIERARCHIES — supplies NAME as HIERARCHY_NAME.
• GL_SUMMARY_TEMPLATES — supplies TEMPLATE_NAME.
• GL_LOOKUPS — referenced twice, resolving GL_DSS_PROGRAM_TYPE and GL_DSS_BALANCE_TYPE lookup codes into their meanings.

All joins to the reference tables are outer joins denoted by the (+) operator, ensuring that a request row is returned even when descriptive name data is absent.

Key Columns

• PROGRAM_TYPE / PROGRAM_NAME — the DSS program code and its decoded lookup meaning.
• REQUEST_ID / CONCURRENT_REQUEST_ID — DSS request identifier and the underlying concurrent request identifier.
• STATUS_FLAG — current processing state of the extraction request.
• FILE_SPEC — extraction output file specification.
• EXTRACTION_START_DATE / EXTRACTION_END_DATE / LOAD_START_DATE / LOAD_END_DATE — extraction and load timing boundaries.
• CHART_OF_ACCOUNTS_ID / CHART_OF_ACCOUNTS_NAME — the accounting flexfield structure identifier and its translated name.
• LEDGER_ID / LEDGER_NAME — the target ledger and its name.
• FROM_PERIOD / TO_PERIOD / PERIOD_YEAR — reporting period boundaries.
• BALANCE_TYPE / BALANCE_MEANING — the balance category code and its lookup meaning.
• BUDGET_VERSION_ID / ENCUMBRANCE_TYPE_ID / BUDGET_ENC_NAME — budget or encumbrance reference and its resolved name.
• TEMPLATE_ID / TEMPLATE_NAME, HIERARCHY_ID / HIERARCHY_NAME — summary template and hierarchy targets.
• DAY_OF_PERIOD — day within the reporting period, where applicable.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing DSS extraction requests, verifying which chart of accounts or ledger a request targeted, and reconciling budget and encumbrance configuration. A representative query listing recent requests with descriptive names is:

• SELECT request_id, program_name, chart_of_accounts_name, ledger_name, from_period, to_period, balance_meaning FROM rg_dss_requests_v WHERE chart_of_accounts_name IS NOT NULL ORDER BY creation_date DESC;
• SELECT request_id, ledger_name, budget_enc_name, template_name FROM rg_dss_requests_v WHERE balance_type = 'B';
• SELECT request_id, hierarchy_name, period_year, status_flag FROM rg_dss_requests_v WHERE hierarchy_id IS NOT NULL;

Because the view encapsulates several outer joins and lookup decodes, it simplifies reporting against RG_DSS_REQUESTS without requiring callers to reconstruct GL and FND reference logic manually.