Search Results iby_xml_hz_addr_1_0_v




Overview
Explore in AI Chat

Overview

IBY_XML_HZ_ADDR_1_0_V is a seeded, valid APPS-schema view in the Oracle E-Business Suite Payments (IBY) module. It is one of the XML-generation views used by the Payments XML Publisher (BI Publisher) infrastructure to render address information for payee, remit-to, or supplier sites within payment instructions, payment process requests, and related XML output. The view produces a single XMLTYPE column named ADDRESS that concatenates individual address elements—address lines, city, county, state, country code and name, postal code, and pre-formatted address strings—into a structured XML fragment. Because the object name carries the "_1_0_" version suffix, this is the version 1.0 XML layout of the address data, reflecting an older but still supported output format used by IBY extract and format programs.

The view is owned by APPS, is currently VALID, and belongs to the IBY - Payments product. Its principal role is to supply a uniformly structured, XML-ready representation of an Oracle Human Resources (HZ) location so that concurrently generated payment XML payloads can embed addresses without custom formatting logic in the calling code.

Underlying Base Objects

Per the ETRM metadata for 12.2.2 (and consistent with 12.1.1), the view is defined over the following referenced base objects:

  • HZ_LOCATIONS (SYNONYM) — the core TCA (Trading Community Architecture) table holding addresses. The view reads LOCATION_ID, ADDRESS1 through ADDRESS3, CITY, COUNTY, STATE, COUNTRY, and POSTAL_CODE from this source (aliased HZ_LOC in the view text).
  • FND_TERRITORIES_VL (VIEW) — a translation view supplying TERRITORY_SHORT_NAME, joined to HZ_LOCATIONS on COUNTRY = TERRITORY_CODE to provide the human-readable country name.
  • IBY_FD_EXTRACT_GEN_PVT (PACKAGE) — the Payments extraction/formatting package. Its presence in the referenced-object list reflects the dependency chain for XML generation; note that the view itself calls HZ_FORMAT_PUB.FORMAT_ADDRESS for the pre-formatted columns.
  • XMLTYPE (TYPE) — the Oracle SQL XML datatype underlying the XMLELEMENT and XMLCONCAT functions used to build the ADDRESS column.

The view performs a single inner join between HZ_LOCATIONS and FND_TERRITORIES_VL, and its returned column list reduces to two items: ADDRESS and LOCATION_ID.

Key Columns

  • ADDRESS — an XMLTYPE value produced by XMLCONCAT(XMLELEMENT(...)). Its constituent elements are ADDRESSINTERNALID, ADDRESSLINE1, ADDRESSLINE2, ADDRESSLINE3, CITY, COUNTY, STATE, COUNTRY, COUNTRYNAME, POSTALCODE, PREFORMATTEDCONCATENATEDADDRESS (via HZ_FORMAT_PUB.FORMAT_ADDRESS(LOCATION_ID)), and PREFORMATTEDMAILINGADDRESS (via HZ_FORMAT_PUB.FORMAT_ADDRESS(LOCATION_ID,'POSTAL_ADDR')).
  • LOCATION_ID — passed through from HZ_LOCATIONS, providing the numeric TCA location identifier and serving as the natural key for joining back to HZ_LOCATIONS or HZ_PARTY_SITES.

Common Use Cases and Queries

Typical scenarios include embedding address XML in payment extracts, validation of address formatting in payee/supplier site setup, and joining to party-site or payment-instruction data.

  • Retrieve a specific location: SELECT LOCATION_ID, ADDRESS FROM APPS.IBY_XML_HZ_ADDR_1_0_V WHERE LOCATION_ID = :p_loc;
  • Extract scalar elements from the XML: SELECT x.LOCATION_ID, EXTRACTVALUE(x.ADDRESS,'//ADDRESSLINE1') line1 FROM APPS.IBY_XML_HZ_ADDR_1_0_V x;
  • Join to party sites: SELECT ps.party_site_id, a.ADDRESS FROM HZ_PARTY_SITES ps, APPS.IBY_XML_HZ_ADDR_1_0_V a WHERE ps.location_id = a.LOCATION_ID;

Because the view is APPS-owned and read-only, it should be queried rather than modified. Performance is governed by the HZ_LOCATIONS–FND_TERRITORIES_VL join and by the relative cost of the HZ_FORMAT_PUB.FORMAT_ADDRESS calls, which are invoked per row.