Results for “frm_directory_b_uk1”

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

Overview

FRM.FRM_DIRECTORY_B is a Report Manager (FRM) base table that stores the un-translated components of the Oracle E-Business Suite directory hierarchy. In Oracle EBS 12.1.1 and 12.2.2, the Report Manager module organizes published report output, concurrent program results, and documents into a navigable tree structure. FRM_DIRECTORY_B holds the language-independent attributes of that tree — identifiers, parent relationships, ordering, archival state, and standard WHO auditing columns — while the corresponding translated directory names reside in the companion table FRM_DIRECTORY_TL. The "_B" suffix confirms this is the base (non-translatable) table in a standard EBS MLS pair.

The table is registered as FND Design Data under FRM.FRM_DIRECTORY_B and resides in the APPS_TS_TX_DATA tablespace. Its primary key is FRM_DIRECTORY_B_PK, defined on DIRECTORY_ID. From a Data Vault modeling perspective, the FK relationship patterns classify this object as hub-leaning: it functions primarily as a persistent, uniquely identified entity registry (the directory node), referenced by dependent objects rather than acting as a transactional link or an attribute-only satellite.

The ETRM documentation exposes one unique business-key candidate, FRM_DIRECTORY_B_UK1, defined across (DIRECTORY_ID, ZD_EDITION_NAME). The investigation of the search term "frm_directory_b_uk1" refers to exactly this unique index, physically located in the APPS_TS_TX_IDX tablespace. Two non-unique indexes, FRM_DIRECTORY_B_N1 on END_DATE and FRM_DIRECTORY_B_N2 on ARCHIVED_FLAG, support archival and purge activity.

Key Information Stored

FRM_DIRECTORY_B comprises twelve documented columns. The most significant are:

• DIRECTORY_ID (NUMBER(15), mandatory) — the surrogate primary key and entity identifier across all applications. It is the join anchor for every dependent table and the first column of the FRM_DIRECTORY_B_UK1 unique index.
• ZD_EDITION_NAME — the edition component of the unique business-key candidate FRM_DIRECTORY_B_UK1 (DIRECTORY_ID, ZD_EDITION_NAME), supporting Edition-Based Redefinition on 12.2.x.
• PARENT_ID (NUMBER(15)) — the next higher level in the Report Manager directory structure; null when the row represents the root directory. This column defines the tree topology.
• SEQUENCE_NUMBER (NUMBER(15)) — the order of the directory within its parent, used to present siblings deterministically in the Report Manager UI.
• OBJECT_VERSION_NUMBER (NUMBER(15)) — the Applications Standard column enabling optimistic locking in a stateless environment.
• END_DATE (DATE) — the date the row is archived or deleted; indexed non-uniquely by FRM_DIRECTORY_B_N1.
• ARCHIVED_FLAG (VARCHAR2) — flag indicating whether the row is archived; indexed non-uniquely by FRM_DIRECTORY_B_N2.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO auditing columns capturing row provenance.

DIRECTORY_ID is unambiguously the surrogate primary key; the business-key candidate is the composite of DIRECTORY_ID and ZD_EDITION_NAME via FRM_DIRECTORY_B_UK1. No other column set in the documented metadata carries a uniqueness constraint.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the directory tree, listing active (non-archived) nodes, and tracing which directories contain documents. The canonical query retrieves the base rows directly:

• Tree traversal: select directories by PARENT_ID to walk the hierarchy, ordering siblings by SEQUENCE_NUMBER.
• Active directory listing: filter on ARCHIVED_FLAG and END_DATE IS NULL to return only live directories.
• Archival reporting: leverage FRM_DIRECTORY_B_N1 and FRM_DIRECTORY_B_N2 to identify nodes scheduled for purge.
• Document roll-up: join FRM_DOCUMENTS_B on DIRECTORY_ID to count or list documents per directory.
• Display-name resolution: join FRM_DIRECTORY_TL on DIRECTORY_ID to obtain translated directory names for a given language.

A representative pattern joining base and translated rows, using the primary key:

• SELECT b.DIRECTORY_ID, t.DIRECTORY_NAME, b.PARENT_ID, b.SEQUENCE_NUMBER FROM FRM.FRM_DIRECTORY_B b, FRM.FRM_DIRECTORY_TL t WHERE b.DIRECTORY_ID = t.DIRECTORY_ID AND b.ARCHIVED_FLAG IS NULL ORDER BY b.PARENT_ID, b.SEQUENCE_NUMBER;

Related Objects

FRM_DIRECTORY_B is a referenced parent within the FRM schema. The FK relationship data identifies two direct dependents, and the translation pair completes the standard MLS pattern:

• FRM_DIRECTORY_TL — references FRM_DIRECTORY_B via FRM_DIRECTORY_TL.DIRECTORY_ID → FRM_DIRECTORY_B. Holds translated directory names and descriptions.
• FRM_DOCUMENTS_B — references FRM_DIRECTORY_B via FRM_DOCUMENTS_B.DIRECTORY_ID → FRM_DIRECTORY_B. Associates published documents with their containing directory.
• FRM_DIRECTORY_B_PK — the primary key constraint on DIRECTORY_ID, enforced by the underlying unique index.
• FRM_DIRECTORY_B_UK1 — the unique index on (DIRECTORY_ID, ZD_EDITION_NAME) in APPS_TS_TX_IDX, the object referenced by the search term.
• FRM_DIRECTORY_B_N1 / FRM_DIRECTORY_B_N2 — non-unique indexes on END_DATE and ARCHIVED_FLAG respectively, supporting archival and purge access paths.

FRM_DIRECTORY_B does not itself reference any database object; it is a foundational parent within the Report Manager schema, and dependent EBS code and views resolve directory metadata through the DIRECTORY_ID foreign key.