Search Results por_template_attributes_s




Overview

POR_IFT_ADMIN_PKG is the administrative PL/SQL package body owned by APPS in Oracle E-Business Procurement (Purchasing / iProcurement). It encapsulates the data-manipulation logic required to create, maintain, and delete supplier "IFT" (Inbound/Interface Template) template definitions and their associated attributes and associations. The package is classified as OTHER in the ETRM repository, indicating it is a supporting internal API rather than a formally published public interface. Its core purpose is to shield callers from the underlying multi-table model of the template schema: a base table (POR_TEMPLATES_ALL_B), a translation table (POR_TEMPLATES_ALL_TL), a sequence-driven template-code generator (POR_TEMPLATES_S), and the child attribute and association tables. The header comment records a version of 115.9 dated 2003/08/25, confirming the package has been stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package exposes fourteen documented program units, organised as families of insert, lock, update, and delete operations:

Tables Accessed

The package reads and writes nine documented tables through APPS synonyms. FND_LANGUAGES supplies the installed language set (INSTALLED_FLAG 'B' or 'I') used when seeding translation rows. POR_TEMPLATES_ALL_B is the base template header table, and POR_TEMPLATES_ALL_TL holds the language-specific template names. POR_TEMPLATES_S is the sequence that produces the numeric portion of each 'IFT_' template code. POR_TEMPLATE_ASSOC and POR_TEMPLATE_ASSOC_S store and sequence template-to-entity associations. POR_TEMPLATE_ATTRIBUTES_B, POR_TEMPLATE_ATTRIBUTES_TL, and POR_TEMPLATE_ATTRIBUTES_S hold, translate, and sequence the template attribute definitions.

Usage Notes

The ETRM metadata reports zero dependent packages, so POR_IFT_ADMIN_PKG is expected to be invoked directly rather than through another PL/SQL layer. In practice it is called by the Oracle Forms and OA Framework pages that administer inbound interface templates, and it may also be reached from concurrent programs or custom extensions that maintain template setup data. The package uses the standard EBS error-handling convention: the private l_progress variable tracks execution position, and the WHEN OTHERS handler calls po_message_s.sql_error before raising app_exception.application_exception. Callers should therefore expect the standard EBS exception contract and should not attempt to associate the raised error with an unrelated PL/SQL unit. Signature changes to any of these procedures are unlikely, given their long publication history.