Results for “clli_code”

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

Overview

IBE_ADDRESSES_V is a database view belonging to the IBE (iStore) product family in Oracle E-Business Suite, supported across releases 12.1.1 and 12.2.2. The view presents address and party-site information used by the iStore storefront and related customer-facing interfaces. Its name and column content indicate that it consolidates address data held in the location repository (typically HR_LOCATIONS_ALL / HR_LOCATIONS_ALL_TL) with party-site linkage held in party-site assignment tables, exposing a denormalized, reporting-friendly projection of customer and location addresses.

The view is significant because address information in EBS is fragmented across multiple entities — locations, party sites, and site-use assignments. Querying the base tables directly requires joins that are difficult to reproduce consistently. IBE_ADDRESSES_V encapsulates that logic and normalizes address representation for downstream consumers. Note that the ETRM metadata records this view as not implemented in the source database from which the documentation was extracted; whether the object is present in a given instance depends on whether the iStore module, and specifically the components that reference this view, have been installed and patched.

Underlying Base Objects

The ETRM metadata documents no referenced base objects. Based on the exposed column set, the view is defined primarily over the HR locations entity (aliased L in the view text, evidenced by LOCATION_ID as the leading column and by HR-style audit and attribute columns) outer-joined to a party-site table (aliased PS, evidenced by PARTY_SITE_ID, PARTY_ID, and the START_DATE_ACTIVE / END_DATE_ACTIVE columns). The attribute and global-attribute columns (ATTRIBUTE1 through ATTRIBUTE20 and GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20) are the standard DFF columns inherited from the location entity. Because the documented view text is truncated, the complete join structure and any partitioned outer joins cannot be verified from the metadata alone; DBAs should extract the installed source via DBA_VIEWS or the EBS data dictionary before relying on the view for custom development.

Key Columns

• LOCATION_ID — primary key of the underlying location record; the principal join key to other location-based objects.
• ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — the formatted address components.
• PARTY_SITE_ID and PARTY_ID — link the address to a specific party site and party, enabling association with customers or prospects.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating columns from the party site, used to filter currently valid site assignments.
• ORIG_SYSTEM_REFERENCE — identifies the source system of the address, relevant in multi-source and data-hub scenarios.
• VALIDATED_FLAG, ADDRESS_STYLE, ADDRESS_ERROR_CODE, ADDRESS_KEY — support address validation and geocoding integrations.
• SALES_TAX_GEOCODE, SALES_TAX_INSIDE_CITY_LIMITS — tax jurisdiction attributes used by order and tax calculation flows.
• Attribute and global-attribute columns (ATTRIBUTE1–20, GLOBAL_ATTRIBUTE1–20) — descriptive flexfield values for site-specific extensions.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) — standard WHO columns for lineage and concurrency.

Common Use Cases and Queries

The view is typically consumed in iStore address book displays, customer registration flows, and reporting extracts that require a single-row address per party site. A representative query filters to active party sites for a given party:

• SELECT location_id, party_site_id, party_id, address1, address2, city, state, postal_code, country FROM ibe_addresses_v WHERE party_id = :p_party_id AND (end_date_active IS NULL OR end_date_active > SYSDATE);
• Address cleansing and validation audits commonly select ORIG_SYSTEM_REFERENCE, VALIDATED_FLAG, and ADDRESS_ERROR_CODE to identify unvalidated or rejected addresses.
• Tax and jurisdiction reporting uses SALES_TAX_GEOCODE and SALES_TAX_INSIDE_CITY_LIMITS alongside COUNTRY and POSTAL_CODE.
• Location-level reporting by country or city joins on LOCATION_ID to inventory, order, or shipping tables that reference locations.

Because the view joins effective-dated party-site data, queries should always consider the date range columns to avoid returning historical site assignments. Where the object is absent, equivalent results can be obtained by joining HR_LOCATIONS_ALL to HZ_PARTY_SITES and HZ_PARTY_SITE_USES, applying the same effective-date and party-site-use filters.