Search Results per_workforce_current_x

Overview

PO_BUYER_NAME_NUM_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, denormalized buyer identity, pairing each purchasing agent defined in PO_AGENTS with the corresponding person record in the HR workforce repository. The view returns two columns: BUYER_INFO, a display string combining the worker's full name with an employee or NPW number, and BUYER_ID, the person identifier. Because it joins the buyer master to workforce data, the view serves as the standard lookup for rendering "who is this buyer" in purchasing reports, custom concurrent programs, BI Publisher data models, and integration extracts.

The user search term "per_workforce_current_x" is directly relevant here: the view's defining query selects from PER_WORKFORCE_CURRENT_X, the dated workforce view (documented in the metadata as the base object PER_WORKFORCE_X). This confirms that PO_BUYER_NAME_NUM_V is date-effective by construction—it resolves the buyer's name and number as of the effective date of the underlying workforce record.

Underlying Base Objects

The documented view text is:

SELECT (SUBSTR(HRE.FULL_NAME, 1, 207) || ', ' || NVL(HRE.EMPLOYEE_NUMBER, HRE.NPW_NUMBER)), HRE.PERSON_ID FROM PER_WORKFORCE_CURRENT_X HRE, PO_AGENTS POA WHERE HRE.PERSON_ID = POA.AGENT_ID

• PO_AGENTS (documented as a synonym): the purchasing agent definition. AGENT_ID is the join key, restricting the result set to actual buyers rather than the entire workforce.
• PER_WORKFORCE_CURRENT_X / PER_WORKFORCE_X: the HRMS workforce view supplying FULL_NAME, EMPLOYEE_NUMBER, and NPW_NUMBER.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages): documented base objects, invoked indirectly through the PER_WORKFORCE_X view to format the name and enforce HR security.

The join is an equality between PERSON_ID and AGENT_ID; no explicit date predicate appears in the view text, so the effective-date filtering is inherited from PER_WORKFORCE_CURRENT_X.

Key Columns

• BUYER_INFO: character string built as SUBSTR(FULL_NAME, 1, 207) concatenated with a comma, a space, and NVL(EMPLOYEE_NUMBER, NPW_NUMBER). The 207-character truncation guarantees the combined value fits the 240-byte column limit of the underlying PO_AGENTS.NAME field (207 + ", " + 30-character number = 240). If an employee number is absent, the NPW (non-payroll worker) number is substituted.
• BUYER_ID: the PERSON_ID from the workforce view, which equals PO_AGENTS.AGENT_ID. This is the value stored in purchasing documents (for example, PO_HEADERS_ALL.AGENT_ID) and is the correct column to join on.

Common Use Cases and Queries

Typical scenarios include listing active buyers for a purchasing report, resolving AGENT_ID values on requisitions and purchase orders to display names, and driving LOV or value-set definitions that need buyer name plus identifier.

Basic buyer listing:

SELECT buyer_id, buyer_info FROM apps.po_buyer_name_num_v ORDER BY buyer_info;

Resolving buyer names on purchase orders:

SELECT pha.segment1, pha.agent_id, b.buyer_info FROM apps.po_headers_all pha, apps.po_buyer_name_num_v b WHERE pha.agent_id = b.buyer_id AND pha.org_id = :p_org_id;

Because the view lacks an ORG_ID column, multi-org filtering must be applied on the calling table (PO_HEADERS_ALL, PO_REQUISITION_HEADERS_ALL) or through PO_AGENTS. Consumers requiring buyers with no current workforce record should query PO_AGENTS directly, since the inner join drops such rows.