Search Results authorization_limit




Overview
Explore in AI Chat

Overview

POBV_BUYERS is a read-only view owned by the APPS schema in Oracle E-Business Suite, shipped under the Purchasing (PO) product family. It is documented in ETRM as a retrofitted object, meaning it survives the upgrade from 12.1.1 to 12.2.2 and continues to expose buyer-level attributes in the same form. The view presents a consolidated, date-effective picture of purchasing agents — that is, the employees who are authorized to place purchase orders and releases on behalf of an operating unit — together with the monetary authorization limit assigned to each agent.

Its practical role is to serve as a reporting and integration convenience layer. Rather than requiring report authors and interface developers to join PO_AGENTS to PER_PEOPLE_F and apply their own effective-dating predicates, POBV_BUYERS performs both operations in a single object. The view carries the WITH READ ONLY clause, so it can be queried freely but never updated through the view path. Because the underlying employee record is filtered to the current date, the view returns only agents whose HR person record is effective as of the system date, which makes it well suited to operational enquiries such as approval routing, spend analysis by buyer, and authorization-limit auditing.

Underlying Base Objects

The view text is defined as a two-table join between PO_AGENTS and PER_PEOPLE_F:

  • PO_AGENTS (aliased BR) — supplies the agent identity, authorization limit, effective start and end dates, category, location, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY). PO_AGENTS is the base table that stores buyer definitions for Purchasing. In this environment it is exposed as a synonym, but it resolves to the APPS-owned table.
  • PER_PEOPLE_F (aliased PP) — the date-effective HR persons view, supplying EMPLOYEE_NUMBER, FULL_NAME, and the EFFECTIVE_START_DATE/EFFECTIVE_END_DATE columns used for the effective-date filter.

The join predicate is BR.AGENT_ID = PP.PERSON_ID. Two additional predicates restrict the person record to the current day: PP.EFFECTIVE_START_DATE <= TRUNC(SYSDATE) and PP.EFFECTIVE_END_DATE >= TRUNC(SYSDATE). ETRM also records supporting dependencies on the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which are invoked indirectly when PER_PEOPLE_F is queried.

Key Columns

  • BUYER_ID — the agent identifier (AGENT_ID), primary correlation key back to PO_AGENTS.
  • BUYER_EMPLOYEE_NUMBER — the HR employee number of the buyer.
  • BUYER_NAME — the full formatted name of the buyer from PER_PEOPLE_F.
  • AUTHORIZATION_LIMIT — the maximum monetary amount the buyer is authorized to commit per document; the column most frequently searched in the context of this view.
  • START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — the active window of the buyer/agent assignment as recorded on PO_AGENTS.
  • CATEGORY_ID — the purchasing category to which the agent assignment is restricted, where applicable.
  • LOCATION_ID — the ship-to or office location associated with the agent record.
  • CREATED_DATE, CREATED_BY, LAST_UPDATED_DATE, LAST_UPDATED_BY — standard audit columns inherited from PO_AGENTS.

Common Use Cases and Queries

Typical uses include identifying buyers with a specific approval ceiling, validating approval hierarchies before enabling document types, and powering buyer-level spend reports. Because the view is already date-filtered, queries need no additional effective-date logic.

  • List active buyers and their limits:
    SELECT buyer_id, buyer_name, authorization_limit FROM apps.pobv_buyers ORDER BY buyer_name;
  • Find buyers authorized above a threshold:
    SELECT buyer_name, authorization_limit FROM apps.pobv_buyers WHERE authorization_limit >= 50000;
  • Report by category and location:
    SELECT buyer_name, category_id, location_id, authorization_limit FROM apps.pobv_buyers WHERE category_id IS NOT NULL;
  • Join to purchasing documents to attribute spend to buyers:
    SELECT b.buyer_name, p.segment1, p.authorization_status FROM apps.po_headers_all p, apps.pobv_buyers b WHERE p.agent_id = b.buyer_id;

All statements should be run with the APPS schema or appropriate MO/PO responsibility grants, since the view is owned by APPS and the referenced synonyms resolve within that schema.