Results for “qrm_saved_analyses_row”

38 results




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

Overview

QRM_SAVED_ANALYSES_ROW is a table owned by the QRM schema within the Oracle E-Business Suite Risk Management module. Its documented purpose is to store the rows that are displayed below the column header for Analysis Results, meaning it persists the row-level layout and content of saved analysis result grids presented to risk analysts. Each record corresponds to one display row within a named saved analysis, allowing the application to reconstruct a previously defined results layout, including row type, visibility, currency context, and the positional cell values that populate the grid.

The table is classified as VALID and is documented in both Oracle EBS 12.1.1 and 12.2.2. The ETRM 12.2.2 physical schema lists 327 columns, reflecting the wide, matrix-style nature of the object where each row can carry up to 100 analysis values (A1–A100), 100 measure values (M1–M100), 100 parameter values (P1–P100), and 100 currency columns (CURR1–CURR100). Under the heuristic Data Vault classification mined from the foreign key structure, this object is assessed as standalone — it participates in no declared foreign key relationships, which suggests it be modeled as an independent satellite or hub-like structure keyed on its own business identifier rather than as a link between entities.

Key Information Stored

The documented primary key is QRM_SAVED_ANALYSES_ROW_PK, defined over the composite of ANALYSIS_NAME and SEQ_NO. A unique index, QRM_SAVED_ANALYSES_ROW_U1, is declared over the same two columns (ANALYSIS_NAME, SEQ_NO), confirming that this composite is the business-key candidate and that ANALYSIS_NAME plus SEQ_NO uniquely identify each grid row.

  • ANALYSIS_NAME — Identifier of the owning saved analysis; the first component of the primary key and the grouping attribute for all rows belonging to one analysis.
  • SEQ_NO — Sequence number that orders rows beneath the column header; the second component of the primary key.
  • TYPE — Classifies the row (for example, its display or structural category) so the application can render it appropriately.
  • HIDDEN — Flag indicating whether the row is suppressed from the visible analysis results grid.
  • TOT_CURRENCY and TOT_CURRENCY_LABEL — Currency code and label used for total or aggregate display on the row.
  • A1–A100 — Positional analysis value columns holding the primary numeric or textual results across up to 100 positions.
  • M1–M100 — Measure columns capturing metric values aligned to the analysis positions.
  • P1–P100 — Parameter columns storing per-position parameters or attributes.
  • CURR1–CURR100 — Currency columns holding currency identifiers associated with each positional value.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

The principal use case is reconstructing a saved Analysis Results grid for display or reporting. Because the composite key is ANALYSIS_NAME and SEQ_NO, queries typically filter on one analysis and order by SEQ_NO to reproduce the original layout.

  • Retrieve all visible rows for an analysis:
    SELECT SEQ_NO, TYPE, A1, A2, M1, M2 FROM QRM.QRM_SAVED_ANALYSES_ROW WHERE ANALYSIS_NAME = :name AND HIDDEN = 'N' ORDER BY SEQ_NO;
  • Resolve a specific row via the primary key: WHERE ANALYSIS_NAME = :name AND SEQ_NO = :seq.
  • Validate uniqueness against QRM_SAVED_ANALYSES_ROW_U1 by grouping on ANALYSIS_NAME, SEQ_NO and checking for duplicates.
  • Audit recently modified analysis layouts using LAST_UPDATED_BY and LAST_UPDATE_DATE.
  • Inventory analyses by counting rows per ANALYSIS_NAME, and reconcile currency totals through TOT_CURRENCY and the CURR1–CURR100 columns.

Related Objects

The documented relationship data classifies this table as standalone, meaning no foreign keys are mined from its structure. Consequently, related objects are implied by shared business keys rather than by enforced constraints. The most significant associations are:

  • QRM_SAVED_ANALYSES_ROW_PK / QRM_SAVED_ANALYSES_ROW_U1 — The primary key constraint and unique index over (ANALYSIS_NAME, SEQ_NO) that govern identity and uniqueness.
  • Parent saved-analysis definition table in QRM — The object that owns ANALYSIS_NAME and to which every row group belongs; joins are made on ANALYSIS_NAME.
  • QRM analysis results views and concurrent programs — Reporting and display components that read rows ordered by SEQ_NO.
  • Other QRM_SAVED_ANALYSES_* tables — Companion objects storing column headers and analysis metadata that align with the positional A, M, P, and CURR columns.
  • FND audit-related objects — Standard EBS audit columns (CREATED_BY, LAST_UPDATED_BY) reference FND_USER identifiers.