Search Results jtf_amv_attachments_s

Overview

The APPS.JTF_AMV_ATTACHMENT_PUB package body is a public (PUB-classified) PL/SQL API that manages attachment records for the Oracle E-Business Suite Attachment Management and Viewing (AMV) framework. In EBS 12.1.1 and 12.2.2, this package provides the server-side runtime implementation of the business logic used to create, maintain, and validate attachments associated with AMV items. Attachments in the AMV model are stored as metadata records that link a document, URL, or file reference to a parent business entity or item, and this package is the supported programmatic entry point for performing those operations in a controlled, API-driven manner.

The body carries a VALID status in the APPS schema and is classified as a public API, meaning it is intended for invocation by other application modules and by customer extensions rather than being restricted to internal use. It is referenced by eight other database objects, indicating that it acts as a shared service across multiple AMV and attachment-aware components. As with all EBS PL/SQL APIs, this package participates in the standard API conventions by relying on the FND_API, FND_MESSAGE, FND_MSG_PUB, and FND_GLOBAL utilities for error handling, message retrieval, and session context.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. The core transactional operations are:

• CREATE_ACT_ATTACHMENT — Creates a new attachment record tied to an activity or item context, persisting the attachment metadata through the AMV tables.
• UPDATE_ACT_ATTACHMENT — Modifies the attributes of an existing attachment record, such as its descriptive or reference content.
• DELETE_ACT_ATTACHMENT — Removes an attachment record from the AMV repository.
• LOCK_ACT_ATTACHMENT — Acquires a lock on the attachment record to serialize concurrent modification and preserve data integrity during multi-step operations.
• VALIDATE_ACT_ATTACHMENT — Performs validation of the attachment data before commit, returning status through the standard FND message stack.

Supporting the record-oriented operations are the following helper routines:

• CHECK_ACT_ATTACHMENT_ITEMS — Verifies the item association for an attachment, confirming that the referenced item exists and is valid.
• CHECK_ACT_ATTACHMENT_RECORD — Validates the presence and integrity of the attachment record itself.
• MISS_ACT_ATTACHMENT_REC — Handles the condition where an expected attachment record is missing.
• COMPLETE_ACT_ATTACHMENT_REC — Finalizes or completes a partially populated attachment record, ensuring all required fields are supplied before the record is committed.

Tables Accessed

The package body reads and writes the following documented AMV tables, accessed through APPS synonyms:

• JTF_AMV_ATTACHMENTS — The base attachment table where attachment metadata records are stored and maintained.
• JTF_AMV_ATTACHMENTS_S — The companion sequence or secondary table used to generate and control the surrogate keys for attachment records.
• JTF_AMV_ITEMS_B — The AMV item base table, consulted to validate that each attachment is associated with a valid item.
• DUAL — The standard Oracle single-row utility table, used for simple evaluation and control-flow queries.

Usage Notes

JTF_AMV_ATTACHMENT_PUB is typically invoked by AMV-related forms and concurrent programs and by custom code that needs to attach documents or URLs to AMV items without manipulating the underlying tables directly. Because it is a public API, it should always be called in preference to direct DML against JTF_AMV_ATTACHMENTS or JTF_AMV_ATTACHMENTS_S, ensuring that validation, locking, and FND error handling remain consistent. Callers should follow the standard EBS API pattern: initialize the FND message stack, invoke the relevant procedure, inspect the return status and message stack, and commit only on success.