Search Results okl_la_bill_to_uv




Overview
Explore in AI Chat

Overview

OKL_LA_BILL_TO_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. Its stated purpose in the Oracle ETRM documentation is to serve as the data source for a "BILL_TO" list of values (LOV), providing the set of customer bill-to site usages that can be selected during lease and finance contract entry. The view is registered with a status of VALID and is available in both 12.1.1 and 12.2.2 environments.

Functionally, the view consolidates bill-to address information from the Oracle Receivables / Trading Community Architecture (TCA) model into a single, denormalized projection suitable for LOV population and lightweight reporting. Rather than requiring the caller to join customer account sites, site uses, and party site attributes independently, OKL_LA_BILL_TO_UV presents the identifying keys, descriptive attributes, and status flags needed to drive a bill-to selector.

Underlying Base Objects

The documented view text references two primary sources joined together, plus a supplementary base object referenced in the metadata:

  • OKX_CUST_SITE_USES_V (aliased SITE_USE) — a view over customer site use data that supplies the site use code, status, identifying address flag, party and account identifiers, and descriptive name.
  • HZ_CUST_ACCT_SITES_ALL (aliased SITE, referenced via a synonym in the metadata) — the TCA customer account sites table that provides the ACCT_SITE_STATUS column and the join key to site uses.
  • ARP_ADDR_LABEL_PKG — a Receivables address labeling package listed among the documented base objects, used to derive formatted address labels that surface through the OKX_CUST_SITE_USES_V layer.

The defining join is an equi-join on CUST_ACCT_SITE_ID between SITE_USE and SITE, filtered by the predicate SITE_USE.SITE_USE_CODE = 'BILL_TO'. This restriction is what narrows the general-purpose site use data down to bill-to usages only.

Key Columns

The view projects the following columns, which correspond directly to the search term "acct_site_status" and the surrounding bill-to context:

  • CUST_ACCT_SITE_ID / CUST_ACCOUNT_ID — the TCA customer account site and customer account identifiers, forming the primary linkage to Receivables.
  • PARTY_SITE_ID / PARTY_ID — the party-level site and party identifiers.
  • PARTY_SITE_NAME, NAME, DESCRIPTION — descriptive attributes used for display in the LOV.
  • SITE_USE_CODE — the site use classification; always 'BILL_TO' given the view's filter.
  • B_STATUS — the bill-to site use status flag carried from the site use source.
  • IDENTIFYING_ADDRESS_FLAG — indicates whether the address is the party's identifying (primary) address.
  • ACCT_SITE_STATUS — the status of the underlying customer account site, sourced from HZ_CUST_ACCT_SITES_ALL.STATUS. This is the column most directly matching the search term and is used to exclude inactive or obsolete account sites from selection.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — exposed as NULL literals, indicating the view does not surface effective dating for these rows.
  • ORG_ID — the operating unit identifier supporting multi-org filtering.

Common Use Cases and Queries

The principal use is filtering valid bill-to sites for a given customer or operating unit. Because ACCT_SITE_STATUS is exposed, callers typically constrain it to 'A' (active) when building a selection list.

  • Retrieve active bill-to sites for a customer account.
  • Restrict results to a single operating unit for multi-org environments.
  • Exclude inactive account sites during lease or contract bill-to assignment.

Representative query:

SELECT cust_acct_site_id, cust_account_id, party_site_name, name, acct_site_status, org_id FROM apps.okl_la_bill_to_uv WHERE cust_account_id = :p_cust_account_id AND acct_site_status = 'A' AND org_id = :p_org_id ORDER BY party_site_name;

Because START_DATE_ACTIVE and END_DATE_ACTIVE are returned as NULL, this view is not suited to effective-dated reporting; consumers requiring date ranges must query OKX_CUST_SITE_USES_V or HZ_CUST_ACCT_SITES_ALL directly.