Results for “fnd_help_targets_u1”

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

Overview

FND_HELP_TARGETS is a reference table in the APPLSYS schema of Oracle E-Business Suite, belonging to the FND (Application Object Library) product family. It stores the definitions of on-line help targets, which are the mapping records that associate a named help topic (a target) with a specific help document file. In EBS releases 12.1.1 and 12.2.2, this table underpins the context-sensitive help infrastructure: when a user invokes help from a form or web page, the system resolves the requested help target name to an underlying document and renders the corresponding help content. Without this table, the application would have no persistent way to bind logical target names to physical help files.

From a Data Vault modeling perspective, the table demonstrates satellite-leaning characteristics. Its dependency on FND_HELP_DOCUMENTS via a foreign key suggests it functions primarily as a descriptive attribute holder attached to a help-document parent, rather than as a standalone business hub or an association link between independent hubs. Analysts designing downstream models should therefore treat it as a satellite keyed to the help document entity, while recognizing that the composite primary key introduces a degree of independent identity for the target itself.

Key Information Stored

The table is physically narrow, comprising only three documented columns. Each plays a distinct role in the help-resolution model:

• TARGET_NAME — The business identifier for a help target. This is the logical name referenced by the application at runtime when a user requests context-sensitive help. It forms the leading component of the composite primary key.
• FILE_ID — A foreign key to FND_HELP_DOCUMENTS, identifying the help document that satisfies the named target. This column links the abstract target name to a concrete file resource.
• ZD_EDITION_NAME — An edition-tracking column supporting the multi-tenant, edition-based redefinition architecture introduced for EBS 12.2 online patching. It permits the same logical target to exist in multiple editions.

The surrogate primary key is defined by FND_HELP_TARGETS_PK over (TARGET_NAME, FILE_ID). A unique index, FND_HELP_TARGETS_U1 over (FILE_ID, TARGET_NAME, ZD_EDITION_NAME), serves as the business-key candidate, ensuring that a given document cannot be registered twice under the same target name within an edition. Note that FILE_ID participates in both the primary key and the unique index, reinforcing the satellite relationship to FND_HELP_DOCUMENTS.

Common Use Cases and Queries

Typical usage centers on diagnosing help configuration, auditing document registration, and migrating custom help content. A common diagnostic query resolves a target to its document:

• Joining FND_HELP_TARGETS to FND_HELP_DOCUMENTS on FILE_ID to return the document behind a given TARGET_NAME.
• Detecting duplicate or orphaned registrations by grouping on TARGET_NAME and counting FILE_ID values.
• Listing all targets bound to a particular document to assess the impact of retiring or replacing help content.
• Filtering on ZD_EDITION_NAME during upgrade or patching cycles to validate that targets were correctly propagated across editions.

Reporting scenarios often combine this table with FND_HELP_DOCUMENTS to produce a complete inventory of help topics and files, supporting content governance and localization reviews. Because the table is small and static, queries are inexpensive and can be executed directly in a read-only session.

Related Objects

The most significant dependency is the foreign key relationship to FND_HELP_DOCUMENTS, joined on FILE_ID—this is the parent entity that supplies the physical document metadata. The primary key and unique index defined on FND_HELP_TARGETS themselves constitute the primary integrity objects. Because FND_HELP_TARGETS is a satellite-leaning object, its broader ecosystem includes the FND help subsystem tables that reference help documents and editions. Administrators investigating help configuration should join to FND_HELP_DOCUMENTS to reach file paths and document attributes, and should account for ZD_EDITION_NAME when comparing metadata across EBS editions. No other foreign keys are documented in the ETRM metadata, indicating that FND_HELP_TARGETS sits near the leaf of the help object graph and depends on, rather than is depended upon by, other FND entities.