Search Results get_attach_text




Overview

POR_IFT_INFO_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an OTHER API within the ETRM repository. Its functional purpose is to support the Information Template (IFT) feature in Oracle Purchasing, specifically as it applies to requisition lines. Information Templates allow buyers and administrators to define structured attribute sets that must be captured against a purchasing document, such as a requisition. The package bridges the gap between this structured template data, which is stored in the POR template tables, and the free-text or attachment-oriented representation that must be presented to users, suppliers, and downstream processes.

The package declares AUTHID CURRENT_USER, meaning its database objects and synonyms are resolved against the privileges of the calling user rather than the package owner. This is standard practice for EBS public APIs that must respect the calling session's security context. As of the 12.0 file header revision (PORIFTS.pls 120.0, dated June 2005), the package has remained stable across the 12.1.1 and 12.2.2 releases and exposes exactly two documented procedures.

Key Procedures and Functions

The package exposes two procedures, both central to requisition information template handling.

  • GET_ATTACH_TEXT — Concatenates all attribute codes and their corresponding values into a single text value for a given requisition line. It outputs two textual and two name-based results, distinguishing text intended for the supplier from text intended for the buyer. This allows the same underlying template data to be rendered appropriately depending on the audience and the preparer's language.
  • ADD_INFO_TEMPLATE_ATTACHMENT — Retrieves requisition lines that have associated information template data and creates the corresponding attachment records. The procedure accepts a requisition header identifier and a preparer language, and applies a default category identifier (33) when no category is explicitly supplied. This is the procedure most directly relevant to users searching for "add_info_template_attachment," since it is the entry point for materializing IFT content as document attachments on a requisition.

Tables Accessed

The package reads and writes across several FND and POR tables through APPS synonyms. FND_DOCUMENTS and FND_ATTACHED_DOCUMENTS are the core attachment infrastructure tables; ADD_INFO_TEMPLATE_ATTACHMENT inserts and maintains rows here to link generated attachment text to requisition entities. FND_FLEX_VALUES and FND_FLEX_VALUES_TL provide the descriptive flexfield value definitions and their translated descriptions, enabling attribute codes and values to be resolved into human-readable text. The POR_TEMPLATES_ALL_B, POR_TEMPLATES_ALL_TL, POR_TEMPLATE_ATTRIBUTES_B, and POR_TEMPLATE_ATTRIBUTES_TL tables hold the template and attribute definitions that drive the concatenation logic. POR_TEMPLATE_INFO stores the actual captured attribute values against the requisition. PO_REQUISITION_LINES_ALL supplies the requisition line context that ties everything together.

Usage Notes

Once installed, API users typically access this package through the standard public synonym, which points to the APPS schema. It is generally invoked from the Oracle Purchasing forms for requisitions, from concurrent programs that perform bulk attachment generation, or from custom extensions that automate information template processing. Only one other package references POR_IFT_INFO_PKG. Because the package relies on translated flexfield and template data, callers should supply the correct p_preparer_language to obtain properly localized output. Implementations should treat it as a supporting utility rather than a standalone business API, invoking ADD_INFO_TEMPLATE_ATTACHMENT after requisition lines and template values have been populated, and reserving GET_ATTACH_TEXT for rendering or export scenarios.