Search Results fnd_dm_functions_u2

Overview

APPLSYS.FND_DM_FUNCTIONS is a seed data table within the Oracle E-Business Suite Applications Object Library (AOL). It stores information about the functions supported through the Oracle Applications Object Library Open Interface, which underpins the document management capability used by products such as Oracle Marketing, Oracle Sales, and other modules that attach, declare, or manage documents. There is exactly one row in this table for each function supported by AOL's document management open API, making it a compact, low-volume reference table rather than a transactional table.

The object is owned by the APPLSYS schema, carries the FND design data designation FND.FND_DM_FUNCTIONS, and is stored in the APPS_TS_SEED tablespace, confirming its role as a seed or setup object delivered with the application. In ETRM 12.2.2 the table is documented with seven columns and is marked VALID. From a Data Vault modeling perspective, the mined relationship structure classifies this table as hub-leaning: FUNCTION_ID and FUNCTION_NAME form stable, non-volatile business keys around which dependent parameter and syntax tables cluster, while the descriptive attributes behave as satellite-style context.

Key Information Stored

The table is narrow but serves as the master list of document-management functions. The most significant columns are:

• FUNCTION_ID — the surrogate primary key (FND_DM_FUNCTIONS_PK), a numeric identifier for each document management function.
• FUNCTION_NAME — an 80-character business-key candidate, uniquely enforced by the FND_DM_FUNCTIONS_U2 index; this is the name a user or API references when invoking the function.
• SEQUENCE — the display ordering used when functions are presented to a user, where 1 is first and 100N is last.
• NEW_DOCUMENT_FUNCTION — a Y|N flag indicating the function is available only when a new document is being created.
• EXISTING_DOCUMENT_FUNCTION — a Y|N flag indicating the function is available only when a document has already been declared.
• RESOURCE_NAME — a 30-character name matching the corresponding entry in the WF_RESOURCES table, linking the function to the Workflow resource registry.
• ICON_NAME — a 30-character file name of the icon that represents the function in the user interface.

Both FUNCTION_ID and FUNCTION_NAME are backed by unique indexes (FND_DM_FUNCTIONS_U1 and FND_DM_FUNCTIONS_U2 respectively), so either can serve as a stable business key for downstream joins. The two document-context flags allow the API layer to filter the function list by document lifecycle state.

Common Use Cases and Queries

Typical usage centers on reporting the available document management functions, confirming which functions apply to new versus existing documents, and joining function metadata to parameter and syntax definitions. A common pattern retrieves the ordered function catalog:

• Selecting FUNCTION_ID, FUNCTION_NAME, and SEQUENCE ordered by SEQUENCE to reproduce the UI ordering of actions.
• Filtering by NEW_DOCUMENT_FUNCTION = 'Y' to enumerate functions exposed during document creation, or by EXISTING_DOCUMENT_FUNCTION = 'Y' for actions on declared documents.
• Joining RESOURCE_NAME to WF_RESOURCES.RESOURCE_NAME to reconcile the function list with Workflow resource definitions.

Because the table is seed data, queries are predominantly read-only. The following pattern, drawn from the documented query text, retrieves the full function definition and is safe to run directly against APPLSYS or the APPS synonym:

• SELECT FUNCTION_ID, FUNCTION_NAME, SEQUENCE, NEW_DOCUMENT_FUNCTION, EXISTING_DOCUMENT_FUNCTION, RESOURCE_NAME, ICON_NAME FROM APPLSYS.FND_DM_FUNCTIONS;

Reporting use cases include auditing the completeness of the document management catalog after an upgrade or patch, and verifying that RESOURCE_NAME values remain synchronized with WF_RESOURCES.

Related Objects

The documented dependency data shows FND_DM_FUNCTIONS does not reference any database object itself, but is referenced by dependent tables through FUNCTION_ID. The most significant related objects are:

• FND_DM_FUNCTION_PARAMETERS — references FND_DM_FUNCTIONS.FUNCTION_ID, holding the parameters accepted by each function.
• FND_DM_PRODUCT_FUNCTION_SYNTAX — references FND_DM_FUNCTIONS.FUNCTION_ID, storing product-specific syntax for invoking functions.
• APPS.FND_DM_FUNCTIONS — the APPS-schema synonym or view through which application code and queries typically access the table.
• WF_RESOURCES — correlated via the RESOURCE_NAME column, providing the Workflow resource definition behind each function.

These relationships confirm the table's role as a hub: it anchors parameter and syntax satellites while linking outward to the Workflow resource registry.