Results for “approver_name”

50+ results




Overview
Explore in AI Chat

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

Overview

The HXC_OVERRIDE_APPROVER_V view is a reporting object owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HXC – Time and Labor Engine product. Its documented purpose is to expose the population of overriding approvers — that is, the supervisors who are eligible to act as approvers on behalf of workers whose assignments are active. The view returns a de-duplicated list of approver identities (name, person identifier, person number, and e-mail address) derived from the intersection of current, effective-dated person records with current, effective-dated assignment records.

Because the view is defined with dynamic date predicates (TRUNC(SYSDATE) BETWEEN ...), it always reflects the approver set as of the moment of query execution rather than a point-in-time snapshot. It is not a key flexfield or transactional entity; it is a convenience access layer typically consumed by Time and Labor approval workflows, self-service approval lists, and custom reporting or integration extracts that need to resolve a valid approver for a given worker population.

Underlying Base Objects

The documented base objects referenced by the view are:

The join logic is a self-referential relationship: a person in PER_PEOPLE_F is joined to an assignment in PER_ASSIGNMENTS_F through P.PERSON_ID = A.SUPERVISOR_ID. This means the view returns supervisors (approvers), not the workers being supervised. Only assignments of type E (Employee) or C (Contingent Worker) are considered, and only those whose status type resolves to ACTIVE_ASSIGN or ACTIVE_CWK in PER_SYSTEM_STATUS. The NVL(P.EMPLOYEE_NUMBER, P.NPW_NUMBER) expression and the CURRENT_EMPLOYEE_FLAG/CURRENT_NPW_FLAG predicates ensure that both payroll employees and non-payrolled workers (NPW) are included when they are currently active.

Key Columns

  • APPROVER_NAME — the formatted full name of the approver (aliased from P.FULL_NAME).
  • PERSON_ID — the unique party/person identifier of the approver, used as the primary key for downstream joins and workflow routing.
  • PERSON_NUMBER — the employee number, or the NPW number when no employee number exists, via NVL.
  • LAST_NAME / FIRST_NAME — individual name components for sorting or display.
  • EMAIL_ADDRESS — the approver e-mail address, useful for notification and workflow delivery.

The DISTINCT modifier suppresses duplicate rows that would otherwise arise when a supervisor has multiple qualifying assignments. This is particularly relevant when a supervisor holds both an Employee (E) and a Contingent Worker (C) assignment simultaneously.

Common Use Cases and Queries

Typical consumption includes approval routing logic, supervisor lookup for time-card submission, and population extracts for custom notifications. A simple listing query follows:

  • SELECT PERSON_ID, APPROVER_NAME, PERSON_NUMBER, EMAIL_ADDRESS FROM APPS.HXC_OVERRIDE_APPROVER_V ORDER BY APPROVER_NAME;
  • Restricting to approvers with an e-mail address available: SELECT * FROM APPS.HXC_OVERRIDE_APPROVER_V WHERE EMAIL_ADDRESS IS NOT NULL;
  • Joining back to HXC_TIME_CARD or approval tables on PERSON_ID to resolve the responsible approver for a given worker's records.

Because the view contains no organization or business-group filter column, any query intended for a specific operating unit or security profile should be composed through an additional join to a security-aware object rather than relying on the view itself. Note also that the "active_cwk" term in the underlying predicate maps to the ACTIVE_CWK system status, confirming that contingent workers are deliberately included in the approver population.