Search Results insert_template

Overview

POR_IFT_ADMIN_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the administrative application programming interface for the iProcurement (Internet Procurement) template framework. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner, a convention common to EBS public APIs that rely on APPS synonyms for data access.

The package governs the definition, maintenance, and translation of iProcurement templates and their constituent elements. A template in this context is a reusable configuration object that determines which attributes, such as descriptive flexfield segments, appear to requisitioners, in what sequence, with what default values, and whether they are mandatory. Through this package, administrators create and update both the template header and its attribute lines, associate templates with organizational or functional contexts, and register additional languages for multilingual deployments. The API is classified as OTHER, indicating it is not a general-purpose open interface but is instead intended for controlled invocation by Oracle Forms or by Oracle's own internal components.

Key Procedures and Functions

The package exposes fourteen documented procedures organized in logical groupings.

• Template header operations — INSERT_TEMPLATE creates a new template record, accepting identifying and organizational information and returning a generated template code and row identifier. LOCK_TEMPLATE obtains a pessimistic lock on an existing template to serialize concurrent modification, a standard EBS API pattern for optimistic concurrency control. UPDATE_TEMPLATE applies changes to an existing template, and DELETE_TEMPLATE removes it.
• Template attribute operations — INSERT_TEMPLATE_ATTRIBUTE, LOCK_TEMPLATE_ATTRIBUTE, UPDATE_TEMPLATE_ATTRIBUTE, and DELETE_TEMPLATE_ATTRIBUTE provide the parallel create, lock, modify, and remove lifecycle for individual attribute definitions within a template, including display sequence, default value, value set reference, required flag, and node display flag.
• Template association operations — INSERT_TEMPLATE_ASSOC, LOCK_TEMPLATE_ASSOC, UPDATE_TEMPLATE_ASSOC, and DELETE_TEMPLATE_ASSOC manage the relationships between templates and their assigned contexts. DELETE_ALL_TEMPLATE_ASSOC removes every association for a given template in a single operation.
• Translation support — ADD_LANGUAGE registers an additional language for template translation, populating the translation tables that back the multilingual template display.

Because the metadata documents only procedure signatures at a structural level, parameter lists are not reproduced here; each procedure is described solely by its functional role.

Tables Accessed

The package operates against the core iProcurement template schema objects, accessed through APPS synonyms. Header data resides in POR_TEMPLATES_ALL_B (base), POR_TEMPLATES_ALL_TL (translation), and the intersection table POR_TEMPLATES_S. Attribute definitions are stored in POR_TEMPLATE_ATTRIBUTES_B, POR_TEMPLATE_ATTRIBUTES_TL, and POR_TEMPLATE_ATTRIBUTES_S. Template associations are held in POR_TEMPLATE_ASSOC and POR_TEMPLATE_ASSOC_S. FND_LANGUAGES supplies the set of installed languages used by ADD_LANGUAGE. The _B/_S/_TL naming convention confirms that the package manages both transactional and translation data through EBS's standard multilingual architecture.

Usage Notes

POR_IFT_ADMIN_PKG is invoked principally by Oracle iProcurement administrative forms and by internal Oracle code, not by customer-written concurrent programs; the metadata records zero dependent packages, indicating its role as a leaf administrative utility. The search term lock_template corresponds directly to the documented LOCK_TEMPLATE procedure, which custom developers may encounter when diagnosing locking behavior during concurrent template edits. Any custom invocation should follow the standard sequence: lock, then insert, update, or delete, committing explicitly, since the package does not manage transaction boundaries on the caller's behalf.