Results for “primary_per_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_AM_PARTY_LOCATION_UV is a read-only Oracle EBS view owned by the APPS schema in the OKL (Leasing and Finance Management) product. It presents a denormalized, reporting-friendly projection of party site and location data drawn from the Oracle Trading Community Architecture (TCA) party model. In the context of OKL leasing operations and the broader E-Business Suite 12.1.1 and 12.2.2 releases, the view serves as a convenient single-row source for address and site information used in contract origination, party-role assignment, and integration interfaces.

The view joins party records, party sites, party site uses, and formatted addresses, restricting results to active parties with active addresses. This makes it suitable for operational reporting where only current, usable locations are relevant. The view is marked VALID and is documented as part of the OKL module's data dictionary.

Underlying Base Objects

The view is defined over four TCA base tables accessed through synonyms, plus one PL/SQL package referenced within the SELECT clause:

• HZ_PARTIES (synonym) — source of PARTY_NAME.
• HZ_PARTY_SITES (synonym) — the party-to-location association, supplying PARTY_ID, LOCATION_ID, PARTY_SITE_ID, END_DATE_ACTIVE, and STATUS.
• HZ_PARTY_SITE_USES (synonym) — supplies PRIMARY_PER_TYPE, SITE_USE_TYPE, and PARTY_SITE_USE_ID.
• HZ_LOCATIONS (synonym) — supplies address attributes ADDRESS1–3, CITY, STATE, POSTAL_CODE, and COUNTRY.
• ARP_ADDR_LABEL_PKG (package) — invoked through ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS to produce the LOCATION_ADDRESS string.

The join filters on S.STATUS = 'A', an open-ended END_DATE_ACTIVE (NVL(S.END_DATE_ACTIVE, SYSDATE) >= SYSDATE), and the standard keys PARTY_SITE_ID, PARTY_ID, and LOCATION_ID linking the respective tables. Because the view combines party site, party site use, and location, it effectively flattens one-to-many relationships into address-level rows.

Key Columns

• PARTY_NAME — the name of the party owning the site.
• PRIMARY_PER_TYPE — flags the primary use for a given purpose type.
• SITE_USE_TYPE — classifies how the site is used (for example, billing, shipping, or pay-to); this is the column most frequently referenced in searches for "site_use_type."
• PARTY_ID, LOCATION_ID, PARTY_SITE_ID, PARTY_SITE_USE_ID — the primary identifiers used for joining back to TCA tables and OKL entities.
• END_DATE_ACTIVE, STATUS — validity and lifecycle indicators; only records with STATUS = 'A' are returned.
• ADDRESS1–ADDRESS3, CITY, STATE, POSTAL_CODE, COUNTRY — the raw location address components.
• LOCATION_ADDRESS — a formatted address string built to a maximum of 80 characters.
• CONTACT, CONTACT_PARTY_ID — placeholders returned as NULL (TO_CHAR(NULL) and TO_NUMBER(NULL)), reserved for interface compatibility.

Common Use Cases and Queries

The view is commonly used to populate LOVs, address displays, and interface staging tables in OKL. The following query retrieves active billing sites for a given party:

• SELECT party_name, site_use_type, location_address FROM okl_am_party_location_uv WHERE party_id = :p_party_id AND site_use_type = 'BILL_TO';
• SELECT party_id, party_site_id, location_address FROM okl_am_party_location_uv WHERE site_use_type = 'SHIP_TO';

Because the view already restricts to active status and open end dates, callers do not need to reapply those filters. However, note that it exposes no contact-level data, so contact enrichment must be sourced separately from TCA contact tables.