Search Results lov_region_code

Overview

POR_TEMPLATE_ATTRIBUTES_V is an Oracle iProcurement (ICX product family) view owned by the APPS schema and stored in the E-Business Suite database. It is documented in ETRM as the "Information Template Attributes View." Its purpose is to expose the attributes that make up iProcurement Information Templates — the configurable templates used at requisition entry to capture supplemental, non-catalog descriptive information such as internal notes, delivery instructions, or user-defined fields.

The view is a reporting and integration convenience object rather than a transactional table. It joins the generic Oracle AK (Attribute/Known) region definitions to the region item definitions that hold the attribute presentation metadata. Because the definition is filtered to the Information Template naming conventions (REGION_CODE LIKE 'IFT_%' and ATTRIBUTE_CODE LIKE 'IFT%'), the view isolates only attributes belonging to Information Template regions and excludes unrelated AK region items registered across other EBS modules. This makes it the preferred source for extracting template attribute metadata in custom reports, data extracts, and integration mappings without having to re-implement the join and filter logic.

Underlying Base Objects

Two synonym-referenced base objects are documented for this view: POR_TEMPLATE_ATTRIBUTES_B and POR_TEMPLATE_ATTRIBUTES_TL. The _B suffix denotes the base (language-independent) table, while the _TL suffix denotes the translation table holding user-facing attribute labels in each installed language. The published view text, however, selects from AK_REGION_ITEMS_VL ARIT and AK_REGION_ITEMS ARI, joined on REGION_CODE and ATTRIBUTE_CODE. The VL (view of language) object supplies the translated short and long attribute labels, and the base AK_REGION_ITEMS table supplies the operational metadata such as display sequence, default value, LOV region, required flag, and audit columns. The POR_TEMPLATE_ATTRIBUTES_B and _TL objects are the model-level anchors from which the iProcurement template metadata derives; POR_TEMPLATE_ATTRIBUTES_V surfaces the corresponding AK region item rows for those templates.

Key Columns

• ROW_ID — the ROWID of the underlying AK_REGION_ITEMS row; a unique physical identifier usable for direct row access.
• REGION_CODE — the Information Template region (always matching IFT_%), identifying which template or template section the attribute belongs to.
• DISPLAY_SEQUENCE — the numeric order in which the attribute is rendered within its template.
• ATTRIBUTE_CODE — the internal attribute identifier (matching IFT%).
• ATTRIBUTE_LABEL_SHORT — the abbreviated label shown where space is constrained.
• ATTRIBUTE_LABEL_LONG — the full descriptive label presented to the user; this is the column most frequently referenced by users searching for attribute_label_long.
• DEFAULT_VALUE_VARCHAR2 — the pre-populated value applied to the attribute at entry time.
• LOV_REGION_CODE — identifies the list-of-values region supplying valid choices, if the attribute uses an LOV.
• REQUIRED_FLAG — indicates whether entry is mandatory (Y/N).
• NODE_DISPLAY_FLAG — controls conditional presentation of the attribute node.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include listing all attributes for a given Information Template, reviewing labels during setup or localization, auditing required versus optional fields, and mapping attribute codes to display labels for downstream integrations.

To list all attributes and their long labels:

SELECT ATTRIBUTE_CODE, ATTRIBUTE_LABEL_LONG
FROM   APPS.POR_TEMPLATE_ATTRIBUTES_V
ORDER  BY REGION_CODE, DISPLAY_SEQUENCE;

To isolate the attributes of one template region:

SELECT ATTRIBUTE_CODE, ATTRIBUTE_LABEL_SHORT, ATTRIBUTE_LABEL_LONG,
       DEFAULT_VALUE_VARCHAR2, REQUIRED_FLAG, LOV_REGION_CODE
FROM   APPS.POR_TEMPLATE_ATTRIBUTES_V
WHERE  REGION_CODE = :p_region_code
ORDER  BY DISPLAY_SEQUENCE;

To find only mandatory attributes:

SELECT ATTRIBUTE_CODE, ATTRIBUTE_LABEL_LONG
FROM   APPS.POR_TEMPLATE_ATTRIBUTES_V
WHERE  REQUIRED_FLAG = 'Y';

Because the view is defined over AK region item data rather than transactional tables, queries are read-only and low risk. Custom reports should select ATTRIBUTE_LABEL_LONG for user-facing output and retain ATTRIBUTE_CODE and REGION_CODE as the stable keys for joining back to template definitions.