Results for “pa_locations”

50+ results




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

Overview

PA_LOCATIONS is a reference table in the Oracle Projects (PA) schema that stores the physical locations associated with projects and project team roles in Oracle E-Business Suite 12.1.1 and 12.2.2. Unlike general-purpose location reference tables, PA_LOCATIONS is populated implicitly: a new row is created automatically whenever a user assigns a location to a project or to a team role assignment. There is no standard user interface for manually inserting location records into this table, which means its contents are entirely driven by transactional activity in the Projects module.

From a dimensional modeling perspective, the mined foreign-key structure suggests a hub-leaning Data Vault classification. PA_LOCATIONS functions as a stable, business-key-identified entity whose LOCATION_ID is referenced by numerous surrounding tables, making it a natural candidate for a hub in a Data Vault model. The absence of foreign keys pointing outward from PA_LOCATIONS reinforces its role as a reference or descriptive entity rather than a transactional or associative link.

Key Information Stored

The table is documented with nine columns in ETRM 12.2.2. The most significant include:

  • LOCATION_ID — The surrogate primary key, enforced by the unique index PA_LOCATIONS_U1 and the constraint PA_LOCATIONS_PK. This is the single business-key candidate and the column through which all dependent tables join.
  • CITY — Descriptive city name for the location.
  • REGION — Geographic region associated with the location.
  • COUNTRY_CODE — Country identifier for the location, typically referencing a standard country reference.
  • LAST_UPDATE_DATE — Audit timestamp of the most recent modification, standard for Oracle EBS concurrent-program awareness.
  • LAST_UPDATED_BY — The user who last modified the row.
  • CREATION_DATE — Audit timestamp of initial insertion.
  • CREATED_BY — The user credited with creating the row.
  • LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for auditing and multi-session traceability.

The WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) conform to Oracle Application Object Library auditing standards. No descriptive address, postal code, or telephone columns are documented, indicating that PA_LOCATIONS is a lightweight geographic descriptor rather than a full address repository.

Common Use Cases and Queries

Typical reporting scenarios include resolving location descriptions onto project and assignment reports, and analyzing project distribution by city, region, or country. Because PA_LOCATIONS is the authoritative source for location text, joins from PA_PROJECTS_ALL or PA_PROJECT_ASSIGNMENTS are common.

  • Resolving project location: SELECT p.project_id, l.city, l.region, l.country_code FROM pa_projects_all p, pa_locations l WHERE p.location_id = l.location_id;
  • Counting assignments by country: SELECT l.country_code, COUNT(*) FROM pa_project_assignments a, pa_locations l WHERE a.location_id = l.location_id GROUP BY l.country_code;
  • Auditing recently created locations: query on CREATION_DATE and CREATED_BY to trace which activity generated new rows.

Because rows are created implicitly, reconciliation queries comparing distinct LOCATION_ID values across dependent tables with PA_LOCATIONS are useful for validating referential integrity and detecting orphaned references.

Related Objects

The documented foreign-key relationships show that PA_LOCATIONS is referenced by the following significant objects, each joining via LOCATION_ID:

  • PA_PROJECTS_ALL — Stores project definitions; LOCATION_ID identifies the project's designated location. This is the primary consumer.
  • PA_PROJECT_ASSIGNMENTS — Team role assignments referencing a location.
  • PA_ASSIGNMENTS_HISTORY — Historical record of team assignments and their locations.
  • PA_PROJECT_ASGMTS_AR — Audit/archive table for project assignments.
  • PA_ASGMTS_HSTRY_AR — Archive of assignment history.
  • PA_PROJ_ELEMENTS — Project elements referencing a location.

Together these dependents establish PA_LOCATIONS as a shared reference hub within Oracle Projects, consumed by both current and historical project and assignment data structures.