Search Results delete_menuform_entries




Overview
Explore in AI Chat

Overview

APPS.FRM_REPOSITORY_MAINTENANCE is a PL/SQL package that belongs to the Oracle E-Business Suite Financial Reporting / FRM (Financial Reporting Manager) product family. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the package owner, a design pattern intended to respect the caller's security context when manipulating repository metadata. The package provides low-level maintenance routines for the FRM repository, whose menu structures, form function assignments, document definitions, and stored report LOBs are held in the underlying FRM and FND tables.

The predominant purpose of the package is deletion and cleanup of repository entries. Where administrators remove or reorganize reporting content in the FRM repository, or where a document must be re-created to overwrite a previously generated report, the package supplies the granular procedures needed to remove the dependent rows in a controlled sequence. The source header indicates the package was created in April 2010 (author DHVENKAT) and subsequently updated in November 2010 to support the overwriting of existing reports, delivered under Bug 8333050. The package is not referenced by any other documented package, which confirms that it is used as a utility layer invoked directly rather than as a shared dependency of the FRM application stack.

Key Procedures and Functions

The package exposes five documented procedures, all of which are oriented toward removal of repository metadata:

  • DELETE_MENU_ENTRIES — Deletes menu entries. This is the procedure matching the user's search term. It accepts a menu identifier and an entry sequence, allowing removal of a specific menu line rather than an entire menu definition. It is the finest-grained deletion routine in the package.
  • DELETE_FORM_ENTRIES — Deletes form entries associated with a given function identifier. This removes the linkage between FRM content and the corresponding FND form function.
  • DELETE_MENUFORM_ENTRIES — Deletes form entries scoped to a document identifier, operating at the document level rather than the function level.
  • DELETE_MARKED_ENTRIES — Removes all rows that have been flagged (marked) for deletion, providing a bulk sweep of pending deletions across the relevant repository tables.
  • DELETE_DOCUMENT_TIMEFRAME — Deletes a report pertaining to a particular time frame from a document. This procedure was introduced with the Bug 8333050 enhancement to permit regeneration and overwrite of an existing report without leaving orphaned time-frame data.

Because the ETRM extract truncates before the full body is shown, no parameter signatures beyond those documented for DELETE_MENU_ENTRIES and DELETE_FORM_ENTRIES are asserted here; the procedures should be treated as internal maintenance routines whose exact parameters are best confirmed against the deployed package specification in the target environment.

Tables Accessed

The package references the following tables through APPS synonyms:

  • FND_MENU_ENTRIES — Holds menu line definitions; read and deleted by DELETE_MENU_ENTRIES.
  • FND_FORM_FUNCTIONS — The form function registry; used to resolve and remove form entry linkages.
  • FRM_DOCUMENT_DETAILS — Document-level metadata for FRM repository content, central to the menu-form deletion logic.
  • FRM_DOC_PUB_OPTIONS — Publication options governing how documents are exposed to end users.
  • FRM_DOC_REVIEWERS — Reviewer assignments tied to documents, cleaned up when documents are removed.
  • FRM_REPOSITORY_LOBS and FRM_ARCHIVED_LOBS — Large object storage for current and archived repository content, including generated report payloads.

Usage Notes

This package is an internal maintenance utility. It is not exposed as a concurrent program and is not typically called from standard FRM forms at runtime; instead it is invoked by FRM administrative processes or by custom code performing repository surgery—for example, removing a menu entry, unlinking a form function, or purging a specific document time frame so that a report can be regenerated in place. Because the deletions cascade across interdependent FND and FRM tables, the procedures should be called in a deliberate sequence (menu entries, then form entries, then document-level cleanup), and all invocations should be performed within a controlled transaction with a prior backup of the affected rows. Customizations should reference the procedures by name only against the certified 12.1.1 and 12.2.2 code lines and should be re-validated after any FRM patch, since the package's Bug 8333050 behavior demonstrates that its scope can change between releases.