Results for “hr_locations_all”

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

Overview

HR_LOCATIONS_ALL is the foundational Human Resources table that stores work location definitions within Oracle E-Business Suite. Owned by the HR schema and classified under the PER (Human Resources) product family, it serves as the authoritative registry of physical and logical address locations used throughout the E-Business Suite, including internal offices, receiving sites, shipping sites, bill-to sites, and inventory organizations. Every seeded or user-defined location in an EBS instance is anchored here, making HR_LOCATIONS_ALL a central master data object rather than a transactional table.

In the heuristic Data Vault classification derived from its foreign key topology, HR_LOCATIONS_ALL is modeled as a hub. This is consistent with its structure: it holds a stable business key (LOCATION_CODE within BUSINESS_GROUP_ID) with descriptive attributes, and is referenced by an exceptionally broad set of dependent tables via the LOCATION_ID foreign key. First-party foreign keys are absent from the documented metadata, reinforcing its role as an independent, referenced entity rather than a link between two hubs. Available in both EBS 12.1.1 and 12.2.2, the table retains the same schema definition with 90 documented columns.

Key Information Stored

The primary surrogate key is LOCATION_ID, enforced by the HR_LOCATIONS_PK index. The business key is captured by the HR_LOCATIONS_UK2 unique index, comprising LOCATION_CODE combined with BUSINESS_GROUP_ID, which ensures a location code is unique within its business group — a critical consideration for multi-organization deployments.

• LOCATION_CODE / BUSINESS_GROUP_ID — the unique business identifier pair; LOCATION_CODE is the human-readable short name.
• DESCRIPTION — the descriptive name displayed in LOVs and reports.
• ADDRESS_LINE_1/2/3, TOWN_OR_CITY, COUNTRY, POSTAL_CODE, REGION_1/2/3 — the physical address components.
• TELEPHONE_NUMBER_1/2/3 — contact numbers for the location.
• SHIP_TO_SITE_FLAG, RECEIVING_SITE_FLAG, BILL_TO_SITE_FLAG, OFFICE_SITE_FLAG — functional flags that qualify how the location may be used in procurement and shipping flows.
• IN_ORGANIZATION_FLAG, INVENTORY_ORGANIZATION_ID — link a location to inventory organization usage.
• INACTIVE_DATE — controlled soft-deactivation rather than deletion.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–20 and GLOBAL_ATTRIBUTE1–20 — the DFF and global DFF storage for client-specific extensions.
• LEGAL_ADDRESS_FLAG, TAX_NAME, TIMEZONE_CODE, DERIVED_LOCALE — statutory and localization attributes.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER — audit and optimistic locking columns.

Common Use Cases and Queries

The most frequent technical need is resolving a LOCATION_ID to its descriptive name, since operational tables store only the surrogate key. A typical lookup joins the hub back to itself where the shipping location differs from the bill-to location:

• Resolving ship-to and bill-to names on a purchase order:
  SELECT pha.segment1, loc.description ship_to FROM po_headers_all pha, hr_locations_all loc WHERE pha.ship_to_location_id = loc.location_id;
• Filtering active locations only: WHERE inactive_date IS NULL — essential because deactivated locations remain in the table.
• Locating a location by code: SELECT location_id FROM hr_locations_all WHERE location_code = :code AND business_group_id = :bg;
• Reporting on tax-relevant locations through ZX or JAI (India localizations), where LOCATION_ID is recorded on statutory registers.
• Auditing flag settings (SHIP_TO_SITE_FLAG, RECEIVING_SITE_FLAG) to diagnose why a location is not selectable in a purchasing or receiving LOV.

Related Objects

HR_LOCATIONS_ALL is referenced by an unusually wide set of dependent tables. The most significant, with their join columns, are:

• HR_ALL_ORGANIZATION_UNITS.LOCATION_ID — links organizations to their addresses.
• HR_ALL_POSITIONS_F.LOCATION_ID / PER_ALL_ASSIGNMENTS_F.LOCATION_ID — associates positions and employee assignments with locations.
• PO_HEADERS_ALL.SHIP_TO_LOCATION_ID / BILL_TO_LOCATION_ID and PO_LINE_LOCATIONS_ALL.SHIP_TO_LOCATION_ID — procurement address references.
• FINANCIALS_SYSTEM_PARAMS_ALL.BILL_TO_LOCATION_ID / SHIP_TO_LOCATION_ID — system-level defaults.
• ZX_LINES_DET_FACTORS — multiple location columns (SHIP_TO, SHIP_FROM, BILL_TO, BILL_FROM, POA, POO, INTERNAL_ORG) for tax determination.
• JAI_RGM_BALANCE_T.LOCATION_ID — the object the user searched for, part of the India localization RGM (receipt goods movement) balance tables.
• HR_LOCATION_EXTRA_INFO.LOCATION_ID — supplementary descriptive child table.