Search Results upload_file

Overview

The APPS.EDR_FILES_PUB package is a public PL/SQL API belonging to the Oracle E-Records (EDR) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide a generic file upload management system for bringing files into the Oracle E-Business Suite and, where required, routing them for approval through the iSign repository. The package is classified as a PUB API, meaning it is intended for external consumption by forms, concurrent programs, and custom code rather than as an internal-only helper. The source header notes a build of 120.0.12000000.1 dated 2007, and the API version constant G_API_VERSION is initialized to 1.0.

The business entity associated with the package is EDR_ISIGN_FILE_UPLOAD, confirming that uploaded files become artifacts within the E-Records signatures and approvals framework. The documented display name, "Upload and request approval for a file," captures the two responsibilities of the API: persisting the binary content and, optionally, submitting that content into an approval workflow.

Key Procedures and Functions

The package exposes exactly one documented procedure, UPLOAD_FILE. It is the sole entry point and carries the full upload workload of the package.

• UPLOAD_FILE — Uploads a supplied file into the iSign repository. It accepts the file name, category, content type, version label, binary file data, file format, source language, and a description, together with a file-exists action that governs behavior when a file of the same identity is already present. A submit-for-approval flag controls whether the uploaded file is routed for approval as part of the same call. Ten generic attribute columns (attribute1 through attribute10) are provided for descriptive flexfield and customer-specific extensions. Audit columns such as created_by, creation_date, last_updated_by, last_update_login, and last_update_date allow the caller to stamp the record explicitly. The procedure returns a standard return status and message data pair for error and success reporting.

No additional procedures or functions are documented in the package specification.

Tables Accessed

The package operates through APPS synonyms against the following documented tables:

• EDR_FILES_B and EDR_FILES_B_S — the base and secondary (translation) tables that store the uploaded file records themselves.
• FND_DOCUMENTS, FND_DOCUMENT_CATEGORIES, and FND_ATTACHED_DOCUMENTS_S — the common attachment and document management infrastructure that integrates the uploaded file into the broader EBS document model.
• FND_LOBS — storage of the binary large object content associated with the document record.
• FND_DESCR_FLEX_COLUMN_USAGES — descriptive flexfield configuration consulted when validating or populating the generic attribute columns.
• DUAL — used for standard single-row evaluations and sequence or default resolution.

Usage Notes

EDR_FILES_PUB.UPLOAD_FILE is typically invoked from Oracle Forms within the E-Records and iSign user interfaces, from concurrent programs that batch-load files, or from custom PL/SQL integrations that need to place a document into the EBS file repository and optionally request approval. The p_called_from_forms flag indicates the API anticipates Forms-based callers and adjusts behavior accordingly.

Callers should supply a valid API version, decide the commit strategy through p_commit, and always inspect x_return_status and x_msg_data before proceeding. Because the API writes to the FND document and LOB tables, it should be invoked with the same care as any attachment API, and the file-exists action must be chosen deliberately to avoid unintended overwrites. The package is referenced by one other package, indicating it participates in a larger dependent call chain within the EDR product.