Results for “security_code”

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

Overview

FRM_DOC_PUB_OPTIONS is a Report Manager (FRM) application table in Oracle E-Business Suite that stores document-specific publishing options for reports distributed to the Report Manager repository. Each row defines how a particular published document behaves with respect to rendering templates, output format, availability windows, security, and menu-based access for a given timeframe. The table resides in the FRM schema and is marked VALID across EBS 12.1.1 and 12.2.2. Its physical schema is documented with twenty-two columns in ETRM 12.2.2.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This suggests the table is best treated as a self-contained satellite-like record keyed by a composite business key rather than as a hub or link participating in extensive referential relationships. The only documented outbound reference is to FND_MENUS, so the table functions largely as a configuration store rather than a transactional junction.

Key Information Stored

The composite primary key FRM_DOC_PUB_OPTIONS_PK is defined on (DOCUMENT_ID, TIMEFRAME), and a unique index FRM_DOC_PUB_OPTIONS_UK1 mirrors the same two-column business key. DOCUMENT_ID identifies the published report document, while TIMEFRAME scopes the option set to a specific publication or validity period.

• DOCUMENT_ID — foreign reference to the published document; part of the primary and unique key.
• TIMEFRAME — the temporal scope for which the option set applies; the second key component.
• TEMPLATE_CODE — the rendering template used when the document is published.
• APPLICATION_SHORT_NAME — the owning application, such as FRM or another product short name.
• OUTPUT_TYPE — the target output format produced for the document.
• AVAILABILITY_TYPE and AVAILABILITY_DATE — control when the published report becomes available to consumers.
• SECURITY_TYPE and SECURITY_CODE — govern access restrictions applied to the document.
• PUBLISHER_TYPE, FUNCTION_ID, MENU_ID, and MENU_ENTRY_SEQ — describe how the report is surfaced, including the menu function and menu placement.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and LAST_UPDATE_DATE — standard EBS audit and concurrency columns.
• END_DATE, ARCHIVED_FLAG, and ARCHIVE_PERIOD_MONTHS — support lifecycle and archival behavior.

Common Use Cases and Queries

Typical scenarios include auditing how a report is published, verifying which menu a document appears under, and reconciling availability or security settings across timeframes. Administrators query this table to troubleshoot why a published report is not visible or is secured unexpectedly.

A sample query to inspect options for a document:

• SELECT DOCUMENT_ID, TIMEFRAME, TEMPLATE_CODE, OUTPUT_TYPE, AVAILABILITY_TYPE, SECURITY_TYPE, MENU_ID FROM FRM.FRM_DOC_PUB_OPTIONS WHERE DOCUMENT_ID = :doc_id ORDER BY TIMEFRAME;
• SELECT DOCUMENT_ID, MENU_ID, PUBLISHER_TYPE FROM FRM.FRM_DOC_PUB_OPTIONS WHERE ARCHIVED_FLAG = 'N' AND MENU_ID IS NOT NULL;
• SELECT p.DOCUMENT_ID, p.TIMEFRAME, m.USER_MENU_NAME FROM FRM.FRM_DOC_PUB_OPTIONS p, FND_MENUS m WHERE p.MENU_ID = m.MENU_ID;

Related Objects

The most significant dependent and referencing object documented is FND_MENUS, joined on MENU_ID. Additional related objects within the Report Manager configuration family — including the parent document repository table referenced by DOCUMENT_ID and the FND function and menu-entry definitions referenced by FUNCTION_ID, MENU_ID, and MENU_ENTRY_SEQ — are commonly joined for reporting. Because the heuristic classification is standalone, relationships should be confirmed against the actual FRM data model for the target EBS release.