Search Results fnd_attachment

Overview

The APPS.AMS_ATTACHMENT_PVT package body is a private (PVT) API within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema, that provides the core attachment handling logic for Oracle Marketing (AMS) entities. The user search term fnd_attachment is directly relevant: this package wraps and orchestrates the Oracle Application Object Library (FND) attachment framework so that Marketing application objects — such as marketing campaigns, events, and deliverables — can be associated with documents stored in the generic FND documents infrastructure. The package name carries the _PVT suffix, which in Oracle's API design convention designates a private implementation layer. Public, invocable behavior is expected to be exposed through a corresponding _PUB wrapper, while this body encapsulates the insert, update, and delete operations against the FND attachment tables. The header comment string (amsvatcb.pls, version 115.15) confirms the file has been part of the AMS code line since 2004 and remains the underlying engine behind attachment persistence in Marketing forms. Its purpose is to standardize attachment creation against FND tables while enforcing the standard Oracle API state model through FND_API return status and message stack conventions.

Key Procedures and Functions

Three documented procedures constitute the API surface of this package body:

• CREATE_FND_ATTACHMENT — Inserts a new attachment record so that a document is linked to an owning AMS entity. The source excerpt shows this procedure accepting standard Oracle API parameters (p_api_version_number, p_init_msg_list, p_commit, p_validation_level) plus the outgoing status trio (x_return_status, x_msg_count, x_msg_data) and an attachment record structure. It returns both the document identifier and the attached document identifier as output parameters. Internally it uses cursors against FND_ATTACHED_DOCUMENTS_S to obtain the next primary key and to verify existence.
• UPDATE_FND_ATTACHMENT — Modifies an existing attachment linkage, for example when the associated file, short text, or descriptive metadata changes. It applies the same standard API control conventions.
• DELETE_FND_ATTACHMENT — Removes an attachment association, breaking the link between the AMS entity and the underlying FND document.

Supporting logic includes debug-level constants derived from FND_MSG_PUB.CHECK_MSG_LEVEL, enabling high, medium, and low debug tracing, and a package-level file name constant (amsvatcb.pls).

Tables Accessed

The package reads and writes the following documented objects via APPS synonyms:

• FND_ATTACHED_DOCUMENTS — the central linkage table associating a document with an entity (category and entity name/ID). Both existence checks and the final attachment records reside here.
• FND_ATTACHED_DOCUMENTS_S — sequence source used to generate the next attached document identifier.
• FND_DOCUMENTS — stores the document header, including media type and datatype.
• FND_DOCUMENTS_TL — holds translated document names and descriptions.
• FND_DOCUMENTS_SHORT_TEXT and FND_DOCUMENTS_SHORT_TEXT_S — store the inline short-text payload and its sequence identifier when the attachment is a text-type document.
• DUAL — used by the sequence cursors to select .nextval.

Usage Notes

Because this is a private package, it is not intended for direct invocation from custom code or concurrent programs. It is typically called from AMS public APIs, Marketing HTML forms, and other internal AMS packages — the metadata records that it is referenced by two other packages. Standard integration patterns should call the public wrapper rather than AMS_ATTACHMENT_PVT directly. When tracing attachment behavior, note that the x_document_id and x_attached_document_id outputs are the join keys for subsequent queries against FND_ATTACHED_DOCUMENTS.