Search Results po_req_lines_sv1




Overview
Explore in AI Chat

Overview

PO_REQ_LINES_SV1 is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite. The "_SV1" suffix identifies it as a server validation or secondary server-side library associated with the Purchasing (PO) module's requisition lines entity. Its documented API classification is OTHER, indicating that it is not registered as a formal public interface such as an Open Interface or an API conformance program, but instead functions as an internal support library. It provides shared runtime logic that other requisition-related packages and views rely upon rather than exposing a standalone business service to end users.

The package status is documented as VALID, and it depends only on the SYS.STANDARD package, revealing that it is intentionally thin: it does not carry an extensive dependency tree of its own, so downstream callers absorb the database objects and business logic rather than this unit. This design is characteristic of helper packages that encapsulate naming, lookup, and defaulting behavior consumed at multiple points in the requisition line lifecycle.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions, of which two are explicitly named: NAMES and NAME. No parameter lists are documented, and none are reproduced here.

  • NAMES — A naming or identifier routine documented within the package. In the requisition line context, routines of this family are typically used to resolve or return descriptive names, labels, or concatenated identifiers for requisition line attributes that must be presented consistently across forms and reports.
  • NAME — The singular counterpart to NAMES, documented for retrieving an individual name value. Such routines are conventionally used to translate an internal code or ID into its user-facing name for display or validation.

The remaining four documented procedures and functions are not individually named in the available extract. Based on the package's naming and its dependency footprint, they perform related lookup and defaulting work for requisition line attributes. Because the metadata does not expose signatures, no parameter details are asserted here.

Tables Accessed

The package accesses the following base tables through APPS synonyms:

  • PO_REQUISITION_LINES — The core requisition line entity storing quantity, price, item, and accounting distributions against which validation and defaulting occurs.
  • PO_REQUISITIONS_INTERFACE — The requisition interface staging table, indicating that the package participates in validation of inbound requisition data before it is processed into the base tables.
  • MTL_SYSTEM_ITEMS — The item master, used to validate and resolve item attributes such as description, unit of measure, and purchasing-enabled status.
  • MTL_UNITS_OF_MEASURE — The unit of measure reference table, used to validate and describe UOM codes on requisition lines.
  • PO_LOCATION_ASSOCIATIONS — Establishes which ship-to and deliver-to locations are valid for a given requisitioning context, supporting location defaulting and validation.

Usage Notes

The dependency information shows that PO_REQ_LINES_SV1 is referenced by POR_AUTOSOURCE_UTIL_PKG, POR_UTIL_PKG, and PO_REQUISITION_HEADERS_V, and is referenced by three other packages in total. This confirms that the package is invoked indirectly: it is called from the autocreate and sourcing utility logic and from the requisition headers view rather than being driven directly by an Oracle Forms block or a concurrent program.

Typical invocation therefore occurs during requisition entry and update, during autocreate processing where requisition lines are sourced to purchase orders, and during requisition interface validation. Customizations should treat the package as an internal library and avoid direct calls where a documented Open Interface or API exists, since the absence of API registration means its behavior is not guaranteed across patches or upgrades.