Search Results fnd_default_folders




Overview
Explore in AI Chat

Overview

FND_DEFAULT_FOLDERS is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) product, residing in the APPLSYS schema. It stores the default folder definitions that govern how Oracle Forms-based EBS screens present and organize records to end users. In Oracle EBS, a "folder" is a saved personalization of a form's block layout — including which columns are displayed, their order, width, and sort behavior. FND_DEFAULT_FOLDERS holds the templates from which such folders are instantiated, either as system-wide defaults or per-user defaults.

The table is registered as VALID in the ETRM inventory for both 12.1.1 and 12.2.2, and is part of the standard Applications technology stack rather than any specific functional module. Its heuristic Data Vault classification, derived from its foreign-key topology, is a link table: it sits at the intersection of a user or object context and a folder definition, resolving the many-to-many relationship between folder identity (FND_FOLDERS) and the application/form context in which the folder applies.

Key Information Stored

The documented physical schema exposes 10 columns. The most significant are:

  • FOLDER_ID — Foreign key to FND_FOLDERS. This is the business-key candidate identifying which folder definition the default row refers to. It is the principal join column for any folder-related reporting.
  • APPLICATION_ID — Foreign key to FND_APPLICATION. Identifies the Oracle EBS application (product) that owns the form context in which the default folder applies, such as Inventory, Purchasing, or General Ledger.
  • OBJECT — Names the form or object for which the default folder is defined. This is the functional discriminator that scopes a folder to a specific screen.
  • USER_ID — Identifies the user to whom a default folder applies. A NULL or sentinel value typically denotes a system-wide default rather than a personal one.
  • BEHAVIOR_MODE — Controls how the default folder behaves when the form opens (for example, whether it is applied automatically or presented as an option).
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns that provide audit lineage for the row.

The surrogate primary key is typically implemented via an internal ROWID or a system sequence; the documented anatomy emphasizes FOLDER_ID and APPLICATION_ID as the meaningful foreign-key references.

Common Use Cases and Queries

DBAs and functional administrators query FND_DEFAULT_FOLDERS to diagnose folder personalization issues, audit which users or applications have custom defaults, and migrate folder setups between environments. A representative join pattern is:

  • List all default folders for an application: SELECT f.folder_name, d.object, d.user_id, d.behavior_mode FROM fnd_default_folders d JOIN fnd_folders f ON f.folder_id = d.folder_id WHERE d.application_id = :app_id;
  • Find system-wide defaults (rows where USER_ID is null) to understand baseline form behavior.
  • Join to FND_APPLICATION to resolve the application short name for reporting.
  • Audit recently modified folders using LAST_UPDATE_DATE for change-tracking during implementations.

These queries support reporting on form-level UX configuration, supporting upgrades and testing cycles where folder behavior must be validated.

Related Objects

  • FND_FOLDERS — Parent table of folder definitions; joined on FOLDER_ID.
  • FND_APPLICATION — Application registry; joined on APPLICATION_ID.
  • FND_FORM — Defines the forms whose folders are referenced by the OBJECT column.
  • FND_USER — Resolves USER_ID values for personal default folders.
  • FND_FOLDER_COLUMNS — Companion table describing the columns belonging to each folder.