Search Results fnd_top




Overview
Explore in AI Chat

Overview

FND_FORM_CUSTOM_RULES_PKG is an Oracle Application Object Library (FND) PL/SQL package that manages the storage of Forms Personalization metadata in Oracle E-Business Suite. Forms Personalizations allow administrators and developers to declare runtime modifications to an Oracle Forms-based application without modifying the underlying form module (for example, hiding fields, changing prompts, adding validations, or invoking custom logic). These personalizations are persisted as rows in the FND_FORM_CUSTOM_* tables and are loaded into the runtime forms engine. FND_FORM_CUSTOM_RULES_PKG is the programmatic interface used by the personalization loader (FNDLOAD) to clear existing definitions before replacement data is uploaded.

As declared (AUTHID CURRENT_USER), the package executes with the privileges of the invoking schema, which in practice is APPS. In EBS 12.1.1 and 12.2.2 the package shipped in the APPS schema and is documented in the ETRM with an API classification of OTHER — that is, it is not a supported public business API intended for direct customer calls, but an internal utility used by Oracle-supplied tooling and patching infrastructure.

Key Procedures and Functions

  • DELETE_SET — Deletes a set of Forms Personalization rules in preparation for upload of replacement data. The rule set is selected by two filters. The rule key filter limits deletes to rules tagged with a specified Rule Key, or to untagged rules when no key is supplied. The rule type filter restricts deletes either to a specified function (when the type indicates a function scope) or to a specified form (when the type indicates a form scope), using the corresponding function or form name parameter.

No other procedures or functions are documented for this package in the ETRM metadata.

Tables Accessed

The package operates against the Forms Personalization data model through APPS synonyms:

  • FND_FORM_CUSTOM_RULES and FND_FORM_CUSTOM_RULES_S — the base and language-specific rule definitions removed by DELETE_SET.
  • FND_FORM_CUSTOM_ACTIONS — the actions (steps) attached to each rule, deleted as dependent children.
  • FND_FORM_CUSTOM_PARAMS — the parameters passed to each action, deleted as dependent children.
  • FND_FORM_CUSTOM_SCOPES — the scope/ownership records (customer versus Oracle-shipped) associated with personalizations, which determine which rows are eligible for deletion.
  • DUAL — used for simple single-row queries or validation checks within the package body.

The package writes (deletes) primarily against the rules and their dependent action, parameter, and scope rows; it is therefore a maintenance routine rather than a query API.

Usage Notes

DELETE_SET is not intended for interactive or ad-hoc invocation. It is invoked by the personalization loader workflow driven by FNDLOAD and the loader configuration file $FND_TOP/pach/115/import/affrmcus.lct, which first removes a matching set of rules and then uploads the replacement definitions from the source file. This pattern allows Oracle to re-ship personalizations via patches without creating duplicates, and allows customers to migrate their own personalizations between instances.

Two conventions are critical. First, all personalizations shipped by Oracle are tagged with a Rule Key; customers should not use Rule Keys, precisely so that Oracle's later DELETE_SET operations (keyed on the Oracle tag) do not remove customer-authored rules. Second, when no rule key is supplied, DELETE_SET targets untagged rules — the customer-owned set — so an unqualified upload can overwrite customer personalizations.

Because the procedure is destructive and executes with CURRENT_USER privileges, calls should be confined to the loader, patch utilities, or carefully controlled migration scripts run as APPS. Customers requiring finer control should export existing personalizations through FNDLOAD before invoking any load that triggers DELETE_SET.