Results for “groupbox_name”

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

Overview

GHR_POIS_V is a reporting view owned by the APPS schema and defined within the GHR — US Federal Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents Personnel Office Identifier (POI) assignment data, exposing the relationship between an employee or applicant and the personnel office record to which they are assigned, along with groupbox classification and the person's current full name. The view is documented as being based on the secure view PER_PEOPLE_V and is consumed by the POI form and its associated inquiries. Because end users frequently search for PER_PEOPLE_V when troubleshooting POI visibility issues, GHR_POIS_V is best understood as an application-facing projection built over the secure people and POI data model rather than as an independent data structure.

Underlying Base Objects

The view text joins three sources. GHR_POIS supplies the transactional POI assignment rows, including PERSONNEL_OFFICE_ID, DESCRIPTION, GROUPBOX_ID, and PERSON_ID, together with the standard WHO columns. GHR_GROUPBOXES is joined with an outer join on GROUPBOX_ID to supply GROUPBOX_NAME; the outer join preserves POI rows whose groupbox reference is null or unresolved. PER_PEOPLE_F, the effective-dated people view, supplies FULL_NAME through an outer join on PERSON_ID, and the predicate SYSDATE BETWEEN NVL(EFFECTIVE_START_DATE, ...) AND NVL(EFFECTIVE_END_DATE, ...) restricts the person row to the currently effective record. The documented referenced objects — GHR_POIS and GHR_GROUPBOXES (both exposed as synonyms), PER_PEOPLE_F (view), and the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages — confirm that name retrieval and row-level security are resolved through the HR security and name-formatting APIs rather than through direct table access. Reading data therefore requires a session whose security profile grants access to the underlying person records.

Key Columns

• ROW_ID — the ROWID of the GHR_POIS row; used as a unique row identifier and commonly referenced by the POI form for update and navigation.
• PERSONNEL_OFFICE_ID — the personnel office identifier associated with the POI record; the primary business key for POI reporting.
• DESCRIPTION — the descriptive text of the personnel office entry.
• GROUPBOX_ID / GROUPBOX_NAME — the groupbox classification key and its resolved name, resolved through the outer join to GHR_GROUPBOXES.
• PERSON_ID — the person identifier linking the POI record to the HR person entity.
• FULL_NAME — the currently effective formatted person name, derived from the people view using the standard HR name-formatting logic.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns inherited from the GHR_POIS row.

Common Use Cases and Queries

Typical uses include validating POI assignments for a person, producing rosters of personnel by office, and diagnosing why a POI row is not visible on the form. Because security is inherited from the people view, queries should be run from a responsibility whose HR security profile covers the intended population.

• Retrieve all POIs for a person:
  SELECT personnel_office_id, description, groupbox_name, full_name FROM apps.ghr_pois_v WHERE person_id = :p_person_id;
• List personnel assigned to an office:
  SELECT person_id, full_name, description FROM apps.ghr_pois_v WHERE personnel_office_id = :p_office ORDER BY full_name;
• Group POI counts by classification:
  SELECT groupbox_name, COUNT(*) FROM apps.ghr_pois_v GROUP BY groupbox_name;
• Locate orphaned rows where the groupbox or person reference is unresolved, indicated by a null GROUPBOX_NAME or FULL_NAME.

When results appear incomplete, the effective-dating predicate and HR security packages are the most common causes and should be investigated before assuming a data defect.