Search Results customer_id2




Overview
Explore in AI Chat

Overview

OKL_CUSTOMER_UV is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) module. It functions as a user interface view that supplies the customer list of values (LOV) on the credit line contract page. In Oracle EBS Release 12.1.1 and 12.2.2, this view is registered as VALID and is not a stored table; it is a query definition resolved at runtime against its underlying base objects. Its purpose is to present only those parties that qualify as a valid "lessee" in the context of an active selling role, allowing the credit line contract form to offer a constrained and contextually correct set of customer choices. Because it abstracts the join logic between party data and role source data, developers and support analysts can query it directly when validating customer LOV behavior, troubleshooting missing customers, or building custom reporting and integration extracts.

Underlying Base Objects

The view is defined over two documented objects:

  • OKC_ROLE_SOURCES RS — referenced as a SYNONYM and used to filter role definitions by role code and buy/sell indicator.
  • OKX_PARTIES_V CUSTOMER — a view that exposes party identification and descriptive information, supplying the customer identifiers, number, and name columns.

The join is driven by role eligibility rather than an explicit key relationship in the view text: the query restricts rows to roles where RLE_CODE equals 'LESSEE', BUY_OR_SELL equals 'S', and the role's START_DATE and END_DATE bracket the current system date (with END_DATE defaulted to SYSDATE when null). This means the view returns customers only when a valid, currently effective lessee role source exists. The relationship to the base objects is therefore filter-oriented: OKC_ROLE_SOURCES determines which customers are eligible, while OKX_PARTIES_V provides the display attributes.

Key Columns

  • CUSTOMER_ID1 — mapped from CUSTOMER.ID1, the primary party identifier.
  • CUSTOMER_ID2 — aliased from CUSTOMER.ID2. This is the column most often associated with the "customer_id2" search term and typically corresponds to a secondary or alternate party identifier used for LOV return values.
  • CUSTOMER_NUMBER — mapped from CUSTOMER.DESCRIPTION, the customer account or party number displayed to users.
  • CUSTOMER_NAME — mapped from CUSTOMER.NAME, the party name shown in the LOV.
  • CUSTOMER_JTOT_OBJECT_CODE — sourced from RS.JTOT_OBJECT_CODE on OKC_ROLE_SOURCES, indicating the JTOT object code associated with the qualifying role.

The dual ID columns allow the LOV to return one identifier for internal processing while presenting another in the user interface. When investigating "customer_id2" issues, CUSTOMER_ID2 is the relevant output column, and its value depends entirely on how OKX_PARTIES_V populates ID2 for the given party.

Common Use Cases and Queries

The view supports credit line contract setup, customer LOV troubleshooting, and reconciliation of eligible lessees. A typical query retrieves the full LOV set:

  • SELECT customer_id1, customer_id2, customer_number, customer_name, customer_jtot_object_code FROM okl_customer_uv;
  • Locating a specific customer by identifier: SELECT customer_id2, customer_name FROM okl_customer_uv WHERE customer_id2 = :p_id;
  • Verifying name-to-ID mapping for a contract: SELECT customer_number, customer_name, customer_id2 FROM okl_customer_uv WHERE customer_name LIKE :p_name;

Because rows are date-filtered against SYSDATE, a customer that exists in OKX_PARTIES_V but lacks a current, effective LESSSEE selling role in OKC_ROLE_SOURCES will not appear. This is the most common root cause when a customer is expected in the credit line contract LOV but cannot be found. The view is read-only, so remediation occurs in the underlying role setup data.