Search Results frm_directory_b




Overview
Explore in AI Chat

Overview

FRM_DIRECTORY_B is the base table of the Oracle E-Business Suite Report Manager (FRM) module that stores the untranslated (language-independent) segments of the Report Manager directory hierarchy. In Oracle EBS 12.1.1 and 12.2.2, Report Manager organizes published concurrent request output, reports, and printable documents into a folder-like structure. That structure is physically split across a base table and a translation table: FRM_DIRECTORY_B holds the structural and administrative attributes of each directory node, while FRM_DIRECTORY_TL holds the language-specific directory names and descriptions. The "_B" suffix denotes the base, non-translated component of a translated (TL) entity pair. The table resides in the FRM schema and is classified as VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. FRM_DIRECTORY_B functions as the central anchor that multiple dependent tables reference through the DIRECTORY_ID key, and it carries descriptive attributes as well. It is also the parent in a self-referencing hierarchy through PARENT_ID, which gives it a recursive, tree-oriented character common to navigational folder structures.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists 12 columns. The most important are:

  • DIRECTORY_ID — the surrogate primary key defined by FRM_DIRECTORY_B_PK, uniquely identifying each directory node.
  • PARENT_ID — references the parent directory, establishing the recursive hierarchy of folders and subfolders.
  • SEQUENCE_NUMBER — controls the ordering of sibling directories within the same parent.
  • OBJECT_VERSION_NUMBER — the standard EBS optimistic-locking token used to detect concurrent updates.
  • ARCHIVED_FLAG — indicates whether a directory node has been archived and is hidden from normal navigation.
  • END_DATE — supports date-effective or soft-deletion semantics for the directory record.
  • ZD_EDITION_NAME — the editioning column associated with EBS 12.2 online patching, enabling edition-based redefinition during upgrade cycles.
  • CREATION_DATE, CREATED_BY — standard WHO columns recording when and by whom the directory was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns capturing the most recent modification.

The unique index FRM_DIRECTORY_B_UK1 spans (DIRECTORY_ID, ZD_EDITION_NAME), which reflects the 12.2 editioning model rather than an independent business key. There is no separate user-meaningful unique key in the base table because the human-readable directory name lives in FRM_DIRECTORY_TL.

Common Use Cases and Queries

Typical applications include navigating the Report Manager folder tree, mapping documents to their containing folders, and reporting on directory structure for administrative cleanup. A common traversal query joins the base and translated tables:

  • Directory listing: SELECT b.directory_id, t.directory_name, b.parent_id, b.sequence_number FROM frm_directory_b b, frm_directory_tl t WHERE b.directory_id = t.directory_id AND t.language = USERENV('LANG');
  • Child lookup by parent: SELECT directory_id FROM frm_directory_b WHERE parent_id = :parent_id ORDER BY sequence_number;
  • Document placement: join FRM_DOCUMENTS_B on DIRECTORY_ID to enumerate the documents contained in each directory.
  • Hierarchical reporting: use a CONNECT BY query on PARENT_ID to render the full tree, or a recursive WITH clause for editioning-aware reporting.

Related Objects

The following objects are the most significant dependents and companions of FRM_DIRECTORY_B:

  • FRM_DIRECTORY_TL — translation table; joins on FRM_DIRECTORY_TL.DIRECTORY_ID = FRM_DIRECTORY_B.DIRECTORY_ID, supplying directory names and descriptions.
  • FRM_DOCUMENTS_B — documents table; joins on FRM_DOCUMENTS_B.DIRECTORY_ID = FRM_DIRECTORY_B.DIRECTORY_ID, linking stored documents to their containing folders.
  • FRM_DIRECTORY_B_PK — the primary key constraint on DIRECTORY_ID enforcing uniqueness.
  • FRM_DIRECTORY_B_UK1 — the unique index on (DIRECTORY_ID, ZD_EDITION_NAME) supporting the 12.2 editioning model.
  • Report Manager concurrent programs and APIs — the FRM product layer that reads and writes this table when users create, move, or delete directories.

Together these objects form the structural backbone of the Report Manager hierarchy in both 12.1.1 and 12.2.2, with the editioning column being the principal difference in the later release.