Search Results site_use




Overview
Explore in AI Chat

Overview

APPS.OKL_LA_BILL_TO_UV is a read-only Oracle E-Business Suite view that exposes the set of customer bill-to site uses that the leasing application (OKL) requires when deriving lease accounting information. The name follows Oracle's standard convention for user views ("_UV"), indicating an interface object intended for consumption by application logic, reports, and integrators rather than for direct DML. The view supplies a normalized, single-purpose projection of bill-to sites: whichever rows exist in the underlying site-use source, only those with a site use code of BILL_TO are returned.

Because bill-to addresses are one of the primary drivers of tax jurisdiction, remit-to routing, invoice formatting, and receivables posting in Oracle Lease Management and Oracle Receivables, OKL_LA_BILL_TO_UV functions as the narrowing layer that lets lease accounting code join directly to a properly qualified bill-to site without re-implementing the site-use filtering logic. It is a reporting and integration convenience view rather than a table of persisted data.

Underlying Base Objects

The view is defined over the following documented objects:

  • OKX_CUST_SITE_USES_V (VIEW) — the aliased source SITE_USE. This supplies the customer site-use attributes: site use identifier components (ID1, ID2), customer account site and account identifiers, party and party site identifiers and names, the site use code, operational status, description, and operating unit. The predicate SITE_USE.SITE_USE_CODE = 'BILL_TO' is applied against this object.
  • HZ_CUST_ACCT_SITES_ALL (SYNONYM) — the aliased source SITE. This supplies the customer account site record and its STATUS column, exposed as ACCT_SITE_STATUS. The join is SITE.CUST_ACCT_SITE_ID = SITE_USE.CUST_ACCT_SITE_ID.
  • ARP_ADDR_LABEL_PKG (PACKAGE) — a Receivables address-labelling package referenced by the view's dependency chain, typically involved in formatting or resolving site/address label values surfaced through the underlying OKX view.

Only the HZ_CUST_ACCT_SITES_ALL join supplies an additional attribute beyond what the site-use view already carries; all remaining projected columns originate from the site-use layer.

Key Columns

  • ID1 / ID2 — the composite identifier of the underlying site-use record, used by the leasing application as a foreign-key reference.
  • CUST_ACCT_SITE_ID — the customer account site identifier; the join key linking site use to the account site record.
  • CUST_ACCOUNT_ID — the customer account to which the bill-to site belongs.
  • PARTY_ID / PARTY_SITE_ID / PARTY_SITE_NAME — the trading party and its party site, plus the human-readable site name.
  • SITE_USE_CODE — always 'BILL_TO' in this view by definition; retained in the projection for consistency with upstream structures.
  • B_STATUS / ACCT_SITE_STATUS — status flags: B_STATUS from the site-use record and ACCT_SITE_STATUS from the customer account site (SITE.STATUS).
  • NAME / DESCRIPTION / IDENTIFYING_ADDRESS_FLAG — descriptive attributes of the bill-to site, including whether it serves as the identifying address.
  • ORG_ID — the operating unit, essential for multi-org security and partitioned reporting.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — exposed as NULL in the view text; these placeholders preserve the column shape expected by downstream consumers.

Common Use Cases and Queries

The view is typically joined by customer account, customer account site, or party to obtain the bill-to site for leasing and receivables processing. A representative query:

  • SELECT b.cust_account_id, b.cust_acct_site_id, b.party_site_name, b.acct_site_status FROM apps.okl_la_bill_to_uv b WHERE b.org_id = :p_org_id ORDER BY b.party_site_name;
  • Joining to a lease or contract header on CUST_ACCT_SITE_ID to resolve the bill-to address used for invoicing and tax determination.
  • Filtering on ACCT_SITE_STATUS (for example, 'A' for active) to exclude inactive bill-to sites from integration extracts.

Typical scenarios include lease accounting rule derivation, invoice-to address validation, receivables integration extracts, and reconciliation reporting where a strictly bill-to-only population is required. Because only the BILL_TO site use code is returned, callers do not need to add their own site-use filtering predicate, which reduces the risk of divergent filtering logic across concurrent programs and interfaces.