Search Results designated_receiver_id




Overview
Explore in AI Chat

Overview

APPS.PO_LOCATIONS_VAL_V is an Oracle E-Business Suite validation view that exposes active location and address information used across Purchasing and related modules. In EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is defined over HR_LOCATIONS, applying a date-based filter to return only records that are currently valid. Its purpose is to present a curated, validated subset of HR location data for list-of-values, address defaulting, and reporting consumers that require ship-to, bill-to, receiving, and office site designations.

The view is closely associated with the "ship_to_site_flag" attribute, which indicates whether a given HR location is enabled as a ship-to site for purchasing and receiving transactions. This makes the view a common reference point when validating supplier sites, purchase order ship-to addresses, and receiving destinations.

Underlying Base Objects

Per the documented ETRM metadata, PO_LOCATIONS_VAL_V is defined over HR_LOCATIONS (VIEW) and references the HR_GENERAL (PACKAGE). The view text is a straightforward projection:

  • SELECT of location, address, and site-designation columns from HR_LOCATIONS
  • WHERE SYSDATE < NVL(INACTIVE_DATE, SYSDATE+1), which excludes any location whose INACTIVE_DATE has passed or is today
  • HR_GENERAL is a supporting package used elsewhere in the HR locations and address validation framework rather than a direct driving table

Because the view sits directly on HR_LOCATIONS, it inherits that object's row population and any underlying location classification logic maintained through HR location setup.

Key Columns

Common Use Cases and Queries

The view is typically queried when a report or interface must return only locations that are active and properly characterized for purchasing and shipping. A common pattern filters on the ship-to designation:

  • SELECT location_id, location_code, description, ship_to_location_id FROM apps.po_locations_val_v WHERE ship_to_site_flag = 'Y';
  • SELECT location_id, address_line_1, town_or_city, postal_code FROM apps.po_locations_val_v WHERE receiving_site_flag = 'Y' AND inventory_organization_id = :p_org_id;
  • SELECT location_code, NVL(ship_to_site_flag,'N') FROM apps.po_locations_val_v ORDER BY location_code;

Report writers joining the view to suppliers or purchase orders use LOCATION_ID or SHIP_TO_LOCATION_ID as the join key, ensuring that only currently active locations are returned. Because inactive locations are automatically excluded, the view is well suited for validation lists without additional date filtering.