Search Results get_purchase_price

Overview

CTO_CUSTOM_PURCHASE_PRICE_PK is an Oracle EBS component belonging to the Configure-to-Order (CTO) family of APIs supplied under the APPS schema. Its documented purpose, as stated in the package header commentary, is to determine a purchase price for a configured model based on the configuration options selected on the sales order line in OE_ORDER_LINES. The package exists to support sourcing and costing decisions made against a model item before the corresponding configuration item has actually been created. It is classified in ETRM as an OTHER API, indicating that it is a customization hook rather than a supported, Oracle-maintained business API.

The package is delivered as a stub. The shipped body contains a single function whose entire executable content is a literal RETURN FALSE; statement, accompanied by source comments instructing implementers that the function may be replaced by custom code that calculates the price for the configuration. Consequently, the functional value of the package is realized only when a customer or partner supplies their own implementation. In its unmodified form it performs no pricing logic and imposes no processing overhead.

Key Procedures and Functions

One program unit is documented: the function GET_PURCHASE_PRICE. Its business purpose is to return a purchase price, or a Boolean indication of whether a purchase price could be determined, for a model item evaluated against a selected vendor and vendor site. The header commentary explains that the price list used for this evaluation can be organization dependent, and that organization context is therefore expected to be supplied through the input parameters. The function is designed to be called while the configuration item is still undefined; all lookups must therefore be resolved against the model item and the options recorded on the sales order. The declared return type is Boolean.

The documented body returns FALSE unconditionally. Where the function returns null or otherwise fails to resolve a price, the model's list price is expected to default through to the configuration item. No other procedures, functions, or overloads are documented for this package.

Tables Accessed

No tables are referenced in the documented metadata. Consistent with the package header, an implemented version of GET_PURCHASE_PRICE would be expected to query OE_ORDER_LINES for the configuration options captured on the sales order, and to consult Oracle Purchasing and Advanced Pricing views to resolve a vendor-specific price list. Any such access is the responsibility of the custom implementation and is not part of the delivered stub. Because no APPS synonym references are documented, no direct table dependencies should be assumed when assessing the impact of database changes on this package.

Usage Notes

The package is invoked during order processing, at the point where a configuration item has not yet been instantiated and a purchase price for the configured model must be established. ETRM records that the package is referenced by one other package, which is the anticipated calling path. Direct invocation from forms code or custom concurrent programs is possible but is not documented. Because the delivered body is a stub that always returns FALSE, any deployment relying on this package must first install a custom body implementing the pricing rules required by the business. The header date stamp of March 2002 and version 115.0 indicate the stub is unchanged across the 12.1.1 and 12.2.2 releases, so customizations written against earlier releases remain structurally valid, though they must be revalidated against online patching and editioning requirements in 12.2.2.