Results for “ece_tp_location_code”

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

Overview

WSH_HR_LOCATIONS_V is an APPS-owned reporting view within the Shipping Execution (WSH) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes Human Resources location records in a form suited to shipping, receiving, and intercompany transaction processing. The view consolidates location identifiers, address information, and site-usage flags into a single denormalized structure, allowing shipping and order-management logic to resolve operational sites without querying HR tables directly.

The view plays a supporting role in integrations and reports that must determine whether a location is a receiving site, ship-to site, bill-to site, or internal organization. Because it joins the base HR locations table with its translation table, it supplies both the numeric LOCATION_ID and the user-facing LOCATION_CODE, making it convenient for both programmatic lookups and descriptive reporting. All queries against the view are read-only; it contains no DML logic and inherits the standard APPS synonym and grant model.

Underlying Base Objects

The documented base objects referenced by the ETRM metadata are HR_GENERAL (PACKAGE), HR_LOCATIONS_ALL (SYNONYM), HR_LOCATIONS_ALL_TL (SYNONYM), and HZ_LOCATIONS (SYNONYM). The view text confirms that the primary data source is HR_LOCATIONS_ALL (aliased L), joined to HR_LOCATIONS_ALL_TL (aliased TL) — the translation table that supplies language-specific LOCATION_CODE and DESCRIPTION values.

The HR_GENERAL package contributes the GET_BUSINESS_GROUP_ID function, used in the filter predicate to default the business group when the location record itself carries a null value. This ensures the query returns locations scoped to the caller's business group. The HZ_LOCATIONS synonym is documented as a referenced object, reflecting the tight coupling between HR locations and the Trading Community Architecture (TCA) location model that underpins Receivables and Order Management. The view therefore sits atop the HR location master while remaining consistent with TCA address handling.

Key Columns

• LOCATION_ID — Primary numeric identifier of the HR location.
• LOCATION_CODE — Language-specific code drawn from the translation table.
• LOCATION_USE — Literal value 'HR', identifying the location's origin.
• RECEIVING_SITE_FLAG — Indicates whether the location is enabled to receive goods; central to the user's search term.
• SHIP_TO_SITE_FLAG and SHIP_TO_LOCATION_ID — Flag and identifier for ship-to designation.
• BILL_TO_SITE_FLAG — Identifies bill-to capable locations.
• IN_ORGANIZATION_FLAG and OFFICE_SITE_FLAG — Internal organization and office-site designations.
• INVENTORY_ORGANIZATION_ID — Links the location to its owning inventory organization.
• DESIGNATED_RECEIVER_ID — Default receiver associated with the location.
• Address columns — ADDRESS_LINE_1..3, TOWN_OR_CITY, COUNTRY, POSTAL_CODE, REGION_1..3, telephone numbers.
• INACTIVE_DATE, STYLE, and the ATTRIBUTE1..20 / GLOBAL_ATTRIBUTE1..20 flexfields.
• UI_LOCATION_CODE — Derived display string concatenating a truncated description or address with the location ID, truncated to fit a 59-character buffer minus the ID length.

Common Use Cases and Queries

The most frequent scenario is validating that a receiving location is active and properly flagged before creating receipts or shipments. The RECEIVING_SITE_FLAG column lets integrators filter candidate locations directly, while SHIP_TO_SITE_FLAG supports order management and delivery routing. Reports commonly combine the view with HR_OPERATING_UNITS or inventory organizations to produce site listings by business group.

A typical query returning active receiving sites follows:

• SELECT location_id, location_code, town_or_city, country, receiving_site_flag
• FROM wsh_hr_locations_v
• WHERE receiving_site_flag = 'Y'
• AND inactive_date IS NULL
• ORDER BY location_code;

For ship-to determination, replace the flag with ship_to_site_flag = 'Y'. Joining on location_id to transaction tables such as WSH_DELIVERY_ASSIGNMENTS or RCV_SHIPMENT_HEADERS allows reporting of receiving performance by site. Because UI_LOCATION_CODE is preformatted for display and limited to Oracle Forms' field width, it is preferred for user-facing LOV-style reports, while LOCATION_CODE should be used for precise programmatic matching.