Search Results get_file_name

Overview

EDR_FILE_UTIL_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. The EDR prefix associates it with the EDR (Engineering Document Repository / Document Repository) product family, which governs file and attachment storage, version control, and metadata management within Oracle EBS. In releases 12.1.1 and 12.2.2 the package is documented as VALID and is classified as a PUB (public) API, indicating that its procedures are exposed for supported invocation by other application code and by custom extensions.

The package's business function is to provide a utility layer for retrieving descriptive and binary information about files registered in the EDR repository. Rather than forcing callers to query repository tables or the generic file-attachment infrastructure directly, EDR_FILE_UTIL_PUB centralizes common read operations: resolving a file's stored name, its version label, its category and author descriptors, general attribute values, and the actual file content held in the database. This makes it a reusable access point for both EDR internal subscription packages and external modules such as GR_ATTACH_DOCUMENTS_PKG.

Key Procedures and Functions

The ETRM documentation records six documented procedures and functions:

• GET_FILE_NAME — Returns the file name associated with a repository file record. Used by callers that need the logical or stored name of a document before download, display, or routing.
• GET_VERSION_LABEL — Returns the version label for a given file, exposing the versioning metadata maintained by the EDR repository.
• GET_CATEGORY_NAME — Returns the category name assigned to a file, enabling callers to present or filter documents by classification.
• GET_AUTHOR_NAME — Returns the author name recorded for a file, supporting audit, display, and ownership-related processing.
• GET_ATTRIBUTE — Returns a specified descriptive attribute value for a file, providing a generic accessor for repository metadata beyond the named getters above.
• GET_FILE_DATA — Returns the file content itself, resolving the binary payload for download, viewing, or transfer operations.

All six are read-oriented accessors; the metadata does not document any write or update behavior in this package.

Tables Accessed

Through APPS synonyms, the package references three documented tables:

• EDR_FILES_B — The base table holding the EDR file records. It supplies the file name, version label, category, author, and attribute values returned by the getter routines.
• FND_LOBS — The standard Oracle EBS large-object repository. GET_FILE_DATA resolves the file's binary content from this table.
• FND_USER — The application user table, used to resolve or validate the author identity associated with a file record.

Usage Notes

EDR_FILE_UTIL_PUB is typically invoked indirectly rather than called ad hoc. Within the EDR product, it is referenced by EDR_GENERAL_SUBS and EDR_TEMPLATE_SUBS, which are internal subscription packages that drive document repository processing. It is also referenced externally by GR_ATTACH_DOCUMENTS_PKG, indicating that attachment handling in the Grants module relies on this utility for file name and content retrieval.

Custom code should treat EDR_FILE_UTIL_PUB as a supported public API and call its functions to obtain file metadata and data instead of querying EDR_FILES_B or FND_LOBS directly; direct queries bypass any validation or profile logic the package may apply. Because the routines are read-only accessors, they are safe to call from forms, concurrent programs, OAF pages, and PL/SQL batch processes that need to display document details or stream file content. The package depends only on SYS.STANDARD and the APPS synonyms listed above, and its VALID status in both 12.1.1 and 12.2.2 confirms it remains available across those releases.