Search Results aso_opp_qte_pub




Overview
Explore in AI Chat

Overview

ASO_OPP_QTE_PUB is a public PL/SQL API package in the Oracle E-Business Suite Order Management/Advanced Pricing family, owned by the APPS schema and classified as a PUB (published) interface. Its stated purpose, taken directly from the package header comments, is to provide an API to create a quote from an opportunity. In the Oracle TeleSales / Sales foundation flow, a sales representative works an opportunity record and, when the prospect is ready to buy, converts that opportunity into a formal quote using Quote Order Management functionality. ASO_OPP_QTE_PUB encapsulates the server-side logic required for that conversion, shielding callers from the underlying complexity of the ASO_QUOTE_PUB quote creation interface and the various related entity tables. The package carries the header identifier asopopqb.pls and the version string 120.16.12000000.3, indicating it is a long-standing, patched component of the EBS 12.1.1 and 12.2.2 code lines. It is one of the integration points between the opportunity/lead tracking data model in Oracle Sales and the quoting data model in Oracle Quoting.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions within the package body:

  • CREATE_QTE_OPPORTUNITY — the principal entry point and the reason the package exists. It accepts a source code that identifies the originating channel, a full quote header record, header-level payment, shipment, and tax detail records, a template collection, and an opportunity-to-quote input record. It returns an opportunity-to-quote output record together with the standard FND_API return status, message count, and message data variables. It also accepts the standard API version number, initial message list flag, commit flag, and validation level. Conceptually it validates the input, drives the creation of the quote and its associated lines and details, links the quote to the originating opportunity, and returns the outcome to the caller.
  • VALIDATE_ITEM — a supporting validation routine used to verify the eligibility or correctness of an item being placed on the quote before the quote is written.
  • SET_COPY_FLAGS — a helper that establishes the flags governing what data is copied from the opportunity or template into the new quote, controlling the copying behavior during conversion.
  • ADDRESS_VALIDATION — a routine that checks the addresses associated with the customer or party for the quote, ensuring that only valid location and site information is carried forward into the quotation.

Tables Accessed

The package reads and writes a broad set of operational tables through APPS synonyms, reflecting the dual nature of the operation (sales opportunity plus quote). Quote-side tables include ASO_QUOTE_HEADERS_ALL (the header being created), ASO_QUOTE_ACCESSES (quote-level access control), and AS_SALES_CREDITS (sales credit assignment for the opportunity/quote). Opportunity and lead-side tables include AS_LEADS_ALL and AS_LEAD_LINES_ALL, which hold the source opportunity and its lines. Trading partner data is drawn from HZ_CUST_ACCOUNTS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOC_ASSIGNMENTS, HZ_CONTACT_POINTS, and HZ_CUSTOMER_PROFILES, supplying account, site, contact, and profile information. The AMS_SOURCE_CODES table supplies the source code that classifies the origin of the opportunity. Finally, FND_ATTACHED_DOCUMENTS, JTF_NOTES_B, and JTF_TASKS_B provide for attachments, notes, and tasks associated with the opportunity or quote.

Usage Notes

ASO_OPP_QTE_PUB is invoked programmatically rather than through direct user data entry. It is referenced by ten other packages in the EBS code base, which use it to perform opportunity-to-quote conversion on behalf of the Applications forms, concurrent processing, and other integration flows. Typical callers include the Oracle TeleSales and Oracle Quoting user interfaces, where the server-side form logic calls this API when a user chooses to generate a quote from an opportunity, and background or workflow-driven processes that automate quote creation. Because the package follows the standard FND_API conventions (API version number, initial message list, commit flag, validation level, return status, and message stack), it is suitable for use from custom PL/SQL, concurrent programs, and integration code, provided that the caller manages transaction boundaries by passing the commit flag appropriately and observes the returned message data for error handling.