Search Results fnd_dm_repository_pkg




Overview

The APPS.FND_DM_REPOSITORY_PKG package is a restricted, internal Oracle E-Business Suite utility used by the Data Management (DM) framework. It provides a single access point for constructing the viewing URL of a document stored within the Data Management repository. The package is defined with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the definer, which is consistent with a low-level lookup helper that inherits the caller's security context.

The package header dates to early releases of the EBS file-attachment and document-management stack (the $Header comment references 2003 and the filename AFAKADMS.pls). It remains present and documented in ETRM metadata for both 12.1.1 and 12.2.2, confirming that its contract has been preserved across the 12.x line. Its scope is deliberately narrow: it resolves a repository node URL for a given document so that callers can render a hyperlink or navigation target without embedding repository-location logic themselves.

Key Procedures and Functions

  • GET_REPOS_DOC_VIEW_URL — Returns the Data Management repository URL used to view a document. The function accepts an inbound document identifier and returns a VARCHAR2 URL string. It encapsulates the mapping from an internal document reference to the externally usable view location, allowing forms, OAF pages, and concurrent logic to obtain a consistent URL without duplicating repository-path construction.

This is the only documented subprogram in the package; no overloads, private helpers, or additional public procedures are recorded in the ETRM metadata. Consistent with its single-purpose name, the function is intended purely as a URL resolver and is not documented to perform insert, update, or delete operations.

Tables Accessed

The package accesses the FND_DM_NODES table through an APPS synonym. This table stores the nodes that make up the Data Management repository hierarchy — that is, the folder and document entries that the repository presents to users. Resolving a view URL requires locating the node associated with the supplied document identifier and deriving the address from that node's stored attributes. Access is read-only in the documented behavior, since the function's sole purpose is retrieval of a URL rather than maintenance of repository structure.

Usage Notes

  • Invocation context. The package is an internal DM framework component. It is not exposed as a user-facing feature and is not referenced by any other documented package (0 dependents in ETRM). Callers are therefore expected to be Oracle's own Data Management forms, OAF regions, or repository-aware servlets rather than general application APIs.
  • Custom code. Because the function is public within the package specification and uses AUTHID CURRENT_USER, custom code can call APPS.FND_DM_REPOSITORY_PKG.GET_REPOS_DOC_VIEW_URL directly, but doing so couples the customization to an unsupported internal interface. Oracle does not document the parameter semantics beyond the document identifier, and the URL format is repository-configuration dependent.
  • Return value handling. Callers should treat the returned VARCHAR2 as a display or navigation target and should anticipate that it may not resolve to a valid address if the document or its repository node is unavailable. Null or unusable results should be handled defensively.
  • Upgrade behavior. Given its stability across 12.1.1 and 12.2.2, the function is unlikely to change in minor upgrades, but reliance on undocumented internals carries normal EBS customization risk.