Results for “ptm_code”

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

Overview

OKL_CS_PROCESS_TMPLTS_UV is a user-facing (UV) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management. The view presents a denormalized, reporting-ready perspective of lease and finance process templates, combining template definitions from OKL_PROCESS_TMPLTS_V with human-readable lookup descriptions and AMV item (template) names.

The object is registered as VALID in ETRM metadata, signifying that Oracle supports its use for reporting and integration purposes. The "_UV" suffix indicates the view is intended for external consumption by reporting tools, interfaces, and possibly Oracle Business Intelligence (OBIEE), providing a stable interface layer over the underlying transactional structures. Its primary role is to expose process template configurations — including the process type, associated template, validity dates, and status — in a single queryable artifact.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, OKL_CS_PROCESS_TMPLTS_UV is defined over the following base objects:

• OKL_PROCESS_TMPLTS_V — the principal source table/view supplying template records, including PTM_CODE, JTF_AMV_ITEM_ID, EMAIL_SUBJECT_LINE, START_DATE, and END_DATE.
• JTF_AMV_ITEMS_VL — provides the TEMPLATE name (ITEM_NAME) correlated via ITEM_ID to JTF_AMV_ITEM_ID.
• FND_LOOKUPS — supplies the human-readable PROCESS description via LOOKUP_TYPE = 'OKL_PROCESSES' joined on PTM_CODE = LOOKUP_CODE.
• OKL_UTIL — a PL/SQL package whose GET_REC_STATUS function derives the record STATUS from START_DATE and END_DATE.
• FND_GLOBAL — the standard EBS package used for session/context resolution (org_id and related security context).

The joining logic ties a template code (PTM_CODE) to its lookup meaning and to its associated AMV item, producing a single row that is directly consumable without further lookup.

Key Columns

The view exposes fourteen columns. The following are the most significant:

• ID — surrogate primary key of the template record.
• ORG_ID — operating unit identifier, supporting multi-org security and filtering.
• OBJECT_VERSION_NUMBER — optimistic locking version used by OAF-based maintenance pages.
• PTM_CODE — the process template code, a lookup code in the OKL_PROCESSES lookup type. This is the value users search for to identify process templates.
• JTF_AMV_ITEM_ID — foreign key to the AMV item (the template body/content) associated with the process.
• EMAIL_SUBJECT_LINE — the subject line used when the template drives notification emails.
• START_DATE / END_DATE — effective date boundaries defining whether the template is active.
• PROCESS — the lookup meaning (business description) corresponding to PTM_CODE.
• TEMPLATE — the AMV item name resolved from JTF_AMV_ITEMS_VL.
• STATUS — derived via OKL_UTIL.GET_REC_STATUS, indicating whether the record is currently valid.
• UPPER_PROCESS / UPPER_TEMPLATE — uppercase variants of PROCESS and TEMPLATE, provided to support case-insensitive searching and LOV filtering.

Common Use Cases and Queries

The view is typically leveraged for reporting on process template configuration, troubleshooting why a particular template was or was not triggered, and building AMV-related integrations. Because it exposes a PTM_CODE column, users searching for "ptm_code" are typically looking for the template code tied to a specific process step or AMV item.

Typical query to list all currently active templates by process:

• SELECT process, ptm_code, template, start_date, end_date, status FROM apps.okl_cs_process_tmplts_uv WHERE status = 'Active' ORDER BY process;

To locate a specific template by its code (the common "ptm_code" search):

• SELECT ptm_code, process, template, email_subject_line, status FROM apps.okl_cs_process_tmplts_uv WHERE ptm_code = :PTM_CODE;

For case-insensitive pattern matching, the UPPER_PROCESS and UPPER_TEMPLATE columns avoid runtime UPPER() calls, which is useful in OAF LOVs and BIP reports:

• SELECT ptm_code, process, template FROM apps.okl_cs_process_tmplts_uv WHERE upper_process LIKE 'LEASE%';

In integration scenarios, the view can be joined to lease contract tables via PTM_CODE or JTF_AMV_ITEM_ID to determine which template body applied to a given process event, supporting audit and template-management reports in EBS 12.1.1 and 12.2.2 alike.