Search Results po_reqs_sv




Overview
Explore in AI Chat

Overview

PO_REQS_SV is a server-side validation and processing package in the Oracle E-Business Suite Purchasing module (APPS schema). The suffix "SV" denotes a server validation package, indicating that its primary responsibility is to enforce business rules and referential integrity for requisition data before records are committed to the database. In Oracle EBS 12.1.1 and 12.2.2, this package supports the Requisition Management functional area by validating requisition headers, lines, and distributions against purchasing controls such as approval status, document attachment integrity, action history, and organizational access through FND_GLOBAL.

The package is classified as OTHER in the ETRM API registry rather than as a public or private API, meaning it is an internal implementation package invoked by Oracle Forms and other Purchasing components rather than a documented integration point for external callers.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within PO_REQS_SV. The available excerpt lists the procedure name column without exposing individual signatures; consistent with its role as a validation server package, these routines collectively perform checks and processing on requisition documents. The documented dependency on PO_MESSAGE_S and FND_MESSAGE indicates that the procedures raise seeded and dynamically composed error messages when validation fails, and the dependency on APP_EXCEPTION confirms structured exception handling is used to surface these failures to the calling form or program.

The package also depends on PO_APPROVAL_REMINDER_SV, indicating that some procedures interact with approval reminder logic, and on FND_ATTACHED_DOCUMENTS2_PKG for attachment-related validation. PO_REQUISITION_HEADERS_PKG is referenced for header-level processing. No parameter lists are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

PO_REQS_SV references four core Purchasing tables through APPS synonyms:

  • PO_REQUISITION_HEADERS — the requisition header record, validated for approval status, document type, and preparer identity.
  • PO_REQUISITION_LINES — requisition line records, validated for item, category, quantity, and price integrity relative to the header.
  • PO_REQ_DISTRIBUTIONS — distribution records that allocate requisition line charges, validated for accounting and charge account consistency.
  • PO_ACTION_HISTORY — the audit trail of actions performed on the requisition, read and written to record approval, submission, and change events.

Additional dependencies include PO_CORE_S, PO_MESSAGE_S, PO_REQS_SV, FND_GLOBAL, FND_MESSAGE, APP_EXCEPTION, FND_ATTACHED_DOCUMENTS2_PKG, PO_APPROVAL_REMINDER_SV, and PO_REQUISITION_HEADERS_PKG.

Usage Notes

PO_REQS_SV is typically invoked indirectly. The Requisition entry forms (such as POXRQERQ) call validation routines in this package when a user saves, submits, or approves a requisition, ensuring that header, line, and distribution data satisfy purchasing business rules before database commit. Concurrent programs and workflows in the requisition approval cycle may also trigger its routines, particularly those interacting with PO_APPROVAL_REMINDER_SV and PO_ACTION_HISTORY.

The ETRM metadata states that PO_REQS_SV is not referenced by any database object but is itself referenced by three other packages. Custom code should avoid calling this package directly; instead, the documented public APIs such as PO_REQUISITION_HEADERS_PKG should be used for requisition creation and modification, leaving PO_REQS_SV as the internal validation layer it is designed to be.