Search Results rg_dss_systems_u1




Overview

RG.RG_DSS_SYSTEMS is a table owned by the RG schema within the Oracle E-Business Suite environment, valid in both 12.1.1 and 12.2.2. It stores the definition of "systems" used by Oracle's Decision Support System (DSS) components, where a system represents a named financial data set configuration. Each row defines the identity of a data set, the key flexfield context under which it operates, and the accounting calendar it is bound to. Indexes and columns are registered in FND Design Data as RG.RG_DSS_SYSTEMS, and storage resides in the APPS_TS_TX_DATA tablespace.

Because the table carries descriptive attributes alongside a stable numeric identifier, it closely resembles a dimension or reference entity in dimensional modeling terms. The mined relationship data classifies RG_DSS_SYSTEMS as hub-leaning in a Data Vault interpretation, suggesting it functions primarily as a business-key hub rather than a link or satellite: SYSTEM_ID is the durable, meaningless surrogate key, while NAME provides a natural business key. This classification should be treated as a modeling suggestion, not a physical fact.

Access is restricted. The object is marked Oracle Internal Use Only; Oracle does not support direct data access except through standard Oracle Applications programs.

Key Information Stored

The table comprises 28 columns. The most consequential are:

Note that SYSTEM_ID and NAME are both uniqueness-enforced, but only SYSTEM_ID is the declared primary key; NAME is the alternate business-key candidate. Applications should therefore join on SYSTEM_ID and treat NAME as a displayable, user-facing identifier.

Common Use Cases and Queries

Typical usage centers on identifying which financial data set drives a given DSS process, verifying calendar or flexfield alignment, and producing inventory reports of defined systems. A standard lookup by business key resembles:

SELECT system_id, name, freeze_flag, id_flex_code, id_flex_num, period_set_name
FROM   rg.rg_dss_systems
WHERE  name = :p_name;

Calendar validation queries join PERIOD_SET_NAME to GL_PERIOD_SETS to confirm that a system references a valid, active calendar. Administrative reporting frequently filters on FREEZE_FLAG to distinguish editable from locked systems, and on SAVE_INCREMENTAL_DATA_FLAG to audit incremental processing configurations. Because descriptive flexfield segments live in ATTRIBUTE1 through ATTRIBUTE15, context-aware reporting should always constrain or project CONTEXT so that attribute semantics remain unambiguous. Where DSS processing consumes system definitions, queries are typically driven by SYSTEM_ID rather than NAME, consistent with the primary key.

Related Objects

RG_DSS_SYSTEMS sits at the center of a small cluster of DSS configuration tables. The documented dependencies are:

  • RG_DSS_SYSTEM_SEG_ORDER — references RG_DSS_SYSTEMS via SYSTEM_ID; holds segment ordering configuration for each system.
  • RG_DSS_SYSTEM_VARIABLES — references RG_DSS_SYSTEMS via SYSTEM_ID; holds variable definitions belonging to a system.
  • GL_PERIOD_SETS — referenced by RG_DSS_SYSTEMS through PERIOD_SET_NAME, supplying the accounting calendar definition.
  • FND_ID_FLEX_STRUCTURES — implied by the ID_FLEX_CODE and ID_FLEX_NUM pair, resolving the key flexfield structure used by the system.
  • FND_DESCRIPTIVE_FLEXS — implied by CONTEXT and the ATTRIBUTE columns, defining the descriptive flexfield behavior attached to each row.

Together these objects form the DSS system definition layer, with RG_DSS_SYSTEMS acting as the parent hub and the SEG_ORDER and VARIABLES tables functioning as dependent configuration satellites.