Search Results customer_postal_code




Overview
Explore in AI Chat

Overview

OKL_AM_PARTIES_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, maintained within the OKL (Lease and Finance Management) product family. It is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exists to expose customer party address and identity information in a denormalized, lease-oriented form, allowing OKL reporting, concurrent programs, and integration routines to retrieve postal address attributes for parties without navigating the full Trading Community Architecture (TCA) relationship model directly.

The view is of particular interest when searching for the field customer_postal_code, since that column is one of its primary outputs. The column is exposed as CUSTOMER_POSTAL_CODE and maps to the TCA postal code attribute on the party record. This view is therefore a convenient access point for lease agreements and downstream reporting that must print or validate a customer's postal code alongside other address components such as city, state, and country.

Underlying Base Objects

The documented base objects referenced by this view are HZ_PARTIES and HZ_RELATIONSHIPS, both accessed through APPS synonyms. HZ_PARTIES is the TCA master table holding party identity and primary address attributes. HZ_RELATIONSHIPS stores the relationships between parties, including directional and reciprocal associations. The view joins these two tables on PARTY_ID and applies a fixed relationship filter: HZ_RELATIONSHIPS.STATUS = 'A' (active), DIRECTIONAL_FLAG = 'F' (forward direction), and a date-bounded validity window in which START_DATE is on or before SYSDATE and NVL(END_DATE, SYSDATE) is on or after SYSDATE. The DISTINCT keyword eliminates duplicate rows produced by multiple matching relationship records. Because both source tables are synonyms in the APPS schema, the view is queryable wherever APPS objects are accessible.

Key Columns

  • CUSTOMER_POSTAL_CODE — The postal or ZIP code from HZ_PARTIES.POSTAL_CODE, the column most commonly searched for by reporting users.
  • CUSTOMER_ADDRESS1 through CUSTOMER_ADDRESS4 — The four address lines from HZ_PARTIES, supporting full mailing address rendering.
  • CUSTOMER_CITY, CUSTOMER_STATE, CUSTOMER_COUNTRY — Location attributes used for geographic grouping, tax determination, and mailing validation.
  • CUSTOMER_PARTY_ID — The unique TCA party identifier, the natural join key back to lease, contract, and customer records.
  • CUSTOMER_PARTY_TYPE — The classification of the party (for example, organization or person), useful for filtering output.
  • CUSTOMER_PARTY_NAME — The party name as stored on HZ_PARTIES, used in reports and correspondence.

Common Use Cases and Queries

The view is typically used to resolve customer postal details for lease agreements, generate address labels, or drive downstream integrations that require a clean, active party address. A representative query retrieving postal codes for a known set of parties is:

  • SELECT CUSTOMER_PARTY_ID, CUSTOMER_PARTY_NAME, CUSTOMER_POSTAL_CODE FROM OKL_AM_PARTIES_UV WHERE CUSTOMER_PARTY_ID = :party_id;
  • SELECT CUSTOMER_PARTY_NAME, CUSTOMER_CITY, CUSTOMER_STATE, CUSTOMER_POSTAL_CODE FROM OKL_AM_PARTIES_UV WHERE CUSTOMER_COUNTRY = :country ORDER BY CUSTOMER_POSTAL_CODE;
  • SELECT COUNT(*) FROM OKL_AM_PARTIES_UV WHERE CUSTOMER_POSTAL_CODE IS NOT NULL;

Because the view enforces active, forward, date-valid relationships, results reflect only currently effective customer associations. Reports that must include historical or terminated relationships should query HZ_PARTIES and HZ_RELATIONSHIPS directly rather than this view. When joining to lease contracts, use CUSTOMER_PARTY_ID as the correlation key to OKL agreement and contract tables.