Results for “template_set_id”

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

Overview

OKS_REPORT_TEMPLATES is a Service Contracts (OKS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual report definitions that belong to a given template set, forming the configuration backbone that drives contract-related reporting and communication generation. Each row associates a specific report with a template set and carries scheduling, status, processing, and messaging attributes that govern how that report is produced and delivered.

From a Data Vault modeling perspective, the metadata relationships suggest this table leans toward a satellite classification. Its primary key (ID) is a surrogate, and it references OKS_TEMPLATE_SET through TEMPLATE_SET_ID (the only documented foreign key). The inclusion of descriptive, time-varying attributes such as STS_CODE, PROCESS_CODE, START_DATE, and END_DATE, plus audit columns (CREATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER), is characteristic of satellite-style descriptive data hanging off a parent template-set reference.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• ID — Surrogate primary key (constraint OKS_REPORT_TEMP_PK), uniquely identifying each report-template row.
• TEMPLATE_SET_ID — Foreign key to OKS_TEMPLATE_SET; the business relationship linking a report to its parent template set.
• REPORT_ID — Identifier of the underlying report definition that this row configures.
• TEMPLATE_SET_TYPE — Classifies the template set (and therefore the report context) the row belongs to.
• START_DATE / END_DATE — Effective period during which the report-template association is valid.
• REPORT_DURATION / REPORT_PERIOD — Timing attributes defining how frequently or over what span the report is generated.
• STS_CODE / PROCESS_CODE — Status and processing-state codes governing lifecycle of the report generation.
• APPLIES_TO — Indicates the applicability scope of the report.
• ATTACHMENT_NAME — Name of the associated attachment or output artifact.
• MESSAGE_TEMPLATE_ID — Reference to a message template used for notifications tied to the report.
• OBJECT_VERSION_NUMBER — Optimistic locking/versioning column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns.

The documented primary key is ID. No separate unique business-key index is documented in the provided metadata, though the natural business combination of TEMPLATE_SET_ID plus REPORT_ID is the likely candidate in practice.

Common Use Cases and Queries

Typical scenarios include enumerating all reports configured for a template set, validating active (in-effect) reports by date range, and auditing status/processing codes for reporting jobs.

• List reports for a template set:

  SELECT rt.id, rt.report_id, rt.template_set_type, rt.sts_code
  FROM   oks.okS_report_templates rt
  WHERE  rt.template_set_id = :template_set_id;

• Active reports as of a date:

  SELECT id, report_id, report_period
  FROM   oks.okS_report_templates
  WHERE  TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);

• Status/processing monitoring: aggregate by STS_CODE and PROCESS_CODE to detect stalled or failed report generation.
• Join to template-set header data to report the owning set name alongside each report.

Related Objects

• OKS_TEMPLATE_SET — Parent table; join on OKS_REPORT_TEMPLATES.TEMPLATE_SET_ID = OKS_TEMPLATE_SET.ID. The only documented foreign-key relationship.
• OKS_REPORT_TEMPLATES-referenced report definitions (via REPORT_ID) — the underlying report catalog entries consumed by these rows.
• Message template objects — referenced through MESSAGE_TEMPLATE_ID for notification generation.
• OKS service contract tables — contract and template-set usages that consume these configurations during report and communication generation.
• EBS audit/WHO columns — shared with standard FND-style auditing, enabling change tracking for compliance reporting.

Because the documented metadata exposes only the single FK to OKS_TEMPLATE_SET, additional dependencies should be confirmed against the 12.1.1/12.2.2 data dictionary before relying on them in production queries.