Search Results get_fetch_document_url

Overview

APPS.FND_DOCUMENT_MANAGEMENT is a server-side PL/SQL package that provides the integration layer between Oracle E-Business Suite forms, HTML pages, and external document management (DM) repositories. It abstracts the differences between registered document management products — such as Oracle Content Management, third-party DMS repositories, and file-system based stores — so that any EBS application can attach, retrieve, display, and version documents without coding product-specific logic. The package is declared AUTHID CURRENT_USER, meaning it executes under the privileges of the calling schema rather than the APPS schema, which allows it to be safely invoked from both OA Framework pages and Forms-based attachments windows.

The package is registered in ETRM 12.2.2 as API classification OTHER and exposes 42 documented procedures and functions. It is referenced by nine other packages, confirming its role as a shared infrastructure component rather than an application-specific API. The 12.1.1 source header (version 120.8) shows the same functional surface carried into 12.2.2 largely unchanged.

Key Procedures and Functions

The documented interface centers on URL and window generation for document operations. Each GET_*_URL function returns a URL (typically built with HTF/HTP) that the calling form or page renders as a hyperlink or launches in a browser frame.

• GET_SEARCH_DOCUMENT_URL — generates the URL for the document search window, allowing a user to locate a document within a chosen DM system.
• GET_CREATE_DOCUMENT_URL and GET_BROWSE_DOCUMENT_URL — build URLs for creating a new document and browsing the repository hierarchy.
• GET_DISPLAY_DOCUMENT_URL, GET_ORIGINAL_DOCUMENT_URL, and GET_FETCH_DOCUMENT_URL — construct URLs that render a document, open its original source file, or fetch it for processing.
• GET_CHECK_OUT_DOCUMENT_URL, GET_CHECK_IN_DOCUMENT_URL, GET_LOCK_DOCUMENT_URL, and GET_UNLOCK_DOCUMENT_URL — support version-control operations against repositories that maintain checkout state and locking.
• GET_DISPLAY_HISTORY_URL — produces the URL for version-history views.
• GET_LAUNCH_DOCUMENT_URL and GET_LAUNCH_ATTACH_URL — open a document or the attachment window directly from a toolbar or menu action.
• GET_OPEN_DM_DISPLAY_WINDOW and GET_OPEN_DM_ATTACH_WINDOW — the entry points most closely associated with the user search term get_open_dm_attach_window; these open the DM display and attachment windows respectively.
• CREATE_DISPLAY_DOCUMENT_URL — creates and returns a display URL in one step.
• SET_DOCUMENT_ID_HTML — writes document identifier markup into the HTML buffer.
• PACKDOCINFO and PARSEDOCINFO — serialize and deserialize document attribute records (the fnd_document_attributes record type covers identifier, name, type, filename, creator, updater, lock owner, size, status, and version fields).
• CREATE_DOCUMENT_TOOLBAR — renders the standard document operations toolbar.

Tables Accessed

The package reads DM configuration and product metadata through APPS synonyms. FND_DM_FUNCTIONS and FND_DM_FUNCTION_PARAMETERS describe the URL-generating functions and their parameter syntax; FND_DM_PRODUCTS identifies registered document management products; FND_DM_NODES stores repository node structure; and FND_DM_PRODUCT_FUNCTION_SYNTAX / FND_DM_PRODUCT_PARM_SYNTAX map each product to its supported operations and parameter formats. Output is generated through HTF, HTP, and OWA_UTIL; UTL_HTTP supports remote repository calls, and PLITBLM is used for PL/SQL table manipulation.

Usage Notes

FND_DOCUMENT_MANAGEMENT is normally invoked indirectly. EBS Forms attachment blocks call the GET_OPEN_DM_ATTACH_WINDOW and related URL functions when a user clicks the attachment icon, and OA Framework pages invoke them to render document links. Custom code may call the URL functions directly to embed document actions in bespoke pages, but the package depends on DM product registration data being correctly configured in the FND_DM_* tables, and on a functioning repository integration for the target product. Because the package runs AUTHID CURRENT_USER, custom callers must ensure the invoking schema has the necessary synonyms and grants.