Search Results opp_qte_in_rec_type

Overview

ASO_OPP_QTE_PUB is the public Oracle E-Business Suite API package responsible for creating and maintaining sales quotes that originate from opportunities or leads within Oracle Sales and Oracle Quoting. The package header identifies its purpose succinctly as an "API to create quote from opportunity," positioning it as the supported programmatic bridge between the lead and opportunity data model (AS_LEADS_ALL, AS_LEAD_LINES_ALL) and the quoting data model (ASO_QUOTE_HEADERS_ALL, ASO_QUOTE_ACCESSES, AS_SALES_CREDITS).

The package is declared with AUTHID CURRENT_USER and resides in the APPS schema, giving it the standard invoker's-rights security semantics used by EBS public APIs. It defines the OPP_QTE_IN_REC_TYPE record and the corresponding OPP_QTE_IN_TBL_TYPE PL/SQL table type, which carry the quote attributes supplied by callers. Each record attribute is defaulted to the corresponding FND_API.G_MISS_* sentinel value, enabling the API to distinguish "not supplied" from an explicit null. Documented attributes include the opportunity identifier, quote number and name, sold-to customer account, primary salesperson and sales group, sold-to contact and party site, price list, order type, agreement and contract template information, currency, marketing source code, quote expiration date, pricing and tax status indicators, and the operating unit identifier (ORG_ID) that supports multi-org access control. The package classifies as a PUB API in the ETRM 12.2.2 metadata and is referenced by ten other application packages.

Key Procedures and Functions

• CREATE_QTE_OPPORTUNITY — The primary documented entry point and the object most frequently targeted by searches such as "create_qte_opportunity." It creates a quote from opportunity or lead data, accepting the OPP_QTE_IN_REC_TYPE record (or table of records) and returning the standard EBS API outputs, including return status, message count, and message data. Callers must supply the opportunity identifier and the operational context needed to derive the quote header and its associated access, credit, and note records.
• VALIDATE_ITEM — Performs validation of item-level information associated with the quote creation flow, ensuring that referenced inventory or pricing entities satisfy the prerequisites expected by the quoting schema before the quote lines are persisted.
• SET_COPY_FLAGS — Establishes the copy-control flags used when quote content is duplicated from a source opportunity or template, allowing the caller to govern which elements of the source are carried forward into the newly created quote.
• ADDRESS_VALIDATION — Validates address data (sold-to party site, contact, location assignments) used on the quote, confirming that the supplied address references exist and are consistent with the customer and party-site model held in the HZ tables.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• ASO_QUOTE_HEADERS_ALL, ASO_QUOTE_ACCESSES, AS_SALES_CREDITS — the core quoting tables written during quote creation, including the header, access control rows, and sales credit assignments.
• AS_LEADS_ALL, AS_LEAD_LINES_ALL — the opportunity/lead source data read to seed the new quote.
• AMS_SOURCE_CODES — marketing source code validation.
• HZ_CUST_ACCOUNTS, HZ_CUSTOMER_PROFILES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOC_ASSIGNMENTS, HZ_CONTACT_POINTS — customer, site, location, and contact validation for sold-to and contact data.
• FND_ATTACHED_DOCUMENTS, JTF_NOTES_B, JTF_TASKS_B — attachment, note, and task records associated with the generated quote.

Usage Notes

ASO_OPP_QTE_PUB is typically invoked from Oracle Sales and Oracle Quoting application flows when a user converts an opportunity or lead into a quote, and from concurrent or custom PL/SQL programs that automate quote generation. Custom code should declare the OPP_QTE_IN_REC_TYPE record, populate only the required attributes (leaving others at their G_MISS_* defaults), and call CREATE_QTE_OPPORTUNITY within the standard EBS API error-handling pattern, checking the return status and message data before committing. Because the package is AUTHID CURRENT_USER, callers require direct grants on the package and on the underlying tables, and appropriate MOAC initialization (setting ORG_ID and the operating unit context) is required for multi-org installations.