Search Results po_global




Overview
Explore in AI Chat

Overview

PO_GLOBAL is a small utility package in the Oracle Purchasing application (APPS schema) whose sole documented responsibility is to hold and expose the current runtime "role" context used by Purchasing when recording lock ownership on rows in PO_HEADERS_ALL. Because Oracle EBS supports multiple concurrent actors against the same purchasing document — a buyer, a catalog administrator, and a supplier or supplier-facing user — the application needs a single, session-visible place to declare which of these actors is performing work. PO_GLOBAL provides exactly that: a package-level variable that stores the active role, along with the getter and setter used to read and change it. The package is classified by ETRM as an OTHER API, meaning it is not a public business API in the same sense as PO_HEADERS_UPDATE or PO_APPROVAL_ACTION, but rather an internal supporting construct referenced throughout Oracle's own Purchasing PL/SQL layer.

Key Procedures and Functions

  • SET_ROLE — Assigns the supplied role name to the package global variable g_role, establishing the acting role for the current database session. Callers invoke it before performing document operations that must be attributed to a specific actor type.
  • ROLE — Returns the currently assigned role as a VARCHAR2. This function is the read-side counterpart to SET_ROLE and allows downstream code to determine which actor context is in effect without querying the underlying tables.

The package additionally declares three constants that define the permitted role literals: g_role_BUYER ('BUYER'), g_role_CAT_ADMIN ('CAT_ADMIN'), and g_role_SUPPLIER ('SUPPLIER'). These values share the data type of PO_HEADERS_ALL.LOCK_OWNER_ROLE, and g_role itself is typed on that same column, ensuring that any role persisted to the header table is one the column can legally hold.

Tables Accessed

ETRM records a single referenced table, PO_HEADERS_ALL, resolved through an APPS synonym. The package does not itself issue DML against this table; rather, it uses the %TYPE anchor on PO_HEADERS_ALL.LOCK_OWNER_ROLE to strongly type the role constants and the package global. The operational significance is that PO_HEADERS_ALL.LOCK_OWNER_ROLE records which actor currently holds the document lock — a mechanism used to prevent conflicting edits during supplier-facing or catalog-maintenance flows as well as standard buyer transactions.

Usage Notes

PO_GLOBAL is typically invoked internally from Oracle Purchasing forms and PL/SQL routines rather than directly by end users. In a typical flow, application code first calls SET_ROLE with one of the declared literals, performs the document work that will stamp LOCK_OWNER_ROLE, and may subsequently call ROLE to verify or branch on the active context. The package is referenced by 13 other packages in the Purchasing schema, which is consistent with it acting as a lightweight, shared session-state holder rather than a business function in its own right.

Because the role is stored in a package-level variable, it persists for the lifetime of the database session and is not automatically reset between logical operations; custom extensions that reuse the same session should therefore set the role explicitly before relying on ROLE. Developers extending Purchasing should treat PO_GLOBAL as an internal dependency, prefer the declared constants over hard-coded role strings, and avoid modifying the package in the APPS schema, since Oracle's patching process may replace it in any release.