Results for “per_establishments_v”

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

Overview

PER_ESTABLISHMENTS_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. In both release 12.1.1 and 12.2.2, the view is documented in the E-Business Suite Technical Reference Manual (ETRM) as being "used to support user interface." This designation indicates that the view exists primarily to feed Oracle Forms-based or OAF-based UI components that require a denormalized or user-friendly presentation of establishment data, rather than to serve as a general-purpose integration interface. The view exposes establishment records with a simplified column set, allowing forms and list-of-values (LOV) regions to display establishment names and associated locations without requiring the calling code to join or decode the underlying base table directly.

Because it is a view and not a table, PER_ESTABLISHMENTS_V holds no data of its own. All queries against it resolve to the underlying PER_ESTABLISHMENTS table at runtime. This means reporting or integration code that selects from the view inherits the base table's privileges, row-level security, and any Org Security or security profile behavior applied to the HR establishment entity.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view references a single base object: PER_ESTABLISHMENTS, which is listed as a SYNONYM. The APPS synonym PER_ESTABLISHMENTS resolves to the HR schema table of the same name, the master repository for establishment (legal employer / reporting establishment) definitions in Oracle HRMS. The view text is a straightforward projection with column aliasing:

• SELECT ESTABLISHMENT_ID, NAME ESTABLISHMENT, LOCATION FROM PER_ESTABLISHMENTS

There are no joins, unions, or filter predicates in the documented view definition. The view is a one-to-one row-for-row reflection of PER_ESTABLISHMENTS, limited to three attributes. Because no WHERE clause is present, any restriction applied at query time (for example, by establishment, business group, or security profile) must be supplied by the caller.

Key Columns

The view exposes exactly three columns, each with a specific role:

• ESTABLISHMENT_ID — The primary key of the establishment record. It is the unique numeric identifier carried from PER_ESTABLISHMENTS.ESTABLISHMENT_ID and is the column most frequently referenced in foreign-key relationships, such as on employee assignment, payroll, and legal reporting entities. Users searching on "establishment_id" are typically attempting to resolve or validate this identifier.
• ESTABLISHMENT — An alias for the base column NAME. It presents the human-readable establishment name, suitable for LOV display and report headings. The aliasing is the primary reason the view exists: it gives the UI a meaningfully labelled column while preserving the underlying identifier.
• LOCATION — The location attribute carried from the base table, typically the location identifier or location name associated with the establishment, used for display and filtering by site.

Note that the view is narrower than PER_ESTABLISHMENTS itself; columns such as business group, legislation code, and other descriptive attributes present in the base table are not exposed here and must be retrieved directly from PER_ESTABLISHMENTS when required.

Common Use Cases and Queries

Typical scenarios include populating establishment LOVs in HR forms, validating an establishment_id supplied by an external interface, and producing lightweight establishment listings for reports. A basic lookup by identifier:

• SELECT establishment_id, establishment, location FROM apps.per_establishments_v WHERE establishment_id = :p_establishment_id;

Listing all establishments for an LOV or report:

• SELECT establishment_id, establishment FROM apps.per_establishments_v ORDER BY establishment;

Joining to employee assignments to resolve establishment names:

• SELECT pa.assignment_id, pe.establishment FROM apps.per_all_assignments_f pa, apps.per_establishments_v pe WHERE pa.establishment_id = pe.establishment_id AND pa.effective_end_date = TO_DATE('4712/12/31','YYYY/MM/DD');

Because the view carries no business-group or security predicate, callers should apply the appropriate business group or security profile filter explicitly, and should join to PER_ESTABLISHMENTS directly when columns beyond the three exposed here are needed. The view is read-only for practical purposes and should not be used as an integration target.