Search Results oks_report_templates_v




Overview
Explore in AI Chat

Overview

OKS_REPORT_TEMPLATES_V is a read-mostly presentation view in the APPS schema that exposes the XSLT report templates used by the Oracle Service Contracts (OKS) electronic renewal process. Electronic renewal generates and delivers contract renewal documents to customers, and the transmittal format is driven by XSLT style sheets held in the repository. This view provides a curated projection of the underlying template records, including identity, validity dates, reporting cadence, and audit columns, so that concurrent programs, Oracle Reports/BI Publisher queries, and integration endpoints can resolve the correct template for a given renewal run without directly touching the base table.

Because the view is owned by APPS and is documented as VALID in ETRM 12.2.2, it is safe to reference from custom concurrent programs, OAF-based extensions, and external integrations. The column TEMPLATE_SET_ID is the attribute most frequently searched by implementers, since it is the primary grouping key that ties a template to a specific template set definition used by the renewal engine.

Underlying Base Objects

The view is defined as a single-table projection over the synonym OKS_REPORT_TEMPLATES, which resolves to the base table in the OKS schema. The defining query is a straightforward SELECT with explicit column aliasing:

  • FROM OKS_REPORT_TEMPLATES RTMP — one row per report template assignment.
  • ROWID ROW_ID is preserved as a pseudo-column, allowing updatable-view behavior and row-level addressing.
  • All business and audit columns are passed through without transformation, joins, or aggregation, so the view is a near-1:1 mirror of the base table.

No joins to OKS template-set headers or contract tables are embedded in the view; referential resolution must be performed by the caller.

Key Columns

  • ROW_ID — the ROWID of the underlying base-table row.
  • ID — primary key of the template record.
  • REPORT_ID — identifier of the report the template applies to.
  • TEMPLATE_SET_ID — the template set the row belongs to; the primary grouping key for electronic renewal template selection.
  • TEMPLATE_SET_TYPE — classification of the template set (for example, the type governing which renewal documents are produced).
  • START_DATE / END_DATE — effective dating window during which the template is valid.
  • REPORT_DURATION / REPORT_PERIOD — scheduling attributes describing how long and how often the report output applies.
  • STS_CODE — status code indicating the lifecycle state of the template record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • OBJECT_VERSION_NUMBER — optimistic locking version, enabling safe concurrent updates through the view.

Common Use Cases and Queries

A typical requirement is to list all active templates for a given template set so that an electronic renewal run can select the correct XSLT:

  • SELECT id, report_id, template_set_type, start_date, end_date, sts_code
  • FROM apps.oks_report_templates_v
  • WHERE template_set_id = :p_template_set_id
  • AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

To audit recent changes to renewal templates, query by audit columns:

  • SELECT template_set_id, template_set_type, sts_code, last_updated_by, last_update_date
  • FROM apps.oks_report_templates_v
  • ORDER BY last_update_date DESC;

For integration diagnostics, join REPORT_ID to the report definition and resolve the template set header to confirm that the expected XSLT is bound. Because the view is a simple projection, it can be used in BI Publisher data models, custom concurrent programs, and REST/SOA integrations that must determine which renewal template is currently effective for a contract population.