Results for “postal_code”

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

Overview

The AST_CUSTOMER_UWQ_LOV_V view is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the AST (TeleSales) product family. It is a purpose-built List of Values (LOV) view, designed to feed the Universal Work Queue (UWQ) and related TeleSales agent-facing screens with a denormalized, display-ready list of customers. Rather than exposing raw HZ_PARTIES columns, the view flattens party identity, address, and certification attributes into a consistent set of columns prefixed IEU_LOV_COL, which is the naming convention used by the Interaction Center / IEU LOV framework. In EBS 12.1.1 and 12.2.2 the view remains valid and is referenced by concurrent programs, forms-based LOVs, and OAF regions that require a queryable customer picker. Its role in reporting and integration is largely that of a read-only lookup source: it provides a governed, profile-aware list of active parties that can be joined into custom reports, BI Publisher data templates, or REST/SOA data services without requiring the consumer to re-implement the underlying TCA join logic.

Underlying Base Objects

The documented metadata identifies four referenced base objects: HZ_PARTIES (synonym), FND_TERRITORIES_TL (synonym), AR_LOOKUPS (view), and the FND_PROFILE package. The view text confirms an outer join from HZ_PARTIES to FND_TERRITORIES_TL on country code, filtered by the session language via USERENV('LANG'), with a further outer join to AR_LOOKUPS on lookup type HZ_PARTY_CERT_LEVEL. The /*+ ORDERED USE_NL(P) */ hint forces the parties table to drive the join, and FND_PROFILE.VALUE('HZ_DISPLAY_CERT_LEVEL') is consulted in the ORDER BY clause to make sorting behavior configurable. Because HZ_PARTIES is the TCA registry of record, the view inherently inherits the trading community architecture's deduplication and party relationship model, though it deliberately restricts output to parties with STATUS = 'A' and PARTY_TYPE of organization or person.

Key Columns

The following columns are exposed and carry both functional and display significance:

• IEU_LOV_COL1 – P.PARTY_NAME, the primary descriptive LOV label.
• IEU_LOV_COL2 – P.PARTY_NUMBER, the TCA party number used as a unique business identifier.
• IEU_LOV_COL3 – P.PARTY_ID, the surrogate primary key linking back to HZ_PARTIES.
• IEU_LOV_COL4 – Concatenated address lines (address1 through address4) for display.
• EMAIL_ADDRESS, CITY, STATE, POSTAL_CODE, COUNTY, PROVINCE – Discrete location attributes for filtering and output.
• COUNTRY_CODE and COUNTRY_NAME – Territory code and short name from FND_TERRITORIES_TL.
• LOCATION – A full concatenated address string combining address, city, state, postal code, county, and country.
• CERTIFICATION_LEVEL and CERTIFICATION_MEANING – Party certification code and translated meaning from AR_LOOKUPS.

Common Use Cases and Queries

Typical usage includes embedding the view in a custom LOV for TeleSales agent forms, joining it to HZ_CUST_ACCOUNTS for account-level reporting, or extracting customer certification data to a data warehouse. A representative query follows:

SELECT ieu_lov_col3 party_id, ieu_lov_col1 party_name, email_address, city, state, country_name, certification_meaning FROM apps.ast_customer_uwq_lov_v WHERE UPPER(ieu_lov_col1) LIKE UPPER('ACME%') ORDER BY 2;

Because the view is not indexed independently, performance depends on indexes on HZ_PARTIES; large implementations should filter on IEU_LOV_COL1 or PARTY_NUMBER to avoid full scans. The view is read-only and should not be used as a basis for DML.