Search Results frm_doc_pub_options_uk1

Overview

FRM.FRM_DOC_PUB_OPTIONS is a transactional configuration table in the Oracle E-Business Suite (EBS) schema FRM, part of the Oracle ETRM / Report Manager publishing framework. It stores the document-specific publishing options that govern how a given report is published to the Report Manager repository. Each row represents the publishing configuration for one document (identified by DOCUMENT_ID) within a particular TIMEFRAME, controlling template selection, output format, availability, security, and the menu navigation used to launch the report.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. Its status is VALID and it is registered under FND Design Data as FRM.FRM_DOC_PUB_OPTIONS. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. In practice, however, the table's structure—a compound key (DOCUMENT_ID, TIMEFRAME) combined with descriptive attribute columns—makes it a natural candidate to model as a satellite attached to a document hub (keyed on DOCUMENT_ID), with TIMEFRAME functioning as a driving/effectivity key that produces multiple configuration versions per document over time.

Key Information Stored

The primary key is FRM_DOC_PUB_OPTIONS_PK, defined on the composite of DOCUMENT_ID and TIMEFRAME. The unique index FRM_DOC_PUB_OPTIONS_UK1 also covers (DOCUMENT_ID, TIMEFRAME) and is therefore the principal business-key candidate; the user's search for "frm_doc_pub_options_uk1" identifies precisely this constraint. Two non-unique indexes support filtering: FRM_DOC_PUB_OPTIONS_N1 on END_DATE and FRM_DOC_PUB_OPTIONS_N2 on ARCHIVED_FLAG. The most significant columns include:

• DOCUMENT_ID (NUMBER 15) and TIMEFRAME (VARCHAR2 240) — the composite unique key identifying the document and its effective timeframe.
• TEMPLATE_CODE (VARCHAR2 80) and APPLICATION_SHORT_NAME (VARCHAR2 50) — locate the XML Publisher template used to render the report.
• OUTPUT_TYPE (VARCHAR2 30) — the required output format (Excel, PDF, HTML, and so on).
• AVAILABILITY_TYPE (VARCHAR2 30) and AVAILABILITY_DATE (DATE) — control whether the document is available immediately, on hold, or at a specific date and time.
• SECURITY_TYPE (VARCHAR2 30) and SECURITY_CODE (VARCHAR2 240) — define the security model and the value set used to secure the report.
• PUBLISHER_TYPE (VARCHAR2 30) — the publishing engine (XML Publisher or Report Manager).
• FUNCTION_ID, MENU_ID, MENU_ENTRY_SEQ — link the report to the form function and menu entry used to launch it.
• END_DATE, ARCHIVED_FLAG, ARCHIVE_PERIOD_MONTHS — drive archival and lifecycle behavior.
• OBJECT_VERSION_NUMBER plus WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) — standard concurrency and audit tracking.

Common Use Cases and Queries

Typical usage centers on auditing and reconciling publishing configuration. A common pattern retrieves the active configuration for a document:

• SELECT document_id, timeframe, template_code, output_type, publisher_type, security_type FROM frm.frm_doc_pub_options WHERE document_id = :p_doc_id;
• Detecting documents awaiting archival: WHERE archived_flag = 'N' AND end_date < SYSDATE;
• Reporting on output format distribution across the repository, grouping by output_type or publisher_type.
• Joining to FND_MENUS via MENU_ID to trace how a published report is navigated to from the menu structure.
• Identifying templates in use by joining TEMPLATE_CODE and APPLICATION_SHORT_NAME to XML Publisher template tables (XDO_TEMPLATES_B / XDO_LOBS).

Related Objects

The documented FK relationship links FRM_DOC_PUB_OPTIONS.MENU_ID to FND_MENUS, enabling jo

ins that resolve the menu entry and its position. Other significant related objects include:

• FND_MENUS — parent of MENU_ID; join on frm_doc_pub_options.menu_id = fnd_menus.menu_id.
• FND_FORM_FUNCTIONS — join via FUNCTION_ID to resolve the function used to launch the report.
• FND_MENU_ENTRIES — resolves the menu entry and entry sequence for the function.
• XDO_TEMPLATES_B / XDO_TEMPLATES_TL — resolve the TEMPLATE_CODE into the XML Publisher template definition.
• XDO_LOBS — stores the physical template file referenced by TEMPLATE_CODE.
• FRM_DOCUMENTS / FRM_DOCUMENT_OPTIONS — the parent document registration tables joining on DOCUMENT_ID.