Search Results pos_po_list_users_v




Overview
Explore in AI Chat

Overview

POS_PO_LIST_USERS_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module, classified with a status of VALID. It exposes the population of employees who have acted as preparers of purchase requisitions, presenting their personal identifiers, names, work telephone numbers, application user names, mailstops, organization, location, and Flexfield attributes. Rather than serving as a transactional view of requisitions, it functions as a lookup and reporting view over the requisition-preparer universe, supplying the descriptive and demographic context required by purchasing reports, value sets, and integration routines. The distinctive column mapping for "WORK_TELEPHONE" — returned by the HR_GENERAL.GET_WORK_PHONE function call — makes the view particularly relevant for contact-oriented reporting. Because membership is derived from the set of preparers present in PO_REQUISITION_HEADERS, the view self-limits to persons with actual requisition activity, avoiding the noise of the complete PER_ALL_PEOPLE_F population.

Underlying Base Objects

The documented 12.2.2 metadata lists the base objects referenced by the view: FND_USER (synonym), HR_GENERAL (package), HR_LOCATIONS_ALL (synonym), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), PER_ALL_ASSIGNMENTS_F (synonym), PER_ALL_PEOPLE_F (synonym), POS_GET (package), and PO_REQUISITION_HEADERS (synonym). The view joins these objects as follows: current person records are drawn from PER_ALL_PEOPLE_F for the system date, each restricted to primary assignments in PER_ALL_ASSIGNMENTS_F that are likewise effective today. The assignment's ORGANIZATION_ID joins to HR_ORGANIZATION_UNITS for the organization name, while the assignment's LOCATION_ID outer-joins to HR_LOCATIONS_ALL for the location code. FND_USER is outer-joined on EMPLOYEE_ID to supply the application user name. The preparer restriction is enforced by an IN subquery over PO_REQUISITION_HEADERS.PREPARER_ID. The HR_GENERAL.GET_WORK_PHONE function resolves the telephone value, and POS_GET.GET_GL_VALUE derives the cost center description from the default code combination.

Key Columns

Common Use Cases and Queries

Typical scenarios include building purchasing contact lists, resolving preparer telephone and user details in requisition reports, populating value sets restricted to active preparers, and validating preparer identity in integrations.

  • Retrieve contact details for a preparer: SELECT full_name, work_telephone, user_name FROM pos_po_list_users_v WHERE person_id = :p_person_id;
  • List preparers for a department: SELECT full_name, work_telephone FROM pos_po_list_users_v WHERE organization_name = :p_org ORDER BY full_name;
  • Resolve cost center reporting: SELECT full_name, cost_center, location_code FROM pos_po_list_users_v;

Because the view is date-sensitive and restricted to requisition preparers, results reflect only persons with current, primary, effective assignments and prior requisition activity.