Search Results edr_files

Overview

EDR_FILES_PUB is the public API package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the EDR product family (Electronic Data Reporting / E-Records), which supports the creation, transmission, and acknowledgment of electronic regulatory reports and associated binary file content. The package provides the externally callable interface through which application code uploads and registers report files into the EDR repository, linking the physical file content stored by the FND_LOBS and FND_DOCUMENTS infrastructure to the EDR transactional entity maintained in EDR_FILES_B and EDR_FILES_B_S. Because the object is classified as a PUB (public) API in the ETRM metadata, its procedures are intended to be invoked from outside the package itself — from forms, concurrent programs, or custom PL/SQL — rather than being called only internally within the EDR schema logic.

Key Procedures and Functions

The documented ETRM metadata for this package lists a single public procedure, UPLOAD_FILE. Its purpose is to accept a caller-supplied file and persist it as an EDR report attachment, performing the necessary coordination between the EDR base tables and the Oracle Attachment / document management framework. In operation, UPLOAD_FILE creates or updates the EDR_FILES_B record (and its _S translation row), registers the underlying document via FND_DOCUMENTS and FND_ATTACHED_DOCUMENTS, and stores the binary payload in FND_LOBS. No parameter list is documented in the supplied metadata, and none is asserted here; callers should obtain the authoritative signature from the live package specification in the target instance.

Tables Accessed

The dependency list and documented table references show that EDR_FILES_PUB reads and writes the following objects via APPS synonyms:

• EDR_FILES_B and EDR_FILES_B_S — the EDR file base table and its MLS/translation table, holding the report file header records.
• FND_DOCUMENTS and FND_DOCUMENT_CATEGORIES — used to create and categorize the attachment document entity that represents the uploaded file.
• FND_ATTACHED_DOCUMENTS_S and FND_DESCR_FLEX_COLUMN_USAGES — used to link the document to its owning EDR entity and to resolve descriptive flexfield context.
• FND_LOBS — stores the actual binary file content for the uploaded report.
• DUAL — used for singleton lookups and sequence/date derivation.

The package additionally calls into EDR_FILES_PKG, EDR_ERES_EVENT_PUB, EDR_TRANS_ACKN_PUB, FND_API, FND_MSG_PUB, FND_GLOBAL, FND_FLEX_EXT, FND_FLEX_DESCVAL, FND_MESSAGE, APP_EXCEPTION, and WF_EVENT to handle validation, message stacking, security context, and workflow event propagation.

Usage Notes

EDR_FILES_PUB is the standard integration point for programmatic uploads into the EDR file repository. It is typically invoked from EDR setup or reporting forms, from concurrent programs that ingest batches of regulatory files, and from custom PL/SQL that must register an externally generated file against an EDR report. The package is not referenced by any other database object, confirming that it is an entry-point API rather than an internal utility. Because it uses FND_API and FND_MSG_PUB, callers should expect standard EBS API conventions: an initialization of the FND_GLOBAL message context, error accumulation via the message stack, and a return status. The related _B_S object name variant, which is what search users often type, refers to the generated MLS/translation companion of the EDR_FILES_B table rather than a separate package. Consumers should rebuild or recompile against the in-instance package specification before coding, since the published ETRM excerpt documents only the UPLOAD_FILE procedure and no parameter metadata.