Search Results competitor_flag

Overview

OKL_CS_CUST_ACCT_OVERVIEW_UV is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. It exposes a consolidated customer account overview used by OKL leasing and finance functionality, particularly the customer account search and overview pages that present Receivables customer account information within the leasing application. The view is defined over Receivables and Trading Community Architecture (TCA) base objects, allowing OKL screens, reports, and integration interfaces to retrieve customer account attributes without directly querying the underlying AR and HZ tables.

Because it is a view rather than a table, the object carries no independent storage; it is a projection that joins the customer account, customer profile, payment term, statement cycle, and lookup data sources into a single denormalized result set. The view is marked VALID, indicating that at the documented release level (12.1.1 / 12.2.2) the underlying objects and the view definition are in a consistent, compiled state.

Underlying Base Objects

The documented referenced base objects for OKL_CS_CUST_ACCT_OVERVIEW_UV are:

• HZ_CUST_ACCOUNTS (synonym) — the primary source of customer account records, supplying account identifiers, party references, account numbers, status, customer type, class and subclass codes, tax attributes, balances, and audit columns. It is aliased as CUST_ACCT in the view text.
• HZ_CUSTOMER_PROFILES (synonym) — joined as CUST_PROF to supply profile-level attributes such as the statement cycle. The join is made on the customer account identifier.
• RA_TERMS_TL (synonym) — joined as PAY_TERMS to resolve the payment term name from the payment term identifier carried on the customer account.
• AR_STATEMENT_CYCLES (synonym) — joined as STMT_CYC to resolve the statement cycle name from the statement cycle identifier on the customer profile.
• AR_LOOKUPS (view) — joined as STATUS_LOOKUP to translate the customer account status code into a user-facing status description.

The dependencies confirm that OKL does not maintain its own customer master for these attributes; it leverages the Receivables and TCA model, which is the shared customer data foundation across EBS.

Key Columns

• CUST_ACCOUNT_ID, PARTY_ID, ORG_ID — primary identifiers linking the account to its owning party and operating unit.
• ACCOUNT_NUMBER, ORIG_SYSTEM_REFERENCE, ACCOUNT_NAME — account identification attributes.
• STATUS, ACCOUNT_STATUS_DESCRIPTION — the raw status code and its decoded description from AR_LOOKUPS.
• CUSTOMER_TYPE, CUSTOMER_CLASS_CODE, SUBCATEGORY_CODE — classification attributes; CATEGORY_CODE is exposed as a hard-coded NULL.
• THIRD_PARTY_FLAG and COMPETITOR_FLAG — both returned as literal NULL values. This is significant: although consumers frequently search for third_party_flag expecting a populated flag, the view deliberately supplies NULL for these columns, so any filter or report relying on them will return no meaningful distinction.
• PAYMENT_TERM_ID, PAYMENT_TERM_NAME, STATEMENT_CYCLE_ID, STATEMENT_CYCLE_NAME — joined descriptive values for terms and statement cycles.
• CURRENT_BALANCE, account date fields, write-off amounts — financial and lifecycle attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15, and audit columns — DFF and standard who-columns.

Common Use Cases and Queries

Typical use is populating OKL customer account overview and search regions, and supplying data to reports or interfaces that require decoded status, payment term, and statement cycle descriptions.

SELECT cust_account_id, account_number, account_name,
       account_status_description, payment_term_name,
       current_balance, third_party_flag
FROM   apps.okl_cs_cust_acct_overview_uv
WHERE  org_id = :p_org_id
AND    account_number LIKE :p_account;

Because THIRD_PARTY_FLAG is NULL, a query such as WHERE third_party_flag = 'Y' returns no rows. Where third-party classification is genuinely required, the underlying HZ_CUST_ACCOUNTS or related TCA tables should be queried directly rather than this view.