Search Results customer_account_id




Overview
Explore in AI Chat

Overview

The OKL_BPD_ALL_CONTRACT_CUST_UV view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and classified under the OKL – Leasing and Finance Management product family. It is a user-facing (UV) view, meaning it is intended to be consumed by Oracle Forms-based LOV (List of Values) mechanisms rather than by internal processing logic. Its documented purpose is to supply the contracts List of Values used on the Transaction Summary screen within the Leasing and Finance Management module.

The view consolidates customer, party, contract, and bill-to-site attributes into a single denormalized result set. This allows the transaction summary form to present a meaningful, human-readable list of lease contracts – with associated customer names, account identifiers, and billing site information – without requiring the form to perform multiple joins at runtime. The view is reported as VALID and is compatible with both EBS 12.1.1 and 12.2.2, as the underlying OKL and OKX/trading community architecture objects remain stable across these releases.

Underlying Base Objects

The view is defined over a join of five primary data sources, supplemented in the referenced-object metadata by ARP_ADDR_LABEL_PKG (a package used for address labeling logic):

The joins are performed on character-converted keys (TO_CHAR), reflecting the legacy design where contract header foreign keys are stored as strings while the TCA views expose numeric IDs.

Key Columns

  • CUSTOMER_ACCOUNT_ID – the TCA customer account identifier (ACCT.ID1), the field most commonly referenced in searches because it anchors the contract to a receivables customer account.
  • CUSTOMER_NAME / CUSTOMER_NUMBER – party name and party number for display in the LOV.
  • CONTRACT_ID / CONTRACT_NUMBER – the OKL contract header key and its user-visible number.
  • CUST_ACCT_SITE_ID / LOCATION_ID – the customer account site and location identifiers for the bill-to site.
  • PARTY_ID – the TCA party identifier derived from the lessee role (RLE.OBJECT1_ID1).
  • BILL_TO_SITE_NAME – the descriptive name of the bill-to site.
  • CURRENCY_CODE – the contract currency from the header.

Common Use Cases and Queries

Typical uses include resolving a contract from a customer account, validating bill-to site assignments, and building custom LOVs or reports. A query to find all contracts for a given customer account might read:

  • SELECT contract_number, customer_name, currency_code FROM okl_bpd_all_contract_cust_uv WHERE customer_account_id = :p_acct_id;
  • SELECT contract_id, contract_number, bill_to_site_name FROM okl_bpd_all_contract_cust_uv WHERE party_id = :p_party_id;
  • SELECT DISTINCT customer_number, customer_name FROM okl_bpd_all_contract_cust_uv ORDER BY customer_name;

Because the view performs inner joins across contract and TCA entities, contracts lacking a valid lessee role or bill-to site will not appear, which is expected for its LOV-gating role.