Results for “ds_app_short_name”

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

Overview

FRM_DOCUMENTS_B is the base table that stores the un-translated portions of a Report Manager document within the Oracle E-Business Suite Report Manager (FRM) module. In Oracle EBS 12.1.1 and 12.2.2, the Report Manager subsystem manages publishing, distribution, and lifecycle of concurrent request output, and FRM_DOCUMENTS_B serves as the master (header) record for each document registered in that repository. Because the table stores language-independent data, all translatable descriptive attributes are held separately in the companion table FRM_DOCUMENTS_TL, following the standard EBS "_B"/"_TL" multilingual pattern.

The object is owned by the FRM schema and is documented as VALID, with a physical definition of 14 columns. Based on the foreign-key topology mined from the ETRM metadata, the table exhibits hub-leaning characteristics: it holds the durable identity of a document (its DOCUMENT_ID) and references a parent directory, while being referenced by dependent detail and translation tables. This suggests a Data Vault modeling classification of a hub, with FRM_DOCUMENT_DETAILS and FRM_DOCUMENTS_TL behaving as satellites or dependent child entities.

Key Information Stored

The table is anchored by its primary key, FRM_DOCUMENTS_B_PK, defined on DOCUMENT_ID. A separate unique index, FRM_DOCUMENTS_B_UK1, is also defined on DOCUMENT_ID, confirming it as the business-key candidate in addition to the surrogate identifier. The most significant columns are:

• DOCUMENT_ID — Surrogate primary key uniquely identifying each Report Manager document.
• DIRECTORY_ID — Foreign key to FRM_DIRECTORY_B, placing the document within the Report Manager directory hierarchy.
• SEQUENCE_NUMBER — Ordering attribute for documents within their parent context.
• EXPANDED_FLAG — Indicates whether the document node is expanded in the Report Manager tree display.
• DS_APP_SHORT_NAME — Application short name of the data source associated with the document.
• DATA_SOURCE_CODE — Code identifying the data source that produced or owns the document.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the EBS framework for concurrent update control.
• ARCHIVED_FLAG — Marks whether the document has been archived.
• END_DATE — Effective end date supporting date-tracked (datetracked) lifecycle management.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the row and when.

The "_B" designation confirms it holds base (non-translated) attributes only; user-facing names and descriptions reside in FRM_DOCUMENTS_TL.

Common Use Cases and Queries

Typical scenarios include reporting on published report documents, tracing a document to its directory, and reconciling document headers with their translated and detail rows. A representative join retrieves translated document identity against a directory:

• SELECT b.document_id, t.document_name, b.data_source_code FROM frm_documents_b b, frm_documents_tl t WHERE b.document_id = t.document_id AND t.language = USERENV('LANG');
• Join to FRM_DIRECTORY_B on b.directory_id = d.directory_id to list documents by directory.
• Filter active documents with b.end_date IS NULL and b.archived_flag = 'N' when reconciling the current Report Manager repository.

Because the table carries audit and datetrack columns, it also supports change audits of document registration and archival status over time.

Related Objects

• FRM_DIRECTORY_B — Parent table referenced via FRM_DOCUMENTS_B.DIRECTORY_ID; defines the directory containing the document.
• FRM_DOCUMENTS_TL — Translation table; references DOCUMENT_ID and holds translatable document text.
• FRM_DOCUMENT_DETAILS — Detail table; references DOCUMENT_ID and stores document-level detail rows.
• FRM_DOCUMENTS_B_PK / FRM_DOCUMENTS_B_UK1 — Primary key constraint and unique index on DOCUMENT_ID.
• Report Manager concurrent programs and publishing APIs — Create and resolve document headers recorded in this table during request output processing.