Search Results get_reserved_flag

Overview

PO_REQS_INQ_SV is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The suffix "SV" denotes a server-side view package, a naming convention Oracle applies to packages that encapsulate query logic for one or more inquiry-only database views. The package exists to expose requisition data — header, line, and distribution information — to inquiry views and dependent programs without requiring those consumers to embed complex joins against the base purchasing tables directly.

In the ETRM record, PO_REQS_INQ_SV is classified as an OTHER API rather than a formal public API, and carries a VALID status. It references only SYS.STANDARD, indicating it is a lightweight, self-contained code unit rather than one built on top of other APPS packages. Its documented procedures and functions number ten, with NAME and GET_SHIPPED_QUANTITY explicitly listed. The package is a dependency of several inquiry views, including ICX_PO_REQUISITION_HEADERS_V, ICX_PO_REQUISITION_LINES_INQ_V, ICX_PO_REQ_HEADERS_V, and ICX_PO_REQ_LINES_V, and is referenced by five other packages within the APPS schema.

Key Procedures and Functions

The documented interface contains ten procedures and functions. Two are named in the available metadata:

• NAME — a function whose conventional role in Oracle view packages is to return a descriptive or concatenated name value used by the associated inquiry views, for example a display label derived from requisition attributes.
• GET_SHIPPED_QUANTITY — a function that returns the shipped quantity associated with a requisition line or distribution. This supports inquiry displays that compare ordered or requested quantities against quantities already shipped.

The remaining eight documented procedures and functions are not individually named in the ETRM excerpt. Parameter lists are not reproduced in the metadata and should not be assumed; consumers should inspect the package specification in the target instance before calling any member directly.

Tables Accessed

The package accesses the following tables through APPS synonyms:

• PO_HEADERS_ALL and PO_HEADERS — the purchasing document headers that supply document type, status, and supplier context for requisition inquiry rows.
• PO_REQUISITION_LINES_ALL — the core requisition line records from which inquiry views derive line-level detail.
• PO_REQ_DISTRIBUTIONS_ALL — distribution-level rows used to resolve charge accounts, quantities, and delivery detail.
• PO_LINE_TYPES_B — the line type definitions used to classify requisition lines for display and filtering.
• PO_SYSTEM_PARAMETERS — purchasing system setup values that influence default behaviour, such as currency or quantity precision.

Because the package is paired with inquiry views, its access pattern is predominantly read-oriented, retrieving and shaping data rather than performing transactional updates.

Usage Notes

PO_REQS_INQ_SV is normally invoked indirectly. The principal invocation path is through the inquiry views ICX_PO_REQ_HEADERS_V, ICX_PO_REQ_LINES_V, ICX_PO_REQUISITION_HEADERS_V, and ICX_PO_REQUISITION_LINES_INQ_V, which the Oracle iProcurement and purchasing inquiry user interfaces query at runtime. PO_LINK_REQ_DIST_PVT also depends on the package, indicating that requisition distribution linking logic reuses its query functions.

Custom code should treat the package as a read-only data source. Direct calls to members such as NAME and GET_SHIPPED_QUANTITY are possible, but since the specification is not a formally supported public API and the parameter signatures are not documented in ETRM, developers should verify the specification in the specific instance before use. The package is self-contained with respect to SYS.STANDARD, so it can be called independently of other APPS packages, but its output is intended for display and inquiry rather than for building transactional integrations.