Results for “sts_code”

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

Overview

The view APPS.OKL_AM_PAYMENT_STREAM_TYPE_UV belongs to the Oracle E-Business Suite module OKL – Leasing and Finance Management, delivered in releases 12.1.1 and 12.2.2. It is a reporting and integration construct defined in the APPS schema and recorded as VALID in the ETRM metadata. Its purpose is to expose the set of payment stream types that have been associated with contract financing or cash-flow records tagged as belonging to the payment schedule. By joining the cash-flow detail table to the stream-type lookup, the view answers the business question: "for a given quote, which payment stream types exist, and what is the corresponding status code (STS_CODE)?" Because it collapses this relationship into a small, three-column, DISTINCT result set, it is well suited for use in concurrent program queries, Oracle Reports, OAF/ADF view objects, and ad-hoc SQL, and it can be referenced from integration layers that need a normalized list of payment streams per quote without traversing the full cash-flow structure.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

• OKL_CASH_FLOWS (alias CAF) — the principal cash-flow table in leasing and finance management. It stores the schedule lines, dates, amounts, and classification codes that drive contract accounting. The view filters this table on CAF.CFT_CODE = 'PAYMENT_SCHEDULE', restricting output to cash flows classified as payment schedules.
• OKL_STRM_TYPE_B (alias STM) — the stream type definition table. It supplies the stream-type code, and it is joined to the cash-flow table on CAF.STY_ID = STM.ID, where STY_ID is the foreign key to the stream type record and ID is its primary key.

The DISTINCT keyword indicates that a single quote may involve many payment-schedule cash flows sharing the same quote identifier, stream type, and status code; the view returns each unique combination only once.

Key Columns

The view projects exactly three columns, all sourced from the documented SELECT statement:

• QTE_ID — sourced as CAF.DNZ_QTE_ID. This is the quote identifier that groups the payment stream types under a single financing or leasing quotation.
• STREAM_TYPE — sourced as STM.CODE. It carries the coded stream type from the stream-type definition table, allowing the caller to distinguish payment streams by type.
• STS_CODE — sourced as CAF.STS_CODE. This is the status code recorded on the underlying cash-flow row. Users searching on "sts_code" will find that this column is exposed directly by the view, making it the primary filter target for status-based queries.

Common Use Cases and Queries

Typical scenarios include identifying the payment stream types for a specific quote, validating that a payment schedule stream has reached an expected status, and feeding downstream reporting with a compact stream-type/status matrix. A representative query filtering by quote is:

• SELECT qte_id, stream_type, sts_code FROM apps.okl_am_payment_stream_type_uv WHERE qte_id = :p_quote_id;
• SELECT stream_type, sts_code, COUNT(*) FROM apps.okl_am_payment_stream_type_uv GROUP BY stream_type, sts_code; — to profile stream types by status.
• SELECT DISTINCT sts_code FROM apps.okl_am_payment_stream_type_uv ORDER BY sts_code; — to enumerate the status codes actually reached by payment schedule streams, a frequent starting point when investigating STS_CODE values.

Because the view contains no bind-dependent logic and performs a simple inner join with an equality filter, it is inexpensive to query and safe for read-only integration use. As with all APPS views, it should be accessed through the standard APPS credentials and never modified directly.