Search Results po_headers_s




Overview
Explore in AI Chat

Overview

PO_RFQS_SV is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the validation logic surrounding Requests for Quotation (RFQ) processing in Oracle Purchasing. The suffix "SV" conventionally denotes a server-side validation package in the EBS naming standard, and PO_RFQS_SV performs exactly that role: it enforces referential and business-rule integrity for RFQ headers and lines prior to deletion or modification. The package is classified as "OTHER" in the ETRM taxonomy, meaning it is an internal, non-public API rather than a certified open interface.

In EBS 12.1.1 and 12.2.2, RFQs are stored in PO_HEADERS (with the "_S" companion table holding descriptive/translatable columns) and their associated quotation lines in PO_LINES. Because RFQs participate in the sourcing lifecycle and may be referenced by vendor lists, approved supplier lists, and quotation responses, the integrity checks performed by PO_RFQS_SV are essential before records can be removed or altered. The package is not referenced by any other database object, confirming its role as a terminal validation layer invoked directly by the application rather than by other PL/SQL units.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions in the package. Four are named in the excerpt:

  • NAMES — A utility routine that resolves or returns naming information associated with RFQ records, typically used to populate descriptive fields or messages.
  • NAME — A singular counterpart to NAMES, returning a single name value for a given RFQ context.
  • VAL_HEADER_DELETE — The header-level validation routine. It determines whether a given RFQ header may be deleted, checking for dependent child records and other business constraints before permitting the delete.
  • VAL_LINE_DELETE — The line-level validation routine. It performs the analogous check at the RFQ line level, verifying that no downstream references prevent deletion of a specific quotation line.

The remaining four documented procedures follow the same naming and validation conventions but are not individually identified in the excerpt. No parameter lists are published; the routines are internal and their signatures are not part of any supported API contract.

Tables Accessed

The package references the following APPS synonyms:

  • PO_HEADERS / PO_HEADERS_S — The primary RFQ header tables; the "_S" table holds the descriptive (translatable) columns. Note that the user's search term "po_headers_s" maps directly to this dependency. These are read to evaluate the header being validated and to confirm its existence and state.
  • PO_LINES — RFQ lines associated with the header; read to detect child records that would block a header delete and to validate individual line deletes.
  • PO_RFQ_VENDORS — Associates vendors with an RFQ; queried to ensure no active vendor solicitation exists before deletion.
  • PO_VENDOR_LIST_ENTRIES / PO_VENDOR_LIST_HEADERS — Vendor list structures used in sourcing; checked for references that would be invalidated by removing the RFQ.

References to PO_VENDORS, PO_VENDOR_LIST_ENTRIES_V, DUAL, and STANDARD also appear in the dependency tree, supporting lookups and basic PL/SQL functionality.

Usage Notes

PO_RFQS_SV is invoked by RFQ maintenance forms and any concurrent or custom code that programmatically manipulates RFQ records. It is not a public API and must not be called directly by customizations; doing so bypasses supported upgrade paths. Integrators working with RFQ data should use the documented Purchasing open interfaces and public APIs, treating PO_RFQS_SV purely as an internal integrity guard. Because it is referenced by two other packages, changes to its behavior can cascade, so it should be treated as read-only from a customization standpoint.