Search Results frm_user_pub_options_uk1

Overview

FRM.FRM_USER_PUB_OPTIONS is a transactional table in the Oracle E-Business Suite FRM (Reporting/Publisher) schema that stores the publishing options associated with a specific report for a specific user. Each row represents the personalised publishing configuration a user has established for a given report, capturing how the report should be rendered, secured, and made available when the user runs it from the EBS menu or form function. The table sits in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its uniqueness is enforced through the APPS_TS_TX_IDX index FRM_USER_PUB_OPTIONS_UK1.

From a heuristic Data Vault modelling perspective, this object is best classified as a satellite. The composite of REPORT_ID and USER_ID forms a natural parent key against which the descriptive publishing attributes — template code, output type, availability, security, and publisher settings — are stored as time-variant descriptive context. No foreign-key relationships to other hubs establish it as a link, and the metadata classifies it as a standalone table.

Key Information Stored

The primary key FRM_USER_PUB_OPTIONS_PK is defined on (REPORT_ID, USER_ID), the surrogate-grade pair that uniquely identifies each publishing option record. Independent of this, the unique index FRM_USER_PUB_OPTIONS_UK1 — which the search term references — is defined on (DOCUMENT_ID, REPORT_ID, USER_ID) and serves as the principal business-key candidate for the object.

• REPORT_ID / USER_ID — the entity identifiers that together form the composite primary key and scope each option set to a user-report pairing.
• TEMPLATE_CODE — the code of the XML Publisher template held in the template repository, controlling rendition of the report.
• APPLICATION_SHORT_NAME — the application short name bound to the template code.
• OUTPUT_TYPE — the required output format, such as Excel, PDF, or HTML.
• AVAILABILITY_TYPE / AVAILABILITY_DATE — whether the document is available now, on hold, or at a specific date and time; the date column carries the timestamp when the latter applies.
• DOCUMENT_ID — the last document id of a report of this type, used to retrieve presentation location data.
• SECURITY_TYPE / SECURITY_CODE — the security model applied and the values or value set used to secure the report.
• PUBLISHER_TYPE — the publishing engine, currently XML Publisher or Report Manager.
• VALUE_SET_ID — the value set id of the last value used for User-to-Value security.
• FUNCTION_ID / MENU_ID / MENU_ENTRY_SEQ — the form function, the menu entry to which it is attached, and its ordering within that menu.
• OBJECT_VERSION_NUMBER — the applications standard optimistic-locking column, alongside the standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reviewing a user's saved publishing preferences, auditing which templates and output types are in use, and troubleshooting reports that fail to launch because of availability dates or security settings. A frequent pattern is to join back to the report and user entities and to the referenced value set.

• Listing all publishing options for a user: SELECT report_id, template_code, output_type FROM frm_user_pub_options WHERE user_id = :p_user_id;
• Identifying reports held from availability: SELECT report_id, user_id, availability_type, availability_date FROM frm_user_pub_options WHERE availability_type = 'SPECIFIC DATE';
• Finding options secured by a particular value set, joining to FRM_PART_VALUE_SETS on VALUE_SET_ID.
• Resolving the menu navigation context by joining MENU_ID to FND_MENUS.

Related Objects

The following objects are significant because of documented foreign-key or key relationships:

• FRM.FRM_PART_VALUE_SETS — referenced by VALUE_SET_ID for User-to-Value security resolution.
• FND.FND_MENUS — referenced by MENU_ID to locate the menu entry through which the report function is launched.

Additional dependent objects include the FRM report definition tables identified by REPORT_ID, the FND user entity identified by USER_ID, and the XML Publisher template repository keyed by TEMPLATE_CODE and APPLICATION_SHORT_NAME. These objects complete the publishing context stored by FRM_USER_PUB_OPTIONS.