Results for “po_agents_v”

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

Overview

PO_AGENTS_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 exposes buyer and purchasing agent records maintained by the purchasing application, joining the transactional agent definition to human resources person and location data so that a single row presents an agent with a resolvable full name and location code. The object carries a status of VALID and is documented in the ETRM repository as "Retrofitted", indicating it was reconstructed or reissued during an environment migration or upgrade effort. It is a reporting-facing, read-only construct rather than a base table, and application logic in the Purchasing module references it wherever agent identity must be presented to users or downstream interfaces. Because agent names are not stored on PO_AGENTS itself, the view performs the denormalization required to present a human-readable agent, making it the preferred access point for agent-centric reports, concurrent program extracts, and inbound/outbound integration payloads that require buyer name and location.

Underlying Base Objects

The documented base objects are PO_AGENTS (synonym), PER_ALL_PEOPLE_F (synonym), HR_LOCATIONS_ALL_TL (synonym), and the HR_GENERAL package. PO_AGENTS supplies the driving rows and all agent attributes except the display name; it is the authoritative storage for authorization limits, category assignments, and effective dates. PER_ALL_PEOPLE_F supplies FULL_NAME and business group context, joined on AGENT_ID = PERSON_ID. Because PER_ALL_PEOPLE_F is date-effective, the view applies TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE to return only the currently effective person record. HR_LOCATIONS_ALL_TL provides LOCATION_CODE through an outer join on LOCATION_ID with LANGUAGE equal to USERENV('LANG'), so agents without a valid location still appear. The HR_GENERAL package is invoked twice, using GET_XBG_PROFILE, GET_BUSINESS_GROUP_ID, and GET_BUSINESS_GROUP_ID predicates to enforce business group security, honoring cross-business-group (XBG) profile settings. The ORDERED and USE_NL hints in the view text direct the optimizer to drive from PO_AGENTS and probe the lookup tables via nested loops.

Key Columns

• ROW_ID — the PO_AGENTS row identifier, used for direct row addressing.
• AGENT_ID — the agent/person identifier; the join key to PER_ALL_PEOPLE_F.
• AGENT_NAME — the agent display name, sourced from PAPF.FULL_NAME.
• LOCATION_ID and LOCATION_CODE — the agent's location and its translated code from HR_LOCATIONS_ALL_TL.
• CATEGORY_ID — the purchasing category associated with the agent's authority.
• AUTHORIZATION_LIMIT — the maximum approvable or purchasable amount for the agent.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range of the agent record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include buyer lists in purchasing reports, validation of approval authority against document amounts, and lookups for interfaces requiring agent name and location. A basic listing is:

SELECT agent_id, agent_name, location_code, authorization_limit
FROM apps.po_agents_v
WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Filtering by category or authority threshold is equally common:

SELECT agent_id, agent_name, category_id, authorization_limit
FROM apps.po_agents_v
WHERE category_id = :p_category_id
AND authorization_limit >= :p_amount;

Because PER_ALL_PEOPLE_F is filtered to the current effective record and business group security is enforced through HR_GENERAL, queries return only agents the calling responsibility is permitted to see. The view should be treated as read-only; agent maintenance is performed against PO_AGENTS.