Search Results fnd_dm_products




Overview
Explore in AI Chat

Overview

FND_DM_PRODUCTS is a reference table residing in the APPLSYS schema of the Oracle E-Business Suite, owned by the FND (Application Object Library) product. Its documented purpose is to store the supported Document Management software products known to the EBS instance. Each row describes a distinct third-party or native document management product, along with the vendor, release version, and the communication protocol through which the EBS Document Management framework interacts with it. The table therefore acts as the master catalog consulted when the application must decide which document repository integration is available and how to address it.

From a Data Vault modeling perspective, the ETRM relationship classification for this object is hub-leaning. This is a heuristic suggestion rather than a documented constraint: the table carries a single-column surrogate primary key, no dependent descriptive attributes beyond a small stable set, and is referenced by a large number of foreign keys, which is characteristic of a hub entity. The table is marked VALID and is present in both EBS 12.1.1 and 12.2.2, where it continues to be defined as APPLSYS.FND_DM_PRODUCTS with a documented physical column count of five.

Key Information Stored

The documented physical schema of FND_DM_PRODUCTS contains five columns retained from the ETRM 12.2.2 metadata; the most significant are listed below.

  • PRODUCT_ID — The surrogate primary key, enforced by constraint FND_DM_PRODUCTS_PK and by the unique index FND_DM_PRODUCTS_U1. This is the integration identifier referenced by all dependent tables, and it is the business-key candidate for the hub.
  • PRODUCT_NAME — The descriptive name of the document management product as presented to the technical configuration layer.
  • VENDOR_NAME — The publisher or supplier of the product, used to distinguish offerings that share similar functionality.
  • VERSION — The release level of the product, which governs compatibility with the EBS Document Management adapter logic.
  • PROTOCOL — The transport or interface protocol through which the EBS framework communicates with the product, determining the integration mechanics.

Because the table is a narrow reference entity, it has no meaningful audit or transactional columns. Attribute history, where maintained, is held in the companion table FND_DM_PRODUCTS_TL, which carries the PRODUCT_ID foreign key back to this table.

Common Use Cases and Queries

Typical usage centers on confirming which document management integrations are enabled for a given instance and resolving a stored PRODUCT_ID to a human-readable product name. Administrators and integrators query the table when diagnosing attachment or document delivery failures, and support teams use it to verify that a referenced product is present before tracing downstream records.

A common lookup resolves the catalog in full:

  • SELECT PRODUCT_ID, PRODUCT_NAME, VENDOR_NAME, VERSION, PROTOCOL FROM APPLSYS.FND_DM_PRODUCTS ORDER BY VENDOR_NAME, PRODUCT_NAME;

Where translated names are required, the query joins to the translation table on PRODUCT_ID. Where the objective is to find all dependent records for a specific product — for example, all document management nodes configured for a product — the join uses FND_DM_NODES.PRODUCT_ID. A frequent validation pattern checks for orphaned foreign keys by left-joining dependent tables to FND_DM_PRODUCTS and filtering on a null primary key, which surfaces records referencing products that no longer exist in the catalog.

Related Objects

FND_DM_PRODUCTS is referenced by an unusually broad set of tables across multiple EBS products. The most significant dependencies documented in the ETRM relationship data are:

In all cases the join predicate is PRODUCT_ID equals the foreign key column of the same name, reinforcing the hub role this table plays within the FND Document Management subsystem and, through shared naming, across the wider EBS data model.