Search Results edr_template_subs




Overview
Explore in AI Chat

Overview

EDR_TEMPLATE_SUBS is an APPS-owned PL/SQL package within the Oracle E-Business Suite that supports the Electronic Document Repository (EDR) and, more specifically, the EDR Template Substitution behavior used by Oracle Procurement documents such as sourcing, RFQs, and purchasing. Its documented object status is VALID, and ETRM classifies the API as OTHER, indicating that it is not a formally published public API but an internal utility package that supports template attachment handling.

The business purpose of the package is to manage the association between documents and the templates used to generate or substitute them. Templates in Oracle Procurement allow predefined document content or attachments to be reused across requisitions, purchase orders, RFQs, and related sourcing artifacts. EDR_TEMPLATE_SUBS provides the procedural logic that links an attachment to a template, ensuring the appropriate file is stored, categorized, and retrievable through the standard attachments framework.

Key Procedures and Functions

The documented package exposes a single procedure:

  • UPLOAD_TEMPLATE — This procedure performs the insertion and registration of a template file into the EDR attachment repository. It handles the creation of the attachment record and its association with the relevant document category so the template becomes available for downstream substitution. The ETRM metadata does not publish the parameter list; consequently, callers should reference the package specification in the target environment rather than assume a signature.

No additional functions or procedures are documented. The package body and specification entries appear in the ETRM dependency listing, confirming that the package is compiled and that its internal logic is stored in the APPS schema.

Tables Accessed

The documented table references, resolved through APPS synonyms, are:

  • FND_ATTACHED_DOCUMENTS_S — the sequence source used by the attachments framework when creating new attachment identifiers. UPLOAD_TEMPLATE draws from this sequence to generate primary keys for the attachment rows it inserts.
  • FND_DOCUMENT_CATEGORIES — defines the valid attachment categories and their functional configuration. The procedure validates or resolves the appropriate category for the template being uploaded, ensuring the document is stored under a category that the EDR engine recognizes.
  • DUAL — used for singleton SQL expressions, typically for sequence invocation or value validation within the procedure body.

The package depends on the SYS STANDARD package, consistent with ordinary PL/SQL runtime behavior. It is not referenced by any other documented package, and its own dependency tree shows a self-reference, indicating internal calls within the package body.

Usage Notes

Because EDR_TEMPLATE_SUBS is classified as OTHER and is not referenced by other documented packages, it is normally invoked from within the EDR template setup and administration flows rather than from general custom code. Typical invocation paths include the Oracle Procurement template and attachment setup forms, where an administrator uploads a template document, and internal calls from other EDR logic that must register a template attachment on demand.

Developers integrating with EDR should treat UPLOAD_TEMPLATE as an internal routine. Direct invocation is possible in a custom concurrent program or form-based extension, but the caller must respect the current attachments schema, category configuration, and any standard who-column values expected by FND_ATTACHED_DOCUMENTS. Because the parameter list is not documented in ETRM, the authoritative interface should be read from the package specification in the target environment. The package is available in both Oracle EBS 12.1.1 and 12.2.2 with equivalent object metadata.