Search Results fnd_form_custom_scopes




Overview
Explore in AI Chat

Overview

FND_FORM_CUSTOM_SCOPES is a transactional configuration table in the Oracle E-Business Suite Application Object Library (product FND), owned by the APPLSYS schema. It stores the scope definitions that determine where a given Forms personalization rule — defined in FND_FORM_CUSTOM_RULES — is permitted to fire at runtime. In effect, this table partitions the applicability of each customization rule by organizational or reference level, so that a single personalization can be targeted to specific operating units, responsibilities, or other level instances rather than applying globally across an entire form.

The object carries no child dependencies in the documented schema and is classified heuristically as a Data Vault standalone structure, meaning it is neither a hub, link, nor satellite in the strict Data Vault sense. Modeling guidance would therefore treat it as a simple reference or detail table rather than a component of a modeled integration bus.

Key Information Stored

The table comprises ten documented columns. The most significant are:

  • RULE_ID — the foreign key to the owning personalization rule in FND_FORM_CUSTOM_RULES; identifies which customization this scope governs.
  • LEVEL_ID — a foreign key to MSD_LEVELS, identifying the reference level (for example, an operating unit, org, or security level) against which the scope is evaluated.
  • LEVEL_VALUE — the specific value of the referenced level for which the rule applies.
  • LEVEL_VALUE_APPLICATION_ID — the application context of the level value, disambiguating values that may collide across products.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified each scope row.
  • ZD_EDITION_NAME — the editioning column used by the Online Patching infrastructure in release 12.2, partitioning rows by edition.

The unique index FND_FORM_CUSTOM_SCOPES_U1 covers RULE_ID, LEVEL_ID, LEVEL_VALUE, LEVEL_VALUE_APPLICATION_ID, and ZD_EDITION_NAME. This composite is the business-key candidate; no single surrogate primary key column is documented.

Common Use Cases and Queries

Functional developers and administrators query this table to determine the effective scope of Forms personalizations, to troubleshoot why a personalization is or is not firing on a given form, and to audit customization coverage across operating units. A typical diagnostic join lists each rule alongside its scope:

  • SELECT r.RULE_ID, r.RULE_NAME, s.LEVEL_ID, s.LEVEL_VALUE FROM FND_FORM_CUSTOM_SCOPES s JOIN FND_FORM_CUSTOM_RULES r ON r.RULE_ID = s.RULE_ID ORDER BY r.RULE_NAME;
  • Filter by a specific level to identify every personalization touching a target operating unit: WHERE s.LEVEL_ID = :level_id AND s.LEVEL_VALUE = :value.
  • Reporting on customizations recently altered: WHERE s.LAST_UPDATE_DATE > SYSDATE - 30.

Because scopes are evaluated at runtime, missing or incorrect scope rows are a frequent cause of personalizations appearing to have no effect.

Related Objects