Search Results por_template_assoc




Overview
Explore in AI Chat

Overview

POR_TEMPLATE_ASSOC is a transactional configuration table owned by the ICX schema in Oracle E-Business Suite, operating within the Oracle iProcurement module. The object stores the association records that drive Self-Service Purchasing Information Templates — the configurable layouts that determine which informational regions, item attributes, and category-specific content appear to requisitioning users during the online shopping and checkout flow. Each row represents a discrete linkage between a template region and either an inventory item or a purchasing category, allowing administrators to tailor the information presented for different segments of the catalog.

Under the heuristic Data Vault classification mined from the documented foreign key structure, POR_TEMPLATE_ASSOC is modeled as a standalone object. This classification reflects that the table carries no declared foreign key relationships to parent entities within the documented schema and that its identity is self-contained through its own surrogate key. Practitioners designing a Data Vault or dimensional representation of iProcurement configuration data should treat this object as an independent satellite-like structure rather than as a dependent child of a larger hub.

Key Information Stored

The table comprises 24 documented columns, with the following carrying the substantive business content:

  • TEMPLATE_ASSOC_ID — the surrogate primary key, enforced through POR_TEMPLATE_ASSOC_PK. A unique index, POR_TEMPLATE_ASSOC_U1, also exists on this column, making it the dominant access path for direct row retrieval.
  • REGION_CODE — identifies the information template region to which the association applies. Along with the item or category discriminator, this column forms the logical business key documented as POR_TEMPLATE_ASSOC_UK, which determines the uniqueness of an association record.
  • ITEM_OR_CATEGORY_FLAG — a discriminator that indicates whether the association targets an inventory item or a purchasing category.
  • ITEM_OR_CATEGORY_ID — the identifier of the specific item or category referenced, interpreted in conjunction with ITEM_OR_CATEGORY_FLAG.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-column audit set, recording the creating and last-modifying user, timestamps, and login context.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns, available for customer-specific extensibility on the association record.

The distinction between the surrogate key and the business key is significant: TEMPLATE_ASSOC_ID provides stable, immutable row identity for joins and audit, while the combination of REGION_CODE, ITEM_OR_CATEGORY_ID, and ITEM_OR_CATEGORY_FLAG expresses the actual business meaning and enforces that a region is associated with a given item or category only once.

Common Use Cases and Queries

Typical usage centers on diagnosing why particular regions or item attributes do or do not appear during iProcurement requisition entry. A common diagnostic query retrieves all associations for a specific item:

  • SELECT template_assoc_id, region_code, item_or_category_flag FROM icx.por_template_assoc WHERE item_or_category_id = :item_id AND item_or_category_flag = 'ITEM';
  • Reporting on template coverage by category, joining REGION_CODE to the template region definition to confirm that all required regions are populated.
  • Auditing changes to template configuration by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • Extracting flexfield values (ATTRIBUTE1–ATTRIBUTE15) where customers have extended the template association for governed or site-specific behavior.

Because the table is configuration rather than transactional volume data, result sets are typically small and index-driven access through TEMPLATE_ASSOC_ID or the business-key columns is sufficient.

Related Objects

The documented metadata classifies POR_TEMPLATE_ASSOC as standalone, so no enforced foreign keys are recorded. In practice, the following objects are the most significant reference and dependency points:

  • POR_TEMPLATE_REGIONS — the template region definition, joined via REGION_CODE to resolve the region's display name and behavior.
  • POR_TEMPLATES — the parent template entity to which regions belong, providing the template-level context.
  • MTL_SYSTEM_ITEMS_B — joined on ITEM_OR_CATEGORY_ID where ITEM_OR_CATEGORY_FLAG indicates an item reference, to resolve item descriptions and attributes.
  • MTL_CATEGORIES_B — joined on ITEM_OR_CATEGORY_ID where the flag indicates a category reference.
  • POR_TEMPLATE_ASSOC_PK and POR_TEMPLATE_ASSOC_U1 — the primary key constraint and unique index that enforce row identity and business-key uniqueness.

Any interface or extraction that stages iProcurement template configuration should preserve TEMPLATE_ASSOC_ID as the durable key and treat REGION_CODE plus the item or category discriminator as the natural key for reconciliation.