Results for “fnd_profile_cat_options”

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

Overview

FND_PROFILE_CAT_OPTIONS is an Application Object Library (FND) intersection table in the APPLSYS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. As its documented description states, it is the "Intersection table between FND_PROFILE_OPTIONS and FND_PROFILE_CATS." It therefore serves as the associative link that binds individual profile options to the categories used to group them within the Profile Options user interface and the System Administrator responsibility. The table is classified as VALID in ETRM and is a core structural component of the profile option framework that governs how runtime and administrative settings are organized across the EBS instance.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as a link. This is consistent with its structure: it records the many-to-many association between profile option categories and profile option definitions rather than storing descriptive attributes about either entity. Practitioners designing a warehouse layer over EBS should treat it as a relationship (link) table joining two business keys.

Key Information Stored

The table is documented with twelve columns in the ETRM 12.2.2 physical schema. The most significant are those forming the primary key and the foreign key relationships:

• CATEGORY_NAME — identifies the profile option category; foreign key to FND_PROFILE_CATS.
• PROFILE_OPTION_APPLICATION_ID — the application owning the profile option; part of the foreign key to FND_PROFILE_OPTIONS.
• PROFILE_OPTION_ID — the profile option identifier; with the application ID, completes the reference to FND_PROFILE_OPTIONS.
• APPLICATION_ID — the application associated with the category assignment; joined with CATEGORY_NAME to reference FND_PROFILE_CATS.
• DISPLAY_SEQUENCE — controls ordering of the option within its category when rendered.
• DISPLAY_TYPE — governs how the option is presented in the category list.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row provenance.
• ZD_EDITION_NAME — the editioning column supporting Online Patching in 12.2.x.

The surrogate primary key is defined by the constraint FND_PROFILE_CAT_OPTIONS_PK over (CATEGORY_NAME, PROFILE_OPTION_APPLICATION_ID, PROFILE_OPTION_ID, APPLICATION_ID). The documented unique index FND_PROFILE_CAT_OPTIONS_U1 (CATEGORY_NAME, APPLICATION_ID, PROFILE_OPTION_APPLICATION_ID, PROFILE_OPTION_ID, ZD_EDITION_NAME) represents the business-key candidate, extended by the editioning column in 12.2.2.

Common Use Cases and Queries

Administrators and developers query this table to determine which categories a given profile option belongs to, and conversely which options populate a specific category. A typical reporting query joins the intersection to both parent tables:

• List all options in a category: select from FND_PROFILE_CAT_OPTIONS where CATEGORY_NAME = :category, joining FND_PROFILE_OPTIONS for the user-facing option name.
• Resolve an option's categories: filter on PROFILE_OPTION_ID and PROFILE_OPTION_APPLICATION_ID.
• Control display order and type when replicating the System Administrator profile screen in custom reporting.
• Audit category membership changes using the WHO columns and, in 12.2.2, respect ZD_EDITION_NAME to isolate the runtime edition during patching.

Related Objects

The table depends on two parent objects through documented foreign keys, and is referenced by the profile administration UI and FND APIs:

• FND_PROFILE_OPTIONS — joined on PROFILE_OPTION_APPLICATION_ID and PROFILE_OPTION_ID.
• FND_PROFILE_CATS — joined on CATEGORY_NAME and APPLICATION_ID.
• FND_PROFILE_OPTION_VALUES — supplies the assignable values typically reported alongside category membership.
• FND_PROFILE_OPTIONS_VL — the translated view used to resolve option display names.
• FND_PROFILE_OPTION_LEVELS — defines the hierarchy levels against which categorized options are set.

Together these objects form the profile option subsystem that underpins configuration and personalization throughout EBS.