Results for “amt_guaranteed”

32 results




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

Overview

OKL_CS_NON_VENDORS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, validated for both 12.1.1 and 12.2.2. It belongs to the OKL (Lease and Finance Management) product family, which is delivered as part of the Oracle Enterprise Contracts and Lease Management stack. The view presents party information for parties associated with an Oracle Lease Management contract who are not vendors — principally customers and guarantors — together with the guaranteed amount recorded against each party.

Unlike base tables in OKL, which require joins across contract headers, party role assignments, address tables, and guarantor detail tables, OKL_CS_NON_VENDORS_UV flattens this information into a single self-service-friendly projection. Its role in Oracle EBS reporting and integration is to serve as a denormalised source for concurrent programs, OA Framework pages, OBIEE/BIP extracts, and custom inbound/outbound interfaces that need a compact list of contract counterparties and their guarantee exposure without touching multiple OKL base tables.

Underlying Base Objects

The view is defined over two documented view dependencies, with an outer join between them, plus an implicit reference to the FND_GLOBAL package for session context (org and user identifiers used during runtime evaluation). The documented base objects are:

  • OKL_CS_ALL_PARTIES_UV — the primary source, supplying contract, party, role, contact, and address attributes. The alias APV is used throughout the view text.
  • OKL_CS_GUARANTOR_AMOUNT_UV — the secondary source, supplying AMOUNT_GUARANTEED. The alias GAV is used in the view text.
  • FND_GLOBAL (package) — supplies the runtime application context (for example, ORG_ID and USER_ID) used by the underlying OKL security views.

The join predicate is APV.CUSTOMER_NUMBER = GAV.CUSTOMER_NUMBER(+). The outer-join symbol on GAV indicates that every party in OKL_CS_ALL_PARTIES_UV is returned even when no corresponding guarantor amount exists; in that case AMT_GUARANTEED is NULL. Because the join is on CUSTOMER_NUMBER alone, the view is effectively a customer-level party list rather than a contract-level guarantee ledger.

Key Columns

  • CONTRACT_ID / CONTRACT_NUMBER — identifier and user-facing number of the associated lease or finance contract.
  • ROLE_NAME — the party role on the contract (for example, lessee, guarantor, or another non-vendor role).
  • AMT_GUARANTEED — the guaranteed amount sourced from OKL_CS_GUARANTOR_AMOUNT_UV; NULL when the party has no guarantee record.
  • PTYPE — party type classification.
  • COMPANY — company or organisation name for the party.
  • CUSTOMER_NUMBER — the customer number used as the join key; the most reliable identifier for correlating the view with customer master data.
  • EMAIL / PHONE — contact details for the party.
  • ADDRESS1 through ADDRESS4, CITY, COUNTY, PROVINCE, STATE, POSTAL_CODE, COUNTRY — the full postal address breakdown for the party.

Common Use Cases and Queries

Typical scenarios include generating contract counterparty lists for legal review, exporting guarantor exposure for credit-risk reporting, and populating custom OA Framework pages that need a single-row-per-party presentation.

Sample query listing non-vendor parties and their guarantee amounts for a contract:

  • SELECT contract_number, role_name, company, amt_guaranteed, city, state, country FROM apps.okl_cs_non_vendors_uv WHERE contract_number = :p_contract_number ORDER BY role_name, company;

Sample query isolating parties with an active guarantee:

  • SELECT contract_number, company, customer_number, amt_guaranteed FROM apps.okl_cs_non_vendors_uv WHERE amt_guaranteed IS NOT NULL AND amt_guaranteed > 0 ORDER BY amt_guaranteed DESC;

Sample extract for a mailing or notification interface:

  • SELECT contract_number, company, email, phone, address1, address2, city, postal_code, country FROM apps.okl_cs_non_vendors_uv WHERE email IS NOT NULL;

Because the view is owned by APPS and depends on secured OKL self-service views, queries should be executed with the standard APPS responsibility context so that FND_GLOBAL populates ORG_ID and the underlying row-level security applies as intended.