Results for “por_template_assoc_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

POR_TEMPLATE_ASSOC_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It is associated with the ICX product group, better known as Oracle iProcurement, and its stated purpose is to expose information template association data. In the iProcurement functional model, information templates define which descriptive attributes, regions, and content appear to a requisitioning user. The association record controls how a particular template is bound to a catalog item or to an entire category, so that the correct informational content is rendered when shoppers browse or search the catalog. This view presents that binding information in a denormalized form suitable for reporting, integration, and diagnostic queries without requiring direct joins to multiple EBS tables. The view is documented as VALID and is reported as depending on FINANCIALS_SYSTEM_PARAMETERS, MTL_SYSTEM_ITEMS_B, and POR_TEMPLATE_ASSOC, which indicates that it combines base association rows with item and system-parameter context. Because it surfaces the TEMPLATE_ASSOC_ID primary key, the view is frequently the first object referenced when a user searches for "template_assoc_id," typically in the course of troubleshooting template-to-item mappings or auditing catalog configuration.

Underlying Base Objects

The documented view text in ETRM shows that POR_TEMPLATE_ASSOC_V is defined as a direct projection of the base table POR_TEMPLATE_ASSOC, aliased PTA. Each column in the view maps one-to-one with a column in that base table, and the view adds no filter predicate in the excerpt. The ROW_ID column is generated from PTA.ROWID to provide a unique row identifier for the Framework-style toolkits used by Oracle Forms and iProcurement. The ETRM metadata for 12.2.2 additionally lists FINANCIALS_SYSTEM_PARAMETERS and MTL_SYSTEM_ITEMS_B as referenced base objects, which reflects the broader dependency graph of the template-association feature: MTL_SYSTEM_ITEMS_B supplies the item master context for ITEM_OR_CATEGORY_ID when the flag denotes an item, and FINANCIALS_SYSTEM_PARAMETERS supplies operating-unit and ledger context. These are accessed as synonyms in the APPS schema. The core transactional relationship, however, remains POR_TEMPLATE_ASSOC, making the view a thin presentation layer over that table.

Key Columns

• ROW_ID — The ROWID of the underlying POR_TEMPLATE_ASSOC row, used as a unique handle for user-interface and API operations.
• TEMPLATE_ASSOC_ID — The surrogate primary key of the association record. This is the value most users are looking for when they search for "template_assoc_id," and it is the key propagated to dependent tables and APIs.
• REGION_CODE — Identifies the template region to which the association applies, determining which area of the iProcurement page displays the configured content.
• ITEM_OR_CATEGORY_FLAG — A discriminator indicating whether the association targets a specific item or a category. This flag governs how ITEM_OR_CATEGORY_ID is interpreted.
• ITEM_OR_CATEGORY_ID — The identifier of the target item or category. When the flag indicates an item, this value generally corresponds to the item identifier in the item master context; when it indicates a category, it corresponds to a category identifier.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit and concurrency information for each association row.

Common Use Cases and Queries

Because the view is a straightforward projection of the base table, it supports fast, readable queries for auditing template associations in iProcurement. A common scenario is locating all associations for a given template region, or determining which items or categories are bound to a particular association identifier. For example:

SELECT template_assoc_id, region_code, item_or_category_flag, item_or_category_id
FROM por_template_assoc_v
WHERE template_assoc_id = :p_assoc_id;

Investigators frequently search by the identifier itself to confirm existence and context:

SELECT template_assoc_id, item_or_category_flag, item_or_category_id, last_update_date
FROM por_template_assoc_v
WHERE item_or_category_id = :p_item_id
AND item_or_category_flag = 'ITEM';

The view also supports reporting on configuration drift, for instance listing associations ordered by region to review coverage, and it can be joined to MTL_SYSTEM_ITEMS_B for descriptive item names when the association targets items. The absence of filtering in the view means it should not be treated as a security-restricted interface; consumers requiring operating-unit or item-secured results must apply those predicates themselves against the referenced base objects.