Search Results delete_attachment

Overview

APPS.PER_FND_ATTACHMENT_PKG is a server-side PL/SQL package body that provides the attachment handling engine for Oracle Human Resources and related E-Business Suite products. Its documented purpose is to upload text or binary document content into the Oracle Application Object Library attachment tables, and to manage the resulting attachment records throughout their lifecycle. The package header comment identifies the file as pefdlpkg.pkb and restricts its use to internal development, meaning it is a supporting API rather than a public, supported interface. The package name combines the PER (Human Resources) product prefix with FND (Application Object Library) attachment functionality, reflecting its role as the bridge between HR entities such as persons and the generic FND_ATTACHED_DOCUMENTS framework. Because attachments in EBS are keyed by a five-segment primary key and a category, this package abstracts the complexity of writing both the attachment metadata and the underlying document data. It is classified as OTHER in the ETRM metadata and is referenced by seven other packages, confirming it is a widely reused internal dependency rather than a standalone utility.

Key Procedures and Functions

The documented API surface consists of seven procedures and functions:

• UPLOAD_ATTACHMENT — Uploads text or document content into the FND attachments table. It accepts person identity, datatype and category identifiers, descriptive attributes (title, description, file name, content type, function name, entity name), the payload (text, URL, or BLOB file data), the five primary key values, a usage type defaulting to 'O', and output parameters for the document identifier, an error message, and a return status.
• DELETE_ATTACHMENT — Removes an existing attachment record. This is the procedure users reach when searching for "delete_attachment".
• UPLOAD_IREC_DOCS — Uploads documents associated with iRecruitment records.
• ADJUST_IREC_DOCS — Adjusts or re-synchronises iRecruitment document records.
• IS_IREC_DOC_EXIST — A function that tests whether a given iRecruitment document already exists.
• DML_ON_LINK_TABLE — Performs insert, update, or delete operations against the attachment link table.
• UPDATE_ON_LINK_TABLE — Updates rows in the attachment link table.

Tables Accessed

The documented table reference is FND_ATTACHED_DOCUMENTS, accessed through an APPS synonym. This is the central table in the Oracle attachments model. It stores one row per attached entity, holding the category, datatype, the five primary key columns that identify the owning business object, the document identifier, the usage type (for example 'O' for owner versus other usages), and descriptive information. The upload path writes to this table; the delete path removes rows from it; the link-table procedures manipulate related linkage records that associate attachments with entities such as persons or iRecruitment records. Because the package is the single write point for these operations, it preserves referential and structural consistency for HR-side attachments.

Usage Notes

PER_FND_ATTACHMENT_PKG is ordinarily invoked indirectly. Oracle Forms attachment zones, the standard attachment UI, and product-specific flows such as iRecruitment document management call these procedures rather than issuing direct DML. Custom code should likewise call the package instead of inserting into or deleting from FND_ATTACHED_DOCUMENTS directly, so that all validation, sequencing, and status handling are applied. The presence of an error message and return status in the upload interface indicates that callers are expected to check status rather than assume success. Given the "Internal Development Use Only" access status and the seven dependent packages, the API should be treated as internal and subject to change; any custom integration should be validated against the target release, whether 12.1.1 or 12.2.2, before deployment. The delete_attachment procedure is the supported internal entry point for removing an attachment and should be preferred over manual deletion of attachment rows.