Search Results val_header_delete

Overview

PO_QUOTES_SV is an Oracle E-Business Suite PL/SQL server-side package owned by APPS and classified by ETRM as an "OTHER" API. It encapsulates the Quotation-specific Application Program Interfaces used by Oracle Purchasing to validate and query supplier quotation (RFQ response) data before database changes are committed. The package header declares AUTHID CURRENT_USER, so it executes with the privileges of the invoking schema rather than as definer-rights code. The header comment identifies the unit as the server-tier quotation API layer, originally authored by Melissa Snyder, with an initial change history entry dated 11-MAY-95. In the 12.1.1 and 12.2.2 code lines the package is deployed under the APPS schema and is referenced by two other packages, indicating it functions as a shared validation and query utility rather than an entry point invoked directly by end users.

Key Procedures and Functions

ETRM documents eleven program units, of which the following public procedures are named in the source excerpt:

• val_header_delete — The procedure matching the search term "val_header_delete". It verifies that the quotation header selected for deletion is not referenced on a Purchase Order line; if such a reference exists, deletion is prohibited. It exposes an IN parameter for the header identifier and an IN OUT NOCOPY BOOLEAN flag that reports whether deletion may proceed.
• val_line_delete — Verifies that the quotation line selected for deletion is not used in autosource rules and is not referenced on a requisition or Purchase Order line. Deletion is blocked when either condition holds. Parameters include the line identifier, line number, header identifier, and an IN OUT flag indicating whether deletion is permitted.
• val_reply — Validates a supplier quotation reply against purchasing rules before it is accepted.
• get_quote_status — Returns the current status of a quotation for display and processing decisions.
• get_from_rfq_defaults — Supplies default values derived from an RFQ when quotation records are created or copied.
• get_approved_status — Returns the approval state of a quotation, drawing on quotation approval data.

The source excerpt also shows a test entry point, test_val_header_delete, which exposes the header-deletion validation directly for diagnostic purposes, and named specification entries such as NAMES and NAME that appear in the ETRM unit list.

Tables Accessed

All table access is performed through APPS synonyms. PO_HEADERS and PO_LINES are read to determine whether a quotation header or line has been carried onto a Purchase Order and therefore cannot be removed. PO_REQUISITION_LINES is queried for the same purpose at line level, since a quotation line may already have been sourced onto an internal requisition. PO_AUTOSOURCE_DOCUMENTS and PO_ASL_DOCUMENTS are consulted to detect whether a quotation line participates in autosource rules or approved supplier list sourcing. PO_QUOTATION_APPROVALS supplies the approval status returned by get_approved_status. DBMS_OUTPUT is referenced for diagnostic message output during validation and debugging. The package is read-oriented for validation; it does not itself delete quotation records, leaving that action to the calling form or program once the flag is returned as TRUE.

Usage Notes

PO_QUOTES_SV is invoked from the Oracle Purchasing Quotations window when a user attempts to delete a quotation header or line; the form calls val_header_delete or val_line_delete and suppresses the delete when the OUT flag is set to FALSE. The query procedures (get_quote_status, get_from_rfq_defaults, get_approved_status) support defaulting and status display on those same forms. Because the package is referenced by two other packages, it may also be called from quotation-related batch or workflow validation logic and from custom extensions that need the same referential checks before purging quotation data. Custom code should call the public procedures rather than the internal test entry point, and should treat the IN OUT delete flag as an authoritative veto: a FALSE result indicates a hard business block, not a warning. As with all APPS-owned APIs, direct modification of the package is not supported; extensions should wrap the documented procedures.