Results for “okl_st_gen_tmpt_sets”

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

Overview

OKL_ST_GEN_TMPT_SETS is a reference table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. As documented in the ETRM repository, the table holds stream template sets — groupings of stream templates that define how contractual cash flows (streams) are generated, scheduled, and priced for lease and loan contracts. Stream template sets act as reusable configuration containers that allow leasing operations to standardize the generation of payment schedules, interest calculations, and accounting events across portfolios of contracts.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, suggesting it can be modeled as an independent hub without inferred parent or child links from the mined foreign-key structure. In practice, a practitioner may still elect to treat it as a hub (business concept) with an associated satellite capturing descriptive attributes, since the table appears to be a configuration/master entity referenced indirectly by transactional stream generation logic rather than a pure transaction or junction table.

The database implementation note indicates the table is not implemented in this database, meaning the reference instance surveyed did not contain the physical object — a common situation when module-specific schemas are not provisioned, or when the search was executed against a database where the OKL streams feature had not been installed.

Key Information Stored

The documented metadata identifies two key structures for this object:

• ID — the surrogate primary key, enforced through constraint OKL_ST_GEN_TMPT_SETS_PK. This is the unique internal identifier for each stream template set row.
• NAME — a business-key column, forming part of unique constraint OKL_GTS_UK together with ORG_ID. The name is the user-facing identifier for the template set.
• ORG_ID — the operating unit (multi-org) discriminator. Combined with NAME, it forms OKL_GTS_UK, ensuring that template-set names are unique within an operating unit while allowing the same logical set to be defined per organization.

The sparse column list reflects the limited metadata excerpt. In a fully implemented instance, one would expect additional descriptive columns (such as effective dates, enabled flags, stream type or generation method indicators, and audit columns like CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE), but only the columns documented above should be treated as confirmed here.

Common Use Cases and Queries

Typical usage revolves around configuration verification and reporting on stream template set definitions per operating unit. Sample query patterns include:

• Listing all template sets for an operating unit:
  SELECT id, name, org_id FROM okl_st_gen_tmpt_sets WHERE org_id = :p_org_id ORDER BY name;
• Resolving a business key to its surrogate key for downstream joins:
  SELECT id FROM okl_st_gen_tmpt_sets WHERE name = :p_name AND org_id = :p_org_id;
• Detecting duplicate or conflicting definitions across organizations:
  SELECT name, COUNT(DISTINCT org_id) FROM okl_st_gen_tmpt_sets GROUP BY name HAVING COUNT(DISTINCT org_id) > 1;
• Reconciliation reporting validating that all active lease contracts reference a recognizable template set, useful during data migration or post-clone validation.

Because the table is configuration-oriented rather than transactional, it is rarely joined directly in high-volume queries; instead it is referenced during stream generation to resolve the template logic applied to a contract.

Related Objects

The mined relationship data classifies this table as standalone, so no direct foreign-key parents or children were identified. Nonetheless, functionally related objects in the OKL streams (OKL_ST_*) family would typically include stream templates, stream generation parameters, stream types, and the contract header tables that consume the template sets. Practitioners investigating OKL_ST_GEN_TMPT_SETS should also examine OKL_ST_TEMPLATES, OKL_ST_TMPT_PARAMS, and the OKL contract header structures to trace how a template set propagates into actual scheduled streams. Because the object is reported as not implemented in the surveyed database, verification of these relationships against a provisioned OKL instance is recommended before relying on them.