Search Results get_requestors




Overview
Explore in AI Chat

Overview

PO_LINE_LOCATIONS_AP_PKG is a small, read-only PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite. Its name indicates its scope: it exposes line-location-level data required by purchasing and payables processing, where a "line location" is a shipment or schedule line beneath a purchase order line. The package header carries the revision marker 120.0.12010000.1 dated 2008/09/18, consistent with its availability in both 12.1.1 and 12.2.2 release levels. Under the ETRM taxonomy it is classified as OTHER, meaning it is not a public, versioned Open Interface API, but rather an internal helper package intended for call by other EBS packages and forms. Its stated purpose is to answer three discrete questions about a given line location: when it was last received, who requested it, and how many distributions exist against it. The package declares no write operations and holds no persistent state, so it functions purely as a data retrieval layer over purchasing and receiving tables.

Key Procedures and Functions

The package specification documents three functions, each accepting a single line location identifier and returning a scalar result.

  • GET_LAST_RECEIPT — Returns the date of the most recent receipt activity recorded against the specified line location. This supports display and validation logic that depends on knowing whether goods have already arrived.
  • GET_REQUESTORS — Returns a character value identifying the requestor or requestors associated with the line location, allowing downstream logic to surface the buyer or requisition originator without an additional query.
  • GET_NUM_DISTRIBUTIONS — Returns a numeric count of the distribution records that exist for the line location, used to determine whether accounting distributions have already been generated or how many are pending.

Notably, the source retains three commented-out PRAGMA RESTRICT_REFERENCES directives. The comment "removed (GK) RNPS for package to compile, need to investigate" indicates the package was not pure enough to satisfy the declared purity levels, an important caveat for any code that assumes deterministic, side-effect-free behavior. No parameter lists beyond the single input argument should be assumed.

Tables Accessed

ETRM records two base tables referenced through APPS synonyms:

  • PO_DISTRIBUTIONS — the purchasing distribution table that records accounting charge allocations for a line location. It is the logical source for GET_NUM_DISTRIBUTIONS and likely contributes requestor and requestor-related data to GET_REQUESTORS.
  • RCV_TRANSACTIONS — the receiving transactions table, the authoritative record of receipts against a shipment. GET_LAST_RECEIPT is derived from this table, typically by selecting the maximum transaction date for the line location.

Both accesses are read-only. No insert, update, or delete behavior is documented.

Usage Notes

Because the package is classified as OTHER and is referenced by only two other packages, it should be treated as an internal dependency rather than a published integration point. It is characteristically invoked from Oracle Forms-based purchasing and receiving screens or from other APPS packages that need lightweight, single-value lookups without embedding their own SQL. Custom code may call it, but doing so carries the usual risk of relying on an unversioned, non-API object that Oracle may change without notice. The absence of active RESTRICT_REFERENCES pragmas means callers should not assume the functions are free of database state dependencies, and the functions should not be used inside SQL statements that require declared purity. For new development, the underlying PO_DISTRIBUTIONS and RCV_TRANSACTIONS tables should be queried directly against supported views.