Search Results edr_files_pkg




Overview
Explore in AI Chat

Overview

EDR_FILES_PKG is an APPS-owned PL/SQL package that belongs to the Oracle E-Business Suite EDR (Electronic Document Repository / Engineering Document Repository) module family. Its business function is to provide the low-level data access layer for the EDR_FILES entity, which stores metadata about files (drawings, specifications, and other controlled documents) registered in the EDR repository. The package encapsulates the standard CRUD behavior for a translated (TL) entity: a base table for language-independent attributes, a translation table for language-dependent descriptive columns, and the associated language-installation logic.

The package is classified as a non-public API (API classification: OTHER) and its status within the ETRM 12.2.2 registry is VALID. It sits beneath the EDR_FILES_PUB public API layer, which is the sanctioned interface for external callers. EDR_FILES_PKG is referenced by two other packages, notably EDR_FILES_PUB and GMA_STANDARD, indicating that it underpins both the EDR document repository and the GMA (Process Manufacturing) standard utilities that consume EDR document metadata.

Key Procedures and Functions

The package exposes six documented procedures and functions that together implement the full lifecycle of an EDR_FILES record:

  • INSERT_ROW — Creates a new EDR_FILES record, writing the language-independent columns to the base table and the language-dependent columns to the translation table.
  • LOCK_ROW — Acquires a row-level lock on an existing EDR_FILES record, typically a prerequisite to UPDATE_ROW/DELETE_ROW within a transactional unit of work.
  • UPDATE_ROW — Modifies an existing EDR_FILES record, updating both the base and translation rows as needed.
  • DELETE_ROW — Removes an EDR_FILES record, including its associated translation rows.
  • ADD_LANGUAGE — Installs the translation rows needed to support an additional language for the entity's language-dependent columns.
  • CHECK_DOCUMENT_REFERENCES — Validates whether an EDR file/document is referenced by other entities before allowing deletion or modification, preserving referential integrity of the attached-document graph.

Tables Accessed

Per the ETRM metadata, EDR_FILES_PKG accesses the following tables through APPS synonyms:

  • EDR_FILES_B — The base table holding language-independent attributes for each registered file.
  • EDR_FILES_TL — The translation table holding language-dependent description columns keyed by language.
  • FND_ATTACHED_DOCUMENTS — The EBS attachments table, used to determine whether an EDR file is referenced as an attachment (supporting CHECK_DOCUMENT_REFERENCES).
  • FND_LANGUAGES — The language installation table, used by ADD_LANGUAGE to seed translation rows for installed languages.

Usage Notes

Because EDR_FILES_PKG is classified as OTHER (not a public API), callers should generally invoke the wrapper package EDR_FILES_PUB rather than calling EDR_FILES_PKG directly. Within the EDR application, EDR_FILES_PUB delegates row-level persistence to this package, and GMA_STANDARD also depends on it for process-manufacturing scenarios that attach EDR documents.

Typical invocations occur from OAF/JSP-based EDR file maintenance pages, from concurrent programs that bulk-load or migrate document metadata, and from custom extensions that manage file records. When developing custom code, developers should call the procedures within a properly initialized EBS session (FND_GLOBAL.APPS_INITIALIZE) and respect the LOCK_ROW/UPDATE_ROW/DELETE_ROW sequence to avoid concurrency issues. Direct DML against EDR_FILES_B or EDR_FILES_TL should be avoided because the package enforces the base/translation consistency, language installation, and document-reference checks documented here.