Results for “cover_letter”

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

Overview

OKS_TEMPLATE_SET_V is a valid, APPS-owned database view within the Oracle E-Business Suite Service Contracts (OKS) module. It operates as a thin projection layer over the base table OKS_TEMPLATE_SET, exposing the full set of operational and audit columns required by concurrent programs, forms, and integration interfaces. The view exists primarily to provide a stable, named access point for template set data without requiring consumers to reference the physical table directly, shielding dependent code from storage-level changes to the underlying base object.

Template sets in Service Contracts represent user-defined groupings that control which contract templates are available to a service authoring flow — for example, restricting template selection by operating unit, by quote letter, or by cover letter defaults. Because downstream functionality such as contract creation, order capture integration, and multi-org reporting all require consistent access to this metadata, the view serves as the canonical read path for template set configuration. When a user searches on "sts_code", they are typically working with the status/state code that governs whether a given template set is currently active and eligible for selection.

Underlying Base Objects

The view is defined over a single referenced base object, OKS_TEMPLATE_SET, resolved in the APPS schema through a synonym. The view text is a straightforward SELECT that aliases the table as TMS and maps every column one-to-one, with no joins, unions, filters, or computed expressions:

SELECT TMS.ROWID ROW_ID, TMS.ID ID, TMS.NAME NAME, ... TMS.STS_CODE STS_CODE, ...
FROM OKS_TEMPLATE_SET TMS

Because the definition contains no predicates or aggregation, the view is fully updateable in principle and imposes no additional performance overhead beyond the resolution of the synonym. The only transformation of note is the renaming of the base table's ROWID pseudocolumn to ROW_ID, which provides a stable row identifier suitable for row-level locking and for integration tooling that expects a surrogate identifier. All other column names are preserved verbatim from the base table.

• OKS_TEMPLATE_SET — the single documented base table, accessed via synonym in the APPS schema.
• No additional joins, lookups, or product-specific views are referenced in the documented definition.
• Multi-org context is carried through the ORG_ID column rather than enforced by a WHERE clause on the view itself.

Key Columns

The sixteen exposed columns fall into three functional groups. The first comprises identity and descriptive attributes: ID uniquely identifies each template set, NAME provides the user-facing label, and DESCRIPTION supplies supporting text. The second group governs applicability and validity: START_DATE and END_DATE bound the effective period, ORG_ID assigns the record to an operating unit for Multi-Org Access Control, and STS_CODE carries the status code that determines whether the template set is selectable. The third group consists of standard EBS audit and concurrency columns.

• STS_CODE — the status indicator for the template set; filters on this column are the most common access pattern given its role in determining active versus inactive configuration.
• QUOTE_LETTER and COVER_LETTER — identifiers linking the template set to quote and cover letter definitions used during contract generation.
• ROW_ID — the base table ROWID, exposed under a distinct name for row identification.
• OBJECT_VERSION_NUMBER — optimistic locking token maintained by the EBS framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns for audit traceability.

Common Use Cases and Queries

Typical consumers include diagnostic queries during contract authoring issues, setup verification reports, and data migration scripts that need to validate template set status before loading. The following examples reflect the documented column set.

Listing active template sets within an operating unit:

SELECT id, name, start_date, end_date, sts_code
FROM   apps.oks_template_set_v
WHERE  org_id = :p_org_id
AND    sts_code = :p_active_status
AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

Resolving a template set by name for validation during an interface run:

SELECT id, sts_code, quote_letter, cover_letter
FROM   apps.oks_template_set_v
WHERE  UPPER(name) = UPPER(:p_name)
AND    org_id = :p_org_id;

Auditing recent configuration changes:

SELECT id, name, last_updated_by, last_update_date
FROM   apps.oks_template_set_v
WHERE  last_update_date >= :p_since
ORDER  BY last_update_date DESC;

Because the view adds no filtering, retain the multi-org and status predicates in every query to avoid returning template sets belonging to other operating units or inactive configurations, and use STS_CODE explicitly whenever the intent is to restrict results to currently usable records.