Search Results frm_reqset_pub_options_uk1

Overview

FRM.FRM_REQSET_PUB_OPTIONS is a transactional configuration table in the Oracle E-Business Suite FRM (report management) schema. It stores the publishing options defined for each report or document produced by a request set. Where a request set defines a sequence of concurrent programs to be run together, this table records how the output of each individual report within that set should be rendered, secured, and made available to end users — for example, whether output is delivered as PDF, Excel, or HTML, whether it is available immediately or held, and which XML Publisher template should be applied.

The table resides in the APPS_TS_TX_DATA tablespace and is populated and maintained by the Oracle Reports Manager and XML Publisher publishing framework. In Data Vault modeling terms, the metadata suggests this table behaves as a satellite that captures descriptive publishing attributes keyed to a composite business entity composed of the request set, report, stage, and sequence. It is classified heuristically as standalone, meaning no strong foreign key lineage beyond reference to FRM_PART_VALUE_SETS is documented, and it therefore functions primarily as a detail/attribute store rather than a central hub or link.

Key Information Stored

The four-column composite primary key (FRM_REQSET_PUB_OPTIONS_PK) consists of REQUEST_SET_ID, REPORT_ID, STAGE_NUMBER, and SEQUENCE_NUMBER. These same four columns form the unique index FRM_REQSET_PUB_OPTIONS_UK1, which the user searched for; this index enforces uniqueness of a publishing option record for a given report at a specific stage and sequence within a request set. All four are NUMBER(15) entity identifiers.

• TEMPLATE_CODE — the XML Publisher template code assigned to the report output.
• APPLICATION_SHORT_NAME — the application owning the template.
• OUTPUT_TYPE — the required output format (Excel, PDF, HTML, etc.).
• AVAILABILITY_TYPE and AVAILABILITY_DATE_TIME — control whether the document is available now, on hold, or at a scheduled date and time.
• DOCUMENT_ID — the last document identifier used to retrieve presentation location data.
• SECURITY_TYPE and SECURITY_CODE — the security model and its value set or literal values.
• PUBLISHER_TYPE — the publishing engine (XML Publisher or Report Manager).
• PRES_FUNCTION_ID, PRES_MENU_ID, PRES_MENU_ENTRY_SEQ, PRES_MENU_NAME, PRES_MENU_PATH — navigation and presentation metadata controlling how users locate the published report.
• PUBLISH_FLAG, DOCUMENT_TYPE, DOCUMENT_NAME, ARCHIVE_DATE — publication lifecycle attributes.
• OBJECT_VERSION_NUMBER and the standard WHO audit columns — concurrency control and audit trail.

VALUE_SET_ID carries a documented foreign key to FRM_PART_VALUE_SETS, supporting user-to-value security.

Common Use Cases and Queries

Typical scenarios include auditing the output configuration of a request set, tracing which template and publisher engine are attached to a report, and diagnosing why a published document is unavailable or misrouted. A representative query joins the table to value set information:

• Listing publishing options for a given request set: SELECT report_id, stage_number, sequence_number, template_code, output_type, availability_type FROM frm_reqset_pub_options WHERE request_set_id = :p_id ORDER BY stage_number, sequence_number;
• Resolving the security value set: SELECT p.report_id, p.security_type, p.security_code, v.value_set_name FROM frm_reqset_pub_options p, frm_part_value_sets v WHERE p.value_set_id = v.value_set_id;
• Reporting on publisher engine usage across all configured reports: SELECT publisher_type, COUNT(*) FROM frm_reqset_pub_options GROUP BY publisher_type;

Related Objects

• FRM_PART_VALUE_SETS — joined via VALUE_SET_ID to resolve user-to-value security definitions.
• FRM_REQSET_PUB_OPTIONS_UK1 — the unique index enforcing business-key uniqueness on REQUEST_SET_ID, REPORT_ID, STAGE_NUMBER, SEQUENCE_NUMBER.
• FRM_REQSET_PUB_OPTIONS_PK — the primary key constraint on the same four columns.
• Request set definition tables (FND_REQUEST_SETS and related stage/sequence tables) — provide the parent request set and report context via REQUEST_SET_ID and REPORT_ID.
• XML Publisher template repository objects (XDO_* tables) — referenced by TEMPLATE_CODE and APPLICATION_SHORT_NAME.
• FND_FORM_FUNCTIONS and FND_MENUS — referenced by PRES_FUNCTION_ID and PRES_MENU_ID for report navigation.