Search Results get_request_date

Overview

ASO_SOURCING_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema associated with the Oracle Advanced Pricing / Oracle Quoting (ASO) product family. It is declared with AUTHID CURRENT_USER and is classified as a Private (PVT) API, meaning it is intended for internal use by Oracle's own Quoting and Sourcing forms, concurrent programs, and dependent server-side logic rather than for direct customer invocation. Its primary business role is to resolve sourcing and defaulting attributes for a quote — that is, to derive the customer classification, sales channel, account type, shipping and invoicing party sites, customer purchase order references, freight terms, requested dates, and other order-entry defaults that a Quoting or Order Capture form needs when a quote header or line is created or processed.

The package follows the common Oracle private-API convention: for each header-level value, a companion line-level function exists (for example, Get_Request_date vs. Get_line_Request_date). This header/line pair pattern lets the calling form default a value from the quote header onto a new line, but also allows a line-specific override to be read back when the line has been saved with its own value.

Key Procedures and Functions

Thirty documented functions make up the package. They fall into several functional groupings:

• Customer and channel derivation: GET_CUSTOMER_CLASS, GET_ACCOUNT_TYPE, GET_SALES_CHANNEL, and GET_GSA return classification attributes for a given customer account id, used to drive pricing, eligibility, and GSA (Government Supply Agency) handling.
• Quote aggregates: GET_QUOTE_QTY and GET_QUOTE_AMOUNT return the total quantity and extended amount for a quote header.
• Fulfillment attributes: GET_SHIPPABLE_FLAG reports whether a quote line is shippable.
• Account resolution: GET_CUST_ACCT returns the customer account id associated with a quote header.
• Party site resolution: GET_SHIP_TO_SITE_USE, GET_INVOICE_TO_SITE_USE, GET_SHIP_TO_PARTY_SITE, and GET_INVOICE_TO_PARTY_SITE (plus their line-level counterparts, GET_LINE_SHIP_TO_SITE_USE, GET_LINE_INVOICE_SITE_USE, GET_LINE_SHIP_PARTY_SITE, and GET_LINE_INVOICE_PARTY_SITE) return the ship-to and bill-to site-use and party-site identifiers for a quote header or line.
• Customer PO references: GET_CUST_PO and GET_LINE_CUST_PO return the customer purchase order number captured on the header or line.
• Requested dates: GET_REQUEST_DATE and GET_LINE_REQUEST_DATE return the requested (scheduled) date from the quote header or line — the object the user searched for.
• Freight terms: GET_FREIGHT_TERM returns the freight term for a quote header.

All functions return scalars (VARCHAR2, NUMBER, or DATE) and take a single identifier — a quote header id, quote line id, or customer account id — as input.

Tables Accessed

The package reads from the ASO Quoting base tables and supporting reference tables through APPS synonyms: ASO_QUOTE_HEADERS_ALL and ASO_QUOTE_LINES_ALL supply header and line records; ASO_QUOTE_LINE_DETAILS, ASO_LINE_RELATIONSHIPS, ASO_SHIPMENTS, and ASO_PAYMENTS supply fulfillment, relationship, and payment context. Customer data is drawn from HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUSTOMER_PROFILES. Item and order context come from MTL_SYSTEM_ITEMS_B and OE_ORDER_LINES_ALL. These tables provide the source values that each GET_ function resolves into a return value.

Usage Notes

Because ASO_SOURCING_PVT is a private API and is referenced by zero other documented packages through the ETRM catalogue, it is normally invoked directly by Oracle Quoting forms, Order Capture flows, and Oracle's own server-side defaulting logic rather than by external callers. Customizations that need quote header/line defaults — such as fetching the requested date or the ship-to party site — can call the package from a custom form or PL/SQL routine, but should treat it as unsupported and be prepared for signature changes across patches (the source header indicates version 115.8 as of May 2003). The function is identical in behavior between 12.1.1 and 12.2.2 because it is not part of the Online Patching (Editioning) migration; AUTHID CURRENT_USER means it executes with the caller's privileges and requires the caller to have execute authority on the package and select authority on the underlying ASO/HZ/OE tables.