Search Results receiving_site

Overview

APPS.HR_LOCATIONS_V is a reporting and integration view that consolidates Oracle E-Business Suite location definitions into a single, denormalized recordset. In Oracle EBS 12.1.1 and 12.2.2, locations are the physical or logical addresses tied to a business group and used across Human Resources, Inventory, Purchasing, Order Management, Payables, and Receivables. The view joins the transactional location table HR_LOCATIONS_ALL with its translated descriptive columns in HR_LOCATIONS_ALL_TL and resolves the various site indicator flags against the HR_LOOKUPS view, which yields the descriptive meanings SHIP_TO_SITE, BILL_TO_SITE, OFFICE_SITE, RECEIVING_SITE, and INTERNAL_SITE.

The view is significant because the base table HR_LOCATIONS_ALL stores site roles as short lookup codes and numeric references, whereas downstream users typically require both the code and a readable description together with address text. HR_LOCATIONS_V supplies that combined picture, allowing a receiving clerk, a requisition approver, or an integration payload to obtain a location code, its ship-to and bill-to designations, and its receiving-site status in one query. Because it is an APPS-owned view, it is treated as a read-only interface object and must never be updated directly.

Underlying Base Objects

The documented base objects referenced by the view are FND_DESCR_FLEX_CONTEXTS_TL, FND_TIMEZONES_VL, HR_API, HR_GENERAL, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, and HR_LOOKUPS. HR_LOCATIONS_ALL is the primary source for identifiers, flags, address lines, and attribute columns, while HR_LOCATIONS_ALL_TL contributes LOCATION_CODE and DESCRIPTION. HR_LOOKUPS is joined multiple times (aliased HR1 through HR5) to convert the stored flag values into their descriptive MEANING text. FND_DESCR_FLEX_CONTEXTS_TL and FND_TIMEZONES_VL supply descriptive flexfield context naming and timezone information. The HR_API and HR_GENERAL packages are referenced for the business-group and session-based security logic that restricts a user to the locations of the current business group. The view therefore behaves as a security-aware, multi-table projection rather than a flat copy of a single table.

Key Columns

• LOCATION_ID — the unique internal identifier for the location; the join key to purchasing, inventory, and HR tables.
• LOCATION_CODE and DESCRIPTION — the human-readable short code and full description from the translated table.
• RECEIVING_SITE_FLAG and RECEIVING_SITE — the stored flag value for whether the location can receive goods, plus its decoded meaning.
• SHIP_TO_SITE_FLAG, BILL_TO_SITE_FLAG, OFFICE_SITE_FLAG, IN_ORGANIZATION_FLAG and their decoded counterparts (SHIP_TO_SITE, BILL_TO_SITE, OFFICE_SITE, INTERNAL_SITE) — the active site roles assigned to the location.
• SHIP_TO_LOCATION_ID and SHIP_TO_LOCATION — a self-referencing pointer for locations that ship to another location.
• ADDRESS_LINE_1 through ADDRESS_LINE_3, TOWN_OR_CITY, POSTAL_CODE, REGION_1, COUNTRY — the formatted address components used on documents and labels.
• INVENTORY_ORGANIZATION_ID — links the location to an inventory organization where applicable.
• ATTRIBUTE1–20 and GLOBAL_ATTRIBUTE1–20 — descriptive flexfield segments captured for the location record.
• INACTIVE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — lifecycle and audit columns for effective-dating and tracking.

Common Use Cases and Queries

The most common requirement, and the one reflected in the search term "receiving_site", is validating which locations may receive goods. A purchasing or receiving report joins this view to purchasing documents using RECEIVING_SITE_FLAG or the decoded RECEIVING_SITE meaning.

SELECT location_id, location_code, receiving_site
FROM   apps.hr_locations_v
WHERE  receiving_site_flag = 'Y'
ORDER  BY location_code;

Integration and master-data extracts commonly select the full address and site flags to populate external systems or interface staging tables. Location-driven document printing uses the same view to resolve the ship-to and bill-to codes for orders and invoices. Because the view enforces business-group security, reports should not add their own ORG_ID filtering unless the query is intended to cross organizations, and callers should treat the view strictly as read-only.