Results for “rg_report_sets”

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

Overview

RG_REPORT_SETS is a table in the RG (Application Report Generator) schema of Oracle E-Business Suite, present and valid in releases 12.1.1 and 12.2.2. It stores report set definitions — the metadata that groups individual report requests into a single logical unit that can be submitted and executed together within the Oracle EBS Report Generator. Each row identifies one report set, together with the general ledger flexfield context, currency/unit-of-measure reference, and period information that govern how the set is generated and rolled up.

From a modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. Although the table carries its own surrogate primary key and descriptive attributes, its foreign keys reach into configuration and reference tables (FND_ID_FLEX_STRUCTURES and FND_CURRENCIES), and it is itself referenced by a transaction-style table (RG_REPORT_REQUESTS). Treating RG_REPORT_SETS as a satellite of the report-generation hub, rather than as an independent hub, is a reasonable heuristic when building a dimensional or Data Vault layer.

Key Information Stored

The documented physical schema for 12.2.2 lists 32 columns. The most significant are the identifying and configuration columns:

• REPORT_SET_ID — the surrogate primary key, enforced by RG_REPORT_SETS_PK and repeated in unique index RG_REPORT_SETS_U1.
• NAME, APPLICATION_ID — the business-key candidate, enforced by unique index RG_REPORT_SETS_U2 (and referenced as RG_REPORT_SETS_UK1 in the documentation). NAME identifies the report set; APPLICATION_ID ties it to the owning application.
• ID_FLEX_CODE, ID_FLEX_CODE_11I, STRUCTURE_ID — the key flexfield code and structure defining the accounting/segment context of the set (linked to FND_ID_FLEX_STRUCTURES).
• UNIT_OF_MEASURE_ID — currency/unit-of-measure reference (linked to FND_CURRENCIES).
• PERIOD_TYPE, PERIOD_NAME — the accounting period classification and name applied to the set.
• SECURITY_FLAG — controls whether the set is subject to security restrictions.
• DESCRIPTION, CONTEXT — descriptive and descriptive-flexfield context fields.
• ATTRIBUTE1 ... ATTRIBUTE15 — the standard EBS descriptive flexfield segment columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — who/when audit columns present on all EBS transactional tables.

Common Use Cases and Queries

RG_REPORT_SETS is queried when administrators or developers need to enumerate defined report sets, determine which sets apply to a given application or period, or resolve the key flexfield structure a set uses before submitting it. Typical joins resolve the application name and flexfield structure, for example:

• List report sets with their owning application: SELECT r.REPORT_SET_ID, r.NAME, r.APPLICATION_ID FROM RG.RG_REPORT_SETS r.
• Find sets by business key: filter on NAME and APPLICATION_ID (the RG_REPORT_SETS_U2 columns).
• Resolve the flexfield structure: join RG_REPORT_SETS.STRUCTURE_ID and APPLICATION_ID to FND_ID_FLEX_STRUCTURES.
• Resolve the currency/UOM: join UNIT_OF_MEASURE_ID to FND_CURRENCIES.
• Report on which sets have been executed: join to RG_REPORT_REQUESTS.REPORT_SET_ID.

Reporting use cases include auditing report-set definitions, verifying period and flexfield configuration, and tracing which report requests belong to which set.

Related Objects

The following objects are the most significant relationships, grounded in the documented foreign keys:

• RG_REPORT_REQUESTS — references this table via RG_REPORT_REQUESTS.REPORT_SET_ID = RG_REPORT_SETS.REPORT_SET_ID; the child that records requests executed for each set.
• FND_ID_FLEX_STRUCTURES — referenced by RG_REPORT_SETS.STRUCTURE_ID (and APPLICATION_ID) to define the key flexfield structure.
• FND_CURRENCIES — referenced by RG_REPORT_SETS.UNIT_OF_MEASURE_ID for currency context.
• The RG schema report-generation objects that consume report sets at submission time, and the standard EBS flexfield/application reference views, complete the dependency chain.

Because RG_REPORT_SETS is referenced by RG_REPORT_REQUESTS, deleting or altering a report set definition affects the historical requests that depend on it.