Results for “ledger_segment_type”

22 results




Overview
Explore in AI Chat

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

Overview

RG_REPORT_CONTENT_OVERRIDES is a table owned by the RG (Application Report Generator) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the financial reporting infrastructure that drives the FSG (Financial Statement Generator) row and column content set mechanism. The table stores the assignment of account ranges to content sets, providing the granular overrides that determine which accounting flexfield combinations are included in, or excluded from, a given report content definition. Content sets are reusable building blocks in FSG reporting; RG_REPORT_CONTENT_OVERRIDES records how individual account ranges are mapped to those sets, together with the ledger context in which the override applies.

The heuristic Data Vault classification mined from the foreign key structure is link. This reflects the table's role as an association object: it resolves relationships between content sets and ledgers, and it carries the range definition attributes that qualify those associations. Modeling it as a link table between the content set hub and the ledger hub is a reasonable analytical convention.

Key Information Stored

The table contains 244 documented columns, the majority of which are repeating SEGMENT and SEGMENT_ATTRIBUTE structures. The most important columns are as follows.

  • CONTENT_SET_ID — Foreign key to RG_REPORT_CONTENT_SETS; identifies the content set to which this override belongs. Part of the composite primary key.
  • OVERRIDE_SEQ — Sequence number ordering the individual range entries within a content set. The second component of the composite primary key.
  • RANGE_MODE — Governs how the low/high segment ranges are interpreted (for example inclusive, exclusive, or a single-value mode).
  • LEDGER_ID — Foreign key to GL_LEDGERS; scopes the override to a specific ledger, enabling ledger-specific content selection.
  • LEDGER_SEGMENT_TYPE — Indicates the type of ledger segment context associated with the override.
  • APPLICATION_ID — Identifies the owning application, consistent with the standard EBS multi-application data model.
  • SEGMENTn_LOW / SEGMENTn_HIGH / SEGMENTn_TYPE — Repeating triplets (n = 1 through 30) defining the low bound, high bound, and comparison type for each accounting flexfield segment in the range.
  • SEGMENT_ATTRIBUTEm_LOW / _HIGH / _TYPE — Repeating triplets (m = 1 through 42) that extend the range definition to segment qualifiers and attributes.
  • CONTEXT — Descriptive context for the override record.
  • ATTRIBUTE1–15 — Standard EBS descriptive flexfield columns for extensible attributes.
  • ALC_LEDGER_CURRENCY — Currency context associated with the ledger selection.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

The surrogate primary key is RG_REPORT_CONTENT_OVERRIDES_PK, comprising (CONTENT_SET_ID, OVERRIDE_SEQ). The unique index RG_REPORT_CONTENT_OVERRIDES_U1 mirrors the same column pair and is the documented business-key candidate. No independent surrogate sequence column exists; the combination of content set and override sequence is the identity of the row.

Common Use Cases and Queries

Typical uses include auditing content set definitions, diagnosing why a report includes or excludes certain accounts, and reconciling ledger-specific overrides across a multi-ledger environment. A common join retrieves overrides with their content set and ledger names.

  • List all overrides for a content set: SELECT * FROM RG.RG_REPORT_CONTENT_OVERRIDES WHERE CONTENT_SET_ID = :p_set ORDER BY OVERRIDE_SEQ;
  • Join to content sets and ledgers: SELECT o.OVERRIDE_SEQ, o.CONTENT_SET_ID, o.LEDGER_ID, o.RANGE_MODE FROM RG.RG_REPORT_CONTENT_OVERRIDES o, RG.RG_REPORT_CONTENT_SETS s, GL.GL_LEDGERS l WHERE o.CONTENT_SET_ID = s.CONTENT_SET_ID AND o.LEDGER_ID = l.LEDGER_ID AND o.CONTENT_SET_ID = :p_set;
  • Inspect range bounds for a specific segment: SELECT CONTENT_SET_ID, OVERRIDE_SEQ, SEGMENT1_LOW, SEGMENT1_HIGH, SEGMENT1_TYPE FROM RG.RG_REPORT_CONTENT_OVERRIDES;
  • Ledger-scoped override audit: filter by LEDGER_ID to determine which ledger receives a given content selection, useful when the same content set behaves differently per ledger.

Because the range and attribute triplet structures are repetitive, reporting queries typically restrict output to the segments relevant to the chart of accounts in use rather than projecting all 244 columns.

Related Objects

The principal related objects, grounded in the documented foreign keys and primary key structure, are:

  • RG_REPORT_CONTENT_SETS — Parent of CONTENT_SET_ID; defines the content set being overridden.
  • GL_LEDGERS — Parent of LEDGER_ID; supplies ledger context.
  • RG_REPORT_CONTENT_OVERRIDES_PK — Primary key constraint on (CONTENT_SET_ID, OVERRIDE_SEQ).
  • RG_REPORT_CONTENT_OVERRIDES_U1 — Unique index providing the business-key candidate on the same columns.
  • FSG report definitions and row/column set tables in the RG schema, which reference content sets and therefore transitively depend on this table.
  • GL_CODE_COMBINATIONS — Although not a direct foreign key, the SEGMENT low/high ranges are resolved against accounting flexfield combinations held in this table during report generation.

Collectively, these objects place RG_REPORT_CONTENT_OVERRIDES at the junction of content set definition and ledger-scoped account selection within the Application Report Generator.