Price Lists

This chapter covers the following topics:

Overview of Price Lists

Price lists are essential to ordering products because each item entered on an order must have a price. Each price list contains basic list information and one or more pricing lines that define prices for all levels of your product hierarchy: at the item level, category level, or any level that you define. Basic price list information includes the price list name, effective dates, currency, pricing controls, and shipping defaults such as freight terms and freight carrier. For a price list, you can define price breaks, pricing attributes, qualifiers, and secondary price lists.

Oracle Advanced Pricing provides an HTML-based user interface (UI) that features guided steps, user-friendly pages, and shortcut links for setting up and maintaining modifiers, price lists, and qualifiers. You can use this HTML format for many tasks that were previously available using only the Oracle forms-based UI.

Information about the following price list topics (for both the HTML UI and the forms-based UI) is available in the Oracle Advanced Pricing User's Guide, Price Lists chapter:

Pricing for Hierarchical Item Categories

You can set up prices and modifiers based on hierarchical item categories and flattened item categories. You must define category-based pricing for hierarchical categories for price lists or modifiers; however, to do this, you must set a default hierarchical category set (catalog) for the functional area of the source system creating the data.

If you are creating category-specific price lists and modifiers, then you can select (from the Product field) the categories associated with those enabled functional areas for a given source system for that pricing transaction entity (PTE). You can select from hierarchical or flattened categories because one or more functional areas can be defined for a source system. The default category set (or catalog) associated with the functional area may be hierarchical.

Note: Item categories for price lists are always based on the item category of the item at the Master level and not at the Org (organization) level.

Related Topics

Oracle Advanced Pricing User's Guide, Price Lists chapter

Bulk Importing of Price Lists

The Pricing Data Bulk Loader API, which is available for Basic and Advanced Pricing, enables you to:

This API consists of a set of interface tables and a concurrent program that enable you to import large volumes of price list data (for example, from a legacy system).

Related Topics

Pricing Data Bulk Loader API

Usage Price Break Proration

You can prorate price breaks to support the following business scenarios:

Some bills are based on predefined cycles; for example, a service provider may bill at the end of every calendar quarter. However, a customer may want to start service with that provider on a date other than the quarter start date. Therefore, the contract start date would fall into the middle of a billing period.

One usage line on a contract may have a complex billing schedule. For example, a bill for one period of 15 days, followed by two periods of 1 month, then four periods of 1 quarter. However, the usage line would be associated with only one pricing definition in the price list.

That pricing definition may be based on monthly usage. So when the 15 days or the quarter billing periods must be billed, the usage breaks must be prorated to suit the circumstances.

Prorating price breaks is optional and controlled by the profile QP: Break UOM Proration Allowed. This profile must be set to Yes to use this feature.

Example 1: Price Break by Quarter

The following table displays the conversion for a break defined by quarter:

Value From/To Conversion
Value From/To Before Conversion) Value From/To (After Conversion)

Note: Prorated breaks will not be truncated.

0 - 5 0 to 1.666...6
5 - 10 1.666...6 to 3.333...3
10 - 20 3.333...3 to 6.666...6
20 - 99 6.666...6 to 33

Example 2: Price Break by Month

The following table displays the conversion for a break defined by month:

Value From/To Conversion
Value From/To (Before Conversion) Value From/To (After Conversion)
0 - 5 0 - 15
5 - 10 15 - 30
10 - 20 30 - 60
20 - 99 60 - 297

If the incoming value is 15, which belongs to the first two breaks, the first break is selected because the calculation is greater than Value From and less than and equal to Value To.