Search Results price_line

Overview

The package body APPS.OE_ORDER_PRICE_PVT1 belongs to the Order Management pricing integration layer in Oracle E-Business Suite. Its documented purpose is to expose the core pricing entry point known as Price_Line, which the source header annotation explicitly describes as "the main Pricing Integration API." The stated design intent is that this API can be used to price an entire order, a single order line, or multiple lines in one invocation, making it the central gateway through which Order Management passes order data to the pricing engine for evaluation, adjustment application, and price finalization.

As its name and classification indicate, this is a private ("_PVT") implementation unit rather than a public-facing API. The _PVT naming convention in Oracle Order Management denotes internal helper packages that support the published OE_ORDER_PUB and related public APIs. Consequently, the package is not intended for direct customer invocation and is listed in the ETRM metadata with an API classification of OTHER. The header revision string (OEXVPRCB.pls 115.10 2003/10/20) shows a file that has been stable since the 11.5.x code line and is carried forward essentially unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package includes one procedure:

• PRICE_LINE — Identified in the source comments as the main Pricing Integration API. It is responsible for driving pricing for an order header, an individual order line, or a set of lines. The commented signature reveals the general shape of the interface: a header identifier, a line identifier, an input/output line collection typed as oe_Order_Pub.Line_Tbl_Type, a control record of type OE_ORDER_PRICE_PVT.control_rec_type, an input string describing the pricing events to be triggered, and an output return status variable. In the delivered body the procedure is a stub — its executable section contains only NULL; — indicating that the active implementation resides elsewhere, and this unit defines the interface contract rather than the processing logic.

No additional procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms by this package body. This is consistent with the fact that the delivered body is a stub: because the executable section contains no DML or queries, no table dependencies are registered. Where the functional implementation performs its work (for example, in the surrounding OE_ORDER_PRICE_PVT family), the pricing process reads and writes order lines, price adjustments, and related pricing structures, but such activity is not attributable to OE_ORDER_PRICE_PVT1 itself according to the documented references.

Usage Notes

• The procedure is not a public API and should not be called directly by custom code; the "_PVT1" suffix marks it as an internal Order Management unit.
• Pricing of orders and lines in standard flows is driven from the Order Management forms and the public Order Management APIs, which internally reach the pricing integration layer rather than this specific body.
• The source comment documents the original intent of the interface; because the delivered body is a stub, any invocation is effectively a no-op, and custom developers should rely on the public pricing and Order Management entry points instead.
• The ETRM metadata lists zero packages referencing OE_ORDER_PRICE_PVT1, reinforcing that it is not a dependency of other documented units.