Search Results fnd_folders_u2

Overview

APPLSYS.FND_FOLDERS is a foundational Oracle E-Business Suite table that stores metadata for every customized folder definition created within the Forms-based (FND) runtime environment. In Oracle EBS 12.1.1 and 12.2.2, a "folder" is a named, user-defined arrangement of fields, query criteria, and sort order applied to a form block. Each time an end user or administrator personalizes a folder and saves it, a row is inserted into this table. The table therefore functions as the repository of folder personalization that drives how a form window renders and queries data when that folder is opened.

From a dimensional modeling perspective, the heuristic Data Vault classification of FND_FOLDERS is hub-leaning. This suggests modeling FOLDER_ID as a hub key, with the descriptive attributes (NAME, OBJECT, WINDOW_WIDTH, flags, clauses) treated as satellite attributes and relationships to FND_FOLDER_COLUMNS and FND_DEFAULT_FOLDERS represented as links. This is a modeling suggestion based on the mined foreign-key topology, not a prescribed implementation.

Key Information Stored

FND_FOLDERS contains fourteen documented columns. Its surrogate primary key is FOLDER_ID (FND_FOLDERS_PK), a system-generated number that uniquely identifies each folder customization. Two unique indexes act as business-key candidates: FND_FOLDERS_U1 on FOLDER_ID and FND_FOLDERS_U2 on the composite of OBJECT, LANGUAGE, CREATED_BY, and NAME — the latter ensuring a given user cannot define two folders of the same name for the same object and language.

• FOLDER_ID — surrogate primary key; folder identifier referenced by child tables.
• OBJECT — the form object (block) that uniquely identifies the set of fields to which the folder applies.
• NAME — the user-visible folder name.
• LANGUAGE — language code for which the folder definition applies, supporting multilingual installations.
• CREATED_BY — the folder owner; combined with OBJECT, LANGUAGE, and NAME in the business key.
• WINDOW_WIDTH — stored width of the folder window, in inches.
• PUBLIC_FLAG — indicates whether the folder may be opened by users other than the owner.
• AUTOQUERY_FLAG — controls whether the window region performs an automatic query upon opening.
• WHERE_CLAUSE — a stored SQL WHERE fragment applied when the folder runs its query.
• ORDER_BY — the sort clause applied to the folder's result set.
• CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns providing audit lineage.

Common Use Cases and Queries

Administrators and developers query FND_FOLDERS to audit folder personalizations, migrate folder definitions between environments, troubleshoot form behavior, or identify public folders shared across users. A typical listing retrieves folders for a specific object:

• SELECT FOLDER_ID, NAME, PUBLIC_FLAG, AUTOQUERY_FLAG FROM FND_FOLDERS WHERE OBJECT = :p_object;
• Identifying owner-defined folders: SELECT NAME, CREATED_BY FROM FND_FOLDERS WHERE CREATED_BY = :user_id AND LANGUAGE = 'US';
• Reviewing stored query logic: selecting WHERE_CLAUSE and ORDER_BY to debug unexpected filtering or sort order in a form.
• Reporting on organizational folder usage: a GROUP BY on OBJECT counts how many customizations exist per form block, useful for personalization governance.

Because FND_FOLDERS is seeded through normal user activity rather than setup, it grows organically and is a common target of personalization cleanup and migration scripts.

Related Objects

Two child tables reference FND_FOLDERS via the FOLDER_ID column, confirming its hub role:

• FND_FOLDER_COLUMNS — join on FOLDER_ID; stores the individual column selections and ordering that make up each folder.
• FND_DEFAULT_FOLDERS — join on FOLDER_ID; designates which folder is the default for a given context.
• FND_FOLDERS_PK — the primary key constraint validating FOLDER_ID uniqueness.
• FND_FOLDERS_U1 / FND_FOLDERS_U2 — unique indexes enforcing the surrogate and composite business keys.

Together these dependencies make FND_FOLDERS the anchor point for folder personalization metadata in the APPLSYS schema.