Search Results aso_i_parties_v




Overview
Explore in AI Chat

Overview

ASO_I_PARTIES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the ASO (Order Capture) product family. Its status is documented as VALID in both ETRM 12.1.1 and 12.2.2. The view is defined over the HZ_PARTIES table and is intended to retrieve party information — the trading partners, customers, persons, and organizations registered in Oracle's Trading Community Architecture (TCA) — in a form suited to Order Capture processing and downstream interfaces. Rather than exposing the raw, highly normalized column set of HZ_PARTIES, the view projects a small, flattened attribute list in which person names are already resolved into discrete first, middle, and last name components. This makes it convenient for reports, concurrent programs, and integration extracts that require a person's full structured name without joining to HZ_PERSON_PROFILES or HZ_PARTY_SITES.

The view is especially relevant to users searching for person_middle_name: whereas HZ_PARTIES itself does not carry a PERSON_MIDDLE_NAME column (middle names reside in HZ_PERSON_PROFILES), ASO_I_PARTIES_V exposes PERSON_MIDDLE_NAME directly, assembled by a PL/SQL function call. This shields the consuming report or interface from the underlying TCA data model.

Underlying Base Objects

The documented base objects referenced by the view are:

Consequently, the view is not a simple join or projection: it wraps HZ_PARTIES with packaged PL/SQL logic. Each function call may internally query additional TCA tables, so the effective read cost is higher than a plain table select, and performance depends on the efficiency of ASO_SHIPMENT_PVT.

Key Columns

  • PARTY_ID — the unique identifier of the party record in HZ_PARTIES; the primary join key to other TCA and Order Capture objects.
  • PARTY_NUMBER — the user-visible, system-generated or user-entered party number.
  • PARTY_TYPE — indicates whether the party is a PERSON, ORGANIZATION, or GROUP; it governs which name components are meaningful.
  • VALIDATED_FLAG — indicates whether the party has been validated (for example, by a third-party verification service).
  • PARTY_NAME — the display or full name of the party, derived via ASO_SHIPMENT_PVT.GET_PARTY_NAME.
  • PERSON_FIRST_NAME — the given name of a person party, derived via GET_PARTY_FIRST_NAME.
  • PERSON_MIDDLE_NAME — the middle name of a person party, derived via GET_PARTY_MID_NAME. This is the column most relevant to the originating search; it is populated only where a middle name exists in the underlying TCA person data.
  • PERSON_LAST_NAME — the family name of a person party, derived via GET_PARTY_LAST_NAME.

Common Use Cases and Queries

Typical applications include Order Capture reports that must present a customer's structured name, interface extracts that map TCA parties to external systems, and validation queries confirming that person name data is complete before an order is submitted.

Sample query to retrieve a person's full structured name by party number:

  • SELECT party_id, party_number, party_type, person_first_name, person_middle_name, person_last_name FROM apps.aso_i_parties_v WHERE party_number = :p_party_number;

Sample query restricted to person parties with a populated middle name:

  • SELECT party_id, party_number, person_first_name, person_middle_name, person_last_name FROM apps.aso_i_parties_v WHERE party_type = 'PERSON' AND person_middle_name IS NOT NULL;

Where a larger volume of party records must be processed, the view is best filtered restrictively (for example, by PARTY_ID list or PARTY_NUMBER) because of the per-row function invocations against ASO_SHIPMENT_PVT.