Search Results frm_document_details




Overview
Explore in AI Chat

Overview

FRM_DOCUMENT_DETAILS is a table in the FRM (Report Manager) schema within Oracle E-Business Suite, validated in both release 12.1.1 and 12.2.2. As its description states, the table stores detail-level information about a document or document set. In the Report Manager model, a document represents a published output or report artifact, and this table captures the granular, line-level context that describes how that document is scoped — for example, the timeframe and the expanded value against which a document was generated. It therefore acts as the child detail table beneath the document header, holding the specific selection criteria that produced a given output.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure suggests a satellite-leaning role: the table hangs off a parent business entity via a foreign key and stores descriptive, time-aware attributes rather than defining independent business keys. Analysts designing a warehouse layer over EBS should treat it as an extension of the document header rather than a standalone hub.

Key Information Stored

The table carries 14 documented columns. The most significant are:

  • DOCUMENT_ID — Foreign key to FRM_DOCUMENTS_B and the leading column of the primary key. It ties each detail row to its parent document.
  • TIMEFRAME — The temporal context (such as a period or accounting timeframe) for which the document detail applies.
  • EXPANDED_VALUE — The expanded selection value associated with the detail line.
  • FILE_ID — Identifier of the physical file or output artifact associated with the detail.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework to manage concurrent updates.
  • PE_SEGMENT and PE_SEGMENT_VALUE — Placement/parameter segment and its value, enabling segmented document selection.
  • ARCHIVED_FLAG — Indicates whether the detail row has been archived.
  • END_DATE — Effective end date for the detail record.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, populated automatically by the EBS who-column conventions.

The primary key, FRM_DOCUMENT_DETAILS_PK, is a composite surrogate key over DOCUMENT_ID, TIMEFRAME, and EXPANDED_VALUE. The unique index FRM_DOCUMENT_DETAILS_UK1 covers the same three columns (DOCUMENT_ID, TIMEFRAME, EXPANDED_VALUE), making it the documented business-key candidate that enforces uniqueness of a detail line within a document.

Common Use Cases and Queries

Typical scenarios include reconciling a report output to its selection criteria, auditing which timeframes or segments produced a document, and reporting on archived versus active document details. A common query joins the detail rows back to the document header:

  • Retrieve all details for one document: SELECT * FROM frm.frm_document_details WHERE document_id = :p_doc_id;
  • Join to the header for descriptive context: SELECT d.document_id, d.timeframe, d.expanded_value, b.name FROM frm.frm_document_details d, frm.frm_documents_b b WHERE d.document_id = b.document_id;
  • Filter active detail records: SELECT * FROM frm.frm_document_details WHERE archived_flag = 'N' AND (end_date IS NULL OR end_date > SYSDATE);
  • Aggregate detail counts per timeframe for a reporting period.

Because the table is keyed on document, timeframe, and expanded value, queries should always constrain on DOCUMENT_ID to exploit the primary key and avoid full scans on this potentially high-volume child table.

Related Objects

The most significant dependent and referenced objects are:

  • FRM_DOCUMENTS_B — Parent table; joined via FRM_DOCUMENT_DETAILS.DOCUMENT_ID = FRM_DOCUMENTS_B.DOCUMENT_ID. This is the sole documented foreign-key relationship.
  • FRM_DOCUMENTS_TL — Translation table for document names/descriptions, joined through the base document ID for multilingual reporting.
  • FRM_DOCUMENT_DETAILS_PK / FRM_DOCUMENT_DETAILS_UK1 — The primary key constraint and unique index enforcing business-key uniqueness.
  • FRM_DOCUMENTS family of views and any Report Manager concurrent programs that publish or archive document output.
  • FND_ATTACHED_DOCUMENTS / FND_LOBS — Related attachment and file infrastructure that may be linked through FILE_ID for the underlying output artifact.

Consumers should treat FRM_DOCUMENT_DETAILS as the authoritative detail layer for Report Manager documents, always resolving document identity through FRM_DOCUMENTS_B.