Search Results get_max_sequence_num

Overview

PO_RFQ_VENDORS_PKG_S3 is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM as OTHER. It belongs to the family of RFQ (Request for Quotation) vendor packages that support the Oracle Purchasing module, specifically the sourcing and supplier response functionality associated with RFQ header and vendor records. The package is declared with AUTHID CURRENT_USER, meaning that at runtime the PL/SQL code executes with the privileges of the invoking user rather than the definer, which is consistent with the security model used by Oracle Purchasing's internal APIs and their handling of RFQ vendor data.

The primary business responsibility of this package is to support uniqueness validation and sequence-number assignment for RFQ vendor records. RFQ processing in Oracle Purchasing requires that vendor lines associated with a given RFQ header be uniquely identified, and the package provides a controlled mechanism to validate incoming row data and to derive the next available sequence number for a given RFQ header. The source header reference dates the file to the 11.5.x era of Oracle Applications, and the object remains documented in the 12.1.1 and 12.2.2 environments as part of the technical foundation that underpins RFQ vendor handling.

Key Procedures and Functions

• CHECK_UNIQUE — A procedure that performs uniqueness validation on RFQ vendor data. Based on the documented signature, it accepts a row identifier, a sequence number, and a PO header identifier. Its purpose is to verify that a given vendor/sequence combination is unique within the scope of the specified RFQ header, preventing the creation of duplicate vendor entries for the same quotation request.
• GET_MAX_SEQUENCE_NUM — A function that returns a number, accepting a PO header identifier as input. Its purpose is to determine the maximum sequence number currently assigned to RFQ vendors belonging to the specified RFQ header, so that a new sequence value can be allocated. This is the function most commonly referenced when developers search for sequence-number management logic in RFQ vendor processing.

The source excerpt includes a commented-out pragma restrict_references directive for GET_MAX_SEQUENCE_NUM, indicating that a purity constraint had been considered but was not active in the shipped version. Only these two documented program units are exposed by the specification.

Tables Accessed

• PO_RFQ_VENDORS — The principal table for RFQ vendor records. CHECK_UNIQUE validates uniqueness against this table, and GET_MAX_SEQUENCE_NUM derives the maximum sequence number from it, scoped by PO header identifier.
• DUAL — Referenced for standard PL/SQL expression evaluation, typically in SELECT statements that compute a value or test for existence without querying a data table directly.

Usage Notes

PO_RFQ_VENDORS_PKG_S3 is an internal Oracle Purchasing package and is not documented in ETRM as being referenced by any other package. It is typically invoked by the RFQ / quotation forms and by server-side logic that manages supplier responses to requests for quotation. Customizations that insert or manipulate RFQ vendor rows should use the package's uniqueness check before committing, and should call GET_MAX_SEQUENCE_NUM to obtain the correct next sequence number rather than querying PO_RFQ_VENDORS directly.

Because the package depends on AUTHID CURRENT_USER semantics, callers must hold the necessary object privileges on the underlying tables, and direct invocation from custom code should be limited to environments where the standard Purchasing schema grants are in place. As with all internal EBS APIs, Oracle does not guarantee backward compatibility of these program units across releases, so custom code referencing them should be validated carefully when upgrading between 12.1.1 and 12.2.2.