Results for “location_code”

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

Overview

The APPS.POS_PO_LOCATION_DETAIL_V view is a reporting and integration object within the Oracle E-Business Suite iSupplier Portal (POS) product module. Its documented purpose is to fetch address information from the HR_LOCATIONS data model, exposing location records in a denormalized, presentation-ready form suitable for use by iSupplier Portal pages, concurrent programs, and external integrations. The view carries a VALID status and is owned by the APPS schema, which is consistent with standard EBS practice of centralizing shared views and APIs under APPS for controlled access by multiple products.

The view is particularly relevant when reporting address components for purchasing and supplier-facing transactions. Because a frequently searched column, CITY_STATE_ZIP, is exposed directly by this view, it serves as a convenient single source when an application needs a concatenated city, state or region, and postal code string without reconstructing the logic across HR tables.

Underlying Base Objects

The view is defined over a single referenced base object, HR_LOCATIONS_ALL, accessed through its synonym. HR_LOCATIONS_ALL stores location and address information used across Oracle HRMS and is commonly referenced by other EBS modules, including Purchasing. The view does not join to additional tables; instead, it selects and transforms columns from HR_LOCATIONS_ALL, which keeps it lightweight and predictable for query performance.

Because the view depends on HR_LOCATIONS_ALL, it inherits the data security and validation behavior of that base table, including any location-level attributes maintained in HRMS. The ETRM metadata confirms HR_LOCATIONS_ALL (SYNONYM) as the only documented referenced base object.

Key Columns

• LOCATION_ID — The unique identifier of the location record; the primary key when joining back to HR_LOCATIONS_ALL or to purchasing entities referencing locations.
• LOCATION_CODE — The user-defined short code that identifies the location in HRMS and in purchasing setups.
• ADDRESS_LINE1, ADDRESS_LINE2, ADDRESS_LINE3 — The address text lines as stored on the location record.
• CITY_STATE_ZIP — A derived column formed by concatenating the town or city, a comma, the appropriate region (REGION_2 when STYLE is 'US', otherwise REGION_1), another comma, and the postal code. This single column supports formatted display of the locality without requiring the caller to apply the DECODE logic.
• COUNTRY — The country value from the location record, useful for filtering or formatting international addresses.

Note that the view text returns the concatenated expression without an explicit alias; ETRM documents the resulting column as CITY_STATE_ZIP in the published column list.

Common Use Cases and Queries

The view is commonly used by iSupplier Portal components and custom reports that need a formatted location string for a purchasing document, supplier site, or delivery address. It also supports data extracts and interfaces where a single concatenated city, state, and postal code field is expected by a downstream system.

Typical usage is a simple SELECT against the view, optionally joined to purchasing tables by LOCATION_ID or LOCATION_CODE:

• Retrieve all locations with a formatted locality: SELECT location_id, location_code, address_line1, city_state_zip, country FROM pos_po_location_detail_v;
• Filter to a specific country or code: SELECT location_code, city_state_zip FROM pos_po_location_detail_v WHERE country = 'US' AND location_code = :p_code;
• Join to a purchasing entity that references the location: SELECT po.location_id, v.city_state_zip FROM pos_po_location_detail_v v, some_po_table po WHERE po.location_id = v.location_id;
• Feed an extract requiring a consolidated address line: select the address lines plus CITY_STATE_ZIP for interface staging or reporting.

Because the view is read-only and derived from a single base table, it is safe to use in queries and views; no DML should be attempted against it. For performance, standard indexing on HR_LOCATIONS_ALL for LOCATION_ID supports efficient joins.