Results for “okl_strm_type_b”

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

Overview

OKL_STRM_TYPE_B is a core setup and reference table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, present in releases 12.1.1 and 12.2.2. The table holds the definition of payment types, referred to throughout the application as stream types. In lease and finance contracts a stream represents a scheduled cash flow such as rent, interest, tax, fee, or a passthru amount. OKL_STRM_TYPE_B defines the master inventory of these stream types, together with the behavioral flags that govern how each one is accrued, taxed, capitalized, billed, funded, and allocated when the contract engine generates a payment schedule.

Because contracts, quotes, cash flows, tax lines, interest calculations, and subsidy rules all resolve their behavior from this single definition set, the table functions as the primary reference hub for the payment-side of the OKL data model. The heuristic Data Vault classification derived from its foreign-key structure is hub: it carries a stable surrogate identifier and is referenced by a very large number of dependent tables, which is characteristic of a hub entity rather than a link or satellite. This classification is a modeling suggestion only; the physical table is an ordinary transactional-application setup table with a single-column surrogate primary key and no natural composite key enforced beyond its unique indexes.

Key Information Stored

The most significant columns capture the identity, classification, and behavioral defaults of each payment type:

• ID — surrogate primary key enforced by OKL_STRM_TYPE_B_PK. Foreign keys across the OKL schema reference this column as STY_ID or STREAM_TYPE_ID.
• CODE, VERSION, STREAM_TYPE_PURPOSE — together form the business-key candidate enforced by unique index OKL_STY_U2, qualified by ZD_EDITION_NAME. The unique index OKL_STRM_TYPE_B_U1 covers ID and ZD_EDITION_NAME.
• STREAM_TYPE_SCOPE, STREAM_TYPE_CLASS, STREAM_TYPE_SUBCLASS — categorize the payment type for processing logic and reporting.
• START_DATE, END_DATE — effective dating that determines when the definition is usable.
• ACCRUAL_YN, TAXABLE_DEFAULT_YN, BILLABLE_YN, CAPITALIZE_YN, PERIODIC_YN, FUNDABLE_YN — behavioral flags consumed by the contract engine during schedule generation.
• ALLOCATION_FACTOR — the default proportionate split applied to the stream during allocation processing.
• CUSTOMIZATION_LEVEL — indicates whether the row is seeded (Oracle-owned) or customer-defined.
• CONTINGENCY, CONTINGENCY_ID — deferral-reason reference, with CONTINGENCY_ID pointing to AR_DEFERRAL_REASONS.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OKL framework, alongside standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS DFF/descriptive flexfield segment set.
• ZD_EDITION_NAME — editioning column used by the Online Patching (AD_ZD) framework in 12.2.x.

Common Use Cases and Queries

Typical usage centers on resolving a stream type's behavior for reporting, validation, and schedule diagnostics. A common lookup joins a transactional stream table such as OKL_STREAMS to its type definition:

• Validation query — find active, non-expired payment types: SELECT code, stream_type_class, stream_type_purpose FROM okl_strm_type_b WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1).
• Behavioral audit — list all accruable and taxable types: SELECT code, accrual_yn, taxable_default_yn FROM okl_strm_type_b WHERE accrual_yn = 'Y' AND taxable_default_yn = 'Y'.
• Flatten stream detail — join OKL_STREAMS to the definition on STY_ID to report stream code, class, or purpose alongside the payment amount and due date.
• Day-two configuration reporting — identify customer-defined (customized) versus Oracle-seeded rows using CUSTOMIZATION_LEVEL for upgrade impact analysis.
• Allocation analysis — inspect ALLOCATION_FACTOR to explain how amounts are split during stream allocation processing.

These queries are most often executed from a read-only reporting user, and should always filter on TRUNC(SYSDATE) or an explicit effective date to avoid returning retired definitions.

Related Objects

OKL_STRM_TYPE_B is referenced by a wide set of dependent objects; the most significant are its closest transactional consumers:

• OKL_STREAMS — the contract's generated cash-flow streams; join on OKL_STREAMS.STY_ID = OKL_STRM_TYPE_B.ID.
• OKL_CASH_FLOWS — transactional cash-flow records referencing STY_ID.
• OKL_QUOTE_LINE_STRM and OKL_QUOTE_LINE_STRM_ALL — quote-side stream definitions carrying STY_ID.
• OKL_SUBSIDIES_B and OKL_SUBSIDIES_ALL_B — subsidy rules keyed by STREAM_TYPE_ID.
• OKL_STRM_TYP_ALLOCS — allocation rules for a given stream type, joined on STY_ID.
• OKL_TAX_SOURCES / OKL_TAX_SOURCES_T — tax setup mappings referencing STY_ID.
• OKL_LATE_INTERESTS, OKL_TBC_DEFINITIONS, and OKL_PARTY_PAYMENT_HDR (via PASSTHRU_STREAM_TYPE_ID) — additional downstream consumers.
• OKL_SYSTEM_PARAMS_ALL — holds TAX_UPFRONT_STY_ID, a system-level pointer to a preferred stream type.

All joins resolve on the surrogate ID column; the unique business key (CODE, VERSION, STREAM_TYPE_PURPOSE, ZD_EDITION_NAME) is used primarily for data-load validation rather than for runtime joins.