Search Results fnd_form_custom_scopes_n1

Overview

APPLSYS.FND_FORM_CUSTOM_SCOPES is a transactional configuration table in Oracle E-Business Suite that stores the scope definitions governing which form personalizations apply under Oracle Forms-based CUSTOM library rules. Each row identifies a scope — an industry, site, responsibility, or user — for which a particular custom rule registered in FND_FORM_CUSTOM_RULES is active. The table therefore acts as the audience-selection layer of the Forms personalization framework: FND_FORM_CUSTOM_RULES defines what custom behavior executes, while FND_FORM_CUSTOM_SCOPES defines who receives it.

The object resides in the APPLSYS schema with FND design data reference FND.FND_FORM_CUSTOM_SCOPES, occupies the APPS_TS_TX_DATA tablespace (PCTFREE 10), is marked VALID, and is exposed in both Oracle EBS 12.1.1 and 12.2.2. Ten columns are documented. The ETRM relationship data classifies the table heuristically as standalone; following Data Vault modeling conventions this would be treated as a hub-adjacent detail entity rather than a link or satellite, as it captures scope attributes without acting as an associative bridge between two business hubs.

Key Information Stored

The most significant columns are:

• RULE_ID — Foreign key to APPLSYS.FND_FORM_CUSTOM_RULES; identifies the parent personalization rule to which the scope belongs. This is the leading column of both indexes.
• LEVEL_ID — Numeric discriminator for the scope type: 10 = Industry, 20 = Site, 30 = Responsibility, 40 = User. A foreign key reference to MSD_LEVELS is documented.
• LEVEL_VALUE — The concrete identifier for the scope: the Industry ID, User ID, or Responsibility ID, interpreted according to LEVEL_ID.
• LEVEL_VALUE_APPLICATION_ID — The application owning the responsibility when LEVEL_ID = 30; disambiguates responsibility IDs that are only unique within an application.
• ZD_EDITION_NAME — The editioning discriminator used by the online patching architecture in 12.2.x.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns tracking creation and modification.

The surrogate business-key candidate is the unique index FND_FORM_CUSTOM_SCOPES_U1 over (RULE_ID, LEVEL_ID, LEVEL_VALUE, LEVEL_VALUE_APPLICATION_ID, ZD_EDITION_NAME). No single-column surrogate primary key is documented; uniqueness is enforced by this composite. A nonunique index, FND_FORM_CUSTOM_SCOPES_N1, on RULE_ID supports lookups by parent rule. The scope table itself references no other database object other than the documented MSD_LEVELS foreign key on LEVEL_ID.

Common Use Cases and Queries

Typical usage centers on auditing personalizations and confirming whether a given user or responsibility is affected by a rule. A representative query joins the scope table to its parent rules:

• Resolve all scopes for a rule: SELECT s.RULE_ID, s.LEVEL_ID, s.LEVEL_VALUE, s.LEVEL_VALUE_APPLICATION_ID FROM APPLSYS.FND_FORM_CUSTOM_SCOPES s WHERE s.RULE_ID = :rule_id;
• Find user-specific scopes: filter LEVEL_ID = 40 and join LEVEL_VALUE to PER_USERS.USER_ID.
• Find responsibility scopes: filter LEVEL_ID = 30 and join LEVEL_VALUE plus LEVEL_VALUE_APPLICATION_ID to FND_RESPONSIBILITY.
• Detect overly broad site scopes: LEVEL_ID = 20 rows represent site-wide personalizations, often flagged during upgrade or regression testing.
• Edition-aware reporting in 12.2.x: include ZD_EDITION_NAME predicates when querying through editioning views during online patching.

Because scope rows drive runtime form behavior, discrepancy reports comparing scopes across environments (DEV versus PROD) are a standard migration-validation technique.

Related Objects

The most significant related objects are:

• APPLSYS.FND_FORM_CUSTOM_RULES — Parent table; joined on FND_FORM_CUSTOM_SCOPES.RULE_ID = FND_FORM_CUSTOM_RULES.RULE_ID.
• MSD_LEVELS — Referenced by the documented foreign key on LEVEL_ID.
• APPLSYS.FND_FORM_CUSTOM_SCOPES# — The editioning base object underlying the 12.2.x editioning view FND_FORM_CUSTOM_SCOPES.
• FND_FORM_CUSTOM_ACTIONS — Sibling child of FND_FORM_CUSTOM_RULES describing executed actions.
• FND_FORM_CUSTOM_PROP_VALUES — Sibling table holding property assignments for the same rules.
• FND_RESPONSIBILITY — Joined on LEVEL_VALUE and LEVEL_VALUE_APPLICATION_ID for responsibility-level scopes.
• PER_USERS — Joined on LEVEL_VALUE for user-level scopes (LEVEL_ID = 40).
• FND_APPLICATION — Resolves LEVEL_VALUE_APPLICATION_ID to an application name.

Collectively, these objects form the Forms personalization data model, with FND_FORM_CUSTOM_SCOPES supplying the targeting criterion that binds each rule to its intended audience.