Results for “template_id”

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

Overview

OKL_AM_ITEM_TEMPLATE_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Lease and Finance Management) product. Its documented purpose is to support the remarketing setup screen, where it displays templates for inventory items. In EBS 12.1.1 and 12.2.2, the view functions as a simplified presentation layer over Oracle Inventory's item template infrastructure, exposing only the subset of template attributes required by the Lease and Finance Management remarketing configuration flow.

Because the view is defined in the APPS schema and stores no data of its own, it acts as a lightweight pass-through: consumers querying OKL_AM_ITEM_TEMPLATE_UV see live data from the underlying Inventory table at the moment of execution. This makes the view suitable for both the standard remarketing setup form and for ad hoc reporting, integration extracts, and data validation scripts, without requiring callers to hold direct privileges on the base Inventory tables.

Underlying Base Objects

The view is defined with a single-table query. Per the documented metadata, the only referenced base object is MTL_ITEM_TEMPLATES, accessed in the APPS schema through a synonym. The view text is:

• SELECT TEMPLATE_ID, TEMPLATE_NAME, DESCRIPTION, CONTEXT_ORGANIZATION_ID FROM MTL_ITEM_TEMPLATES

MTL_ITEM_TEMPLATES is the Oracle Inventory table that stores reusable item attribute templates. Each row represents a template that can be applied when creating new inventory items, pre-populating attribute values and reducing manual entry. No joins, unions, aggregation, or database links are present in the view definition, so the relationship between the view and its base object is strictly one-to-one: every row in MTL_ITEM_TEMPLATES produces exactly one row in OKL_AM_ITEM_TEMPLATE_UV, with no filtering predicates applied.

Key Columns

• TEMPLATE_ID — Primary identifier for the item template. This is the key value passed by the remarketing setup screen when a specific template is selected, and it is the recommended join column when correlating the view to template attribute data elsewhere.
• TEMPLATE_NAME — The user-visible name of the template. This is the value rendered in template selection lists and value lists (LOVs) on the remarketing setup screen.
• DESCRIPTION — Free-form descriptive text explaining the intent or contents of the template, used to disambiguate similarly named templates.
• CONTEXT_ORGANIZATION_ID — The inventory organization context to which the template is scoped. This column is the attribute most frequently searched by users (as reflected in the common search term "context_organization_id"). It determines the organization-level visibility of the template and is the principal column for filtering template queries by operating unit or inventory organization.

Common Use Cases and Queries

The primary use case is the remarketing setup screen in Lease and Finance Management, which queries the view to populate the available item template list. Typical ad hoc and integration scenarios include filtering templates by organization context, joining template names to remarketing configuration data, and validating that templates exist before invoking item creation APIs.

• List all templates: SELECT template_id, template_name, description, context_organization_id FROM okl_am_item_template_uv ORDER BY template_name;
• Filter by organization context (matching the common search term): SELECT template_id, template_name, description FROM okl_am_item_template_uv WHERE context_organization_id = :org_id;
• Search by name pattern: SELECT template_id, template_name, context_organization_id FROM okl_am_item_template_uv WHERE template_name LIKE 'LEASE%';
• Join to downstream remarketing data by template: SELECT t.template_name, r.* FROM okl_am_item_template_uv t, okl_remarketing_setup r WHERE t.template_id = r.template_id;

Because the view applies no row filtering, queries should always include a CONTEXT_ORGANIZATION_ID predicate in multi-organization environments to avoid returning templates belonging to unrelated inventory organizations.