Results for “get_selling_price”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CTO_PUBLIC_UTILITY_PK is a public PL/SQL package in the Oracle E-Business Suite Configure-to-Order (CTO) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its stated purpose, per the package header, is to expose APIs that are called from other Oracle products. The package was deliberately segregated into its own file (CTOPUTLS.pls) to minimize compile-time and runtime dependencies on the broader CTO code base, making it a stable, lightweight integration surface for external callers. Within ETRM the package is classified under the API classification "OTHER," indicating that it is not a standard Open Interface or public business API in the strict sense, but rather a utility API intended for controlled cross-product consumption. Its principal business role is the calculation of selling prices for configured (ATO/CTO) items, removing the need for calling applications to reimplement configuration pricing logic. The package originates from a 2002 creation by Shashi Bhaskaran and was subsequently maintained through bug fixes tracked in the source header (for example, Bugfix 2695239). The behavior described below is consistent across Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented API surface consists of a single procedure, GET_SELLING_PRICE. This procedure calculates the selling price of a configured model and returns both unit-level and quantity-extended price information to the caller.

• GET_SELLING_PRICE — Computes the selling price for a configuration. Inputs identify the configuration line, the parent ATO model line (optional, defaulting to NULL), and the quantity for which the total selling price is required. Outputs include the unit selling price of the model, the total selling price for the requested quantity, and the currency code of the associated order line. The procedure also returns a standard API return status (FND_API.G_RET_STS_SUCCESS or FND_API.G_RET_STS_ERROR) together with an error code. It distinguishes between hard errors, where both the error code is set and the return status reports an error, and soft errors, where the error code is set but the return status still reports success, allowing the caller to proceed while capturing diagnostic information.

Tables Accessed

ETRM documents references to two base tables through APPS synonyms:

• OE_ORDER_HEADERS_ALL — The order header provides order-level context, including the currency in which the configuration is priced, which the procedure returns as the currency code output.
• OE_ORDER_LINES_ALL — The order line supplies the configuration line and model line identified by the input parameters, and is the source of the configuration and pricing attributes evaluated during price calculation.

These tables are read to resolve the order context and configuration identity required to derive selling prices; the procedure is oriented toward retrieval and calculation rather than maintenance of order data.

Usage Notes

GET_SELLING_PRICE is intended for invocation from other Oracle application modules and from custom code that needs configuration pricing without duplicating CTO logic. Typical callers include order-entry forms and related pricing flows in Order Management, other CTO packages, and customer extensions or integrations. ETRM records that the package is referenced by two other packages, confirming its role as a shared dependency. Because the inputs include both a configuration line identifier and an optional model line identifier with a default of NULL, callers can invoke the API when only the configuration line is known, or pass the model line explicitly when it is available. Callers should always inspect the return status and error code, and should treat the soft-error condition as a signal that pricing completed but with a reportable exception.