Search Results req_lines

Overview

APPS.POR_IFT_INFO_PKG is a Purchasing (POR) module package body that supports the Information Template (IFT) framework in Oracle E-Business Suite 12.1.1 and 12.2.2. Information Templates allow organizations to associate structured, template-driven attributes with purchasing documents such as requisition lines. The package is responsible for persisting attribute values entered against a requisition line and for assembling those values into a concatenated, human-readable text block that can be attached to the document as an informational attachment. In this way, the package bridges the template configuration metadata held in the POR_TEMPLATES and POR_TEMPLATE_ATTRIBUTES tables with the transactional requisition data held in PO_REQUISITION_LINES_ALL, and it produces formatted text output that buyers and suppliers can read on the document or its attachment.

The package is classified by ETRM as an OTHER API, meaning it is not formally documented as a public interface but is used internally by the purchasing application to render and store information template attachments. The excerpt header dates the file to 2005 and marks it "noship," consistent with its role as an internal implementation package. Its primary input key is the requisition line identifier, which ties every operation to a specific transactional line.

Key Procedures and Functions

• GET_ATTACH_TEXT — Concatenates all information template attribute codes and their corresponding values into formatted text associated with a given requisition line. It produces separate text blocks and display names for the "to supplier" and "to buyer" directions, allowing the same attribute set to be presented differently depending on audience. Internally it resolves attribute values that reference a value set by joining to FND_FLEX_VALUES and FND_FLEX_VALUES_TL to return the translated flex value meaning, falling back to the raw stored attribute value when no value set is defined. It also honors a preparer language parameter for multilingual rendering.
• ADD_INFO_TEMPLATE_ATTACHMENT — Creates the information template attachment against the requisition line, persisting the template attribute values and linking the resulting document to the line through the attachment and document tables. This procedure is the write-side counterpart to GET_ATTACH_TEXT.

Tables Accessed

The package reads and writes a defined set of template configuration and attachment tables. POR_TEMPLATE_INFO stores the per-requisition-line attribute values, joined to POR_TEMPLATES_ALL_B and POR_TEMPLATES_ALL_TL for template definitions and their translated names, and to POR_TEMPLATE_ATTRIBUTES_B and POR_TEMPLATE_ATTRIBUTES_TL for attribute definitions, prompts, and value set references. FND_FLEX_VALUES and FND_FLEX_VALUES_TL are queried to translate coded attribute values into descriptive meanings based on the configured value set. PO_REQUISITION_LINES_ALL anchors the operation to the requisition line being processed. FND_DOCUMENTS and FND_ATTACHED_DOCUMENTS are used to create and link the attachment record that carries the concatenated text.

Usage Notes

The package is invoked by the purchasing application rather than directly by end users. Typical invocation points include the requisition entry form and related Information Template flows, where buyers enter template attribute values that must be saved against the requisition line and rendered as an attachment. It may also be called from concurrent or batch processes that regenerate document attachments, and from custom extensions that need to reproduce the standard information template text. Because the package is an internal, unshipped API, customizations should treat its signature as subject to change across patch levels and should prefer the supported document attachment interfaces where available. Referenced by one other package, it sits near the lower layer of the IFT processing stack, and its language handling makes it suitable for multilingual deployments.