Results for “fnd_profile_cats”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_PROFILE_CATS is a core setup table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of Profile (Option) Categories, which are logical groupings used to organize FND_PROFILE_OPTION_VALUES and their associated profile options into meaningful families such as "Currency," "Security," "Personal Profile," or site-specific custom categories. Profile categories drive how profile options are presented in the System Administrator responsibility and how they are queried in the Define Profile Option form.

The table's documented row count of columns is nine, and its primary key is defined by FND_PROFILE_CATS_PK on the composite of (NAME, APPLICATION_ID). The heuristic Data Vault classification derived from the foreign-key topology is hub-leaning: the table behaves as a hub of category identities keyed by name and owning application, with dependent detail (translations and category-option mappings) modeled as satellites and links around it. This classification is a modeling suggestion only; the physical EBS schema is a normalized transactional model, not a Data Vault.

Key Information Stored

The documented columns are NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, APPLICATION_ID, ENABLED, and ZD_EDITION_NAME.

  • NAME — the business name of the profile category. Together with APPLICATION_ID it forms the primary key FND_PROFILE_CATS_PK and the first component of unique index FND_PROFILE_CATS_U1.
  • APPLICATION_ID — the application that owns the category; a foreign key to FND_APPLICATION. It is the second PK component and the second U1 column.
  • ENABLED — flag controlling whether the category is active and selectable in the profile setup UI.
  • ZD_EDITION_NAME — the editioning column used by EBS 12.2 online patching; it is the third component of FND_PROFILE_CATS_U1 and supports Edition-Based Redefinition.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY capture WHO columns maintained by the Oracle Forms trigger framework.

The surrogate/business key distinction here follows Oracle's standard pattern: no single surrogate column exists; the primary key is a natural composite (NAME, APPLICATION_ID). FND_PROFILE_CATS_U1 adds ZD_EDITION_NAME as the edition-scoped unique business key.

Common Use Cases and Queries

Administrators query FND_PROFILE_CATS to list available categories before assigning profile options, and developers join it to FND_PROFILE_CAT_OPTIONS and FND_PROFILE_OPTIONS_VL to render category-filtered profile setups. A typical query enumerates categories for an application:

  • SELECT name, application_id, enabled FROM applsys.fnd_profile_cats WHERE application_id = :app_id AND enabled = 'Y';
  • Join to the translation table: SELECT pc.name, pct.user_profile_option_name FROM fnd_profile_cats pc, fnd_profile_cats_tl pct WHERE pc.name = pct.name AND pc.application_id = pct.application_id AND pct.language = USERENV('LANG');
  • Reporting on category-to-option coverage: join FND_PROFILE_CAT_OPTIONS.CATEGORY_NAME and APPLICATION_ID back to this table to audit which profile options fall under each category.

These queries are common in profile-option migration scripts, personalization diagnostics, and upgrade impact assessments.

Related Objects

  • FND_PROFILE_CATS_TL — the translation (satellite) table; joined on NAME and APPLICATION_ID to provide language-specific category names.
  • FND_PROFILE_CAT_OPTIONS — the assignment (link) table mapping categories to profile options; joined via CATEGORY_NAME and APPLICATION_ID.
  • FND_PROFILE_OPTIONS / FND_PROFILE_OPTIONS_VL — the profile option definitions referenced through FND_PROFILE_CAT_OPTIONS.
  • FND_APPLICATION — source of APPLICATION_ID, providing application name and short name.
  • FND_PROFILE_OPTION_VALUES — actual profile values assigned at user, responsibility, or site level and grouped by category for reporting.

Together these objects form the profile-management cluster that governs option behavior across the EBS instance.