Search Results address_line_4




Overview
Explore in AI Chat

Overview

EDW_GEOG_LOCATION_LTC_IV is an Oracle E-Business Suite database view belonging to the BIS (Business Intelligence System) product family. The suffix "IV" denotes an "interface view," a naming convention used within the ETRM (E-Business Suite Technical Reference Manual) and EDW (Enterprise Data Warehouse) layers to identify objects intended to expose source data for extraction, staging, or downstream integration. This view presents a flattened, report-oriented projection of geographic location data — specifically addresses, names, and location surrogate keys — originating from the EDW_GEOG_LOCATION_LTC base object.

The object is documented in the Oracle EBS 12.1.1 / 12.2.2 technical reference. Per the ETRM metadata, it is not implemented in the database referenced by the documentation, meaning the definition is shipped as part of the product's documented schema but is not necessarily deployed in every environment. Consultants should therefore treat it as a reference definition rather than a guaranteed runtime object, and verify its existence in the target instance before relying on it. The search term "address_line_4" corresponds directly to one of the address columns the view exposes.

Underlying Base Objects

The view is defined over a single base object: EDW_GEOG_LOCATION_LTC. No other referenced base objects are documented in the ETRM metadata. The view text is a straightforward projection with one synthetic column:

  • A ROWID alias, exposed as ROW_ID, providing a physical row identifier.
  • Direct pass-through of all documented columns from EDW_GEOG_LOCATION_LTC.
  • A literal ' ' (space) exposed as OPERATION_CODE, a conventional EDW technique for tagging rows with an operation indicator in change-data or delta-extraction pipelines.

Because the view performs no joins or filters, its cardinality and grain match the base object one-to-one. Any row-level security, org-level filtering, or translation applied upstream in EDW_GEOG_LOCATION_LTC carries through unchanged.

Key Columns

  • LOCATION_PK / LOCATION_PK_KEY — Surrogate and keyed identifiers for the geographic location, used to join to location dimensions elsewhere in the warehouse.
  • LOCATION_DP — Likely a datapoint or data-provider indicator associated with the location record.
  • NAME — The location or site name.
  • ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, ADDRESS_LINE_4 — The four free-form address lines. ADDRESS_LINE_4 is typically reserved for supplemental locality, region, or delivery-instruction data in regions that require additional address depth.
  • POSTCODE_CITY_FK / POSTCODE_CITY_FK_KEY — Foreign key linking to a postcode/city reference dimension, enabling geographic roll-ups.
  • INSTANCE — Identifies the source EBS instance, supporting multi-instance consolidation.
  • USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Descriptive flexfield (DFF) segments carried through for customer-specific extensions.
  • CREATION_DATE / LAST_UPDATE_DATE — Standard audit columns supporting incremental and delta extraction.
  • OPERATION_CODE — Constant space value; used by ETL to signal operation type.

Common Use Cases and Queries

This view is typically consumed in address-cleansing, deduplication, and geographic reporting pipelines, and in integrations that load location masters into a data warehouse or third-party system. A basic extraction selecting the requested address_line_4 alongside identifying keys would resemble:

  • SELECT LOCATION_PK, NAME, ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, ADDRESS_LINE_4, POSTCODE_CITY_FK FROM EDW_GEOG_LOCATION_LTC_IV WHERE ADDRESS_LINE_4 IS NOT NULL;
  • SELECT LOCATION_PK_KEY, INSTANCE, USER_ATTRIBUTE1, ADDRESS_LINE_4, LAST_UPDATE_DATE FROM EDW_GEOG_LOCATION_LTC_IV WHERE LAST_UPDATE_DATE >= :last_run_date; — standard incremental delta pull.
  • SELECT POSTCODE_CITY_FK_KEY, COUNT(*) FROM EDW_GEOG_LOCATION_LTC_IV GROUP BY POSTCODE_CITY_FK_KEY; — geographic distribution analysis.

Given the "not implemented" status in the documented database, always confirm availability with a data dictionary query against ALL_VIEWS before deploying dependent extract logic.