Search Results amt_guaranteed




Overview
Explore in AI Chat

Overview

APPS.OKL_CS_ALL_PARTIES_W_AMOUNT_UV is a reporting view within the Oracle E-Business Suite (EBS) Enterprise Contracts / Lease Management (formerly Telecom Service Management, ETRM) module. Its name denotes its two defining characteristics: it consolidates all parties associated with a contract and augments each party record with a monetary amount attribute, specifically the amount guaranteed. The view presents a flattened, denormalized result set that unites multiple party roles — vendors, lessors, guarantors, and other contract parties — into a single, query-friendly structure.

This view is intended primarily for reporting and integration scenarios. Because it pre-joins and standardizes party data across roles, it spares report developers and downstream integrations from constructing multi-branch queries themselves. It is commonly referenced in operational reporting, contract dashboards, and interfaces that must surface each party's contact details alongside any guaranteed monetary amount, such as guarantee tracking or exposure analysis. The user keyword amt_guaranteed directly maps to the AMT_GUARANTEED column, which is the view's most significant financial attribute.

Underlying Base Objects

The view is defined as a UNION (not UNION ALL) of four constituent views, each supplying a distinct category of party data using an identical column list. The documented base objects are:

In addition to these views, the documented dependency list includes shared utility packages: ARP_ADDR_LABEL_PKG (address label formatting), FND_GLOBAL (session and user context), and HR_GENERAL (person/party name handling). These are typically referenced by the underlying party views rather than the outer UNION itself. The UNION subsequently applies INITCAP to ROLE_NAME and wraps the guaranteed amount in NVL(...,0) to guarantee a non-null numeric value.

Key Columns

  • CONTRACT_ID / CONTRACT_NUMBER — the contract identifier and human-readable number to which the party is attached.
  • ROLE_NAME — the party's role, normalized via INITCAP for consistent presentation.
  • AMT_GUARANTEED — the guaranteed monetary amount; nulls are coerced to 0. This is the column corresponding to the search term amt_guaranteed.
  • PTYPE — the party type classification from the source view.
  • COMPANY, CUSTOMER_NUMBER — organizational and customer reference identifiers.
  • EMAIL, PHONE — contact details (note the guarantor branch maps raw_PHONE_number to PHONE).
  • ADDRESS1–ADDRESS4, CITY, COUNTY, PROVINCE, STATE, POSTAL_CODE, COUNTRY — the full postal address block.

Common Use Cases and Queries

Typical usage includes identifying all parties on a contract with their guaranteed amounts, and filtering for parties holding non-zero guarantees. A representative query:

  • SELECT contract_number, role_name, amt_guaranteed, company FROM apps.okl_cs_all_parties_w_amount_uv WHERE amt_guaranteed > 0 ORDER BY contract_number;
  • SELECT role_name, SUM(amt_guaranteed) FROM apps.okl_cs_all_parties_w_amount_uv GROUP BY role_name; — aggregate guarantee exposure by role.
  • SELECT * FROM apps.okl_cs_all_parties_w_amount_uv WHERE contract_id = :p_contract_id; — retrieve all parties and contacts for a specific contract.

Because the view is a UNION, duplicate rows are eliminated; consumers should be aware that identical party records arising from different source views are collapsed. Developers should treat this object as read-only reporting infrastructure within the ETRM schema.