Search Results fnd_user_desktop_objects




Overview
Explore in AI Chat

Overview

FND_USER_DESKTOP_OBJECTS is an 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 personal desktop objects that individual users have saved on the EBS Navigator, effectively persisting the shortcuts, favorites, and self-defined navigation entries that appear on a user's home page. Each row associates a saved Navigator document with a specific user, responsibility, and the underlying desktop object definition, producing a per-user, per-responsibility personalization layer over the shared object definitions held in FND_DESKTOP_OBJECTS.

The status of the object is VALID, and the table is classified as an Oracle EBS data object of type TABLE. The documentation notes it under the FND - Application Object Library product with the concise description "Documents saved by a user on the Navigator." From a Data Vault perspective, the mined relationship structure — a single primary key with several foreign keys resolving to independent parent entities — suggests a link classification, modeling the many-to-many associations between users, responsibilities, and desktop objects. This is offered as a modeling suggestion rather than a mandated design; in native EBS terms the table functions as an associative entity that records user-level personalizations.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is DESKTOP_OBJECT_ID, enforced through the FND_USER_DESKTOP_OBJECTS_PK constraint and also backed by the unique index FND_USER_DESKTOP_OBJECTS_U1, making it the primary business-key candidate. The most significant columns are:

  • DESKTOP_OBJECT_ID — surrogate primary key uniquely identifying each saved desktop object row.
  • USER_ID — identifies the user who owns the saved Navigator document; references FND_USER.
  • APPLICATION_ID and RESPONSIBILITY_ID — together identify the responsibility context in which the object was saved; reference FND_RESPONSIBILITY.
  • OBJECT_NAME — names the desktop object being saved; references FND_DESKTOP_OBJECTS.OBJECT_NAME.
  • FUNCTION_NAME — the function associated with the saved object, when applicable.
  • OBJECT_LABEL — the display label shown to the user on the Navigator.
  • PARAMETER_STRING — any parameters passed to the function or object when invoked.
  • SEQUENCE — controls the ordering of saved objects on the user's Navigator.
  • TYPE — categorizes the desktop object entry.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified each row and from which login.

Common Use Cases and Queries

Typical uses include auditing which users have saved which objects, identifying orphaned or stale personalizations after a responsibility or object change, and reporting on Navigator customization. A common pattern joins the table to FND_USER and FND_RESPONSIBILITY:

  • SELECT u.user_name, r.responsibility_name, d.object_name, d.object_label FROM fnd_user_desktop_objects d, fnd_user u, fnd_responsibility r WHERE d.user_id = u.user_id AND d.responsibility_id = r.responsibility_id AND d.application_id = r.application_id;
  • Count saved objects per user or responsibility: SELECT user_id, COUNT(*) FROM fnd_user_desktop_objects GROUP BY user_id;
  • Find rows referencing a specific object across all users: SELECT * FROM fnd_user_desktop_objects WHERE object_name = :object_name;
  • Detect stale entries where the parent desktop object no longer exists by outer-joining to FND_DESKTOP_OBJECTS.

Related Objects

  • FND_DESKTOP_OBJECTS — parent definition table joined on OBJECT_NAME.
  • FND_USER — parent user table joined on USER_ID.
  • FND_RESPONSIBILITY — parent responsibility table joined on APPLICATION_ID and RESPONSIBILITY_ID.
  • FND_USER_DESKTOP_OBJECTS_PK — primary key constraint on DESKTOP_OBJECT_ID.
  • FND_USER_DESKTOP_OBJECTS_U1 — unique index on DESKTOP_OBJECT_ID.