Search Results dom_attachment_util_pkg




Overview
Explore in AI Chat

Overview

APPS.DOM_ATTACHMENT_UTIL_PKG is a utility package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that centralizes the management of document attachments and repository-backed content. It belongs to the DOM (Documents) product family and operates as an internal utility layer that abstracts the complexity of managing rows across the FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, and FND_LOBS entity structures, along with the DOM repository configuration tables. In the EBS architecture, attachments may be stored as short text, long text, or as files held in a repository (for example, a WebDAV or Oracle Content Management repository). DOM_ATTACHMENT_UTIL_PKG provides the standardized programmatic interface through which other EBS modules create, link, copy, update, version, and delete these attachments without duplicating low-level DML logic.

The package is classified as a non-public API (OTHER). It is not intended as a standalone business interface but as a shared dependency used by higher-level components. ETRM documents ten procedures/functions and confirms the object status is VALID in the APPS schema.

Key Procedures and Functions

The documented routines cover the full attachment lifecycle:

  • CREATE_ATTACHMENT and ATTACH — Establish a new document record and associate (link) it to a business entity. CREATE_ATTACHMENT typically builds the underlying FND_DOCUMENTS row, while ATTACH links that document to a specific entity via the attached-documents tables.
  • DETACH — Removes the association between a document and its entity without necessarily deleting the underlying document.
  • UPDATE_DOCUMENT — Modifies document metadata or content stored in the short-text, long-text, or LOB structures.
  • CHANGE_VERSION — Creates or promotes a new version of an existing document, supporting version-controlled attachments.
  • CHANGE_STATUS — Alters the lifecycle status of a document, for example activating, obsoleting, or archiving it.
  • GET_REPOS_DOC_VIEW_URL — Returns the repository view URL for a document, used by the UI layer to render a hyperlink to repository-stored content.
  • DELETE_ATTACHMENTS — Purges attachment linkages (and, where applicable, associated document rows).
  • COPY_DOCUMENTS and COPY_ATTACHMENTS — Duplicate documents and their entity associations, supporting scenarios such as copying a quote with its attachments or replicating an entity across business flows. COPY_DOCUMENTS acts on the document master data, while COPY_ATTACHMENTS replicates the linkage records.

No parameter signatures are reproduced here, consistent with the documented API classification. Callers should obtain the exact specification from the package header in the EBS instance.

Tables Accessed

The package reads and writes a well-defined set of FND and DOM tables via APPS synonyms:

  • FND_DOCUMENTS, FND_DOCUMENTS_S, FND_DOCUMENTS_TL — Document master, security, and translation records; the foundation of every attachment.
  • FND_DOCUMENTS_SHORT_TEXT and FND_DOCUMENTS_LONG_TEXT — Textual content storage for short and long text attachments.
  • FND_LOBS — Binary large object storage for file-based attachment content.
  • FND_ATTACHED_DOCUMENTS and FND_ATTACHED_DOCUMENTS_S — The entity-to-document linkage and its security view.
  • DOM_FILE_EXT and DOM_REPOSITORIES — DOM configuration tables defining allowed file extensions and repository definitions.
  • FND_USER — Used to attribute creation and update actions to the acting user.
  • DUAL — Utility selection for scalar computations.

Usage Notes

DOM_ATTACHMENT_UTIL_PKG is invoked indirectly by higher-level EBS logic rather than directly by end users. ETRM confirms it is referenced by two other packages, notably EGO_IMPORT_UTIL_PVT (product data hub import) and ENG_ATTACHMENT_IMPLEMENTATION (engineering attachment handling), indicating its role in both engineering and item/product import flows. It is typically called from:

  • Attachment-enabled forms and OAF pages that create or manage attachments on entities.
  • Concurrent programs and import processes that must programmatically attach files to imported records.
  • Custom extensions that need to manipulate attachments without reimplementing FND document DML.

Because it is classified as OTHER rather than a public API, Oracle does not guarantee its interface across releases. Custom code that calls it should be reviewed during upgrades, and reliance on undocumented behavior or parameter lists should be avoided.