Results for “dependent_sty_id”

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

Overview

OKL_ST_GEN_TMPT_LNS_ALL is a transactional configuration table in the Oracle Leasing and Finance Management (OKL) module, one of the vertical applications within Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the individual lines that make up a stream template — the reusable definitional structures that determine how cash flows, payment streams, and pricing components are generated for a lease or loan contract. Each row represents a single line entry within a given stream template, defining the relationship between a primary stream type and an optional dependent stream type, along with the pricing rule that applies.

Because stream templates drive the automated generation of contractual cash flow schedules, this table functions as a critical piece of OKL setup and configuration data. In practice it is seeded and maintained during implementation to model the financial products an institution offers, and it is read at runtime whenever a contract's streams are created. Its column layout includes the standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER for optimistic locking, confirming it is an application-maintained, multi-org-aware table via the ORG_ID column.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. That is a modeling suggestion rather than a physical constraint: no foreign-key relationships were mined from the schema, so the table is best treated as an independent hub-like entity keyed on its own surrogate identifier, with an accompanying satellite carrying the descriptive attributes. Analysts building a warehouse should not infer that the table is unrelated to other OKL objects; rather, that relationships are enforced by the application tier rather than by declared database constraints.

Key Information Stored

The table documents 13 physical columns. The most important are:

• ID — the surrogate primary key, enforced by the OKL_ST_GEN_TMPT_LNS_ALL_PK constraint and a supporting unique index (OKL_ST_GEN_TMPT_LNS_ALL_U2). This is the internal row identifier and carries no business meaning.
• GTT_ID — the identifier of the parent stream template (the "generation template") to which this line belongs. Together with the stream type identifiers below, it forms the primary business-key candidate via the unique index OKL_ST_GEN_TMPT_LNS_ALL_U1.
• PRIMARY_STY_ID — the primary stream type for this line, implicitly referencing a stream type definition elsewhere in the OKL schema.
• DEPENDENT_STY_ID — the dependent stream type, used where a line's behavior is conditioned on or paired with another stream type.
• PRIMARY_YN — a flag indicating whether the primary stream type on this line is designated as the primary component for the template.
• PRICING_NAME — the pricing name or pricing rule identifier applied to the line, linking the template line to a pricing definition.
• ORG_ID — the operating unit, confirming the table is partitioned by organization for multi-org security.

The composite unique index OKL_ST_GEN_TMPT_LNS_ALL_U1 spans (GTT_ID, PRIMARY_STY_ID, DEPENDENT_STY_ID), which establishes the real business rule: within a single stream template, a unique combination of primary and dependent stream type exists. The surrogate ID remains the technical primary key, while the three-column index is the business-key candidate for data-quality and de-duplication checks.

Common Use Cases and Queries

The most frequent access pattern is retrieving all lines belonging to a template, ordered for display or processing:

SELECT id, gtt_id, primary_sty_id, dependent_sty_id, primary_yn, pricing_name
FROM   okl.okl_st_gen_tmpt_lns_all
WHERE  gtt_id = :p_template_id
ORDER  BY id;

A second common pattern is identifying which templates reference a given stream type, useful during impact analysis before modifying a stream type definition:

SELECT gtt_id, primary_sty_id, dependent_sty_id
FROM   okl.okl_st_gen_tmpt_lns_all
WHERE  primary_sty_id = :p_stream_type_id
OR     dependent_sty_id = :p_stream_type_id;

Reporting use cases include validating configured templates for completeness (templates with zero lines will not generate streams), auditing the distinct pricing names in use, and reconciling template configuration across operating units by filtering on ORG_ID. Because the table is configuration data rather than high-volume transaction data, queries are typically light, but joins to stream type definition tables add value in descriptive reports. Since there are no declared foreign keys, join conditions must be written from application knowledge, and analysts should expect orphan-risk checks (lines pointing to deleted templates or stream types) to be a routine data-quality test.

Related Objects

Although the ETRM metadata records no mined foreign keys, the following objects are the most significant dependencies based on the logical model:

• OKL_ST_GEN_TMPTS_ALL (or equivalent stream template header table) — the parent template; join on OKL_ST_GEN_TMPT_LNS_ALL.GTT_ID = template header ID.
• OKL_STREAM_TYPES / OKL_STY_* tables — define the stream types referenced by PRIMARY_STY_ID and DEPENDENT_STY_ID.
• OKL_PRICING_* tables — provide the pricing definitions resolved through PRICING_NAME.
• OKL_ST_GEN_TMPT_LNS_B / _TL — the base-table and translation-table variants that accompany the _ALL view in the MLS pattern; OKL_ST_GEN_TMPT_LNS_ALL is the multi-lingual view over them.
• OKL_TRX_* contract stream tables — consume the template line definitions when generating streams for a contract, carrying the runtime values derived from this configuration.
• OKL Stream Generation APIs (e.g., OKL_STREAM_PVT) — read template lines during stream generation for a contract.

Because relationships are application-enforced, implementers should consult the OKL data model diagrams alongside this table listing rather than relying solely on catalogued constraints.