Results for “rg_report_content_sets”

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

Overview

RG_REPORT_CONTENT_SETS is a table in the RG (Application Report Generator / Oracle Reports) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores content set definitions — reusable groupings of report content that control how Report Generator reports are assembled, secured, and executed. The table acts as a configuration registry: each row defines a named content set, optionally tied to a specific application and to a key flexfield structure, which downstream Report Generator objects consume when a report is defined or submitted.

Based on the Data Vault classification heuristic derived from its foreign key structure, this table is hub-leaning. In Data Vault terms, it behaves as a hub: it holds a stable, uniquely identified business concept (the content set) whose surrogate key does not change, with descriptive and administrative attributes appended. It is not a link table, since it does not model a many-to-many relationship between two independent hubs, and it is not a pure satellite, since it carries its own surrogate primary key and business identifier. This classification is a modeling suggestion rather than a statement of physical design.

Key Information Stored

The table is documented with 30 columns, of which the following are the most operationally significant.

• CONTENT_SET_ID — the surrogate primary key, enforced by RG_REPORT_CONTENT_SETS_PK and additionally by the unique index RG_REPORT_CONTENT_SETSETS_U1. It is the identifier referenced by all dependent Report Generator tables.
• NAME — the user-visible content set name; combined with APPLICATION_ID it forms the business key enforced by the unique index RG_REPORT_CONTENT_SETS_U2.
• APPLICATION_ID — the owning application, and the column participating in the foreign key to FND_ID_FLEX_STRUCTURES.
• ID_FLEX_CODE_11I and STRUCTURE_ID — identify the key flexfield definition associated with the content set; together with APPLICATION_ID they reference FND_ID_FLEX_STRUCTURES.
• ID_FLEX_CODE — the flexfield code used for the same flexfield context in the 12.2.2 data model.
• REPORT_RUN_TYPE — indicates the execution mode associated with the content set.
• DESCRIPTION — free-text explanation of the content set's purpose.
• SECURITY_FLAG — controls whether the content set is subject to Report Generator security enforcement.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield context and segment columns, used for customer-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO columns capturing audit and responsibility context.

Common Use Cases and Queries

The principal use case is administrative and diagnostic: identifying which content sets exist, which application owns them, and what flexfield structure they are bound to. A typical lookup by name is:

• SELECT content_set_id, name, application_id, security_flag FROM rg_report_content_sets WHERE name = :name AND application_id = :app_id;

Because RG_REPORTS, RG_REPORT_REQUESTS, and RG_REPORT_OVERRIDES all carry CONTENT_SET_ID, a common diagnostic query resolves the content sets actually exercised at runtime:

• SELECT r.name report_name, c.name content_set_name FROM rg_reports r, rg_report_content_sets c WHERE r.content_set_id = c.content_set_id;

Migration and upgrade testing frequently use these joins to confirm that no report references a content set that has been deleted or that belongs to an unexpected application. Flexfield validation queries join on APPLICATION_ID, ID_FLEX_CODE_11I, and STRUCTURE_ID to confirm the structural binding is still valid.

Related Objects

• FND_ID_FLEX_STRUCTURES — referenced from RG_REPORT_CONTENT_SETS via APPLICATION_ID, ID_FLEX_CODE_11I, and STRUCTURE_ID; validates the flexfield structure definition.
• RG_REPORTS — depends on this table through RG_REPORTS.CONTENT_SET_ID, linking each report definition to its content set.
• RG_REPORT_CONTENT_OVERRIDES — references CONTENT_SET_ID to define per-content-set overrides.
• RG_REPORT_REQUESTS — references CONTENT_SET_ID to record the content set used in a submission.
• RG_REPORT_CONTENT_SET_ITEMS — the logical child object holding the individual content items belonging to a set, joined on CONTENT_SET_ID.
• RG_REPORT_TEMPLATES — the report template layer that consumes content sets during report generation.