Search Results fnd_desktop_objects




Overview
Explore in AI Chat

Overview

FND_DESKTOP_OBJECTS is a core Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the icon definitions associated with Navigator objects, which are the functional menu entries and application shortcuts presented to end users in the EBS Navigator window (the "Applications" and "Functions" dashboard). Each row provides the graphical identity — an icon name resolved against the deployed icon directory — for a given Navigator object identified by OBJECT_NAME.

Functionally, the table acts as the icon attribute catalog for the Navigator. Application and function definitions registered in FND menus and FND_APPLICATION reference the desktop object by name, and the framework uses the stored ICON_NAME to render the appropriate glyph in the user interface. Because it centralizes icon assignments, administrators can modify branding or update graphics without altering the functional definitions themselves.

Under a heuristic Data Vault classification derived from the foreign-key topology, FND_DESKTOP_OBJECTS is hub-leaning. It is referenced by FND_USER_DESKTOP_OBJECTS, making it a stable business-key dimension anchored on OBJECT_NAME. In Data Vault modeling terms, this suggests treating OBJECT_NAME as the hub business key, with descriptive attributes such as ICON_NAME modeled in a satellite.

Key Information Stored

The documented physical schema for 12.2.2 contains seven columns. The most significant are:

  • OBJECT_NAME — The business key and primary/unique identifier of the desktop object. It is enforced by the unique index FND_DESKTOP_OBJECTS_U1 (also referenced as the primary key FND_DESKTOP_OBJECTS_UK1). This is the column joined by dependent tables.
  • ICON_NAME — The filename or logical identifier of the icon graphic displayed for the corresponding Navigator object. This is the table's principal descriptive payload.
  • CREATION_DATE — Timestamp when the icon record was first created.
  • CREATED_BY — User ID of the account that inserted the record.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification, used by audit and concurrent-program logic.
  • LAST_UPDATED_BY — User ID of the account that performed the last update.
  • LAST_UPDATE_LOGIN — Login ID associated with the last update, typically used for concurrent manager audit trails.

There is no separately generated surrogate primary key documented; OBJECT_NAME serves simultaneously as the business key and the enforced unique identifier.

Common Use Cases and Queries

The primary operational use case is auditing or customizing Navigator icon assignments. Administrators may query ICON_NAME to confirm which graphic is rendered for a given Navigator object, or to identify objects lacking a customized icon. A typical retrieval pattern is:

  • SELECT object_name, icon_name FROM fnd_desktop_objects WHERE object_name = :object_name;
  • SELECT object_name, icon_name FROM fnd_desktop_objects ORDER BY object_name;
  • Join to per-user preferences: SELECT d.object_name, d.icon_name FROM fnd_desktop_objects d, fnd_user_desktop_objects u WHERE d.object_name = u.object_name AND u.user_name = :user_name;

Reporting scenarios include validating that icon files referenced in ICON_NAME exist in the deployed icon directory, reconciling the count of desktop objects against the count of active Navigator functions, and identifying stale rows created by decommissioned applications. Change-tracking audits can leverage LAST_UPDATE_DATE and LAST_UPDATED_BY to detect unauthorized icon modifications.

Related Objects

The documented foreign-key relationship places FND_USER_DESKTOP_OBJECTS as the primary dependent table, joined on OBJECT_NAME (FND_USER_DESKTOP_OBJECTS.OBJECT_NAME → FND_DESKTOP_OBJECTS.OBJECT_NAME). This table stores per-user desktop object preferences, extending the global icon definition with user-level overrides. Other significant related objects in the FND schema include FND_APPLICATION and FND_MENUS, which define the Navigator objects themselves, and FND_USER, which identifies the accounts referenced by CREATED_BY and LAST_UPDATED_BY. Querying across these tables supports end-to-end Navigator configuration reporting and customization impact analysis.