Search Results fnd_document_management




Overview
Explore in AI Chat

Overview

FND_DOCUMENT_MANAGEMENT is a PL/SQL package body owned by the APPS schema that provides the server-side URL-generation and HTML-rendering engine for Oracle E-Business Suite's Document Management (DM) framework. Document Management allows EBS forms and self-service pages to attach, view, check in/out, lock, and version files that are stored externally and registered in the Oracle Applications File Manager. Rather than embedding URL logic in each calling form, the DM framework centralizes it here, so that any module — a Forms-based professional UI, an OAF page, or a workflow notification — can obtain a correctly formed, security-aware Document Management URL by calling a single packaged API with the document identifier and product context.

The package is classified under ETRM as "OTHER" (not a public, frozen API), which is consistent with its role as an internal utility layer consumed almost exclusively by other Document Management components. The metadata confirms it is referenced by nine other database objects and depends on the FND_DM_* family of setup tables, the Workflow HTML and security packages (WFA_HTML, WFA_SEC, WF_CORE, WF_DIRECTORY, WF_PREF), and the standard Oracle PL/SQL Web Toolkit (HTF, HTP, OWA_UTIL, PLITBLM, UTL_HTTP).

Key Procedures and Functions

Roughly forty-two documented procedures and functions are grouped into three functional clusters:

No parameter lists are published in the ETRM record; callers should obtain signatures from the package specification on their release.

Tables Accessed

The package reads Document Management configuration and routing data through APPS synonyms:

HTF, HTP, OWA_UTIL, PLITBLM, and UTL_HTTP are invoked for HTML output and outbound HTTP calls rather than as data sources.

Usage Notes

FND_DOCUMENT_MANAGEMENT is invoked at runtime, not scheduled. Typical callers are the Document Management-enabled EBS forms (for example, the Attachments and DM toolbar in purchasing, order management, and HR), OAF pages in the self-service modules, and Workflow notifications that expose document links. Custom code should generally use the formally supported DM APIs rather than calling these URL builders directly, since the package is designated "OTHER" and may change between releases. Administrators configuring DM must keep FND_DM_PRODUCTS, FND_DM_FUNCTIONS, and the parameter syntax tables populated; if the syntax rows are missing, the URL generators return incomplete or failing links even though the package itself remains VALID. Because the package relies on UTL_HTTP and the Web Toolkit, the database and application tier must be configured for outbound HTTP access and the standard OWA PL/SQL gateway.