User’s Guide Release 11i...viii QP: Bulk Import of Price List program..... 10-17 QP: Maintains the...

Oracle® Advanced PricingUser’s Guide

Release 11i

Part No. B13966-01

May 2004

Oracle Advanced Pricing User’s Guide, Release 11i

Part No. B13966-01

Copyright © 1996, 2004, Oracle. All rights reserved.

Primary Author: John Salvini

Contributing Authors: Manoj Arya, Rajendra Badadare, Hariram Balasubramanian, Vishwajit Bhave, Reb Bowman, Rajeshwari Chellam, Amy Cui, Spencer Firestone, T. Geresh, Sripriya Gopal, Vivek Gulati, Dharmender Gupta, Nitin Hase, Leslie Hershey, Natarajan Kannan, Nirmal Kumar, Justin Kuo, Jeff Lee, Vivian Lee, Justin Lin, Shu-Hui Lin, Maria Viglionese Matheny, Steven Mosura, Tom Myers, Rajmohan Nair, Vinod Narayanan, Sameer Phatarpekar, Abhijit Prasad, Sweta Rashmi, Sumeet Rijhsinghani, Nisha Samaga, Renganathan Sreenivasan, Ravi Tata, Boon Tea, Giridhar Tippireddy, Kiran Umakanth, Hock-Shan Wong, Linda Xu, Li Yang

Contributors: Elizabeth Looney, David Reitan, Rebecca Zarchikoff

The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.

If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Contents

Send Us Your Comments ................................................................................................................... ix

Preface............................................................................................................................................................ xi

Audience for this Guide ...................................................................................................................... xiiHow To Use This Guide ...................................................................................................................... xiiiDocumentation Accessibility ............................................................................................................ xiv

Accessibility of Code Examples in Documentation.................................................................. xivAccessibility of Links to External Web Sites in Documentation............................................. xiv

Other Information Sources ................................................................................................................. xvOnline Documentation................................................................................................................... xvRelated User Guides....................................................................................................................... xvGuides Related to All Products ................................................................................................... xviInstallation and System Administration .................................................................................... xviOther Implementation Documentation..................................................................................... xviii

Training and Support ........................................................................................................................... xxTraining............................................................................................................................................ xxSupport............................................................................................................................................. xx

Do Not Use Database Tools to Modify Oracle Applications Data............................................. xxiAbout Oracle........................................................................................................................................ xxiiFeedback ............................................................................................................................................... xxiii

1 Oracle Advanced Pricing

Overview of Oracle Advanced Pricing ........................................................................................... 1-2Using Oracle Advanced Pricing in the HTML Interface ........................................................ 1-6

iii

General Pricing Concepts .......................................................................................................... 1-11Pricing Components ................................................................................................................... 1-15

2 Qualifiers and Qualifier Groups

Overview of Oracle Advanced Pricing Qualifiers ....................................................................... 2-2Using Qualifiers ............................................................................................................................ 2-3Creating Qualifiers for Price Lists .............................................................................................. 2-5Creating Qualifiers for Modifiers ............................................................................................... 2-5

Creating Qualifiers (HTML Interface)............................................................................................ 2-6Updating a Qualifier (HTML Interface) .................................................................................. 2-12Deleting a Qualifier (HTML Interface) .................................................................................... 2-14Appending a Qualifier Group (HTML Interface) .................................................................. 2-15

Creating a Qualifier Group ............................................................................................................. 2-17Using Qualifier Grouping Numbers........................................................................................ 2-21Using Qualifier Grouping Numbers across Qualifier Groups............................................. 2-25

Querying a Qualifier Group ........................................................................................................... 2-28Modifying or Deleting Qualifier Groups .................................................................................... 2-29

3 Modifiers

Overview of Modifiers ...................................................................................................................... 3-3Using the HTML User Interface with Modifier Lists and Modifiers .................................... 3-3Modifier Concepts ........................................................................................................................ 3-5

Creating a Modifier List .................................................................................................................. 3-22Creating List Level Qualifiers ........................................................................................................ 3-29Creating Modifier Lines .................................................................................................................. 3-33

Using Accumulated Range Breaks........................................................................................... 3-65Attaching Pricing Attributes to Modifier Lines ..................................................................... 3-69Excluding Items from a Modifier ............................................................................................. 3-71Creating Line Level Qualifiers.................................................................................................. 3-74

Copying a Modifier List .................................................................................................................. 3-77Copying a Modifier Line ................................................................................................................. 3-80Using Modifiers in the HTML User Interface............................................................................. 3-81

Creating a Modifier List (HTML Interface)............................................................................. 3-83Modifier Lists and Line Types .................................................................................................. 3-84Other Concepts............................................................................................................................ 3-84

iv

Creating Modifier Lines (HTML Interface) ............................................................................ 3-92Defining Controls for Modifier Lines (HTML Interface)...................................................... 3-95Creating a Discount Modifier Line (HTML Interface) .......................................................... 3-99Creating a Price Break Modifier Line (HTML Interface) .................................................... 3-104Creating a Promotional Goods Modifier Line (HTML Interface)...................................... 3-111Creating a Surcharge Modifier Line (HTML Interface) ...................................................... 3-116Searching for Modifier Lists (HTML Interface).................................................................... 3-120Updating a Modifier (HTML Interface) ................................................................................ 3-123Updating a Modifier Line (HTML Interface)........................................................................ 3-125

Redeeming Accruals....................................................................................................................... 3-130Changing Modifier Incompatibility ........................................................................................... 3-131Archiving and Purging Modifiers .............................................................................................. 3-136Using the Pricing Organizer ......................................................................................................... 3-137

Creating a Query in the Find Modifiers window ................................................................ 3-138Examples of Querying by Effective Dates ............................................................................ 3-142Using the Pricing Organizer as Query Find ......................................................................... 3-157Running the Modifier Query .................................................................................................. 3-160Opening a Queried Modifier (from the Pricing Organizer) ............................................... 3-163Saving a Modifier Query ......................................................................................................... 3-164Maintaining a Modifier Query ............................................................................................... 3-165

Overview of Promotional Limits ................................................................................................. 3-167Creating Limits ......................................................................................................................... 3-169Viewing Limit Balances and Transaction Details ................................................................ 3-177Updating an Existing Limit Balance ...................................................................................... 3-181Enforcing Limits ....................................................................................................................... 3-183Adjusting the Limit Amount .................................................................................................. 3-184

4 Formulas

Overview of Formulas ....................................................................................................................... 4-2Creating a Pricing Formula ............................................................................................................... 4-3Finding Formula Factor Lines ........................................................................................................ 4-12Updating Formula Prices................................................................................................................. 4-14

5 Price Lists

Overview of Price Lists...................................................................................................................... 5-2

v

Using Price Lists in the HTML User Interface.......................................................................... 5-2Price List Terms............................................................................................................................. 5-3

Creating a Price List............................................................................................................................ 5-6Creating Price List Lines.................................................................................................................. 5-11

Defining Price Breaks for a Price List Line.............................................................................. 5-19Defining Price Breaks with Block Pricing (for application method Block Price) .............. 5-23

Finding Price List Lines ................................................................................................................... 5-28Creating a GSA Price List ................................................................................................................ 5-29Maintaining Price Lists .................................................................................................................... 5-34Adding Items to a Price List............................................................................................................ 5-36Adjusting Prices for a Price List ..................................................................................................... 5-39Copying a Price List.......................................................................................................................... 5-42Copying a Price List Line ................................................................................................................ 5-45Oracle Advanced Pricing Home page (HTML Interface) ......................................................... 5-46Using Price Lists in the HTML User Interface ............................................................................ 5-49

Creating a Price List (HTML Interface) ................................................................................... 5-50Creating Price List Lines (HTML Interface)............................................................................ 5-55Creating Price Breaks for a Price List Line (HTML Interface).............................................. 5-59Searching for Price Lists (HTML Interface) ............................................................................ 5-66Searching for Price List Lines (HTML Interface).................................................................... 5-69Updating a Price List (HTML Interface).................................................................................. 5-71Updating Price List Lines (HTML Interface) .......................................................................... 5-73

Archiving, Deleting, and Purging Price List Information ....................................................... 5-77Using the Price List Maintenance feature (HTML Interface) ................................................... 5-78

Searching for Price Lists and Price List Lines (HTML Interface)......................................... 5-80Making Detail or Bulk Changes to Price Lists (HTML Interface)........................................ 5-88Making Detail Changes across a Selected Group of Lines ................................................... 5-89Making Bulk Changes across a Selected Group of Lines...................................................... 5-94

6 Archiving and Purging Pricing Entities

Overview of Archiving and Purging Pricing Entities.................................................................. 6-2Archiving Pricing Entities .......................................................................................................... 6-3Purging Pricing Entities ............................................................................................................. 6-10

vi

7 Multi-Currency Conversion Lists

Overview of Multi-Currency Conversion Lists ............................................................................ 7-2Summary of Multi-Currency Changes to Price Lists and Agreements ................................ 7-3

Creating a Multi-Currency Conversion List .................................................................................. 7-5Considerations for Modifiers Using Multi-Currency Conversion List as a Qualifier ...... 7-11Using a formula with component type as Price List Lines................................................... 7-11Using Promotional Good type of Modifier Line.................................................................... 7-12Rounding Behavior during Currency Conversion Calculation........................................... 7-13

Attaching the Multi-Currency Conversion List to a Price List or Pricing Agreement ........ 7-17Updating the Multi-Currency Conversion List........................................................................... 7-20

8 Agreements

Overview of Creating Agreements.................................................................................................. 8-2Creating Agreements ................................................................................................................... 8-5Revising an Existing Agreement .............................................................................................. 8-14Finding Agreements................................................................................................................... 8-17Deleting Agreements ................................................................................................................. 8-18

9 Pricing Engine Request Viewer

Overview of the Pricing Engine Request Viewer ........................................................................ 9-2Viewing Information in the Pricing Engine Request Viewer................................................. 9-5

10 Reports and Concurrent Programs

Overview of Reports and Concurrent Programs ........................................................................ 10-2Accrual Details report ................................................................................................................ 10-3Attribute Mapping Rules Error report .................................................................................... 10-4Build Attribute Mapping Rules program ............................................................................... 10-5Build Formula Package program ............................................................................................. 10-7Cross Order Volume Load ........................................................................................................ 10-8Cross Order Volume Report ................................................................................................... 10-10Modifier Details report ............................................................................................................ 10-11Price Lists report ....................................................................................................................... 10-13Pricing Formulas report........................................................................................................... 10-15 Purge Pricing Engine Requests program ............................................................................. 10-16

vii

QP: Bulk Import of Price List program.................................................................................. 10-17QP: Maintains the Denormalized Data in QP Qualifiers .................................................... 10-22Qualifier Grouping report ....................................................................................................... 10-24Update Price Lists with Multi-Currency Conversion Criteria ........................................... 10-25Update Promotional Limit Balances program...................................................................... 10-28

A Formula Scenarios

Formula Scenarios............................................................................................................................... C-2

B Modifier Scenarios

Modifier Scenarios ............................................................................................................................. D-2Discount ......................................................................................................................................... D-2Surcharge ....................................................................................................................................... D-5Price Break ..................................................................................................................................... D-7Other Item Discount ..................................................................................................................... D-9Promotional Goods.................................................................................................................... D-11Coupon Issue.............................................................................................................................. D-14Item Upgrade.............................................................................................................................. D-16Terms Substitution..................................................................................................................... D-17Freight and Special Charges..................................................................................................... D-18Newprice..................................................................................................................................... D-21

C Windows and Navigator Paths

Windows and Navigator Paths ......................................................................................................... E-1

Glossary

Index

viii

Send Us Your Comments

Oracle Advanced Pricing User’s Guide, Release 11i

Part No. B13966-01

Oracle welcomes your comments and suggestions on the quality and usefulness of this document. Your input is an important part of the information used for revision.

■ Did you find any errors?■ Is the information clearly presented?■ Do you need more information? If so, where?■ Are the examples correct? Do you need more examples?■ What features did you like most?

If you find any errors or have any other suggestions for improvement, please indicate the document title and part number, and the chapter, section, and page number (if available). You can send com-ments to us in the following ways:

■ Electronic mail: [email protected] ■ FAX: (650) 506-7200 Attn: Oracle Applications Documentation Manager■ Postal service:

Oracle Corporation Oracle Applications Documentation Manager500 Oracle ParkwayRedwood Shores, CA 94065USA

If you would like a reply, please give your name, address, telephone number, and (optionally) elec-tronic mail address.

If you have problems with the software, please contact your local Oracle Support Services.

ix

x

Preface

The Oracle Advanced Pricing User’s Guide provides information on how to use Oracle Advanced Pricing.

The following sections are included in this preface:

■ Audience for this Guide

■ How To Use This Guide

■ Documentation Accessibility

■ Other Information Sources

■ Training and Support

■ Do Not Use Database Tools to Modify Oracle Applications Data

■ About Oracle

■ Feedback

xi

Audience for this GuideWelcome to Release 11i of the Oracle Advanced Pricing User’s Guide.

This guide assumes users have a working knowledge of the following:

■ principles and customary practices of the business area

■ Oracle Advanced Pricing

Oracle suggests that users who have never used Oracle Advanced Pricing attend one or more of the Oracle Applications training classes available through Oracle University.

■ Oracle Self Service Web Applications

To learn more about Oracle Self Service Web Applications, read the Oracle Self-Service Web Applications Implementation Manual.

■ Oracle Applications graphical user interface

To learn more about the Oracle Applications graphical user interface, read the Oracle Applications User’s Guide.

See Other Information Sources for more information about Oracle Applications product information.

xii

How To Use This GuideThis guide contains the information you need to understand and use Oracle Advanced Pricing.

Chapter 1 Introduces Oracle Advanced Pricing concepts and provides an overview of Oracle Advanced Pricing functionality.

Chapter 2 Introduces Oracle Advanced Pricing qualifiers, qualifier groups, and associated qualifier functionality.

Chapter 3 Introduces Oracle Advanced Pricing modifiers, Pricing Organizer, pricing limits, and associated modifier functionality.

Chapter 4 Introduces Oracle Advanced Pricing formulas and associated formula functionality.

Chapter 5 Explains Oracle Advanced Pricing price lists and associated price list usage and functionality.

Chapter 6 Explains Oracle Advanced Pricing archiving and purging pricing entities such as price list and modifier lines.

Chapter 7 Explains Oracle Advanced Pricing multi-currency conversion lists and how to use them with price lists and agreements.

Chapter 8 Introduces Oracle Advanced Pricing agreements and associated agreement functionality.

Chapter 9 Introduces Oracle Advanced Pricing Pricing Engine Request Viewer and associated functionality.

Chapter 10 Listing and definition of Oracle Advanced Pricing reports and concurrent programs.

Appendix A Provides Oracle Advanced Pricing usage scenarios for formulas.

Appendix B Provides Oracle Advanced Pricing usage scenarios for modifiers.

Appendix C Provides a listing of Oracle Advanced Pricing navigation paths.

xiii

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/

Accessibility of Code Examples in DocumentationJAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

xiv

Other Information SourcesUsers can choose from many sources of information, including documentation, training, and support services, to increase their knowledge and understanding of Oracle Advanced Pricing.

When this guide refers to other Oracle Applications documentation, use only the Release 11i versions of those guides.

Online DocumentationAll Oracle Applications documentation is available online in HTML or PDF.

■ PDF Documentation - See the Online Documentation CD for current PDF documentation for your product with each release. This Documentation CD is also available on OracleMetaLink and is updated frequently.

■ Online Help - You can refer to Oracle Applications Help for current HTML online help for your product. Oracle provides patchable online help, which you can apply to your system for updated implementation and end user documentation. No system downtime is required to apply online help.

■ Release Content Document - See the Release Content Document for descriptions of new features available by release. The Release Content Document is available on OracleMetaLink.

■ About Document - Refer to the About document for information about your release, including feature updates, installation information, and new documentation or documentation patches that you can download. The About document is available on OracleMetaLink.

Related User GuidesOracle Advanced Pricing shares business and setup information with other Oracle Applications products. Users may want to refer to other user guides when setting up and using Oracle Advanced Pricing.

Read the guides online by choosing Library from the expandable menu on the HTML help window, by reading from the Oracle Applications Document Library CD included in the media pack, or using a Web browser with a URL provided by the system administrator.

Purchase printed guides, if required, from the Oracle Store at http://oraclestore.oracle.com.

xv

Guides Related to All Products

Oracle Applications User’s GuideThis guide explains how to enter data, query, run reports, and navigate using the graphical user interface (GUI). This guide also includes information on setting user profiles, as well as running and reviewing reports and concurrent processes.

Access this user’s guide online by choosing Getting Started with Oracle Applications from any Oracle Applications help file.

Oracle Applications Developer’s GuideThis guide contains the coding standards followed by the Oracle Applications development staff. It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards. It also provides information to help you build your custom Oracle Developer forms so that they integrate with Oracle Applications.

Oracle Applications User Interface StandardsThis guide contains the user interface (UI) standards followed by the Oracle Applications development staff. It describes the UI for the Oracle Applications products and how to apply this UI to the design of an application built by using Oracle Forms.

Installation and System Administration

Oracle Advanced Pricing Implementation ManualThis manual contains the information you need to set up and implement Oracle Advanced Pricing.

Oracle Applications ConceptsThis guide provides an introduction to the concepts, features, technology stack, architecture, and terminology for Oracle Applications, Release 11i. It is a useful first book to read before an installation of Oracle Applications. This guide also introduces the concepts behind Applications-wide features such as Business Intelligence (BIS), languages and character sets, and Self Service Web Applications.

xvi

Installing Oracle ApplicationsThis guide provides instructions for managing the installation of Oracle Applications products. In Release 11i, much of the installation process is handled using Oracle Rapid Install, which minimizes the time to install Oracle Applications and the Oracle technology stack, by automating many of the required steps. This guide contains instructions for using Oracle Rapid Install and lists the tasks you need to perform to finish your installation. You should use this guide in conjunction with individual product user’s guides and implementation guides.

Upgrading Oracle ApplicationsRefer to this guide when upgrading Oracle Applications Release 10.7 or Release 11.0 products to Release 11i. This guide describes the upgrade process and lists database and product-specific upgrade tasks. To upgrade to Release 11i, users must be at Release 10.7, in NCA, SmartClient, or character mode, or Release 11.0. Users cannot upgrade to Release 11i directly from releases prior to 10.7.

"About" DocumentFor information about implementation and user documentation, instructions for applying patches, new and changed setup steps, and descriptions of software updates, refer to the "About" document for your product. "About" documents are available on OracleMetaLink for most products starting with Release 11.5.8.

Maintaining Oracle ApplicationsUse this guide to run various AD utilities, such as AutoUpgrade, AutoPatch, AD Administration, AD Controller, AD Relink, License Manager, and others. The guide contains how-to steps, screenshots, and other information needed to run the AD utilities. This guide also provides information on maintaining the Oracle Applications file system and database.

Oracle Applications System Administrator’s GuideThe guide provides planning and reference information for the Oracle Applications system administrator. The guide contains information on how to define security, customize menus and online help, and manage concurrent processing.

Oracle Alert User’s GuideThis guide explains how to define periodic and event alerts to monitor the status of Oracle Applications data.

xvii

Oracle Applications Developer’s GuideThis guide contains the coding standards followed by the Oracle Applications development staff. It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface (UI) described in the Oracle Applications User Interface Standards for Forms-Based Products. It also provides information to help users build custom Oracle Forms Developer forms so that they integrate with Oracle Applications.

Oracle Applications User Interface Standards for Forms-Based ProductsThis guide contains the UI standards followed by the Oracle Applications development staff. It describes the UI for Oracle Applications products and how to apply this UI to the design of an application built by using Oracle Forms.

Other Implementation Documentation

Oracle Applications Product Update NotesUse this guide as a reference for upgrading an installation of Oracle Applications. It provides a history of the changes to individual Oracle Applications products between Release 11.0 and Release 11i. It includes new features, enhancements, and changes made to database objects, profile options, and seed data for this interval.

Oracle Workflow Administrator’s GuideThis guide explains how to complete the setup steps necessary for any Oracle Applications product that includes workflow-enabled processes, as well as how to monitor the progress of runtime workflow processes.

Oracle Workflow Developer’s GuideThis guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions.

Oracle Workflow User’s GuideThis guide explains how Oracle Applications users can view and respond to workflow notifications and monitor the progress of their workflow processes.

xviii

Oracle Workflow API ReferenceThis guide describes the APIs provided for developers and administrators to access Oracle Workflow.

Oracle Applications Flexfields GuideThis guide provides flexfields planning, setup, and reference information for the Oracle Advanced Pricing implementation team, as well as for users responsible for the ongoing maintenance of Oracle Applications product data. This manual also provides information on creating custom reports on flexfields data.

Oracle eTechnical Reference ManualsEach eTechnical Reference Manual (eTRM) contains database diagrams and a detailed description of database tables, forms, reports, and programs for a specific Oracle Applications product. This information helps users convert data from existing applications, integrate Oracle Applications data with non-Oracle applications, and write custom reports for Oracle Applications products. Oracle eTRM is available on OracleMetaLink.

Oracle Applications Message ManualThis manual describes all Oracle Applications messages. The guide is available in HTML format on the documentation CD-ROM for Release 11i.

xix

Training and Support

TrainingOracle offers a complete set of training courses to help users and their staff master Oracle Advanced Pricing and reach full productivity quickly. These courses are organized into functional learning paths, so users take only those courses appropriate to their jobs or areas of responsibility.

Users have a choice of educational environments. They can attend courses offered by Oracle University at any one of our many Education Centers, or can arrange for our trainers to teach at their facility, or can use Oracle Learning Network (OLN), Oracle University’s online education utility. In addition, Oracle training professionals can tailor standard courses or develop custom courses to meet your needs. For example, you may want to use your organization structure, terminology, and data as examples in a customized training session delivered at your own facility.

SupportFrom on-site support to central support, our team of experienced professionals provides the help and information needed to keep Oracle Advanced Pricing working for all users. This team includes the technical representative, account manager, and Oracle’s large staff of consultants and support specialists with expertise in your business area, managing an Oracle server, and your hardware and software environment.

xx

Do Not Use Database Tools to Modify Oracle Applications DataOracle STRONGLY RECOMMENDs that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle Applications data unless otherwise instructed.

Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.

Because Oracle Applications tables are interrelated, any change you make using Oracle Applications can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications.

When you use Oracle Applications to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.

xxi

About OracleOracle develops and markets an integrated line of software products for database management, applications development, decision support, and office automation, as well as Oracle Applications, an integrated suite of more than 160 software modules for financial management, supply chain management, manufacturing, project systems, human resources, and customer relationship management.

Oracle products are available for mainframes, minicomputers, personal computers, network computers, and personal digital assistants, allowing organizations to integrate different computers, different operating systems, different networks, and even different database management systems, into a single, unified computing and information resource.

Oracle is the world’s leading supplier of software for information management, and the world’s second largest software company. Oracle offers its database, tools, and application products, along with related consulting, education, and support services, in over 145 countries around the world.

xxii

FeedbackThank you for using Oracle Advanced Pricing and this user’s guide.

Oracle values your comments and feedback. This guide includes a Reader’s Comment Form that you can use to explain what you like or dislike about Oracle Advanced Pricing or this user’s guide. Mail your comments to the following address or call us directly at (650) 506-7000.

Oracle Applications Documentation Manager

Oracle Corporation

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A

Or, send electronic mail to [email protected].

xxiii

xxiv

Oracle Advanced P

1
Oracle Advanced Pricing
This chapter explains Oracle Advanced Pricing and includes the following topic:

■ Overview of Oracle Advanced Pricing on page 1-2.

■ Pricing Security on page 1-4.

■ Using Oracle Advanced Pricing in the HTML Interface on page 1-6.

■ General Pricing Concepts on page 1-11.

■ Pricing Engine on page 1-13.

■ Pricing Components on page 1-15.

■ Pricing Service Items on page 1-17.

■ Implementation Planning on page 1-19.

ricing 1-1

Overview of Oracle Advanced Pricing

Overview of Oracle Advanced PricingOracle Advanced Pricing supports e-business applications by providing a flexible pricing engine that executes pricing and promotional calculations for Oracle Order Management and other Oracle Applications. This application is licensed as Oracle Advanced Pricing.

Oracle Advanced Pricing provides the flexibility to meet the needs of complex pricing situations for a range of demanding industry business requirements which include:

■ Consumer goods, telecommunications, services, high technology, automotive, and aerospace/defense businesses which sell to other businesses.

■ Telemarketing, mail order catalog, and web store businesses which sell directly to consumers.

Oracle Advanced Pricing provides advanced pricing capabilities that enable you to set up your pricing information and to model complex data relationships to determine the correct price.

With Oracle Advanced Pricing, you can perform the following functions:

■ Create a list price for an item or item hierarchy.

■ Set a list price based on volume breaks.

■ Assign security privileges to pricing users to control their view or maintain access to price lists and modifiers. Control which operating units can use price lists or modifiers.

■ Define price breaks using block pricing to evaluate prices as a single block. For example, if item weight is between 5-15 pounds, then the price is $5. If the weight is between 16-30 pounds, the price is $10.

■ Do Price List Maintenance tasks such as searching across a single or multiple price lists and updating the price, formula, or effective dates of price list lines.

■ Usage Pricing/counter price: calculate price based on usage brackets.

■ Point break (all quantity in one bracket).

Note: For more information on implementation steps, setup procedures, and profile options, see: Oracle Advanced Pricing Implementation Manual.

1-2 Oracle Advanced Pricing User’s Guide


■ Use price breaks (quantity in each break gets the price of that break).

■ Set a list price/ discounts at multiple levels of flattened hierarchies and use precedence to select the right price/discount.

■ Define a formula to dynamically calculate the price based on simple or a complex formula or to create a price relation (price of item A is Price of Item B + $20).

■ Create multiple currency conversion criteria for a single base currency price list.

■ Set up GSA prices.

■ Define pricing agreements.

■ Get a price/discount from an external source (my price = competitors price - 5%).

■ Set a percent/fixed/lump sum discount or surcharge.

■ N-Dimensional Pricing (if width between 2-4 and thickness between 1-3 then multiple the price by 0.3).

■ Benefit/surcharge based on total volume of multiple order lines of the same order.

■ Set up deals and promotions.

■ Buy one get one free.

■ Coupon issue (Buy over $1000 and get a coupon of $100 for future purchase).

■ Other item discount (Buy A and B get 20% off on C).

■ Item Upgrade (For the price of 12 Oz. Shampoo get 16 Oz. Shampoo).

■ Terms upgrade (Buy over $100 and get upgraded to air shipment).

■ Set discounts as “to be accrued.”

■ Set up freight and special charges.

■ Mark discounts as exclusive or incompatible to each other.

■ Create Cascading discounts (discounts to be applied on subtotals).

■ Set spending and usage constraints to stop application of promotion when limit is reached.

■ Query on multiple modifier criteria across all modifier setups.

■ Create your own eligibility conditions by grouping the qualifiers.

Oracle Advanced Pricing 1-3


■ Define your own qualifier and qualifier sourcing rules (if today = Sunday then give 10%).

■ View the criteria that the engine uses to select price and modifiers for a pricing request.

Oracle Advanced Pricing and its pricing engine work through open, business object oriented APIs. The following Oracle Application Suites use the pricing engine:

■ Oracle Order Management

■ Oracle Customer Relationship Management

■ Oracle Procurement

Pricing SecurityIn Oracle Applications, a basic level of security called functional security is used to manage users’ access to each application and control their access to windows, functions, and reports within an application.

Typically, the System Administrator administers functional security and assigns operating unit, responsibility, and system access to users. See the Oracle Applications System Administrator’s Guide for more information about functional security.

Oracle Advanced Pricing provides an additional level of security called pricing security in addition to the existing functional security. Pricing security enables you to restrict pricing activities such as updating and viewing pricing entities to users granted specific access privileges.

Pricing security can be set up and maintained by a user who is assigned the Oracle Pricing Administrator responsibility. Pricing security is set up and maintained in the HTML user interface. The Oracle Pricing Administrator has the authorization to access and update all pricing entities for all functional users. Pricing entities include price lists, pricing agreements, and modifiers. See the Oracle Advanced Pricing Implementation Manual, Pricing Security section, for more information on pricing security.

Pricing Security (HTML Interface)Pricing security settings also impact the Update/Details icons for price lists and modifiers in the HTML user interface in the following ways:



When Pricing Security is ON■ If the modifier or price list has Maintain and View privileges and belongs to the

same PTE/Source System as the user’s profile, the Update icon will be enabled and the Details icon will be disabled.

■ If the modifier or price list has Maintain and View privileges and belongs to a different PTE/Source System, as the user’s profile, the Update icon will be disabled and Details icon will be enabled.

■ If the modifier or price list has View-privilege only, the Update icon will be disabled and Details icon will be enabled, regardless of the PTE/Source System the modifier or price list belongs to.

When Pricing Security is OFF■ If the modifier or price list belongs to the same PTE/Source System as the user’s

profile, the Update icon will be enabled and Details icon will be disabled.

■ If the modifier or price list belongs to a different PTE/Source System as the user’s profile, the Update icon will be disabled and Details icon will be enabled.



Using Oracle Advanced Pricing in the HTML InterfaceFor many pricing features, Oracle Advanced Pricing provides an HTML-based user interface (UI) that features guided steps and user-friendly pages for setting up and maintaining modifiers, price lists, and qualifiers.

Accessing the HTML User Interface To access the HTML user interface, select the Oracle Pricing User responsibility and click the Home link to display the Oracle Advanced Pricing Home page.

You can use HTML user interface to complete many of the pricing tasks that were previously only available in the Oracle Forms-based interface.

The following graphics compare the HTML UI and Forms-based UI used in Oracle Advanced Pricing. The first example shows an Oracle Advanced Pricing HTML page used to create a price list.

Note: The HTML user interface is available only in Oracle Advanced Pricing.



Figure 1–1 Example of Oracle Advanced Pricing HTML format: Create Price List page

The second example shows an Oracle Advanced Pricing Forms-based window used to create a price list.



Figure 1–2 Example of Oracle Advanced Pricing Forms-based format: Advanced Pricing - Price Lists window

You can use the HTML UI for completing the following common pricing tasks:

■ Create price lists, price list lines and price break lines for price lists.

■ Create the following modifier list types:

■ Deal List

■ Discount List

■ Promotional Goods

■ Surcharge List

■ Create the following modifier line types:

■ Discount

■ Surcharge

■ Price Break




■ Maintain price lists in the Price List Maintenance feature.

■ Create qualifiers for price lists and modifiers.

■ Search for price lists or modifiers.

Cross-Format Compatibility For features unavailable in HTML, you can still use the Forms-based user interface to set up and maintain pricing functions and features as in previous releases. If an entity cannot be created in HTML, for example, qualifier groups, then you must use the Forms-based UI for these tasks.

Navigation flow behavior in HTML user interfaceThe following section describes selected HTML user interface behavior when navigating through certain flows in the Price List, Modifier List General Info, and Qualifiers pages.

Behavior 1The following table summarizes expected outcomes when you make changes in the Price List, Modifier List General Information, and Qualifiers pages:

Note: Pricing entities such as price lists, modifiers, or qualifiers created in one format can be maintained in the other. For example, if you created a price list in the Forms-based UI, you could update and maintain the price list in the HTML UI.

Table 1–1 Navigation flow behavior

Page Name Action Outcome

Price List, Modifier List General Information, Qualifiers

Make changes, click Apply.

Information is saved > Price/Modifier Lists rollup page displays.

Price List, Modifier List General Information, Qualifiers

Make changes, click Cancel.

Changes are not be saved and the Price List/Modifier Lists rollup page displays.

General Information or Qualifiers

Click Cancel after a line has been created and saved.

The line changes are already saved.



Behavior 2After creating a price list or modifier list, you can make changes to the list by updating fields on the General Information or Qualifiers page:

■ If you change information in the General Information or Qualifiers page, then navigate to the Lines page and either create or update a line, a dialog box displays and asks if you want to continue to save the changes on the General Information and Qualifiers page:

a. If you click Yes to Continue, then the changes from the General Information and Qualifier pages are saved and you continue with the flow. Any deleted lines will also be saved.

b. If you click No, you return to the Lines page. The changes are kept but not saved. If lines have been deleted, you must click Apply to save the changes.

■ If you create or update a line without going making any changes to the General Information and Qualifiers page, then the dialog box does not display and you can proceed directly into the create or update flow.

■ If you cancel a create/update line flow, then you must click Apply on the General Information, Lines, or Qualifiers pages to save the changes to the list.

Behavior 3: DeletingFor price list lines, the delete is not saved until you click Apply in the Lines page. No warning or confirmation message is displayed.

Qualifiers or qualifier conditions are not permanently deleted until you click the Apply button. A warning or confirmation message does not display.

See:Oracle Advanced Pricing Home page (HTML Interface) on page 5-46

Using Modifiers in the HTML User Interface on page 3-81

Using Price Lists in the HTML User Interface on page 5-2

Creating Qualifiers (HTML Interface) on page 2-6

Using the Price List Maintenance feature (HTML Interface) on page 5-78



General Pricing ConceptsThe pricing engine receives transaction information, prepares pricing requests, selects price lists and modifier lists, and applies price adjustments (benefits) to the transaction.

The pricing engine, displayed in the following graphic, evaluates the following questions to determine a price:

■ Who qualifies for prices and benefits?

■ What is the product hierarchy and what pricing attributes pertain to this item or service?

■ How should I adjust the order price or order line price?

The following diagram shows the elements of the pricing concept:

■ A sales order

■ The qualifier hierarchy

■ The pricing request

■ The pricing engine

■ The list price and adjustments

■ The setup entities: Price lists, qualifiers, modifiers, products, formulas, and pricing attributes

After the diagram, the text explains these elements.



Figure 1–3 Pricing Overview



Who Qualifies?Pricing qualifiers control who is eligible for certain prices (price lists) and benefits (modifiers).

Some example qualifiers are:

■ Customer Class = VIP

■ Order Type = Special

What is the Product Hierarchy and Pricing Attributes?The product hierarchy and pricing attributes control what is being priced or modified on a price list or modifier list.

An example of a product hierarchy with pricing attributes is All Plastic items of Grade B quality get 50% discount.

How Should I Adjust the Price?Pricing modifiers control how a modifiers affect the final price (selling price).

Some example modifiers are:

■ Discount of 2%

■ Buy 1 get 1 free

■ Get 480 ml shampoo for the same price as 360 ml shampoo

■ Get a coupon for 100 currency units if you buy over 1000 currency units

Pricing EngineThe advanced, flexible pricing engine performs pricing and benefit calculations for Oracle Order Management products and Oracle Customer Relationship Management products through open APIs.

The pricing engine performs the following functions:

■ Prepares the price request structure

■ Selects applicable price lists and modifier lists

■ Determines base list price

■ Calculates final selling price

■ Applies benefits and surcharges (from modifier lists) to list price to determine selling price



Preparing the Price Request StructureThe calling applications submit price requests. This function configures a pricing request into a pricing request structure. The pricing request structure provides information about all the qualifiers and product pricing attributes.

Selecting the Price List or Modifier ListThis function selects which price lists are eligible for the current pricing request. It uses the qualifiers and pricing attributes to select an eligible list of prices or modifiers it can apply to the pricing request lines according to the certain rules.

Determining List PriceThis function takes the validated price list lines and applies them to the pricing request lines. You can specify the list price on a price list as unit price, percent price, or formula.

Applying Price and Modifier AdjustmentsThis function takes the validated modifier list lines and applies them to the pricing request lines.

The modifier function provides price adjustments such as discounts, price breaks, surcharges, coupons, item and term substitutions, and other item discounts. Discount and surcharges modifiers affect the selling price; freight charge modifiers do not affect the selling price.



Pricing Components

Qualifiers and Qualifier GroupsQualifiers control who receives benefits, and can be used to assign discounts and promotions to:

■ Specific customers

■ Customer groups

■ Order types

■ Order amount

■ Specific customer or group of customers

Qualifier groups allow you to group multiple conditions and to assign them to a single benefit. For more information, see: Oracle Advanced Pricing User’s Guide, Qualifiers.

Pricing AttributesPricing attributes control what is being priced or modified on a price list or modifier list. See the Oracle Advanced Pricing Implementation Manual for information about creating new contexts and attributes, attribute management, mapping rules, and associated functionality.

Price ListsPrice lists contain prices and currencies associated with products and services. Each price list contains basic header information with one or more item lines. Price lists can have:

■ Prices for specific products and services or for product groups

■ Prices as absolute values, percents of other prices, or as formulas

■ Prices applicable to the entire organization or to one operating unit

■ Negative prices

For more information, see: Oracle Advanced Pricing User’s Guide, Price Lists.

Modifier ListsPricing modifiers control how the pricing engine can modify the pricing requests and pricing request lines. You can select from the following modifier list types and



then add modifier lines to define the actual adjustments or benefit such as a 10% discount:

■ Deal

■ Discount List

■ Freight and Special charge List

■ Promotion

■ Surcharge List

The following table shows scenarios with examples of the qualifiers, modifiers, and pricing attributes that support them:

See Oracle Advanced Pricing User’s Guide, Overview of Modifiers on page 3-3 for more information on modifier list and line types and using modifiers.

FormulasPricing formulas allow the pricing engine to determine item prices based on the following:

■ A combination of pricing attributes and factors based on the value of a pricing attribute

■ The list price on the price list line to which the formula is attached

■ The list price on any specific price list line

■ A numeric constant

Table 1–2 Scenarios where Qualifiers, Modifiers, and Pricing Attributes are Used

Scenario Qualifier ModifierProduct Hierarchy

Pricing attribute

XYZ Corporation gets 10% discount on all the products

Customer = XYZ Corporation

10% discount Null Null

If Order_Type = Return and customer class = Retail then apply 15% surcharge for all the “Electronic” items.

Order Type = Return

Customer Class = Retail

15% Surcharge Electronic Items

Null

Grade B Motor Oil gets $20 off

Null $20.00 discount Motor Oil Grade B



■ A customizable function

You can also attach a formula to a modifier line to calculate discounts. A price list line uses two types of formulas:

■ Static: You specify the formula and execute a concurrent process which calculates absolute price values.

■ Dynamic: You specify the formula and the pricing engine uses the formula in its calculations each time that someone orders the product.

For more information, see: Oracle Advanced Pricing User’s Guide, Formulas.

Pricing Service ItemsThe pricing engine prices service items in the same way that it prices inventory items. In Oracle Order Management, the parent item is the serviceable item and must be in the install base. Oracle Order Management passes both the serviceable item and the service item to the pricing engine; the pricing engine first prices the serviceable item and then prices the service item.

You can price service items as follows:

■ Unit price: You set a list price for the service item.

■ Percent price: You set a percentage; the price of the service item is that percentage of the serviceable item list price. To use this method, select the flag Service Item in the Service tab when you define the item.

When pricing service items, attend to the following order management attributes when pricing service items. They are passed through the pricing engine application program interface (API):

■ Ordered Quantity (API: P_Line_Tbl.Line_Quantity): The order quantity of the service item expressed in the in the serviceable item unit of measure.

■ Ordered UOM Code (API: P_Line_Tbl.Line_Uom_Code): The unit of measure in the time scale.

■ Service Duration and Service Period (API: P_line_Tbl.UOM_Quantity): The duration of the service being ordered, for example, to order Computer Maintenance for one year, set Service Duration to 1 and Service Period to Year. You set these values in the Service tab when you enter the item in the order. In the API, P_line_Tbl.UOM_Quantity is the service duration expressed in Ordered UOM Code service period.



Oracle Order Management Service Item: Pricing ExamplePrice list setup for laptop computer:

■ Product: Laptop Computer

■ Application Method: Unit Price

■ UOM Code: EA

■ List Price: 1000 currency units

Price list setup for computer service-unit price method■ Product: Computer Service

■ Application Method: Unit Price

■ UOM Code: Month

■ List Price: 10 currency units

Price list setup for computer service-percent price method■ Product: Computer Service

■ Application Method: Percent Price

■ UOM Code: Month

■ Percent Price: 2

Order line

■ Product: Computer Service

■ Ordered Quantity: 1

■ Ordered UOM: Month

■ Service Period: Year

■ Service Duration: 1

■ Serviceable Item: Laptop Computer

List price calculation for computer service■ Unit price method: 10 currency units per month * 12 months service

period/duration = 120 currency units



■ Percent price method: (1000 currency unit laptop computer * 2% computer service percent price) * 12 months service period/duration = 240 currency units

Implementation PlanningVisualizing the price bands of an organization may assist you in developing an effective implementation plan for Oracle Advanced Pricing.

The following table provides a visual guide for mapping the modifiers of an organization to the components of Oracle Advanced Pricing.

The source pricing data is based upon the assumptions that item Super Wine has an item category of Wine. An order for a quantity 15 was placed on 15-Jun-2000 for a customer XYZ Corporation, who belongs to a customer class VIP.

Note: See the Oracle Advanced Pricing Implementation Manual for information on implementation steps, setup procedures, and profile options.

Table 1–3 Implementation Planning:

BucketsPricing Phases

Incompatibility Group

Qualifiers/ Product Attributes (Precedence)

Modifiers/ Price List Discount

Sub Total

Base Price

List Line Base Price

EXCLUSIVE Customer Class - VIP (310)

Item Code - Super Wine (220)

Corporate List - $1000

Null Null

Base Price


EXCLUSIVE Item Category - Wine (290)

Preferred Vendors - $800

Null Null

Base Price


Null Null Null Null $1,000



Bucket 1 List Line Adjust-ments

Level 1 Item Quantity > 10 (800)

Item Code - Super Wine (220

4th July Promotion 10%

$100 Null


Level 1 Customer Class - VIP (310)

Summer Promotion 15%

Null Null


Level 2 Customer id - XYZ Corp (260)

VIP discount $40

$40 Null


Level 2 Customer id - XYZ Corp (260)

Weekday Discount $20

Null Null

Bucket 1 All Line Adjustments

Level 1 Item Category - Wine (290)

General Discount - $20

$10 Null

Bucket 1 All Line Adjust-ments

Exclusive Order Date < 01-Dec-2000 (510)

Seasonal Discount - $10

Null Null

Bucket 1 Header Level Adjustments

Level 1 Null Preferred Customer 10%

100 Null

Bucket 1 Line Charges

Level 1 Null Handling Charge $20

$20 Null

Bucket 1 Header Level Charges

Level 1 Null Null Null Null


Null Null Null Null $750






Sub Total



The following factors should be considered when planning your implementation. For more information on setting up, see: Oracle Advanced Pricing Implementation Manual.

List priceDecide whether your prices are at an individual product level or at the product hierarchy or both. Also, determine the precedence levels in your organization. Determine if you base list prices on the volume purchased. Plan the number of price lists. To get a better performance, minimize the number of price lists and price list lines by using a combination of qualifiers, modifiers, pricing attributes, and formulas.

Based upon the source pricing data, the product attribute Item Code of Super Wine for Corporate price list has a product precedence of 220, where as product attribute Item Category of Wine for Preferred vendors price list has a product precedence of

Bucket 2 Adjustments

Level 2 Null High usage surcharge 2%

($15) Null

Bucket 2 All Line Adjustments


Bucket 2 Header Level Adjustments


Bucket 2 Line Charges






Bucket 2 Null Null Null Null Null $765






Sub Total



290. Pricing picks up a list of lower precedence and hence $1000 from Corporate List is returned. This is because the pricing phase “List line base price” has “Precedence” for resolving the incompatibility.

Modifier typesCategorize your discounts and promotions into the appropriate modifier types; each modifier type produces different results. For example, the Other Item Discount requires the customer to order the original item as a prerequisite to offering the discount; however, the Promotional Goods discount adds a new line to the order.

BucketsThe pricing engine may calculate different selling prices depending on how you group your discounts into buckets. Plan your cascading discounts so that you can assign discounts to buckets based on the subtotal on which each discount needs to be applied.

PhasesDecide to which event and phase each discount and promotion belongs. Oracle recommends that you place:

■ Line level discounts in the Line Adjustments phase

■ A promotion such as "buy items A and B and get a discount on Item C" in the All Lines phase

■ Modifiers to apply when orders ship in a ship event

Phases are also associated with order events. To apply a discount only when an order is shipped, assign the modifier to a phase which is executed in SHIP event.

Incompatibility groups and exclusivityDetermine the pricing bands to which the various discounts and promotions belong. Determine which discounts and promotions apply on top of one another, are incompatible, or are exclusive. Analyze all discount schemes and promotions to determine the impact.

Based upon the source pricing data, the bucket Bucket 1 and pricing phase List Line Adjustments has two Incompatibility groups called Level 1 and Level 2. Level 1 has two promotions: 4th July Promotion and Summer Promotion. The 4th July Promotion has a product precedence of 220 and Summer promotion has a qualifier precedence of



310. The 4th July promotion is picked from incompatibility group Level 1 because it has the lower precedence.

Incompatibility Group Level 2 has two discounts: VIP discount and Weekday Discount, both with a qualifier precedence of 260. Pricing resolves the incompatibility by picking the best discount.

The bucket Bucket 1 and pricing phase All Line Adjustments has two incompatibility groups: Level 1 and Exclusive. Although General Discount in Level 1 has a lower product precedence, Seasonal discount for $10 which is in the Exclusive bucket is picked up by the engine.

Modifier levelsCategorize the modifiers into line, group line, and order modifiers. How the pricing engine treats a modifier can change depending on your classification.

Automatic, Override, Asked for, and Accrual flagsIt is very important that you understand how the pricing engine operates with these flags so that you can set them to reflect your business needs. Analyze all of your discounts, promotions, and charges in terms of these features.

Other setupsPrecedence preferences, profile options, break types, and pricing attribute control the pricing engine behavior. Determine the values for these settings that reflect your business needs.

Precedence setupsEvaluate default precedence values for qualifiers and product hierarchy and change them to reflect your business needs.

For a list of seeded precedence values, see: Oracle Advanced Pricing User’s Guide, Pricing Attribute Seed Data.

Unit of MeasureDecide the pricing units of measure for each item because it determines if the pricing engine selects a modifier.

Note: The pricing engine determines incompatibility and exclusivity within phases.



The list price in the order unit of measure overrides the precedence. When it processes a pricing request, the pricing engine first chooses eligible price list lines whose unit of measure matches the calling unit of measure. If there are multiple price list lines with matching unit of measure, the pricing engine chooses the price list line with the better precedence. If there are no price list lines with matching unit of measure, the pricing engine looks for price list lines with selected primary unit of measure flag for that item, then chooses the best precedence price list line.

Determine whether you need to set up new qualifier attributes and mapping rules. While Oracle Advanced Pricing has certain qualifier attributes and mapping rules seeded, you may need to define discounts, promotions, and charges based on other qualifier attributes.

See the Oracle Advanced Pricing Implementation Manual for information about attribute management, mapping rules, and associated functionality.


Qualifiers and Qualifier G

2
Qualifiers and Qualifier Groups
This chapter describes how to use qualifiers with modifiers and price lists, and how to create, query, delete, and modify qualifier groups.

This chapter includes the following topics:

■ Overview of Oracle Advanced Pricing Qualifiers on page 2-2.

■ Creating Qualifiers for Price Lists on page 2-5.

■ Creating Qualifiers for Modifiers on page 2-5.

■ Creating Qualifiers (HTML Interface) on page 2-6.

■ Updating a Qualifier (HTML Interface) on page 2-12.

■ Appending a Qualifier Group (HTML Interface) on page 2-15.

■ Deleting a Qualifier (HTML Interface) on page 2-14.


■ Creating a Qualifier Group on page 2-17.

■ Querying a Qualifier Group on page 2-28.

■ Modifying or Deleting Qualifier Groups on page 2-29.

■ Deleting a Qualifier (HTML Interface) on page 2-14.


roups 2-1

Overview of Oracle Advanced Pricing Qualifiers

Overview of Oracle Advanced Pricing QualifiersOracle Advanced Pricing lets you define qualifiers to determine eligibility rules governing who can receive a particular price, discount, promotion, or benefit. Qualifiers and qualifier groups can then be linked to Oracle price lists and modifiers.

Oracle provides predefined (seeded) qualifier contexts and attributes. Qualifier values for these predefined attributes are sourced from the Oracle Application database whenever applicable. The following table illustrates several predefined structures that can be used in determining benefit eligibility.

See the Oracle Advanced Pricing Implementation Manual for more information on seeded attributes.

You can set up qualifier context/attributes to suit your own business needs to determine eligibility for benefits or price.

Qualifier TermsThe following lists common qualifier terms:

Qualifier ContextsQualifier contexts are flattened hierarchies where similar qualifying attributes can be grouped into logical categories. The specificity is indicated by precedence.

QualifiersQualifiers consist of specific attribute conditions that assist the pricing engine to derive the eligibility for a benefit or price.

Table 2–1 Predefined Qualifier hierarchy structures

Qualifier Context Qualifier Attributes

Customer Customer Name, Bill To, Sales Channel

Order Order Type, Shipment Date, Line Type

Terms Payment Term, Freight Terms, Shipping Method

Volume Order Amount, Line Volume.

Note: Order Amount as a qualifier refers to the sum of the list prices on all active order lines. It is not the same as Order Total in Oracle Order Management which can include the effect of modifiers.



Qualifier ValueA qualifier value is a value you choose to associate with a qualifier attribute.

Qualifier Grouping NumbersA qualifier consists of qualifier lines that define eligibility for a particular price, discount, promotion, or benefit. Qualifier grouping numbers are assigned to qualifier lines to create AND and OR conditions that define how the pricing engine should evaluate the qualifier lines. See Using Qualifier Grouping Numbers on page 2-21 for more information.

Using QualifiersQualifiers and qualifier groups can be associated with Oracle price lists and modifiers at the following levels:

■ Price list: Price List

■ Modifier: Modifier list and modifier line

Various methods can be used to associate qualifiers with price lists or modifiers:

■ Create qualifier(s), and then attach individual qualifiers within the Price List or Modifiers window.

■ Create qualifier groups using the Qualifier Groups window and then attach the qualifier group to the price list, modifier list, or modifier list line.

■ Any combination of method 1 and 2.

Once an entity has qualified for a particular benefit, Oracle Advanced Pricing attributes can further refine which benefits can be given.

You can create, modify, query, and delete qualifier groups.

You can set up hierarchies using qualifier contexts and attributes. Flattened format is required as qualifiers do not store any relationships among the hierarchies. The following table illustrates a hierarchy with 3 different levels of qualifier attributes. This hierarchy can be stored by creating a context such as Geography. Under this context, you would define 3 attributes, such as State, Territory, and Customers.

Note: In the HTML user interface, Common and Unique qualifiers are used to create grouping conditions instead of grouping numbers. See Creating Qualifiers (HTML Interface) on page 2-6 for more information.

Qualifiers and Qualifier Groups 2-3


To enable the user to select and enter correct values for the three attributes, you would have to define specific validation sets for each attribute, using value set definitions to provide the correct source.

For more information on Value Sets, see Oracle Applications Flexfields User’s Guide, Planning and Defining Values and Value Sets.

Since hierarchical relationships are not stored, you need to define the sourcing information. This is required because when the pricing engine has to make a determination as to whether a particular customer can receive a particular benefit, the engine needs to know the information at all the levels of hierarchy.

In this hierarchy, if the qualifying conditions established were that Territory must be West and State must be California, then the pricing engine would need to know both the Territory and the State of the customer in order to determine eligibility. If the qualifying conditions established were that Territory must be West or State must be California, then the pricing engine would need to know only the Territory or the State of the customer in order to determine eligibility.

Qualifier Group Impact when Merging Customers (Oracle Receivables)When you merge customers in Oracle Receivables, you can merge:

■ The information from one customer (the From customer) with the information from another customer (the To customer).

■ The information from one or more customer sites of that customer (the From sites) with the site information from the other customer (the To sites).

If the From customer is referenced in any qualifiers (the qualifier context is Customer), the Oracle Receivables merge process executes an Oracle Advanced Pricing process to update the following qualifier information:

■ If you merge customer: The process changes the customer name on the qualifier from the From customer to the To customer.

Table 2–2 Example qualifier “Geography” Context

Qualifier attribute Qualifier attribute value

State CA, MN,WA,NY,FL

Territory East, West, South, North

Customers all customers, subset of customers by purchase volume



■ If you merge sites: The process changes the site from the From customer to the To customer for qualifiers with the following attributes:

■ Bill To

■ Site Use

■ Ship To

Verify these changes in the Value From and Value To fields of the following windows:

■ Qualifier Group form, Qualifiers tab

■ Advanced Pricing - Price Lists window, Qualifiers tab

■ Qualifiers - Header Level Qualifiers window (from Advanced Pricing - Define Modifier window), Qualifiers tab

■ Qualifiers - Line Level Qualifiers form (from Advanced Pricing - Define Modifier window), Qualifiers region

Creating Qualifiers for Price ListsSee Oracle Advanced Pricing User’s Guide, Price Lists, for more information on creating qualifiers or attaching a qualifier group to price lists (for Forms-based user interface).

Creating Qualifiers for ModifiersSee Oracle Advanced Pricing User’s Guide, Modifiers, for more information on creating qualifiers or attaching a qualifier group to modifiers and modifier lines (for Forms-based user interface).


Creating Qualifiers (HTML Interface)

Creating Qualifiers (HTML Interface)A qualifier consists of one or more conditions that define eligibility for a particular price, discount, promotion, or benefit. You can assign qualifiers and qualifier groups to modifiers lists, modifier lines, and price lists. You can create different qualifying conditions depending on how you set up your qualifiers. The different qualifying rules are outlined as follows:

Qualifier ConditionsA qualifier condition defines an eligibility rule, for example, the customer name must be Vision Operations. You can set up one or more conditions for a single qualifier. Multiple conditions within the same qualifier are joined to each other by AND:

Condition1: Customer Name must be Vision Corporation AND

Condition 2: Order Type must be Standard AND

Condition 3: Credit Type must be Good

If ALL the qualifier conditions are met, then the qualifier evaluates as true, and the modifier or price list can be applied.

Unique QualifiersEach separate qualifier created for a modifier or price list is called a unique qualifier. Unique qualifiers are evaluated by an "OR" condition; for example, either Qualifier 1 OR Qualifier 2 can qualify before the price list or modifier is applied.

Each unique qualifier may consist of one or more conditions. The conditions for each unique qualifier are still joined by AND and must evaluate as true before the modifier or price list is applied:

■ Qualifier 1

a. Customer = Vision Operations

b. Customer Class = Gold Standard

OR

■ Qualifier 2

a. Customer Region = Western



Common QualifierA Common Qualifier is used to create a mandatory condition across all qualifiers. A common qualifier consists of conditions which are joined by AND to all qualifiers in a table. When created, it displays on the qualifier table as a Common Qualifier.

You can create a common qualifier by selecting the Common Qualifier box when creating a qualifier. The search engine processes the common qualifier conditions first, and only processes other unique qualifiers if the pricing request qualifies for the common qualifier conditions.

For example, suppose you wanted to give a 10% discount with the following qualifying conditions.

■ Qualifier 1: Customer is "Preferred" status.

■ Qualifier 2: Customers must order more than $150 from your web site.

So far the customer can receive the discount if their status is Preferred OR if they order more than $150 from your web site. However, suppose you wanted to make a mandatory condition that the customer must pay by Credit Card.

To do this, you must set up a Common Qualifier where the payment method = Credit Card to make it a mandatory condition across all qualifiers. This means that either Qualifier 1 OR Qualifier 2 could qualify but regardless, the payment method must be Credit Card.

Note: In the Forms-based interface, Grouping Numbers are used to create AND/OR conditions. A grouping number of -1 is used to create the "Common qualifier" conditions. See Using Qualifier Grouping Numbers on page 2-21 for more information on Forms-based qualifier grouping numbers.

Note: It is important to familiarize yourself with certain navigational flow considerations in the HTML user interface when updating, changing, saving, or deleting data for price lists, modifiers, qualifiers, and their related lines. See Navigation flow behavior in HTML user interface on page 1-9 for more information.



To create a qualifier:1. Navigate to the Create Qualifiers page. The actual page name may vary

depending on the modifier type or price list associated with the qualifier.

Figure 2–1 Create Qualifiers page

2. From this page, you can create a qualifier or append an existing qualifier group for price lists and modifiers. To append a qualifier group, see Appending a Qualifier Group (HTML Interface) on page 2-15 for more information.

3. Click Create Qualifier to display the Qualifiers: Create Qualifier page.



Figure 2–2 Qualifiers: Create Qualifier page

4. Optionally, select "This is a common qualifier" to create a Common Qualifier. The conditions defined for a Common Qualifier will apply in addition to all unique qualifiers.

5. Select an Attribute to define a condition for the qualifier; for example, the Customer Class (attribute) is Platinum. You can create one or more conditions for each qualifier. Each condition is added as a new row in the table for the qualifier.

Note: When creating a new qualifier, if a common qualifier has been created, the conditions of the common qualifier are displayed as read only.

Note: Each condition within a qualifier are linked by AND conditions. This means that each condition within the qualifier must be met before the qualifying conditions are satisfied.



6. Select from the following Operator values: Is, Is not, and Between. The operator value links the attribute to the value; for example, the Customer Name Is Vision Corporation.

7. Select the Value From/To.

8. Select a range for the Start/End Dates. If left blank, then the condition will not expire.

9. Enter a Precedence value. The precedence value defaults from the attribute selected and can be updated. This value is used in incompatibility processing.

10. Optionally, click Add Another Row to add another qualifier condition.

11. Click Apply to save your changes and view the newly-created qualifier. Click the Expand node to view the qualifier details.

12. Optionally, click Create Qualifier to add Unique Qualifiers.

Figure 2–3 Example of Qualifiers page showing recently-created qualifiers

See:Updating a Qualifier (HTML Interface) on page 2-12



Deleting a Qualifier (HTML Interface) on page 2-14



Updating a Qualifier (HTML Interface)You can update a unique qualifier or common qualifier by adding, updating or deleting qualifier conditions. You can update the qualifier from the Create page or the Update mode of the modifiers or price lists.

To update a qualifier:1. Navigate to the Update Qualifier page. Alternately, the Update Common

Qualifier page displays if you are updating a Common Qualifier.

Figure 2–4 Update Common Qualifier page

2. Select the qualifier to be updated and click Update.

3. Complete your changes to the selected qualifier.




4. Click Apply to save your changes.

See:Creating Qualifiers (HTML Interface) on page 2-6


Note: When updating a unique qualifier, "This is a common qualifier" box is cleared if a common qualifier has not been defined. Select this box to convert the unique qualifier to a common qualifier.



Deleting a Qualifier (HTML Interface)You can delete unique or common qualifier conditions from the qualifiers table by clicking Delete at the qualifier condition level. Alternately, you can delete all the conditions of a qualifier by clicking Delete at the qualifier level.

Note: If you delete a qualifier during an update flow (for example when updating a modifier), you need to click Apply to save the changes.



Appending a Qualifier Group (HTML Interface)Qualifier groups consist of multiple qualifiers that can be associated with either price lists or modifiers. Qualifier groups can be appended to one or more price lists and modifiers. You can search by Group Name to find an existing Qualifier Group and append it to an existing qualifier.

To append a qualifier group:1. Navigate to the Qualifiers: Append Group page. In this page, you can attach

existing Qualifier Group(s).

Figure 2–5 Qualifiers: Append Group page

Note: You can append but not create qualifier groups using the HTML interface. See Creating a Qualifier Group on page 2-17 for information about creating qualifier groups.



2. Select the Group Name(s) to be added, then click Apply to append the qualifier group to the modifier or price list.

See: Creating a Qualifier Group on page 2-17


Creating a Qualifier Group

Creating a Qualifier GroupIn the Qualifier Group window, you can create a new qualifier group which consists of associated qualifiers. An example of a qualifier group could be:

■ Customer must be in territory WEST

■ Order Amount is between $2000 and $5000

■ Order Quantity must be greater than 10,000

The Qualifier Group can use seeded qualifiers (source attributes) such as Customer Name and Order Amount or your own qualifier attributes. These qualifiers could come from one or more qualifier contexts.

Note: You can create qualifier groups in the Forms-based user interface only.



To create a qualifier group:1. Navigate to the Qualifier Group window.

Figure 2–6 Qualifier Group window

2. Enter the qualifier group Name and a Description.

3. In the Qualifiers tab, enter a Grouping No. If you enter the same numeric value for more than one qualifier within a group, this creates an AND condition.

■ When entering different numeric values for multiple qualifiers within a group in the Grouping No. field, this creates an OR condition.

■ You must enter the EXACT values for Start Date and End date for EACH qualifier with a qualifier group when simulating an AND condition. If different dates are entered in either field, then the entire qualifier grouping will be ignored by the pricing engine

See: Using Qualifier Grouping Numbers on page 2-3 for more information on conditions set up with grouping numbers.

4. Select a qualifier Context.



5. Select a qualifying Attribute for the selected context.

6. In the Operator field select a value (=, BETWEEN, NOT =)

7. Enter Value From/To. You can select values based on the value set definition of the qualifier attribute chosen.

Some qualifiers use large value sets, for example, those based on all customers. To reduce the number of items that display in the Value From and Value To fields, you can:

■ Enter search criteria in the field.

■ Click the list of values indicator.

If you do not enter search criteria and click the list of values indicator, a warning advises you that you have not entered search criteria and that the search may take a long time:

■ To view a reduced list of values, click No, enter search criteria, and click the list of values indicator.

■ To view the entire list of values display, click Yes.

■ If you do not want to see the list of values, click Cancel.

Set the profile option QP: Valueset Lookup Filter to avoid this message.

8. The field Value From Meaning displays additional details of the qualifier when you query a qualifier after saving it. For example, if the context is CUSTOMER and the attribute is Ship To, Value From displays the customer name and Value From Meaning displays the site use location for the customer. If the context/attribute combination has no additional details, Value From and Value From Meaning are identical.

9. In the Start Date field, enter an optional date that the qualifier becomes active

10. In the End Date field, enter an optional date that the qualifier becomes inactive

Note: The Between operator serves as Between condition when Value from and Value to field both contain a value.

■ To simulate a Greater Than condition, enter a value in the Value From field, and leave Value To field blank.

■ To simulate a Less Than condition, enter a value in the Value To field, and leave Value From field blank.



11. Save your work.

Example of Qualifier GroupCustomer must be in territory WEST and Order Amount is between $2000 and $5000 or Order Type must be Standard.

Create a qualifier group, for example West1. The following table demonstrates field values to define the qualifier group West1.

Table 2–3 Example qualifier group “West1”

Grouping Number Context Attribute Operator Value From Value To

1 Geography Territory = West Null

1 Volume Order Amount

Between 2000 5000

2 Order Order Type = Standard Null



Using Qualifier Grouping NumbersA qualifier consists of qualifier lines that define eligibility for a particular price, discount, promotion, or benefit. You can assign qualifier grouping numbers to qualifier lines to create AND and OR conditions that define how the pricing engine should evaluate the qualifier lines. For example, if the customer is Vision Corporation AND they pay by credit card then apply the 10% Discount modifier.

It is important to use qualifier grouping numbers correctly because it indicates to the pricing engine how to evaluate the qualifiers:

■ Qualifiers with the same grouping number are evaluated as a boolean AND condition (an entity must meet all of the conditions to qualify).

■ Qualifiers with different grouping numbers are evaluated as a boolean OR condition (an entity must meet one of the conditions to qualify).

■ If -1 is used as a qualifier grouping number, the qualifier is ANDED to each qualifier group so you do not have to manually add it to each qualifier group.

AND ConditionsAn AND condition means that all qualifier lines with the same Qualifier Grouping Number must evaluate as "true" before the pricing engine can select the associated modifier.

In the following example, both Line A and Line B, which have the same Qualifier Grouping Number, must be true to satisfy the AND condition. So, for example, if the customer is not Vision Operations but the credit rating is Excellent, then the modifier cannot be selected (assuming these are the only qualifiers for the modifier). The modifier will only be selected if the customer is Vision Operations (qualifier line A) AND their credit rating is Excellent (qualifier line B).

Note: Qualifier grouping numbers are not used in the HTML user interface. Instead, you use Common or Unique qualifiers to create grouping conditions. See Creating Qualifiers (HTML Interface) on page 2-6 for more information.



The next table shows a setup where a 10% discount on each order is offered only if a Preferred customer spends more than $150:

OR ConditionsAn OR condition is created by assigning a different qualifier grouping number (such as 1 and 2) to successive qualifier lines. The OR condition provides more flexibility because only one of the qualifier groups needs to be eligible to be selected. So in the following example, if either the customer is Vision Operations (qualifier line A) OR if the credit rating is Excellent (qualifier line B) then the modifier is eligible for selection. If both are true then the modifier is also selected:

In the following example, a 10% discount is given on each order placed by a preferred customer OR each order in which a customer spends more than $150:

Table 2–4 AND Conditions

Qualifier Grouping Number Qualifier Line

Qualifier Context and Attribute Values

Condition Created

1 Line A Customer: Vision Operations AND

1 Line B Credit Rating: Excellent AND

Table 2–5 AND qualifying condition

Qualifier Group Qualifier Attribute Operator Value From Value To

1 Customer Class = Preferred Null

1 Order Amount Between 150 Null

Table 2–6 OR Conditions

Qualifier Grouping Number Qualifier Line Qualifier Context and Attribute Values

Condition Created

1 Line A Customer: Vision Operations OR

2 Line B Credit Rating: Excellent OR

Table 2–7 OR qualifying condition


1 Customer Class = Preferred Null



Using Combined AND/OR Conditions The following table displays a grouping number setup using a combination of AND and OR conditions:

An AND condition is created for Lines A and B because they are both assigned the same qualifier grouping number (1). Qualifier lines assigned the same grouping number must both be evaluated as true statements before they can be selected.

An OR condition is created between qualifier lines with different grouping numbers. So if either Line A/B (both must be evaluated together) OR Line C OR Line D evaluate as true, then the pricing engine can select the modifier.

Using -1 as Qualifier Grouping NumberTypically, positive integers are used for qualifier grouping numbers such as 1, 2, or 3. However, if -1 is used as a qualifier grouping number, the qualifier is ANDED to each qualifier group saving you time from manually adding the AND qualifier.

2 Order Amount Between 150 Null

Table 2–8 Using Combined AND and OR Conditions

Qualifier Grouping Number Qualifier Line Condition Created

1 Line A AND

1 Line B AND

2 Line C OR

3 Line D OR

Note: In the HTML user interface, the Common qualifier is used to create a common qualifier condition instead of the -1 grouping number. See Creating Qualifiers (HTML Interface) on page 2-6 for more information.

Table 2–7 OR qualifying condition




For example, to offer a discount in which a qualifier is mandatory for all qualifying conditions, the mandatory qualifier would be assigned the -1 qualifier group. The search engine processes -1 qualifying conditions first and only processes other qualifier groups if the pricing request qualifies for the -1 qualifier grouping number conditions.

For example, suppose you wanted to give a 10% discount on an order provided the:

■ Customer is a "Preferred" customer.

■ Customer (any customer) orders from a US web site and spends more than $150.

However, to be eligible for the discount the customer must use a VISA credit card to pay. In the following example, the credit card type of Visa is assigned the -1 Qualifier Grouping Number to make it a mandatory qualifier before the modifier can be selected.



Using Qualifier Grouping Numbers across Qualifier GroupsWhen qualifiers are assigned to a qualifier groups, all the qualifiers in the qualifier group are attached to the modifier or price list. Before you attach multiple qualifier groups, you must indicate how the process should coordinate the grouping numbers. You select one of the following grouping number options:

■ Retain Grouping Numbers Across Qualifier Groups: The grouping numbers of each attached qualifier remains as it appears in its qualifier group. In this case, the collection of attached qualifiers does not mirror the AND and OR combinations within each of the original qualifier groups.

■ Generate Unique Grouping Numbers Across Qualifier Groups: The process maintains the AND and OR combinations within each of the original qualifier groups and then creates OR conditions between the groups. It attaches the first qualifier group with grouping numbers as is, then finds the highest grouping number used, increases it by one, and increases all of the grouping numbers of the second group by this number. It attaches subsequent groups in the same manner, using the highest grouping number used by the just previously attached group.

■ Both: If you attach qualifiers using one option and then re-access the window and attach additional qualifiers using the other option, the second round qualifiers attach differently depending on the option. If the second round option is Retain Grouping Numbers Across Qualifier Groups, the process attaches those qualifiers among the already existing qualifiers. If the second round option is Generate Unique Grouping Numbers Across Qualifier Groups, the process begins attaching groups using grouping numbers incremented from the highest existing grouping number.

The following tables show examples of how the process sets the grouping numbers when you use each option. It presents the qualifiers grouped by each qualifier group:

Table 2–9 Selected Qualifier Groups

Qualifier Qualifier GroupQualifier Grouping Number

Q1 G1 1

Q2 G1 2

Q3 G1 2

Q4 G1 3



The grouping numbers within group G1, for example, create the qualification that the entity qualifies if it meets condition Q1 OR (condition Q2 AND condition Q3) OR condition Q4.

The following table shows the attached qualifiers when you select the option Retain Grouping Numbers Across Qualifier Groups. It presents the qualifiers grouped by each qualifier grouping number to highlight that it does not retain the original qualifier group relationships:

Q5 G2 1

Q6 G2 1

Q7 G2 1

Q8 G3 1

Q9 G3 2

Q10 G3 3

Table 2–10 Option: Retain Grouping Numbers Across Qualifier Groups

Qualifier Group QualifierQualifier Grouping Number

G1 Q1 1

G2 Q5 1

G2 Q6 1

G2 Q7 1

G3 Q8 1

Null Null Null

G1 Q2 2

G1 Q3 2

G3 Q9 2

Null Null Null

G1 Q4 3

Table 2–9 Selected Qualifier Groups

Qualifier Qualifier GroupQualifier Grouping Number



The following table shows the attached qualifiers when you select the option Retain Grouping Numbers Across Qualifier Groups. It presents the qualifiers grouped by each qualifier group to highlight that it does retain the original qualifier group relationships:

G3 Q10 3

Table 2–11 Option: Generate Unique Grouping Numbers Across Qualifier Groups

Qualifier Qualifier Group Qualifier Grouping Number

Q1 G1 1

Q2 G1 2

Q3 G1 2

Q4 G1 3

Q5 G2 4 (3 + 1)

Q6 G2 4 (3 + 1)

Q7 G2 4 (3 + 1)

Q8 G3 5 (4 + 1)

Q9 G3 6 (4 + 2)

Q10 G3 7 (4 + 3)

Table 2–10 Option: Retain Grouping Numbers Across Qualifier Groups

Qualifier Group QualifierQualifier Grouping Number


Querying a Qualifier Group

Querying a Qualifier GroupThe Find Qualifiers window lets you query for a specific qualifier group or define a new qualifier groups.

To query for a qualifier group:1. Navigate to the Find Qualifiers window.

Figure 2–7 Find Qualifiers window

2. Select the name of the qualifier group that you want to find.

3. Click Find to display the search results in the Qualifier Group window.


Modifying or Deleting Qualifier Groups

Modifying or Deleting Qualifier GroupsIn the Qualifier window, you can update or delete a qualifier group or an associated qualifier.

To modify a qualifier group and qualifiers:1. Navigate to the Qualifiers window.

2. Locate the Qualifier Group to modify or delete.

3. Modify or delete the record.

4. Click Save.

Note: You must first delete all associated qualifiers within a group before you can delete the qualifier group.


Modifying or Deleting Qualifier Groups


Mo

3
Modifiers
This chapter describes modifiers and includes the following topics:

■ Overview of Modifiers on page 3-3.

■ Creating a Modifier List on page 3-22.

■ Creating List Level Qualifiers on page 3-29.

■ Creating Modifier Lines on page 3-33.

■ Excluding Items from a Modifier on page 3-71.

■ Creating Line Level Qualifiers on page 3-74.

■ Copying a Modifier List on page 3-77.

■ Copying a Modifier Line on page 3-80.

■ Using Modifiers in the HTML User Interface on page 3-81.

■ Creating a Modifier List (HTML Interface) on page 3-83.

■ Creating Modifier Lines (HTML Interface) on page 3-92.

■ Searching for Modifier Lists (HTML Interface) on page 3-120.

■ Updating a Modifier (HTML Interface) on page 3-123.

■ Updating a Modifier Line (HTML Interface) on page 125.

■ Redeeming Accruals on page 3-130.

■ Changing Modifier Incompatibility on page 3-131.

■ Archiving and Purging Modifiers on page 3-136.

■ Using the Pricing Organizer on page 3-137.

■ Using the Pricing Organizer as Query Find on page 3-157.

difiers 3-1

■ Overview of Promotional Limits on page 3-167.


Overview of Modifiers

Overview of ModifiersModifiers enable you to set up price adjustments (for example, discounts and surcharges), benefits (for example, free goods, coupons) and freight and special charges that the pricing engine applies immediately to pricing requests or accrues for later disbursement. Using modifiers, you can:

■ Set up a modifier list with multiple modifier lines that define the terms of the price adjustment.

■ Create eligibility rules for modifiers by assigning list and line level qualifiers.

■ Define modifiers that are incompatible with other modifiers.

■ Create exclusive modifiers.

■ Create cascading modifiers.

■ Accrue monetary and non-monetary benefits.

■ Create monetary or usage limits that a customer can receive for a promotion, deal, or other modifier.

Using the HTML User Interface with Modifier Lists and Modifiers 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 only using the Oracle Forms-based interface. Tasks that can be completed in HTML are identified with "HTML Interface" in the task title, for example, Creating a Modifier List (HTML Interface)

Note: If you are using the multi-currency feature with price lists and modifiers, see: Considerations for Modifiers Using Multi-Currency Conversion List as a Qualifier on page 7-11.

You can only view or update a modifier in your pricing transaction entity. The profile QP: Pricing Transaction Entity must match the pricing transaction entity of the modifier.

You can only view or update a modifier in your source system. The profile QP: Source System Code must match the source system of the modifier. Otherwise, the modifier is view-only.

Modifiers 3-3


See:Using Modifiers in the HTML User Interface on page 3-81



Modifier ConceptsUsing modifiers, you can set up price adjustments, benefits, freight and special charges, and promotional limits to control spending or usage. You can define simple discounts and surcharges as well as more advanced deals and promotions. The following describes the main modifier concepts and related entities:

■ Modifier lists contain one or more modifiers. Modifiers have list level and line level components. Each list level must have one or more lines associated with it.

■ By defining qualifiers at the list and line levels, you define a customer’s eligibility for the modifier.

■ Control features that influence modifiers are products and product groups, pricing attributes, phases, incompatibility groups, levels, and buckets.

■ The use of modifiers can result in volume breaks, additional buy/get products, and benefits.

The following diagram provides an overview of modifiers and related concepts such as modifiers, modifier lists and qualifiers.

Modifiers 3-5


Figure 3–1 Modifier Overview

Modifier Lists and LinesUsing modifier lists, you can create groupings of price adjustments, benefits, and freight and special charges that you offer and report together to meet various business needs. At the list level, you define criteria that is common to the modifier lines.

Create modifier lines for a modifier list to define the type of price adjustments, benefits or freight and special charges that the pricing engine applies to pricing requests.



Application Method (Adjustment Method)The Application Method (or Adjustment Method in the HTML interface) determines how the modifier applies the price adjustment. You can select from the following application methods:

■ Percent: Creates a percentage price adjustment on each unit based on the percentage entered in the Value field. For example, to apply a 10% discount, select Percent as the Application Method.

■ Amount: Creates a fixed price adjustment on each unit using the amount entered in the Value field.

■ Lumpsum: Creates a price adjustment for this lump sum amount on the entire line.

■ New price: Overrides the selling price of this item and makes the new price defined in the Value field the new selling price. Creates a price adjustment for the difference in list price and the new price.

The following table shows examples of how the pricing engine uses the Application Method to calculate the extended selling price of an order line:

The application method available for a modifier line depends on the Level selected for that modifier line: Order, Line, or Group of Lines.

The following tables show what Application Method is available for each level: Order Level, Line Level, or Group of Lines. The Formula column shows if you can use a formula for the value for the modifier:

Table 3–1 Pricing Engine Calculating Extended Selling Price

List Price Item

Quantity Ordered

Application Method Value

Price Adjustment

Extended Selling Price

10 Item A 200 Amount 5 5 per unit 1000

10 Item A 200 Percent 5 5% per unit 1900

10 Item A 200 New Price 5 5 1000

10 Item A 200 Lumpsum 5 5 off for the entire line

1995

Modifiers 3-7


Table 3–2 Modifier Application Methods and Level Matrix

Level Modifier Type Application Method availableUse with Formula?

Order Level Discount Percent Yes

Order Level Surcharge Percent Yes

Order Level Freight/Special Charges

Lumpsum Yes

Line Level Discount Percent, Amount, Newprice, or Lumpsum

Yes

Line Level Surcharge Percent, Amount, Newprice, or Lumpsum

Yes

Line Level Freight/Special Charges

Percent, Amount, Lumpsum Yes

Line Level Other Item Discount (Get)

Percent, Amount, Newprice, or Lumpsum

No

Line Level Price Break Percent, Amount, Newprice, or Lumpsum

Yes

Line Level Promotional Good (Get)


No

Group of Lines Level

Discount Percent, Amount, Newprice, or Lumpsum

Yes


Surcharge Percent, Amount, Newprice, or Lumpsum

Yes


Other Item Discount (Get)


No


Price Break Percent, Amount, Newprice, or Lumpsum

Yes


Promotional Good (Get)


No



Using Lumpsum Application Method with Group of LinesWhen Lumpsum is selected as the Application Method for a modifier line, the pricing engine creates a price adjustment for the defined lumpsum amount. The lumpsum can be based on group quantity (sum of item quantities) or an item amount (a monetary amount).

Two examples are provided to compare how the lumpsum amount is calculated if either 1) Group Quantity or 2) Item Quantity is selected.

The following Discount List modifier is used in each example.

Lumpsum calculations based on Group Quantity The following example demonstrates how the adjustment amount is calculated when the Lumpsum modifier is applied against the group quantity of an order:

The pricing engine calculates the adjustment amount as follows:

1. The pricing engine calculates the Group Quantity value which is the sum of all item quantity lines. Therefore, the Group value is 50 (10 + 40).

Group value for Line 1: 50

Group value for Line 2: 50

2. To obtain the adjusted amount, the Value (from the Value field of the modifier—in this case, 1000) is divided by the Group value (50):

■ Line 1: 1000/50 = 20

■ Line 2: 1000/50 = 20

Table 3–3 "Lumpsum" Modifier used in example

Level

Modifier Type (Line level)

Product Attribute

Product Attribute Value Value

Application Method

Group of Lines Discount All Items All 1000 Lumpsum

Table 3–4 Lumpsum Group Quantity Calculation and Sample Price List

Line Item Quantity PriceAdjustment Amount calculated when Lumpsum Modifier Applied

1 AS54888 10 $80 $20 * 10 qty

2 AS54999 40 $20 $20 * 40 qty

Modifiers 3-9


The adjustment amount per quantity is $20. The total adjusted amount for the entire order is $1000: Line 1 is $200, and Line 2 is $800.

Lumpsum calculations based on Item AmountThe following example demonstrates how an adjustment for lumpsum modifier is calculated based on Item Amount (the monetary amount for each item). Suppose the Lumpsum modifier is applied against the following items on a sample sales order:

The engine calculates the lumpsum based on Item Amount as follows: Value divided (/) by Group Value:

1. Group Value is calculated as follows:

Group Value = Sum of all lines’ unit price * quantity/unit price per line:

Total Group Value= $80*10 + $20*40 = 1600

■ Group Value for Line 1 = 1600/80 = 20

■ Group Value for Line 2 = 1600/20 = 80

2. To obtain the adjusted amount per unit, the Value (from the Value field of the modifier—in this case, 1000) is divided by the Group value for each line:

■ Line 1: 1000/20 = 50

■ Line 2: 1000/80 = 12.5

Therefore, the adjustment amount for the first line is 50 and for the second line 80.

Table 3–5 Lumpsum Item Amount Calculation and Sample Price List

Line Item Quantity Price Adjustment Amount

1 AS54888 10 $80 50

2 AS54999 40 $20 12.5



Using Modifiers with Negative Unit Selling PricesA Discount or Surcharge modifier can be used to adjust the final unit selling price regardless of whether the item list price is a positive or negative value.

Example 1: Positive priced item If a product is $100 and the customer gets a 40% discount, then the customer gets a $40 discount, which means the price would be $60.

The following calculations are used to get this result:

List price * modifier % = line discount amount

List price - line discount amount = line price

Example 2: Negative priced itemIf a product is <-$100> and the customer gets a 40% discount, then the customer gets a <-$40> discount, which results in a price of <-$60>.

The following calculations are used to get this result:

<list price> * modifier % = <line discount amount>

<list price> - <line discount amount) = <list price> + line discount amount = <line price>

Example 3: Surcharge with Negative-Priced Items The following example shows the results when a Surcharge modifier is applied to a price list line with a negative price:

a. Create a simple modifier (ABC-MN) with type = Surcharge of 10%.

b. Create a price list line (ABC-N) with a value of <-$100>.

c. Enter a sales order with price list ABC-N and the item of the price list ABC-N.

d. Save the order.

e. The surcharge is applied, and the Unit Selling Price is <$-110.00>.

Note: The brackets <> indicate a negative price.

Modifiers 3-11


Incompatibility ProcessingWhen a customer is eligible for more than one modifier, you can use incompatibility processing to determine which of the modifiers the pricing engine should select and apply to an order or order line. See Changing Modifier Incompatibility on page 3-131 for more information.

BucketsWhen setting up a modifier, you can assign a modifier line to a particular bucket such as Bucket 1, 2, or 3 to define cascading price adjustments. This controls how discounts and other benefits are calculated. See Bucket on page 3-96 for more information on using buckets.

Manual ModifiersFor manual modifiers, the modifier adjustment is not applied automatically. Rather, you must manually select the adjustment to be applied to an order line. The following modifier types can be manual:

■ Discounts

■ Freight and special charges

■ Price Breaks

■ Surcharges

Manual modifiers can also be used with price break lines. You can set manual modifiers at the order, line, and group of lines levels and make them overridable.

Using pricing buckets with manual modifiers: Pricing buckets can be used with manual modifiers at the line or group of line level for the discounts, surcharges, freight and special charges, and price break modifiers. You can use this feature if the profile option QP: Allow Buckets for Manual Modifiers is set to Yes.

Once created, the manual modifier can be selected from the View Adjustments window in Order Management or the Price Adjustments window in Oracle Quoting. If a manual modifier is applied in an earlier bucket, then all subsequent adjustments will be recalculated. Alternately, when you overtype the selling price on the order line in Order Management, you can only apply manual adjustments in the null bucket. See the Oracle Order Management User’s Guide, Pricing chapter and the Oracle Quoting User’s Guide for more information on using manual modifiers.



EventsEvents are points in the process flow when the calling application sends a pricing request to the pricing engine (similar to a workflow event). The information that the pricing engine returns, for example, base prices, price adjustments, promotions, or freight charges, depends on the pricing phases of the event.

For example, if you need to price sales orders at shipment, use the Reprice Line event and insert the Reprice Line workflow activity into the order process workflow to invoke the repricing. The pricing engine uses the price list and modifiers that are in effect at order entry to meet booking requirements such as credit check.

AccrualsYou can create monetary and non-monetary accruals. For example, a customer accrues ten airline frequent flyer credits for each item they purchase. The pricing engine uses the accruals in price calculations and passes them to the calling application.

Accruals:

■ Do not affect the selling price of an order line

■ Do not appear as chargeable items on invoices

■ Create an adjustment record in the database

You can:

■ Assign expiration dates to accruals

■ Mark accruals as redeemed

■ Assign monetary accruals to buckets. Since accruals do not effect the selling price of an order line, the pricing engine does not include them in bucket calculations but uses bucket numbers to determine the price from which to calculate the accrual value.

Accruals using BucketsThe following table shows how accruals are calculated using buckets:

■ The Price Adjustment column shows the value of each modifier.

■ The Bucket Subtotal column shows the total value of all modifiers for the bucket.

■ The Selling Price shows the price at the beginning of the calculation and after the application of each bucket subtotal.

Modifiers 3-13


The value Null in a cell means that there is no value for that cell; the value Null Bucket means that the modifier is grouped in the null bucket:

Table 3–6 Accrual Value Calculation

Bucket Modifier Price Adjustment Bucket Subtotal Selling Price

Null Null Null Null 100.00

Null Null Null Null Null

1 Null Null (7.00) 93.00

2 Null Null (5.00) 88.00

3 Null Null (6.80) 81.20

Null Bucket

Null Null (15.00) 66.20

Null Null Null Null Null

1 10% accrual (10.00) Null Null





Example of Non-Monetary Accruals The following is an example of a setup for a non-monetary accrual.

If an Accrual Conversion Rate is used, then the Value = the monetary value of the points. The Accrual Value is calculated using the Benefit Quantity * Accrual Conversion Rate:

5 * 0.5 = 2.5

Qualifier Groups and Grouping NumbersWhen qualifiers are assigned to a qualifier groups, all the qualifiers in the qualifier group are attached to the modifier. Before you attach multiple qualifier groups, you must indicate how the process should coordinate the grouping numbers. For more information on qualifier groups, see: Using Qualifier Grouping Numbers across Qualifier Groups on page 2-25.

Cross Order VolumeYou can provide extra benefits to a customer after they place a certain amount of business with you. The cross order volume feature allows you to create modifiers that are qualified across an accumulation of orders and applied when a customer meets certain volume levels. It accumulates and sums order amount, item quantity, and item amount across the orders of each customer.

Table 3–7 Example of Non-Monetary Accruals Setup

Field Value

Volume Type Item Quantity

Break Type Recurring

Operator Between

UOM EA

Value From 2

Value to 99999999

Application Method Lumpsum

Accrual Value 2.5

Benefit Quantity 5

Benefit UOM PN (for Points)

Accrual Conversion Rate 0.5

Modifiers 3-15


Cross Order Volume Profile OptionsTo use cross order volumes, set up periods in the following profile options:

■ QP: Cross Order Volume Period 1



Assign a default value to each profile option in unit of measure Days. For example, set the profile options as follows:

■ QP: Cross Order Volume Period 1: 30



Cross Order Volume LoadRun the concurrent process Cross Order Volume Load to populate the cross order volume tables. The qualifier and pricing attribute sourcing functions determine the cross order volumes for a customers and customer-item combinations.

To run the Cross Order Volume Load process:1. Select Cross Order Volume Load to execute either for a single operating unit or

for all operating units.

2. Enter the load effective date; otherwise the process uses the current date. It uses the cross order volume profile options to determine the order lines included in the cross order volumes.

For example:

■ Profile option QP: Cross Order Volume Period 1: 30



■ Concurrent process Cross Order Volume Load, Effective Date: 31-December

■ Cross order period 1: Order lines with request date between 1-December and 31-December

■ Cross order period 2: Order lines with request date between 1-November and 31-December-2000



■ Cross order period 3: Order lines with request date between 2-October and 31-December-2000

The Cross Order Volume Load concurrent process has been coded so the qualifier and pricing attribute sourcing functions determine the cross order volumes for a customer and customer-item combinations. The Cross Order Volume Load considers only orders and order lines in Booked status. The Cross Order Volume Load does not look at returned or cancelled order lines.

The information in the cross order volume tables is only as current as when the last Cross Order Volume Load concurrent process was run. As orders continued to be booked the concurrent process will need to be executed to include this information. Your business processes should dictate how often these tables need to be loaded with more current information.

The pricing engine calculates the Cross Order/Item Amounts using the List Price on the Order Line not the Selling Price, this is consistent with the calculation of all non-Cross Order Amount based Qualifiers/Pricing Attributes.

The cross order loader calculates the order total and item amount in the currency that is in the set of books. For example, if your set of books is in USD (dollars) and you also have orders in Japanese Yen, the Cross Order Amounts are calculated and summed in USD. The value of the order in Japanese Yen is converted to USD by the cross order loader before including the value in the total amount.

When an order is input as Japanese Yen, and the engine is pricing in Japanese Yen, in an Organization where the Set of Books currency was USD, the seeded sourcing APIs for the Cross Order Amount qualifiers convert the total Cross Order Amount in USD to Japanese Yen.

The pricing engine accumulates all Cross Order totals for an Organization, but it does not summarize across Organizations. The pricing engine only takes into account the orders that a customer has placed with each Sales Organization, and does not consider orders that the customer placed with other Sales Organizations. When running the Cross Order Volume Loader, if you specify an organization, it runs the load for that organization; if you leave it null, it will summarize for all organizations for which there are orders (assuming a multi-org install). Even if it is loading for multiple organizations, each summary is still within each organization.

When performing currency conversions in the Cross Order Volume Loader or Sourcing APIs, the engine performs the conversion using the order header currency conversion rate in Oracle Order Management. If the order header has no currency conversion rate, the pricing engine determines the conversion rate from the rates defined in Oracle General Ledger.

Modifiers 3-17


When you have different units of measure (UOM) for orders, the Cross Order Volume Loader converts from the ordered UOM to the Oracle Inventory primary UOM. In the cross order tables, the item quantity is always the primary UOM of the Item. When the pricing engine sources a Cross Order Quantity for an item, the seeded sourcing API converts the Cross Order Item Quantity from the primary UOM to the Ordered UOM and the pricing engine then converts the Cross Order Item Quantity from the Ordered UOM to the Pricing UOM.

If the pricing engine cannot find a UOM conversion rate for an item to convert from the Ordered UOM to the Primary UOM, the engine returns an Error Message in the Cross Order Loader log file. In this case the total Cross Order Quantity for this item will be incorrect.

Cross Order Volume ModifiersYou set up cross order modifiers by using cross order qualifiers or volume attributes.

Seeded cross order qualifiers are:

■ Context: Volume

■ Qualifier Attributes:

■ PERIOD1_ORDER_AMOUNT



You use this qualifier attribute if you want your modifier to be qualified based on the total order amount for the period specified in the profile option. You can set up these qualifiers at the modifier list level or line level.

For example, set up the modifier with a list level qualifier as follows:

■ Context: Volume

■ Qualifier Attributes: PERIOD1_ORDER_AMOUNT

■ Operator: Between

■ Value From: 10000

■ Value To: 49999

At order entry time, information is sent to the pricing engine. For example, the pricing engine determines if this customer is eligible to receive this modifier. The engine compares the Qualifier attribute value of 10,000 against the total order



amount for this customer in the cross order volume tables. If the total order amount in the cross order volume tables is between 10,000 and 49,999, the order line is eligible to receive the modifier and the pricing engine applies this modifier.

You can use the cross order qualifiers with any modifier list or line type.

Seeded cross order item attributes are:

■ PERIOD1_ITEM_AMOUNT



■ PERIOD1_ITEM_QUANTITY



You use the volume attribute if you want your modifier to be applied based on the item amount or item quantity for the period specified in the profile option. This volume attribute is setup on the modifier line in the volume type field. For example:

■ Product Attribute: Item Number

■ Product Attribute Value: Item A

■ Volume Type: Period 1 Item Quantity

■ Break Type: Point

■ Operator: Between

■ UOM: EA

■ Value From: 100

■ Value To: 999

■ Application Method: Percent

■ Value: 10

Note: Since the cross order volume load sourcing does not add the current order amount to the Cross Order Amount, you could also use the Cross Order Amount qualifiers to qualify a Price List.

Modifiers 3-19


At order entry time, information is sent to pricing engine. The engine determines if this customer is eligible to receive this modifier. The engine compares the volume attribute value of 100 against the total item quantity for this customer-item in the cross order volume tables. If the total item quantity in the cross order volume tables is between 100 and 999, the order line is eligible to receive the modifier and the engine applies this modifier.

There are restrictions by modifier line type with the use of the cross order volume attributes:

■ You can use cross order volume attributes with any line type as a single line break.

■ You can use cross order volume attributes with modifier line type Price Break, thus you can create multiple level breaks and apply a discount or a surcharge based upon the tier level that is met.

Cross Order Volume ReportRun the Cross Order Volume Report to view the information in the cross order volume tables. The report displays the total order amount, total item amounts and total item quantities for each customer and period.

Note: It is critical that the Cross Order Volume Period profile options be setup prior to the cross order qualifier and volume attribute use in setting up modifiers. There is no system validation during modifier setup between the Cross Order Volume Period profile options and the cross order qualifiers and volume attributes. Thus it is possible for a user to define a modifier with the cross order qualifier and volume and this modifier fail and not be applied at order execution. There is not an error message given to the user that notifies of this failure, the modifier just isn’t applied.



Note: The cross order volume loader only accumulates orders for items in the Cross Order Item Amount/Quantity Summary that have modifiers using the cross order volume attributes. Similarly the engine only gives total Cross Order summaries if a Cross Order qualifier has been used in a modifier. Therefore it necessary to run the cross order volume concurrent request after you setup any modifiers using either (a) a Cross Order Amount Qualifier that has not been used previously or (b) a Cross Order Item Amount/Quantity Pricing Attribute for an item that has not been used previously. This is to ensure that all items totals are accumulated and loaded into the cross order tables.

Modifiers 3-21

Creating a Modifier List

Creating a Modifier ListUsing modifier lists, you can create groupings of price adjustments, benefits, and freight and special charges that you offer and report together to meet various business needs. At the list level, you define criteria such as the modifier currency that applies to the modifier and any modifier lines you add to the modifier list.

You can create the following modifier list types:

■ Deal

■ Discount List

■ Freight and Special charge List

■ Promotion

■ Surcharge List

Note: Oracle Advanced Pricing also provides an HTML-based user interface for setting up and maintaining most modifier and modifier line types. See Using Modifiers in the HTML User Interface on page 3-81 for information on using the HTML user interface with modifiers.



To create a modifier list:1. Navigate to the Advanced Pricing-Define Modifier window.

Figure 3–2 Advanced Pricing - Define Modifier window

2. In the Main tab, select the a modifier Type.

3. Enter the modifier list Number.

4. Select or clear Active.

Note: If you cannot query or update the modifier after saving it or exiting, consult with your Pricing Administrator for access privileges. Your security privileges may not allow you to access this window.

Modifiers 3-23


5. Enter a Name to identify the modifier.

6. Enter a Version if the modifier Type is Promotion or Deal.

A Global box displays if the Pricing Security Control Profile is set to ON. If the box is selected, the modifier list can be used by all operating units for pricing transactions. If cleared, the modifier’s use is restricted to the operating unit of the user creating the modifier list.

7. Select or clear the Automatic box:

■ If selected, the Automatic box is also selected at the line level, and the pricing engine automatically applies the modifier.

■ If cleared, then the modifier is considered a "manual" modifier and the adjustment must be applied manually rather than automatically. See Manual Modifiers on page 3-12 for more information.

8. Choose one of the following:

■ Select a Currency. If a currency is selected such as US dollars (USD), the sales order must match the modifier currency to determine pricing for the

Note: The pricing engine evaluates the modifier only if the Active box is selected (inactive modifiers are not evaluated further by the pricing engine). The pricing engine performs more effectively if the Active box is cleared for expired modifiers. You can query inactive modifier lists.

Note: The modifier Name should be unique across all PTEs (Pricing Transaction Entities) otherwise an error occurs. For example, if a modifier named "Corporate" is created in the Order Management PTE, an error message displays if you create a "Corporate" modifier in the Purchasing PTE.

Note: If Automatic is enabled at the modifier list level, you can still manually apply line types of Discount, Surcharge, and Freight/Special Charges by clearing the Automatic box at the line level.



order. The modifier can then be used with a matching base currency or "to currency" (for a multi-currency price list).

■ Optionally, select Optional Currency to leave the Currency field in the modifier list blank. This option can be selected for modifiers where currency is not used as a criteria to select modifiers for the order.

9. Enter the Start and End Date range for the modifier.

10. Enter a Description for the modifier list. If the modifier list Type is Promotion or Deal, select the Advanced tab.

11. Save your work.

See:Creating List Level Qualifiers on page 3-29

Overview of Promotional Limits on page 3-167

Note: If you do not enter dates and check Active, the list is effective from the creation date.

Modifiers 3-25


In the Advanced tab1. If the modifier list Type is Promotion or Deal, select the Advanced tab.

2. Enter the Parent Number and Parent Version to specify the promotion to which the deal is associated.

3. Select the Ask for box to create an Ask for modifier. This means the customer must specifically request that the modifier benefit be applied (for example, by providing a special discount number), otherwise it will not be applied. The Ask for box is only available for modifier list types of Deal and Promotion.

4. Select Date Type I field to specify Order Date and Date Type II field to specify Requested Ship Date. Order Date and Requested Ship Date are passed by Order Management and cannot be changed. If you enter both dates, the sales order must meet both dates to be eligible for the modifier.

5. Save your work.

Note: Modifier list types of Promotion and Deal have a parent-child relationship for reporting purposes. A Deal modifier list must be associated with a parent Promotion by providing the promotion name and version. Since this association is for reporting purposes, information that you define on the promotion is independent of and does not affect the information on the Deal modifier. You must have already created the Promotion modifier to

Note: If the pricing engine selects multiple modifiers to apply to an order line, Ask for promotions receive a higher preference than other modifiers.

Note: The same results can be achieved by creating qualifiers for Order Date and Ship Date and attaching them to the modifier. These qualifiers are sourced and the user can override the mapping rules for these qualifiers.



In the Other tab1. Select the Other tab.

Figure 3–3 Advanced Pricing - Define Modifier window: Other tab

This tab displays the following information including details about any related Blanket Sales Agreement:

■ List Source Document Number: This is the Blanket Number of the blanket sales agreement associated with the modifier.

■ List Source Code: Displays the code associated with the modifier source. For example, BSO indicates Blanket Sales Order.

■ Pricing Transaction Entity (PTE): Displays the pricing transaction entity associated with the modifier. The Pricing Transaction Entity value defaults from the PTE that created the modifier. This field cannot be updated.

■ Source System Code: Displays the source system code of the modifier such as QP for pricing.

Modifiers 3-27


■ Shareable box: Indicates if the modifier is shared or not. If non-shareable (the default), then this modifier is specific to that blanket and cannot be used with other blanket sales agreements.

If shared, the modifier is not exclusive to the blanket sales agreement and can be selected for use with other agreements.

Note: The Pricing Transaction Entity and Source System fields display for all modifiers regardless of whether there is a related Blanket Sales Agreement.


Creating List Level Qualifiers

Creating List Level QualifiersYou can create qualifiers to determine the eligibility of who can receive modifiers at the list level. If an order is not eligible for a modifier list, it is not eligible for that list’s line level modifiers even if the lines have qualifiers for which the order is eligible.

To create list level qualifiers:1. Navigate to the Advanced Pricing - Define Modifier window.

Figure 3–4 Advanced Pricing - Define Modifier: Modifiers Summary tab

2. In the Main tab, click List Qualifiers to display the Qualifier Groups window. If qualifiers are associated with the modifier list, then the Qualifier Groups window does not display.

Modifiers 3-29


Figure 3–5 Qualifier Groups window

3. If you do not want to add qualifiers from qualifier groups, click Cancel. Alternately, to add qualifiers from qualifier groups, select one or more qualifier groups that you want to attach.

4. Select one of the grouping options (Retain Grouping Numbers Across Qualifier Groups or Generate Unique Grouping Numbers Across Qualifier Groups). For more information, see: Using Qualifier Grouping Numbers across Qualifier Groups on page 2-25.

5. Click OK to display the Qualifier window. In this window the qualifiers associated with the qualifier groups are listed.

You can add, change, and delete individual qualifiers and change the grouping numbers or dates. If you have attached qualifier groups, verify that the grouping numbers in the window display the correct combination of AND and OR conditions.



Figure 3–6 QUALIFIER - Header Level Qualifiers

6. Enter the Grouping Number. Qualifiers with the same grouping number generate an AND condition and qualifiers with different grouping numbers generate an OR condition. If -1 is used as a qualifier grouping number, the qualifier is ANDED to each qualifier group so you do not have to manually add it to each qualifier group. For more information, see: Using Qualifier Grouping Numbers on page 2-21.

7. Enter the Qualifier Context.

8. Enter the Qualifier Attribute.

9. Enter the Operator, Value From, and Value To.

The Value From Meaning field provides additional details about the selected qualifier. For example, if the qualifier context is CUSTOMER and the attribute is Ship To, Value From displays the customer name and Value From Meaning displays the site use location for the customer. If the context/attribute

Note: After you save a qualifier with Qualifier Context of Modifier List and Qualifier Attribute of Coupon Number, you cannot modify or delete it. Since the pricing engine creates coupons (and a qualifier for each coupon) these coupon qualifiers are not subject to manual changes and deletions.

Modifiers 3-31


combination has no additional details, Value From and Value From Meaning are identical.

10. Click Copy Groups to add qualifiers from other qualifier groups, and enter Start and End dates of the qualifier. For more information on Qualifiers, see: Oracle Advanced Pricing User’s Guide, Qualifier Groups.

11. View and, if necessary, adjust the precedence numbers that default from the qualifier definition.

The pricing engine uses the Precedence to resolve incompatibility. If multiple modifiers are eligible within the same phase and incompatibility level, the modifier with the lowest precedence is applied.

12. Click OK and save your work.

Note: The start and end dates of the list qualifiers must be within the start and end date of the modifier list.


Creating Modifier Lines

Creating Modifier LinesYou can add modifier lines to a modifier list to define the type of price adjustments, benefits or freight and special charges that the pricing engine applies to pricing requests.

For each list type that you define, you can select certain modifier line types. The following modifier types are available at the line level:

■ Coupon Issue: Issues a coupon on one order that the customer can redeem for a price adjustment or benefit on a later order.

■ Discount: Creates a negative price adjustment such as a 10% discount.

■ Freight/Special Charge: Applies a freight charge.

■ Item Upgrade: Replaces a specific item ordered with another item for the same price.

■ Other Item Discount: Gives a price adjustment or benefit to a specified item on an order when the customer orders one or more other items on the same order.

■ Price Break Header: Applies a variable discount or surcharge price adjustment to a pricing request based meeting the condition of a break type. You can use both point and range type breaks.

■ Promotional Goods: Adds a new item with a price adjustment or benefit when the customer orders one or more other items on the same order.

■ Surcharge: Creates a positive price adjustment.

■ Term Substitution: Replaces freight charges, shipping charges, and payment terms with typically more favorable charges.

Note: Oracle Advanced Pricing also provides an HTML-based user interface (UI) for setting up and maintaining most modifier and modifier line types. See Using Modifiers in the HTML User Interface on page 3-81 for information on using the HTML user interface with modifiers.

Note: If you are using Promotional Good (PRG) type of Modifier Line with multi-currency price lists, see: Using Promotional Good type of Modifier Line on page 7-12.

Modifiers 3-33


The following table details the modifier line types that can be used with a selected modifier list type. Each row is a modifier line type and each column is a modifier list type. A Yes in a row indicates that you can use the line type in the list type, a No indicates that you cannot:

Once you have created and saved a modifier line, you cannot edit or change the Product Attribute Value (or primary buy item) for the line. To change the Product Attribute Value for a line, you should end date the existing modifier and create a new modifier.

This following section describes general setup information common to most modifier line types. For information on setting up the following modifier line types, see the following:

Table 3–8 Modifier List and Modifier Line Types Compatibility

Modifier Line Type (listed in column below) Deal

Discount List

F&S charge List Promotion

Surcharge List

Coupon Issue Yes No No Yes No

Discount Yes Yes No Yes No

Freight/Special Charge No No Yes No No

Item Upgrade Yes No No Yes No

Other Item Discount Yes No No Yes No

Price Break Header Yes Yes No Yes Yes

Promotional Goods Yes No No Yes No

Surcharge Yes Yes No Yes Yes

Terms Substitution Yes No No Yes No

Note: You cannot create promotional limits for the modifier line if:

■ The Modifier line type is Other Item Discount, Promotional Goods, Coupon Issue, Item Upgrade, or Term Substitution.

■ The Automatic box is cleared (if the modifier line is manually applied).

■ The Override box is enabled.



To enter discount/charges information: on page 3-43.

To enter freight charge information: on page 3-46.

To enter item upgrade information: on page 3-48

To enter terms substitution information: on page 3-50

To enter coupon issue information: on page 3-51

To enter Promotional Goods and Other Item Discount information: on page 3-54

To enter price break header information: on page 3-59

Modifiers 3-35


To enter basic modifier line information:1. Navigate to the Advanced Pricing - Define Modifier window.


2. In the Modifiers Summary tab, Modifier No field, a default modifier number identifies the modifier line. You can change this value; however, the Modifier No for each modifier line must be unique within the modifier list.

3. Select the Level that the modifier is applied:

■ Order: If the line is eligible to receive the modifier, the pricing engine applies the modifier at the order level.

■ Line: If the line is eligible to receive the modifier, the pricing engine applies the modifier at the line level.

■ Group of Lines: If the pricing request is eligible to receive the modifier, the pricing engine considers the item quantity or item amount consumed for a group of order lines. The following table displays the available modifier



types and volume types that can be selected for a modifier line when Group of Lines is selected:

4. You can select a formula to calculate a price adjustment. For example, to calculate a discount using a formula, attach a formula to a discount line.

Formulas are available only with the following modifier list types: Discount, Surcharge, or Freight and Special charge List.

5. Select a modifier type. If you plan to set up promotional limits for the modifier, confirm using the following table that promotional limits can be applied to the modifier line type:

6. Enter the Start/End Dates for the modifier line.

Table 3–9 Modifier Types and Volume Types available when Group of Lines selected

Level Modifier Types that can be created with Group of Lines

Volume Types that can be used with Group of Lines

Group of Lines Discount, Item Upgrade, Other Item Discount, Price Break Header, Promotional Good, Surcharge, Terms Substitution,

Item Quantity, Item Amount

Table 3–10 Promotional Limits for Modifier

Modifier TypeCan Promotional Limits be applied?

Coupon Issue No

Discount Yes

Item Upgrade No

Other Item Discount No

Price Break Header Yes

Promotional Goods No

Surcharge Yes

Term Substitution No

Modifiers 3-37


Print On Invoice is reserved for future use.


■ Select Automatic to have the pricing engine automatically apply this modifier. The Automatic box for each modifier line also becomes selected.

■ Clear the Automatic box if you want the modifier to be manually applied. See Manual Modifiers on page 3-12 for more information on manual modifiers.

For Promotional Limits: If you are using promotional limits with the modifier, the Automatic box must be selected and remain selected at both the modifier header and line level. Limits do not function with a modifier that is applied manually.

8. Select Override to enable the modifier adjusted price to be manually overridden. If not selected then the modifier adjusted price cannot be overridden.

9. Enter the Pricing Phase for this modifier line. Only valid phases for this modifier level appear in the list of values.

If you attach a phase with a PRICE event to the following promotional modifier types - Promotional Goods/Other Item Discount/Item Upgrade/Terms Substitution/Coupon Issue - and save the modifier line, then the following error message displays:

The pricing phase for this modifier is attached to a PRICE event and cannot be used for this modifier type. Please change the pricing phase or remove a PRICE event for this phase from the Event Phases form.

Note: The start and end date for the modifier line must be between the start and end date on the modifier list. The pricing engine confirms that the dates for the modifier line are valid so that the modifier line can be applied.

Note: In the Advanced Pricing - Define Modifier window, you can clear the Automatic box for the following line level modifiers: Discount, Surcharge, and Freight/Special Charges.



10. Select an Incompatibility Group. See Changing Modifier Incompatibility on page 3-131 for more information about incompatibility groups.

11. Enter a Bucket value.

12. Enter a numeric Comparison Value. The pricing engine uses this value to compare modifier types of Item Upgrade, Other Item Discount, and Term Substitution to resolve incompatibility and determine which modifier(s) to apply. This is used when the pricing phase incompatibility resolution is Best Price.

13. Select a Product Attribute value such as Item Number, Item Category, or All Items.

14. Select a Product Attribute Value. If you select ALL_ITEMS for Product Attribute, the Product Attribute Value is ALL.

15. The Precedence value will default based on the Product Attribute Value. This value can be updated.

If two or more modifiers tie based on precedence processing, then the engine resolves using best price processing without going below the established precedence.

Note: The Proration Type field is reserved for future use.

Note: Best Price processing cannot be used for the following order-level modifier list types (Discount, Surcharge, Freight and Special charge).

Note: Use All Items to define a modifier that applies to all items in your product hierarchy.

Note: If you do not enter values for Product Attribute and Product Attribute Value, the Pricing Engine applies the modifier line as if you selected ALL_ITEMS for Product Attribute.

Modifiers 3-39


16. Enter a Volume Type to instruct the pricing engine which item attribute to use when qualifying for a modifier.

17. Select an Operator value such as = or BETWEEN; for example, item quantity = 5 or item quantity BETWEEN 5 and 20.

18. Select the unit of measure (UOM) for the item or item category. If the line type is Promotional Goods, Other Item Discount, Item Upgrade and Volume Type is Item Quantity, then the UOM is mandatory.

19. To create greater than and less than conditions, leave From Value and To Value blank, as follows:

■ From Value = 5 and To Value blank creates the condition Value > 5

■ From Value blank and To Value = 100 creates the condition Value < 100

■ From Value = 5 and To Value = 100 creates the condition Value >= 5 and value <= 100Enter the Value From/To.

20. Select either Point or Recurring as the Break Type. The Break Type is optional for the following modifier types:

Note: Valid Volume types are Item Quantity and Item Amount. Period is reserved for future use.

Note: If you select Recurring for Break Type, you must select BETWEEN.

Note: For Promotional Limits:

■ If no Product UOM is defined for the Modifier Line, line limits with basis of Item Quantity will not get created.

■ If no Benefit UOM is defined for a Modifier Line, line limits with basis as Accrual Units will not get created.

■ If no Benefit or Product UOM is defined, neither Item Quantity or Accrual Units displays in the Basis list of values (LOV) to prevent line limits from being created.



■ Discount

■ Surcharge

■ Freight Charge


■ Coupon Issue

The following table provides an example of a setup for a point break.

The pricing engine interprets this point setup as follows: an order of 100 cases of item A gets a 2 currency unit discount. If you order 200 cases of item A, you receive a 2 currency unit discount. The following table details an example setup for a recurring price break:

Table 3–11 Point Break Type

Field Value

Break Type Point

Modifier Line Type Discount

Product Attribute Item

Product Attribute Value Item A


Operator Between

UOM Cases

Value From 100

Application Method Amount

Value 2

Table 3–12 Recurring Break Type

Field Value

Break Type Recurring

Modifier Line Type Discount

Product Attribute Item

Product Attribute Value Item A

Modifiers 3-41


The pricing engine interprets this recurring setup as order 100 cases of item A and get a 2 currency unit discount. If you order 200 cases of item A you receive a 4 currency unit discount.

21. Select Point or Range to calculate the volume break.

See:Using Point and Range Price Breaks on page 3-104


Operator Between

UOM Cases

Value From 100

Application Method Percent

Value 2

Table 3–12 Recurring Break Type

Field Value



To enter discount/charges information:1. In the Discounts/Charges tab, select or clear Include on Returns. If you select it,

the pricing engine includes freight charge on returns.

Figure 3–8 Advanced Pricing - Define Modifier window: Discounts/ Charges tab

2. For modifier line types of Discount, Surcharge or Price Break Header, you can select a Formula to calculate the amount. If the formula equation includes a Modifier Value (MV), the value for MV originates from the Value field in the Discounts/Charges tab.

For example, consider a formula with the following equation:

List Price * Modifier Value = Final Discount

Table 3–13 Example of Formula and Modifier Value

Formula List Price (LP) Modifier Value (MV) Final Discount

LP *MV=Final Discount 20 3 60

Modifiers 3-43


At Order Entry, when the modifier is selected and the formula LP *MV is applied, the list price of the item on the order (LP) is multiplied by the value that is entered in the modifier’s Value field. In this case, the value is 3. So the final discount is 20*3=60.

A formula without a Modifier Value component can be attached to a modifier even if a value is entered on the modifier line. In this case, the formula takes precedence and the modifier value is not used. Instead, the number returned by the formula is considered as a final discount.

3. Select an Application Method (Adjustment Method) that defines how the pricing engine applies this modifier.

4. Enter a numeric value also known as the modifier value (MV). The application method selected in the preceding step determines how the modifier value is applied. For example, if the application value is Percent, then the value is applied as a percent.

■ If you selected a formula and the formula equation includes a component type of Modifier Value (MV), the value entered in the modifier line is used in the equation.

■ If a formula without a Modifier Value component is attached to the modifier line, then the value is not used during the formula calculation when the final discount is returned.

Complete the remaining steps to enter an accrual:

5. For line type Discount, select Accrue to enter accrual information.

6. Enter Benefit Qty and Benefit UOM of the benefit that you want to accrue. Use the benefit columns to define non-monetary accruals.

7. Enter Expiration Date to specify when the accrued transactions expire.

8. Enter Expiration Period and Period Type. The pricing engine calculates the expiration date. The Expiration Period begins when item begins to accrue.

9. Rebate Transaction Type is reserved for future use.

You can enter or modify the Accrual Redemption Rate once the Accrue box is selected.

Note: These fields are unavailable if you enter an Expiration Date.



10. Enter an Accrual Conversion Rate to specify the conversion of the Benefit UOM to the primary currency. For example, if one air mile is 0.50 currency units, the accrual conversion rate is 0.50.

11. Save your work.

Modifiers 3-45


To enter freight charge information:1. Enter the following information in the Modifiers Summary tab:

■ Level: Use Line or Order

■ Modifier Type: Use Freight/Special Charge

■ Phase: If Level is Line: use Line Charge or Line Manual Charge. If level is Order, enter the Charge Name.

■ Bucket

2. In the Discounts/Charges tab, select the Charge Name such as Freight Costs.

Figure 3–9 Advanced Pricing - Define Modifier window: Discounts/Charges tab

3. The Include on Returns box is selected by default so that the pricing engine includes freight charge on returns. Alternately, clear this selection if freight charges should not be included on returns.

4. Enter a Formula name to use a formula to calculate a discount, surcharge, or freight charge.



5. Select an Application Method (Adjustment Method) to instruct the pricing engine how to apply this modifier.

6. Enter a Value unless you are using a formula.

7. Save your work.

Note: For Order Level modifier lines of type Discount and Surcharge, only Percent can be selected as the Application Method. For Freight/Special Charge modifiers, Lumpsum must be selected as the Application Method.

Note: For Freight/Special Charges, if an Incompatibility Group is not selected for the modifier line, then the pricing engine will use BEST PRICE incompatibility processing instead of Precedence. Precedence is defined as the Incompatibility Resolve Code in the Event Phases window.

Modifiers 3-47


To enter item upgrade information:1. Enter the following information in the Modifiers Summary tab:

■ Level

■ Modifier Type: Use Item Upgrade

■ Phase

■ Bucket

■ Product Attribute

■ Product Attribute Value

■ UOM

2. In the Promotion Upgrades tab, select Upgrade Item.

Figure 3–10 Advanced Pricing - Define Modifier window: Promotion Upgrades tab



When the pricing engine applies the qualifying item on the order line, it changes the original item to the upgraded item and retains the price of the original item.

3. Save your work.

Considerations when Copying an Order with a Item Upgrade LineWhen you copy a sales order with an Item Upgrade line, the Item Upgrade line is copied to the new order and the Calculate Price Flag field for the item in the Pricing tab is set to Calculate Price.

If you view the copied upgrade item in the Adjustments window, the copied item is no longer designated as an Item Upgrade as the original was. If you inactivate the modifier that resulted in the item upgrade and reprice the copied order, the copied Item Upgrade item will not revert to the pre-upgrade item.

Note: Before entering the upgrade item, relate the item and its upgrade item in Oracle Inventory. Select Promotional Upgrade for Relationship Type. When you complete this relationship, the related item appears in the list of values for this field.

Modifiers 3-49


To enter terms substitution information:1. Enter the following information in the Modifiers Summary tab:

■ Level

■ Modifier Type

■ Phase

■ Bucket

2. In the Promotion Terms tab, enter the Terms Attribute.

Figure 3–11 Advanced Pricing - Define Modifier window: Promotion Terms tab

The pricing engine substitutes the terms on the order or line with the terms that you specify:

3. Enter the new terms in Terms Value.

4. Save your work.



To enter coupon issue information:A Coupon Issue modifier is created in two parts:

a. In the first modifier line, you create the "benefit" that the coupon provides such as a 10% discount. This is the "Benefit" modifier line.

b. In a second modifier line, you define the coupon details such as the coupon name, its expiration date, and other details. This is the "Coupon Issue" line. Then you link the benefit line to the coupon issue line.

When setting up the coupon issue line, entering a Coupon Modifier Number is mandatory. The pricing engine uses the number to generate a unique number series for the coupon which it passes to the calling application. The customer must quote the coupon number to redeem the coupon in the calling application. However,

When the customer redeems the coupon, the pricing engine validates the coupon number against the qualifier and also validates the qualifiers for the discount or promotional goods benefit (the get).

The following steps outline how to create a coupon issue modifier:

1. In the Modifiers Summary tab, create a "benefit" modifier line that defines the benefit the coupon issue provides; for example, a 10% discount or 6$ off the order.

Warning in Oracle Order Management: Typically, the coupon is issued for an order, and the actual discount line (the benefit the coupon applies) is applied to a subsequent order when the coupon is redeemed.

However, if you set up a line level qualifier for the discount line with the following settings:

■ Grouping Number = -1

■ Grouping Number = Any of the Coupon Modifier Numbers

then both the discount line and coupon line are applied to the same order.

If you are intentionally including a line level qualifier on the discount line which is of grouping no. not equal to any of the coupon modifier numbers and is not equal to -1, it means that you actually want the discount to be applied independent of coupon redemption.

Modifiers 3-51


The Modifier No (or number) defaults for the modifier line. This number is used to generate a unique number series for the coupon and the coupon number is passed to the calling application. The customer can also use this number to redeem the coupon.

2. When you have completed your entries for the benefit line, enter a new modifier line to define the coupon issue.

A new Modifier No defaults for the coupon issue modifier line.

3. Select a Level.

4. Select Coupon Issue as the Modifier Type.


Note: You can select a modifier line type of Discount or Promotional Goods to define the benefit received when the coupon is redeemed.



5. Enter a Benefit Quantity and Benefit UOM.

6. Enter a Redemption Rate to specify the percentage probability that customers might redeem this coupon.

7. Enter Coupon Conversion Rate to specify the conversion of the Benefit UOM to the primary currency. For example, if one air mile is 0.50 currency units, the coupon conversion rate is 0.50.

8. Enter the Expiration Date which is the last date that the customer can redeem the coupon.

Alternately, if you enter values for the Expiration Start Date, Expiration Period, and Expiration Period Type, the pricing engine automatically calculates the Expiration Date. For example, for the following coupon set up, the pricing engine calculates an expiration date of 20 July:

■ Expiration Period Start Date: 20 April

■ Expiration Period: 3

■ Expiration Period Type: Month

9. Enter the Coupon Modifier Number to link the Coupon Issue modifier line to the benefit modifier line.

10. Save your work.

Note: If you do not enter Expiration Period Start Date, the pricing engine will use the date that the calling application issued the coupon.

Modifiers 3-53


To enter Promotional Goods and Other Item Discount information:You can create a Promotional Goods modifier line to add a new item to an order and provide a price adjustment or benefit for the item when the customer orders one or more specified items on the same order. The item does not need to be originally on the order. Even if the item is on the order, the pricing engine creates a new line for the item.

The modifier setup requires that you specify a quantity but you can use any unit of measure (UOM) set up on your system.

Other Item Discounts: When the customer orders one or more other specified items (the buy items) on the same order, you can create an Other Item Discount modifier line to provide a price adjustment or benefit to another item (the get item) on the order. The Other Item Discount modifier must be applied at the Group of Lines level.

Examples of Promotional Goods modifiersYou can create as many "must buy" items as desired and as many "get" items as required. Here are some sample scenarios of "must buy" and "get" promotional modifiers.

■ Customer must buy A to get B

■ Customer must buy A and B to get C

■ Customer must buy A and B and C to get D

However, you cannot create a combination of "must buy" products or "get" products where the promotional goods modifier must evaluate multiple items. For example, the customer receives 20 units free of the following products or a combination of products A, B, C if the customer buys at least 20 units from the specified products (X or Y) or a combination.

Instead you must specify explicit must buy and get amounts:

For example, the customer must buy 10 of Product X and 10 of Product Y to get 20 free units of Product A.

Note: When you create or duplicate a modifier, you can change the following: Primary buy item, Additional buy items, Get items. However, once the modifier is saved, then you cannot change or delete the additional buy or get items. You can add additional buy and get items.



1. In the Modifiers Summary tab, select the Level.

2. Select the Modifier Type.

3. Select the Phase.

■ For Other Item Discounts, the phase defaults to All Lines Adjustment. If you create a new phase to use for this modifier type, set Phase to All Lines Adjustment.

■ For Promotional Goods (PRG) modifiers: To have the PRG modifier applied in conjunction with an order-level modifier (assuming the order-level modifier has been created), then select All Lines Adjustment as the Pricing Phase for the PRG modifier. This enables both the PRG modifier and the order-level modifier to be applied in conjunction to an order.

However, if Pricing Phase = List Line Adjustment, it will prevent an order level modifier from being applied in conjunction with the PRG modifier. Only the eligible PRG modifier will be applied.

4. Enter a Bucket.

5. Select a Product Attribute, Product Attribute Value, and UOM (unit of measure).

6. Click Define Details to display the Define Modifier Details window.

Note: If you are using Promotional Good (PRG) type of Modifier Line with Multi-Currency, see: Using Promotional Good type of Modifier Line on page 7-12.

Note: Promotional Goods modifiers are not supported at the Order level.

Modifiers 3-55


Figure 3–13 Advanced Pricing - Define Modifier window: Details for Modifier List

7. Do steps 8 to 14 for each buy product.

8. In the Additional Buy Products region, enter the Group Number to specify the AND or OR condition of the buy side of the modifier. To join lines with AND, use the same group number on each line; to join lines with OR, use a different group number on each line

9. Select a Product Attribute, for example, Item, Item Category, or All Items

10. Select a Product Value for the Product Attribute selected in the preceding step.

Note: Use the Additional Buy Products region to specify the buy condition of the modifier along with the original product from the Modifiers Summary tab. The pricing engine considers the product that you define in the Modifier Summary as the primary item and uses it to determine the eligibility of the get condition. It also verifies other buy items.



11. Enter a Pricing Attribute.

12. Enter = or Between in Operator.

13. Enter Value From and Value To.

14. Enter the unit of measure of the item or item category in Buy UOM.

15. In the Get region, complete the following steps to define each get product.

The Get Product Attribute defaults to Item Number.

16. Enter the item number in Get Product Value.

17. Select the UOM (unit of measure).

18. Enter the Get Quantity of the product to offer.

19. Enter the Get UOM (unit of measure) for this product.

20. Select Get Price. The list of values displays all price lists that contain the item.

21. Select an Application Method (Adjustment Method).

22. Enter the Value for the application method.

23. Save your work.

Note: This is a volume pricing attribute; use either item quantity or item amount.

Note: It is recommended that you do not define a Get Line for a Promotional Goods using price list lines with the following setups:

■ Those with dynamic formulas.

■ Those with arithmetic operator of Block Price or Percent price.

Note: Once you save the Promotional Goods or Other Item Discount line, you cannot update the Primary Buy, Additional Buy, or Get Product attributes.

Modifiers 3-57


Note: If you manually delete or change a free good line for an order/quote line on the order, for example, change the number of free good items from 3 to 2 on the Sales Order pad, for subsequent repricing calls, the overridden manual entry is retained.

For example, suppose a customer buys Item A and gets two of Item B free. If you change the number of free goods that the customer gets from one to two on the Sales Order pad, on subsequent repricing, the manually overwritten amount is retained so the customer gets the one free good.



To enter price break header information:1. Select the Modifiers Summary tab.

2. Select the Level for the modifier to be applied: Group of Lines or Line.

3. Select Price Break Header as the Modifier Type.

4. Optionally, enter a Start and End Date range for the modifier line.

5. Select Automatic to have the modifier applied automatically by the pricing engine.

6. Complete the following entries:

■ Pricing Phase

■ Incompatibility Group

■ Bucket

■ Break Type:

Point: The pricing engine charges each unit of volume at the price of the break within which the total falls.

Range: The pricing engine charges each unit of volume at the price of the break within which it falls.

■ Product Attribute and Product Attribute Value

■ UOM

■ Volume Type

7. Select the Price Breaks tab.

Modifiers 3-59


Figure 3–14 Advanced Pricing - Define Modifier window: Price Breaks tab

8. Select an Adjustment Type:

■ Discount

■ Surcharge

9. Select Accumulation Attribute if you are setting up range price breaks that accumulate across orders. This option is available for Range breaks only. See Using Accumulated Range Breaks on page 3-65 for more information.

10. Select the Net Amount box to calculate the selling price based on the bucketed Item Amount volume. To select the Net Amount box, the following must also be selected in the Advanced Pricing - Define Modifiers window:

■ Modifier Type: Price Break Header

■ Automatic box in the Modifiers Summary tab must be selected

■ Volume Type: Item Amount

■ Level is Line or Group of Lines

■ Price break cannot be overrideable



For more information, see: Using Net Amount with Price Breaks on page 3-63.

11. To use the price break to calculate an accrual, select Accrue.

12. If using accruals, enter an Expiration Date to specify when the accrued transactions expire.

13. Enter Expiration Start Date, Expiration Period and Period Type. The pricing engine calculates expiration date. Expiration period begins when the item begins to accrue.

The Rebate Transaction Type defaults to Credit Memo and is reserved for future use.


Note: The Accrual box can only be used if Discount is selected as the Adjustment Type.

Modifiers 3-61


Figure 3–15 Define Modifier Details window

The Break Line Type, Break Type, and Net Amount values default from the modifier line.

15. Enter the Value From/To. To use a formula to calculate a discount, select the Formula.

16. Select an Application Method (Adjustment Method).

17. Enter a Value for the Application Method. The Value is related to the Application Method selected. For example, if the Application Method is Percent, and 10 is the Value, the discount (if applied as a discount) is 10-percent.

18. If applicable, enter the Benefit Quantity and Benefit UOM (unit of measure).

19. For non-monetary accruals, enter the Accrual Conversion Rate to specify the conversion of Benefit UOM to the modifier primary currency. For example, if 1 air mile is 0.50 currency units, the Accrual Conversion Rate is 0.5.

20. Save your work.



Using Net Amount with Price Breaks The Net Amount feature calculates the selling price based on the bucketed item amount for price break modifiers. To use the net amount feature, select the Net Amount box for a modifier line.

The following conditions are required for the modifier line before you can select Net Amount:

■ Automatic check box for the modifier line must be selected.

■ Modifier Type for the modifier line must be Price Break Header and related price breaks must be set up

■ Volume Type for the modifier line is Amount

■ Can be Line and Group of Line level

■ Cannot be Overrideable

Example of Net Amount CalculationsThe following table displays a modifier setup that will calculate Net Amount for an order using a break range type of Point):

Suppose this modifier were applied to the following order:

If the modifier were applied to this order, the Net Amount selling price would be calculated as follows:

Table 3–14 Example: Modifier Setup for Net Amount Price Breaks

Modifier Setup Bucket Discount Break Ranges

Line 1: Discount A 1 40% n/a

Line 2: Discount B 1 30% n/a

Line 3: Price Break Header (PBH) C

2 5% $0-1000

- - 7% $1001-2000

- - 10% $2001-9999

Table 3–15 Sample Order

Order Item List price Order quantity

AS54888 $2000 each (per unit) 2

Modifiers 3-63


a. First Discount A (40%) is applied resulting in the unit adjusted amount of $800.

b. Then Discount B (30%) is applied resulting in a unit adjusted amount of $600.

c. The unit selling price at the end of Bucket 1 is $2000-($800+$600) = $600. This becomes the unit selling price for the next bucket.

d. For PBH C to apply: the Net Amount is ($2000*2)-(800*2)-(600*2) = $1200. This qualifies for the second break of C, which is 7%.

e. PBH C applied: the unit adjustment amount is 7%*600 = $42. This will be applied to the unit selling price of the previous bucket.

So final unit selling price will be $600-42 = $558.



Using Accumulated Range BreaksSetting up modifiers with accumulated range breaks provides additional flexibility to existing price break processing. Using accumulated range breaks, you can set up range price breaks that accumulate within and across orders based on some attribute value (for example, quantity) that is accumulated from previous orders or order lines.

The pricing engine uses the accumulation value as the starting point of the break calculation. Advanced Pricing does not store these accumulated values. The value is passed by the calling application in the engine request or the engine dynamically sources the attribute from a customer API.

Values can be accumulated across different orders or within an order. For example, suppose a customer places the following two orders:

■ Order A: Orders 2 of Item "Shampoo"

■ Order B: Orders 3 of Item "Shampoo"

Under regular range price break processing, each order would be evaluated independently of each other. However, with accumulated range price breaks, the accumulated quantity value from Order A is the starting point for evaluating the range break for Order B.

The value of the accumulation attribute is sourced from the pricing request when evaluating accumulated range price breaks for modifiers. Customers are responsible for accumulating and maintaining the values from prior transactions in any manner of their choice. This value is the starting point for range price breaks in subsequent transactions that are passed to the pricing engine.

Setting the Profile Option and Volume AttributeTo begin using the accumulation attribute feature, the profile QP: Accumulation Attributes Enabled must be set to Yes. Typically, this is set by the System Administrator. The profile option also enables the Accumulation Attribute field in the Price Breaks tab on the Define Modifier window.

Do the following steps to set up this feature (no seeded attributes are provided for this feature).

1. You can create two types of accumulation volume attributes in Attribute Management to use this feature.

■ Use the mapping method of Attribute Mapping to source the accumulation value from the pricing request.

Modifiers 3-65


■ Use the new attribute mapping method Runtime_Sourced to enable the pricing engine to source the attribute and accumulation values from a custom API. A new package has been created, QP_RUNTIME_SOURCE, containing a specification for the custom API. Customers are required to write a corresponding body to this package. See the Advanced Pricing Implementation Manual for more information.

2. Set profile QP: Accumulation Attributes Enabled to Yes at Site and/or Application level.

3. Define a modifier line with the following setup:

■ Line type: Price Break Header

■ Break type: RANGE

■ Select Accumulation Attribute from the list of values.

The profile enables the Accumulation Attribute field in modifier lines. Price break details are defined in Define Details.

Using Accumulated Range Break across OrdersWhen using accumulated range breaks, the accumulation total must be passed as the starting point for each pricing request. For example, suppose the following discount has been set up to give a discount across orders.

If a customer then places three separate orders for 5 items each, then the adjustment amount is calculated as follows:

Table 3–16 Discount range breaks and the adjustment amount for each break

Volume Attribute From Volume Attribute To Adjustment Amount

1 5 5%

6 10 10%

11 15 15%

Table 3–17 Adjustment amount applied across orders

Order No. QuantityAccumulated Value Adjustment Amount

1 5 0 5%

2 5 5 10%



The adjustment calculations for the preceding example are as follows:

For the first order, the accumulated value is 0. A discount of 5% is given because the order quantity of 5 satisfies the first quantity range break of 1-5.

For the second order, the accumulated value passed to the pricing engine is 5. (5 from Order 1). A discount of 10% is given, because the break is evaluated starting with quantity 6 and satisfies the range 6-10.

Finally, for the third order, the accumulated value passed to the pricing engine is 10. A discount of 15% is given, because the break is evaluated starting with quantity11 and satisfies the range 11-15.

3 5 10 15%

Table 3–17 Adjustment amount applied across orders

Order No. QuantityAccumulated Value Adjustment Amount

Modifiers 3-67


Using Accumulated Range Breaks within an OrderAccumulated range price breaks can be used to evaluate the volume of order lines within the same order.

For example, if a customer orders 3 lines of the same item that is eligible for a discount, then each line is priced based on the accumulated value of the previous qualifying line for the same product.

Suppose a price break modifier is set up with the following volume ranges and adjustment amount:

When this discount is applied, the accumulated values and adjustment amounts are calculated as follows:

The accumulation value and discounts are evaluated as follows:

■ The first line is given a discount of 5% because an accumulation value of 0 is passed and the order quantity of 3 satisfies the range 1-5.

■ Line 4.2 is evaluated with starting at the accumulated value of 3. Two of the ordered quantity 6 fall within the range of 1-5 and 4 fall within the range 6-10 resulting in an 8.33% adjustment.

■ Line 4.3 is evaluated with a starting point of (3+6) = 9 passed by the calling application and an order quantity of 4. One of quantity 4 falls within range 6-10 and 3 fall within the range of 11-15 resulting in a 13.75% adjustment.

Table 3–18 Price Break range breaks and the adjustment amount for each break

Volume Attribute From Volume Attribute To Adjustment Amount (Percent)

1 5 5%

6 10 10%

11 15 15%

Table 3–19 Accumulated values within an order

Line No. Quantity Accumulated Value Adjustment Amount

4.1 3 0 5%

4.2 6 3 8.33%

4.3 4 9 13.75%



Attaching Pricing Attributes to Modifier LinesUse this process to attach attributes to the items and item categories that you define in modifier lines. When the pricing engine determines eligibility for a modifier, it validates the pricing attributes along with the item number or item category.

To attach pricing attributes to modifier lines:1. Navigate to the Advanced Pricing - Define Modifier window.

2. Select the Modifiers Summary tab and select a modifier.

3. Click Pricing Attribute to display the More Pricing Attributes window.

Figure 3–16 More Pricing Attributes window

4. Enter a Pricing Context.


6. Enter a operator value such as = or BETWEEN.

Note: Pricing attributes apply only to the primary items that you define in the Modifiers Summary tab. They do not apply to items that you define for additional buy items and get items.

Modifiers 3-69


7. Enter Value From and Value To.

8. Click OK and save your work.



Excluding Items from a ModifierUse this process to exclude items from a modifier. When the pricing engine evaluates order lines, if an order line contains an item or item category that is defined as an excluded item or item category, then these lines are considered ineligible and will not be evaluated for the modifier.

The following example shows the difference between a modifier defined without an Excluded Item and one defined with an Excluded Item:

Modifier without Excluded ItemThe following example shows the effects of applying a modifier when no excluded item is defined for the modifier. The modifier, Modifier_Shampoo1, is set up with the following criteria:

■ Level: Group of Lines

■ Item Category: Shampoo

■ Quantity: > 100 quantity

To be eligible for the modifier, the item category of the ordered item(s) must be Shampoo and the total item quantity of the eligible order lines must be greater than 100.

Suppose a customer then places the following order for two "shampoo" items and a "conditioner" item:

The modifier will be applied because the item total for the eligible group of lines is 120 (100 + 20).

Modifier with Excluded ItemThe following modifier, Modifier_Shampoo2, has been set up, and the item Shampoo1 is defined as the Excluded Item:

Table 3–20 Shampoo Modifier Example

Order Line ID Qty Item Category

1 100 Shampoo1 Shampoo

2 20 Shampoo2 Shampoo

3 30 Conditioner1 Conditioner

Modifiers 3-71


■ Level: Group of Lines, Item Category: Shampoo

■ Quantity: > 100 quantity

■ Excluded Item: Shampoo1

Suppose a customer then places the following order for two "shampoo" items and a "conditioner" item as in the previous order:

To be eligible for this modifier, the item category of the ordered items must be Shampoo and the item quantity of the eligible order lines must be greater than 100. However, the item Shampoo1, which is defined as an excluded item for this modifier, will not be evaluated. The group of lines from the order are evaluated against the modifier requirements as follows:

■ Order Line 1: Rejected because it contains the Excluded (Item Shampoo1).

■ Order Line 2: Accepted because the Category is Shampoo.

■ Order Line 3: Rejected because Category is not Shampoo.

Then, the modifier evaluates the total quantity of the eligible order lines. If the total item quantity is greater than 100, then the modifier is applied. Since the quantity of the eligible lines is 20 (Order Line 2) the modifier will not be applied.

To add exclude items to a modifier:1. Navigate to the Advanced Pricing - Define Modifier window (Summary tab)

and select a modifier. You cannot add Excluded items if the modifier level is Order.

2. Click Exclude to display the Exclude Items window.

Table 3–21 Shampoo Modifier Example (Excluded Item)

Order Line ID Item

Quantity (Qty) Category

1 Shampoo1 100 Shampoo

2 Shampoo2 20 Shampoo

3 Conditioner1 30 Conditioner



Figure 3–17 Exclude Items window

3. Enter a Product Attribute and Product Value to be excluded.

4. Select Exclude and click OK.

5. Save your work.

Modifiers 3-73


Creating Line Level QualifiersUse this process to create qualifiers for modifiers at the line level. The pricing engine evaluates qualifiers to determine eligibility for line level modifiers. If an order is not eligible for a list level modifier, the order lines may be eligible for list line level modifiers if the order lines have qualifiers for which the order is eligible.

When creating qualifiers, consider secondary price lists that may need to be included to be considered for the modifier. For example, if a customer qualifies for a discount from Price List A but the effectivity of the item drives the engine to the secondary price list (Price List B), the customer does not receive the discount unless the qualifier also includes Price List B.

To create line level qualifiers:1. Navigate to the Advanced Pricing - Define Modifier window.

2. Choose the Modifiers Summary tab and select a modifier line.

3. Click Line Qualifiers.


4. If this modifier list has no qualifiers, the Qualifier Groups window appears. Do one of the following:



■ To add qualifiers from qualifier groups:

a. Select the qualifier group(s).

b. Select a grouping option: Retain Grouping Numbers Across Qualifier Groups or Generate Unique Grouping Numbers Across Qualifier Groups. For more information on qualifier groups, see: Using Qualifier Grouping Numbers across Qualifier Groups on page 2-25.

c. Click OK to display the Qualifier - Line Level Qualifiers window. The qualifier and qualifier conditions from the selected qualifier group(s) display in this window.

The Group name (from the related Qualifier Group) displays in the Group column. Verify that the Grouping Number that defaults from the qualifier group creates the AND and OR conditions that you want.

■ To add qualifiers and skip the Qualifier Groups window, click OK and go to step 5.

5. In the Qualifier - Line Level Qualifiers window, you can add, change, and delete qualifiers, change the grouping numbers, and change the dates.

Figure 3–19 Qualifier - Line Level Qualifiers

6. If you are entering a new qualifier, enter a Grouping Number. Qualifiers with the same grouping number generate an AND condition while qualifiers with

Modifiers 3-75


different grouping numbers generate an OR condition. For more information on grouping numbers, see: Using Qualifier Grouping Numbers on page 2-21.

7. Enter the Qualifier Context.


View the Precedence numbers that default from the qualifier definition. The pricing engine uses precedence for resolving incompatibility. If multiple modifiers are eligible within the same phase and incompatibility level, the modifier with the lowest precedence is applied.

9. Enter the Operator, Value From, and Value To (if applicable).

The Value From Meaning field provides additional details about the selected qualifier. For example, if the qualifier context is CUSTOMER and the attribute is Ship To, the Value From field displays the customer name and the Value From Meaning field displays the site-use location for the customer. If the context/attribute combination has no additional details, Value From and Value From Meaning are identical.

10. Click Copy Group to add qualifiers from other qualifier groups.

11. Click OK.

12. Save your work.

Note: After you save a qualifier with Qualifier Context of Modifier List and Qualifier Attribute of Coupon Number, you cannot modify or delete it. Since the pricing engine creates coupons (and a qualifier for each coupon) these coupon qualifiers are not subject to manual changes and deletions.



Copying a Modifier List

Copying a Modifier ListYou can create a new modifier by copying an existing one. The following modifier information is copied from the original modifier to the new one:

■ Modifier lines

■ Pricing attributes: Price breaks, other item discounts, coupons, promotional goods, setups and lines.

■ Qualifiers

When you copy a modifier, you can enter a unique number and name for the new modifier and either update or keep the effective dates for the modifier list and lines. The combination of modifier name, number, and version must be unique across modifier lists. Although it is possible to copy an existing modifier name, you must enter a unique number for the new modifier.

Promotional limits attached to the original modifier are not copied. The promotional limits must be created again for the new modifier.

Note: If you do not see the modifier list that you are trying to copy, it is possible that you may not have access privileges to it. You must have at least View Only security privilege to copy a modifier list. Consult your Pricing Administrator.

Modifiers 3-77


To copy a modifier list:1. Navigate to the Copy Modifiers window.

Figure 3–20 Copy Modifiers window

In the Copy From region:

2. In the Number field, select the modifier list to be copied.

The currency and name displays for the selected modifier.

3. Select Retain Effective Dates to copy the effective dates from the original to the new modifier.

In the Copy To region:

4. In the Number field, enter a name for the new modifier.

5. Optionally, enter a description in the Name field and the effective dates for the modifier.



6. Click Submit to copy the modifier. A Request ID number displays so you can track your copy request. Select View > Requests and search by your Request ID number to view your request status.

In Advanced Pricing, the copied modifier list is always inactive so you must select the Active box to make the modifier active.

7. Search for the new modifier in the Find Modifier Lists window.

8. Select the modifier, then select Active to activate the modifier.

Note: If you enabled the Retain Effective Dates check box, then the effective dates from the original modifier are copied from the original to the new modifier. If you do not select this option, you can add effective dates to the new modifier once it is created.

Modifiers 3-79

Copying a Modifier Line

Copying a Modifier LineYou can quickly copy an existing modifier line to a new line record in the Advanced Pricing - Define Modifier window. The following information is copied to the new modifier line:

■ All the contents of the modifier summary and all other tabs.

■ All the Exclude Products attached to this modifier line.

■ All the Pricing Attributes attached to this modifier line.

■ All the Line Qualifiers attached to this modifier line.

■ All the Line Details (additional and get products, price break lines) attached to this modifier line.

All fields that are copied can be updated except for the Level and Modifier type fields. The Product Attribute and Product Value fields can be updated even after clicking Define Details. However, once the new modifier line is saved, these fields cannot be updated.

To copy a modifier line:1. Display the modifier in the Advanced Pricing - Define Modifier window.

2. Select the modifier line to be copied, and click the New icon in the toolbar to create a new blank line beneath the original line.

3. Choose Edit > Duplicate > Record Above to duplicate the original line. Alternately, select the SHIFT + F6 keys.

4. Once the line is duplicated, you can modify or save it.

5. Save your work.

Note: Duplicate Modifiers

"Basic" Pricing provides a profile option, QP: Allow Duplicate Modifiers, that can be set to "Yes" or "No" to control if duplicate modifiers are permitted. This functionality is for Basic Pricing only. In Advanced Pricing, this profile option does is non-functional and therefore, does not restrict your ability to copy a modifier line. See the Oracle Advanced Pricing Implementation Manual, Profiles Option chapter for more information about this profile option.


Using Modifiers in the HTML User Interface

Using Modifiers in the HTML User InterfaceOracle 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 the HTML UI to complete many of the pricing tasks that you previously completed using the Oracle Forms-based UI such as:

■ Searching for modifier lists and modifier lines.

■ Creating modifier lists for the following modifier types only: Deal, Discount List, Promotion, or Surcharge List.

■ Updating a modifier.

■ Creating the following modifier line types:

■ Discount

■ Surcharge

■ Price Break Header


Oracle Advanced Pricing still provides the Oracle Forms-based interface for features and tasks currently unavailable in the HTML format such as creating qualifier groups.


Note: You must use Oracle Forms-based user interface to create Freight and Special charge List.

Note: You must use the Oracle Forms-based UI to create all other modifier line types.

Modifiers 3-81


Warning: Pricing security can affect the View and Maintain features associated with the Update and Details icons in the HTML user interface. See Pricing Security (HTML Interface) on page 1-4 for more information.



Creating a Modifier List (HTML Interface)A Modifier List contains general information that applies to all modifier lines created for the list. You can use modifier lists and lines to adjust net prices either up or down through modifier actions such as discounting, adding surcharges, charging for shipping, or adjusting price based on promotional pricing.

In the HTML user interface, you can create the following modifier list types.

■ Deal

■ Discount List

■ Promotion

■ Surcharge list

You can create modifier lines for the modifier list to define the actual price adjustment details such as the item(s) to be discounted and the amount and type of discount to be applied.

Creating a modifier list and modifier lines involves the following steps:

a. Entering general modifier list information.

b. Creating qualifiers that define eligibility rules for the modifier list. For example, the customer must be a Gold class customer to receive the adjustments and benefit for the modifier list.

c. Reviewing and then saving the modifier list.

d. Adding modifier lines to the modifier list to define the type and amount of price adjustment or benefit offered.

Note: You must use Oracle Forms-based user interface to create Freight and Special charge List.


Modifiers 3-83


Modifier Lists and Line TypesAt the modifier list level, you define criteria that is common to the line level modifiers. For each list type, you can create modifier lines that define the price adjustment or benefit to be applied to the pricing requests. See Creating Modifier Lines (HTML Interface) on page 3-92 to view which modifier line types are supported for each modifier list.

Other Concepts

CurrencyThe pricing engine applies modifiers to sales orders of the same currency. If a specific currency is selected such as USD (US dollars), then the modifier list can only be used with a price list with a matching base currency or "to currency" (for a multi-currency price list). See Considerations for Modifiers Using Multi-Currency Conversion List as a Qualifier on page 7-11.

Optional CurrencySelect Optional Currency if currency is not used as a criteria to select modifiers for the order (this leaves the Currency field in the modifier list blank). When Optional Currency is selected, the modifier can be used with any price list regardless of its currency. Such modifiers could be used with both single price lists that are set up in a single currency, or with multi-currency enabled price lists.

Selecting optional currency can provide the following advantages to your business:

■ Enables your business to reduce the number of modifiers required to support sales orders in all currencies for which you do business. For example, Optional Currency could be selected for modifiers that are set up with the application method of Percent, since these modifiers could be applied to any sales order regardless of the currency (since no currency conversion is required).

■ Reduces the cost of setup and maintenance of modifiers.

■ Reduces cost of data storage.

Note: Multi-currency enabled price lists are set up in a base currency and associated with a currency conversion list containing the base currency and other currencies with conversion criteria.



Warning: Although Optional Currency is applicable to all modifier types and application methods, it may not be appropriate for all types of modifiers since NO currency conversion is done with such modifiers. You must determine if it suits your business requirements and in what situations.

Modifiers 3-85


Pricing For Global UseThe Pricing For Global Use box identifies if this modifier list and lines are available to all operating units or a specific operating unit.

■ If selected, then the modifier list and lines are available for all operating units.

■ If cleared, then the modifier list and lines are specific to the operating unit of the person that created the modifier. The pricing engine will only consider this modifier if the order has the same operating unit.

The Pricing For Global Use box displays only if the profile QP: Security Control is turned on. Once the profile is turned on, all newly created modifier lists will have the global box selected as a default. You can clear the box only if you are assigned Maintain security access privilege.

Customer Must Ask For List If the Customer Must Ask For List box is selected, the customer must specifically request that the modifier benefit be applied (for example, by providing a special discount number), otherwise it will not be applied. This box is only available for modifier list types of Deal and Promotion.

Note: If the pricing engine selects multiple modifiers to apply to an order line, the modifiers for a Customer Must Ask For List receive a higher preference than other modifiers.



To create a modifier list:1. Navigate to the Modifier Lists page.

Figure 3–21 Modifier Lists page

2. In the Create List field, select the type of modifier to be created.

■ Deal

■ Discount List

■ Promotion

■ Surcharge list

3. Click Go to display the Create [Modifier Type] General Information page.

Note: The page name and details may vary slightly depending on the modifier list type being created.

Modifiers 3-87


Figure 3–22 Example of a Create Deal List: General Information page

The Type field displays the modifier list type you are creating.

The Pricing Transaction Entity and Source System values default from the profiles QP: Pricing Transaction Entity and QP: Source System Code.

4. Enter a Name for the modifier list. You can use an alphabetic or alpha-numeric combination to identify the modifier; for example, "Promo Modifier" or "Mod1234."

5. Enter a modifier list Number. This can be an alpha-numeric combination.

6. Enter a Version Number.

Note: The modifier Name should be unique across PTEs (Pricing Transaction Entities) otherwise an error occurs. For example, if a modifier named "Corporate" is created in the Order Management PTE, an error message displays if you create a "Corporate" modifier in the Purchasing PTE.



7. Enter a Description for the modifier list.

8. Choose one of the following:

■ Select a Currency. If a currency is selected such as US dollars (USD), the sales order must match the modifier currency to determine pricing for the order.

■ Optionally, select Optional Currency to leave the Currency field in the modifier list blank. This option can be selected for modifiers where currency is not used as a criteria to select modifiers for the order.

9. Enter a Start/End Date.

10. Enter an Order Date From/To range.

11. Enter a Requested Shipped Date From/To range.

12. The Pricing For Global Use box identifies if this modifier list and lines are available to all operating units or a specific operating unit:

■ If selected, then the modifier list and lines are available for all operating units.

■ If cleared, then the modifier list and lines are specific to the operating unit of the person that created the modifier. The pricing engine will only consider this modifier if the order has the same operating unit.

If the Customer Must Ask For List box (available for modifier list type of Deal and Promotion) is selected, the customer must specifically request that the modifier benefit be applied, for example, by providing a special discount number, otherwise it will not be applied.

13. In the Parent Promotions Detail region, enter the Parent Number and Parent Version to specify the promotion to which the deal is associated.

Note: If the pricing engine selects multiple modifiers to apply to an order line, the modifiers for a Customer Must Ask For List receive a higher preference than other modifiers.

Modifiers 3-89


14. Click Next to display the Qualifiers page where you can define eligibility rules for the modifier list. See Creating Qualifiers (HTML Interface) on page 2-6.

15. Complete your entries and click Next to display the Create [Modifier List Type] Review page.

Figure 3–23 Create [Modifier Type] Review page

16. Review your entries. If changes are required, click the Back button to update the page.

Note: The Parent Promotion region displays if the modifier list Type is Deal. Modifier list types of Promotion and Deal have a parent-child relationship for reporting purposes. A Deal modifier list must be associated with a parent Promotion by providing the promotion name and version. Since this association is for reporting purposes, information that you define on the promotion is independent of and does not affect the information on the Deal modifier. The Promotion must already exist before you can select it.



17. Click Finish to save your work. A Confirmation page confirms that the modifier list has been created, and asks if you want to add modifier lines.

See:Creating Modifier Lines (HTML Interface) on page 3-92

Modifiers 3-91


Creating Modifier Lines (HTML Interface)Once you have created a modifier list, you can add modifier lines that define the type of price adjustments and benefits that the pricing engine applies to pricing requests.

You can add modifier lines:

■ Directly after you create the modifier list from the Update {Modifier List Type}: Modifier Lines page.

■ Whenever you want to add additional lines.

The following tables shows the type of modifier line you can create for a modifier list:

Table 3–22 Modifier List Types and Line Types

For the following Modifier List Type.. You can create these Modifier Line Types

Deal Discount, Price Break, Promotional Goods, or Surcharge

Discount List Discount, Price Break, or Surcharge

Promotion List Discount, Price Break, Promotional Goods, or Surcharge

Surcharge List Price Break, Surcharge




To create modifier lines:1. Navigate to the Create Line page.

Figure 3–24 Create Line page

2. Select from the following modifier line types. The available line types depend on the modifier list type selected.

■ Discount: Creates a negative price adjustment. See Creating a Discount Modifier Line (HTML Interface) on page 3-99 for more information.

■ Promotional Goods: Adds a new item to the order line with a price adjustment or benefit when the customer orders a particular item on the same order. See Creating a Promotional Goods Modifier Line (HTML Interface) on page 3-111.

■ Price Break: Applies a variable discount or surcharge price adjustment to a pricing request based meeting the condition of a break type. You can use both point and range type breaks. See Creating a Price Break Modifier Line (HTML Interface) on page 3-104.

Modifiers 3-93


■ Surcharge: Creates a positive price adjustment. For example, a 10 percent handling charge is applied to a customer order. See Creating a Surcharge Modifier Line (HTML Interface) on page 3-116

The modifier Line Number defaults and can be updated. Each modifier line number must be unique within the modifier list (the line number cannot be duplicated).

3. Enter the Start and End Date range for this modifier. If you do not end an End Date then the modifier does not expire.

4. Click Continue to display the Controls page.



Defining Controls for Modifier Lines (HTML Interface)In the Controls page, you define pricing controls that govern how the modifier line should be applied.

To define controls for modifier lines: 1. Navigate to the Controls page.

Figure 3–25 Controls page

2. Complete your entries as described in this section, then click Next to go to the next step:

Modifier LevelSelect a Modifier Level to determine at which level--line, group of lines, or order--the modifier line should be applied:

Modifiers 3-95


■ Line: Applies only to a specific order line.

■ Group of Lines: Applies to groups of lines in the order.

■ Order: Applies to an entire order. If Order is selected, then all products on the order will receive the benefit or price adjustment.

For example, a volume-based discount modifier applied at the line level will consider only volume on the qualifying line. A volume-based discount modifier applied at the group of lines level will process the volume across all qualifying lines in the product hierarchy.

Pricing PhaseSelect a pricing phase that determines when the pricing engine applies a modifier. For example, modifiers in the List Line Adjustment phase are applied only after leaving the line. Modifiers in the All Lines Adjustment phase are applied only after saving the line. Select the Pricing Phase when you want the modifier line applied.

See the Oracle Advanced Pricing Implementation Manual for more information on pricing phases.

BucketSelect a pricing bucket. Pricing buckets control how the calculation of discounts and other benefits is sequenced using cascading price adjustments. This grouping helps to determine the net selling price. Grouping discounts and benefits into buckets helps determine the net selling price across all pricing phases.

When the pricing engine calculates price adjustments, it:

■ Calculates percent type modifiers using the previous bucket’s subtotal

■ Sums all bucket modifier values to create a bucket subtotal

Different selling prices can result depending on how you group the discounts and benefits modifiers into buckets. When the pricing engine calculates price adjustments, it:

■ Calculates percent type modifiers using the previous bucket’s subtotal

■ Sums all bucket modifier values to create a bucket subtotal

If the Bucket field is left blank, the modifier line is assigned to a "Null" bucket. Also, Order level modifiers must be in the Null bucket.



Modifiers assigned to a Null bucket are applied last and always adjust from the list price. The pricing engine used the following steps to evaluate the Null buckets and calculate the selling price:

1. Calculates percent discounts using the list price.

2. Sums all bucket modifier values to create a bucket subtotal.

3. Applies the subtotal after the last numbered bucket.

Example: Suppose that the following buckets are set up, each with a different adjustment:

■ Null bucket: a 50% discount is assigned to the Null bucket.

■ Bucket 1: a 10% discount is assigned.

■ Bucket 2: a 10% surcharge is assigned.

The buckets are used to calculate the price for an SP ATO Model with a list price of $55. The following table shows how the final price is calculated:

IncompatibilitySelect an incompatibility group for the modifier line:

■ Exclusive: If one of the modifiers is Exclusive, then only the Exclusive modifier is applied.

■ Group 1 incompatibility



Incompatibility occurs when the pricing engine finds more than one modifier to return but only one can be applied. The engine resolves this incompatibility using either precedence or best price.

Table 3–23 Example of Bucket Calculations using Null Bucket: List Price=$55

Bucket Modifier Adjustment Calculated Price Final Price

Bucket 1 10% discount 55 - (10%*55) $49.50

Bucket 2 10% surcharge 49.5 + (10%*49.5) $54.45

Null bucket 50% discount. Note: The modifiers are applied last and taken out of the list price.

54.45 - (50%*55) $26.95

Modifiers 3-97


You can make modifiers incompatible with each other by placing them in the same incompatibility group level. When this is done, the pricing engine applies only one modifier per phase to the order line or order.

Only one modifier within the same incompatibility group will be applied for a phase. See the Oracle Advanced Pricing Implementation Manual for more information on incompatibility resolution, precedence, and best price.

Automatically Apply Select Automatically Apply to have the modifier applied automatically by the pricing engine. Certain modifiers must be applied automatically and in these cases, you cannot change the value.

Customer Must Ask For ListOn the modifier line, this field is read-only, based on the value selected for the Modifier List. This field will only be visible when the list type is Promotion or Deal.

OverrideSelect Override to enable the modifier adjusted price to be manually overridden. if not selected then the modifier adjusted price cannot be overridden. The Override box displays only for those types of modifier that supports override.



Creating a Discount Modifier Line (HTML Interface)You can create a discount modifier line to create a negative price adjustment. For example, to give a 10 percent discount.

To create a discount modifier line:1. Navigate to the Create Line page.

Figure 3–26 Create Line page: Discount Modifier

2. Select Discount as the Modifier Type.


3. Select a date range for the Start/End Dates.

4. Click Continue to display the Create Discount Line: Controls page.

Modifiers 3-99


In this page, you can define controls for the modifier line. See Defining Controls for Modifier Lines (HTML Interface) on page 3-95 for more information on setting up and using controls.

5. After you have set up the controls, click Next to display the Create Discount Line: Product and Benefit page.

Figure 3–27 Create Discount Line: Product and Benefit page

6. Select a Product Level. The available values depend on the Modifier Level selected from the Controls page:

■ Order level selected: Then all products on the order will receive the discount.

■ Line level selected: Then the Product Level field defaults to null.

■ Group of Lines selected: Then the Product Level defaults to Item Number.



7. Select a Product that is eligible for the discount. Click the Search icon to search for available products. The Product Description defaults based on the product selected.

8. Select a unit of measure (UOM):

■ If the Modifier Level is Line, the UOM field is required only if the volume type is Item Quantity.

■ If the Modifier Level is Group of Lines, the UOM is required except when the volume type is Item Amount.

The Precedence value defaults based on the product level selected. You can overtype this value.

9. Select a Volume Method.

a. For the selected Volume Method, enter the Value From/To. For example, if you selected "Is Between," then you can enter a range in the Value From and Value To fields.

b. Select a Based On value.

10. In the Pricing Attributes region, select an Attribute to further define how you want to price the product such as by color or size.

The Context value defaults and is display only.

a. Select an Operator such as Is, Is Not, or Between.

b. Enter a Value From/To. For example, if you selected "Between," then you can enter a range in Value From and Value To fields.

c. Optionally, click Add Another Row to add additional pricing attributes or click Remove to remove a pricing attribute.

Note: Alternately, you can leave the Product Level field blank to create a "blind" discount that is not product-specific. If the Product Level field is left blank, then the Pricing Attributes, Volume Method, and Excluded regions do not display.

Note: If the Volume Method field is left blank, the Value From/To and Based On fields do not display.

Modifiers 3-101


11. In the Excluded Products region, you can exclude certain products so that the pricing adjustments from the modifier line will not be applied to those products.

For example, suppose you set up a Discount modifier line for the Item Category of "designer shoes;" however, some brands of designer shoes should be "excluded" from the price adjustment. Therefore, in the Excluded Products region, you would select the brands of designer shoes to be excluded from the price adjustment.

a. Select the Product Level and Product for the excluded item. This product will be excluded from the Item Category or All Items selected in the Product level field.

b. Optionally, click Add Another Row to enter additional Excluded Products or click Remove to remove a selected product.

12. In the Benefit region, select an Application Method (Adjustment Method).

a. Enter the Value for the selected Adjustment Method. For example, if you selected Percent as the adjustment method, enter 10 as the Value to give a 10% adjustment.

b. Optionally, select a Formula if you are using a formula to calculate the benefit.

13. Click Next to display the Qualifiers page where you can define eligibility rules for the modifier line.

Complete your entries, and click Next to proceed to the review page, or click Finish to skip the review page and save the line.

A Confirmation message confirms if the modifier line is successfully created.

Note: The Excluded Products region does not display if Item Number is selected as the Product Level or if the Product Level field is left blank.

Note: Both the Value and Formula fields are not required, but at least one of these fields must be entered.



See:Creating Qualifiers (HTML Interface) on page 2-6

Modifiers 3-103


Creating a Price Break Modifier Line (HTML Interface)A Price Break Modifier applies a variable discount or surcharge price adjustment to a pricing request based on the conditions of the break type. You can use both point and range type breaks.

Using Point and Range Price BreaksYou can use either Point price breaks or Range price breaks to apply a variable discount or surcharge price adjustment to a pricing request:

■ Point: The pricing engine charges each unit of volume at the price of the break within which the total falls.

■ Range: The pricing engine charges each unit of volume at the price of the break within which it falls.

The following example table provides an example of a price break sequence:

Suppose a customer is eligible for the preceding price break, and places an order for a quantity of 150 of Item A. The pricing engine calculates the discount differently depending on the type of price break selected:

■ Point: If the total quantity of Item A is 150, the discount is against 150 at 10%.

■ Range: If the total quantity of Item A is 150, the discount is against 100 at 5% and 50 at 10%.

Table 3–24 Price Break Sequence

Product Attribute Value From Value To Value (%)

Item A 1 100 5

Item A 101 200 10

Item A 250 <all 9’s> 15



To create a price break modifier:1. Navigate to the Create Line page.

Figure 3–28 Create Line page: Price Break

2. Select Price Break as the Modifier Type.


3. Select a Start and End Date range when the modifier line is effective. You should specify a range that coincides with the period of time that the benefit is offered. If no End Date is entered, then the modifier line does not expire.

4. Click Continue to display the Create Price Break Line: Controls page.


Modifiers 3-105


5. After you have set up the controls, click Next to display the Create Price Break Line: Products page.

Figure 3–29 Create Price Break Line: Products page

In this page, enter information about the product and product volume that the customer must buy to get the benefit.

6. Select the Product Level.

7. Select a Product that is eligible for the price break. Click the Search icon to search for available products.

Note: If All Items is selected for Product Level, then the Product field defaults to "All" meaning all products.



The Product Description defaults based on the product selected.

8. Enter a UOM (unit of measure).


9. In the Pricing Attributes region, select a pricing Attribute(s) that further define how you want to price the product such as by color or size.

a. Select an Attribute.


b. Select an Operator such as Is, Is Not, or Between.

c. Enter a Value From/To. The fields that display depend on the Volume Method selected in the preceding steps. For example, if you selected Is Between, then you can enter a range in Value From and Value To.

d. Optionally, click Add Another Row to add additional pricing attributes or click Remove to remove a pricing attribute.


For example, suppose you set up a Discount modifier line for the Item Category of "designer shoes;" however, some brands of designer shoes should be "excluded" from the price adjustment.

Therefore, in the Excluded Products region, you would select the brands of designer shoes to be excluded from the price adjustment.

a. Select the Product Level and Product for the excluded item. This product will be excluded from the Item Category or All Items selected in the Product Level field.



Modifiers 3-107


11. In the Price Break Benefits region, define the price break benefits for the modifier line:

a. Select an Adjustment Type such as Discount or Surcharge.

b. Select a "Volume Based on" value to define how the "buy" volume is evaluated before the benefit is given:

■ Item Quantity: Creates a price break based on the number of items that the customer orders.

■ Item Amount: This could be a monetary value. When selected, the Net Amount box also displays. Select Net Amount to calculate the selling price based on the bucketed Item Amount volume. For more information, see: Using Net Amount with Price Breaks on page 3-63.

■ Accumulate Line Quantity: Creates an accumulated range price break that accumulates across orders. If Accumulate Line Quantity is selected, then the Accumulation Attribute field displays. Select an Accumulation Attribute that defines the value to be accumulated. This option can only be selected for Range price breaks. See Using Accumulated Range Breaks on page 3-65 for more information.

c. Select a Volume Method: Point or Range. See Using Point and Range Price Breaks on page 3-104 for more information.

12. Click Next to display the Create Price Break Line: Benefits page.

Note: To select the Net Amount box, the following must also be selected:

■ Modifier Line Type: Price Break

■ Automatic box: Selected

■ Volume Based on: Item Amount



Figure 3–30 Create Price Break Line: Benefits page

Define the following values for each price break:

13. Enter the Value From/To to define the price break range. For example, to define a break for the first 10 items ordered, create a range from 1-10. To do this, enter 1 in Value From and 10 in Value To.

14. Enter an Adjustment Value. For example, if you enter 10 in the Adjustment Value field and select Percent as the Adjustment Method, then you create a 10% adjustment.

15. Select an Application Method (Adjustment Method) to define how the price is to be adjusted.

16. Optionally, select a Formula if you are using a formula to calculate the benefit.

Modifiers 3-109


17. Click Add Another Row to create additional price break lines, or click Delete to remove a selected price break.

18. Click Next to display the Create Line Qualifiers page where you can define eligibility rules for the modifier line. See Creating Qualifiers (HTML Interface) on page 2-6 for more information on setting up qualifiers.

19. Complete your entries, and click Next to display the review page, or click Finish to skip the review page and save the line.


Note: Both the Value and Formula fields are not required, but at least one of these fields must be entered.



Creating a Promotional Goods Modifier Line (HTML Interface)A Promotional Goods modifier line adds a new item to an order and provides a price adjustment or benefit for the item when the customer orders one or more specified items on the same order. The item does not need to be originally on the order. Even if the item is on the order, the pricing engine creates a new line for the item.

To create a promotional good modifier:1. Navigate to the Create Line page.


2. Select Promotional Goods as the Modifier Type.


Modifiers 3-111


3. Select a Start and End Date range when the modifier line is effective. You should specify a range that coincides with the period of time that the benefit is offered. If no End Date is entered, then the modifier line does not expire.

4. Click Continue to display the Create Promotional Good Line: Controls page.


5. When you have entered the Controls, click Next to display the Create Promotional Goods Line: Products page.

Figure 3–32 Create Promotional Goods Line: Products page

In this page, you define the "buy" product item (or item category) that the customer must order to get the benefit. For example: buy a toothbrush, get a free bottle of mouthwash.



6. Select a Product Level and Product. Click the Flashlight icon to search for a product. The Product Description defaults based on the product selected.

7. Select a unit of measure (UOM):







9. In the Pricing Attributes region, select an Attribute(s) that further define how you want to price the product such as by color or size.





10. In the Excluded Products region (if applicable), you can exclude certain products so that the pricing adjustments will not be applied to the excluded products.


Note: The Excluded Products region does not display if Item Number is selected as the Product Level in the Products region.

Modifiers 3-113


For example, suppose you set up a discount modifier for the Item Category of "designer shoes;" however, some brands of designer shoes should never be discounted. Therefore, in the Excluded Products region, you would select the brands of designer shoes to be excluded from the benefit.

a. Select the Product Level and Product for the excluded item.

b. Optionally, click Add Another Row to enter additional Excluded Products, or click Remove to remove a selected product.

11. When you have completed your entries, click Next to display the Create Promotional Goods Line: Benefits page.

Figure 3–33 Create Promotional Goods Line: Benefits page

In this page, you can define the product the customers get when they purchase the "buy" product defined in the preceding step. For example, if they buy a toothbrush, the toothpaste is automatically added to the order line at a 10% discount.



12. Select a Product, or click the Search icon to search for the Product. The Product Description defaults based on the product selected.

13. Enter a UOM (unit of measure) such as each (Ea). The unit of measure is used with the Quantity field to determine how the benefit is applied.

14. Enter the Quantity.

15. Select the List Price.

16. Select an Application Method (Adjustment Method) that defines how the pricing engine applies this modifier.

17. Enter the Value for the selected Adjustment Method. For example, if you selected Percent as the adjustment method, enter 10 as the Value to give a 10% adjustment.

18. Optionally, click Add Another Row to add additional lines, or click Remove to remove a selected line. However, once the benefit line is created and saved, you cannot remove this benefit line or update the product.

19. Click Next to display the Create Promotional Good Line: Qualifiers page where you can define eligibility rules for the modifier line. See Creating Qualifiers (HTML Interface) on page 2-6 for more information on setting up qualifiers.

20. Complete your entries, and click Next to proceed to the review page, or click Finish to skip the review page and save the line.


Modifiers 3-115


Creating a Surcharge Modifier Line (HTML Interface)You can use a Surcharge modifier line to add a positive price adjustment. For example, to apply a 10 percent special charge to a customer’s order.

To create a surcharge modifier line:1. Navigate to the Create Line page.


2. Click Create Line to create a blank line.

3. Select Surcharge as the Modifier Type.


4. Select a range for the Start/End Dates.

5. Click Continue to display the Create Surcharge Line: Controls page.



In this page, you can define controls that govern how the modifier line should be applied. See Defining Controls for Modifier Lines (HTML Interface) on page 3-95 for information on setting up pricing controls.

6. When you have completed your entries, click Next to display the Create Surcharge Line: Product and Benefit page.

Figure 3–35 Create Surcharge Line: Product and Benefit page

7. Select a Product Level. If the Modifier level selected on the Controls page is:

■ Order level: Then all products on the order will receive the surcharge.

■ Line level: Then the Product level field defaults to null.

■ Group of Lines: Then the Product Level defaults to Item Number.

8. Select a Product or click the Search icon to search for available products. The Product Description defaults based on the product selected.

Note: If All Items is selected for Product Level, then the Product field defaults to "All" meaning all products.

Modifiers 3-117


9. Select a UOM (unit of measure):



The Precedence value defaults based on the Product Level selected. You can overtype this value.




11. In the Pricing Attributes region, select an Attribute(s) that further define how you want to price the product such as by color or size.










For example, suppose you set up a Discount modifier line for the Item Category of "designer shoes;" however, some brands of designer shoes should be "excluded" from the price adjustment.

Therefore, in the Excluded Products region, you would select the brands of designer shoes to be excluded from the price adjustment.

a. Select the Product Level and Product for the excluded item. This product will be excluded from the Item Category or All Items selected in the Product level field.


13. In the Benefit region, enter a Value, then select an Application Method (Adjustment Method). For example, if you selected Percent as the Adjustment Method and 10 for the Value, then the price is adjusted by10%.

14. Optionally, select a Formula.

15. Click Next to display the Create Surcharge Line: Qualifiers page where you can define eligibility rules for the modifier line. See Creating Qualifiers (HTML Interface) on page 2-6 for more information on setting up qualifiers.

16. Complete your entries, and click Next to proceed to the review page, or click Finish to skip the review page and save the line.


Note: Both the Value and Formula fields are not required, but at least one of these fields must be entered. Formulas are available for modifier lines types of Discount and Surcharge.

Modifiers 3-119


Searching for Modifier Lists (HTML Interface)In the Modifier Lists Search page, you can use searches to quickly retrieve information about modifiers. This helps you find information essential to your business such as:

■ All modifier lists in USD currency.

■ Specific modifier lines.

■ All active Promotion modifier lists.

■ All modifier lists for Customer A.

■ All discount modifier lists.

■ All promotions that will end on May 31st (must be an exact date match only).

Once the search results are returned, you can view a summary of modifier lists, view general information about the modifier list such as Name, Number, Type, Start/End Dates, and Active status, or select a specific modifier list to view additional details.

In addition to viewing the modifier lists, you can choose to update, and create a new modifier list.

Note: Alternately, you can do searches for modifier lists from the Oracle Advanced Pricing Home page. See Oracle Advanced Pricing Home page (HTML Interface) on page 5-46 for more information.

Note: You must be assigned Maintain privileges in pricing security to update or create a new modifier. The Details icon is enabled if you have view or update privileges assigned through pricing security.



To search for modifier lists:1. Navigate to the Modifier Lists Search page.

Figure 3–36 Modifier Lists Search page

2. Select a search category from the Search list, then enter additional criteria next to the Search list to narrow your search results. Select from the following search categories:

■ Status: Search by Active or non-Active modifier lists.

Active: Finds all Active modifier lists.

Inactive: Finds Inactive modifier lists.

■ Currency: Search by Currency. Select a specific currency such as USD (US dollars) to find all modifier lists set up in USD.

■ List Name: Search by the modifier list name. Enter a specific name or enter the percent sign (%) to list all modifier lists.

Modifiers 3-121


■ Dates: Search by modifier list Dates. These start and end dates must match exactly to the dates in the modifier list setup.

■ Line Number: Search by a modifier line number.

■ Type: Search by a specific modifier list type such as Deal, Discount List, Promotion, or Surcharge List.

■ List Number: Search by modifier list number. Enter a List Number to find a specific modifier list.

For example, to find a modifier list by its name, select Name from the Search list, then enter the specific name of the modifier list such as Summer Discount Modifier.

3. Click Go to display the following search results in a table:

■ Name: The modifier list Name.

■ Number: The modifier list Number.

■ Type: The modifier list Type.

■ Start/End Date: The start and end date for the modifier list.

■ Active: Indicates if the modifier is Active or Inactive.

4. Optionally, click Update to update the modifier list, or click Details to view additional details about the modifier list.

See:Oracle Advanced Pricing Home page (HTML Interface) on page 5-46

Creating a Modifier List (HTML Interface) on page 3-83

Updating a Modifier (HTML Interface) on page 3-123

Note: When pricing security is turned off, either the Details or Update icon displays depending on the profile QP: Source System. If the modifier list is created in a different source system within the same PTE, you can only view the list. You can only update the modifier list that matches your PTE and Source System.



Updating a Modifier (HTML Interface)You can update a modifier to change information such as its effective start and end dates then save your changes. All fields can be updated except for the List Type, Pricing Transaction Entity (if there are modifier lines), Source System (if there are modifier lines), Name, and Number.

To update a modifier:1. Navigate to the Update [Modifier Type]: General Information page. The actual

page name changes depending on the type of modifier being updated.

Figure 3–37 Update [Modifier Type]: General Information page

2. Update the fields that require changes:


Modifiers 3-123


■ Version Number

■ Requested Ship date

■ Start/End Date

■ Order Date From/To

■ Requested Ship Date From/To

■ Description

■ Currency

3. Select or clear the Customer Must Ask For List box (if applicable).

4. Select or clear the Active box:

■ To make a modifier active, select Active.

■ To make a modifier inactive, clear Active.

When a modifier list is first created, it is Inactive. The pricing engine evaluates only Active modifiers (when the Active box is selected). When a modifier is no longer required, change the status of the modifier to Inactive so only Active modifiers are evaluated.

5. Click Apply to save the changes.

A Confirmation pages displays to advise you if the changes were updated successfully.




Updating a Modifier Line (HTML Interface)You can update an existing modifier line to change information such as controls, products and benefits, and qualifiers. You can add additional qualifiers, excluded items, and additional buy and get products.

However, you cannot update the following:

■ The primary buy product for the modifier line cannot be removed or changed.

■ Once a modifier line is saved, you cannot delete additional buy and get items.

The following fields cannot be updated: List Type, Pricing Transaction Entity/Source System, Name, Number, Product Level, Product, Modifier Level, and Line Number.


Modifiers 3-125


To update a modifier line:1. Navigate to the Update [Modifier Type]: Modifier Lines page.

Figure 3–38 Update [Modifier Type]: Modifier Lines page

2. To find modifier lines for the selected modifier, select a Search category and enter additional criteria for the selected category:

■ Line Number: Enter a modifier line number.

■ Type: Select a modifier Type to search by: Discount, Price Break, Promotional Goods, and Surcharge.

3. Click Go to display the search results.

4. Click Update to display the Update Line page.



Figure 3–39 Update Line page

5. Select the Controls tab to update controls that define how the modifier line is applied such as the Start/End Dates, Pricing Phase, Bucket, and Incompatibility Levels. See Defining Controls for Modifier Lines (HTML Interface) on page 3-95.


Modifiers 3-127


6. Select the Products tab to update information related to the selected product such as UOM and Precedence. You cannot update the Product Level or Product in the update mode. In the Pricing Attributes region (if applicable), you can update, add, or remove pricing attributes related to the product. In the Price Break Benefits region (if applicable), you can update the Adjustment Type, Volume Based on, Volume Method, and related fields.

Figure 3–40 Products tab

7. Select the Benefits tab to update the benefit information for the modifier line such as Value From/To, Adjustment Value, Adjustment Method, and Formula. For example, you could change the Adjustment Value from 10 to 15 for the Adjustment Method of Percent.



Figure 3–41 Benefits tab

8. Select the Qualifiers tab to update qualifiers and qualifier groups currently associated with the modifier line. You can update the qualifier information, add new qualifiers by clicking Create Qualifier, or append qualifier groups by clicking Append Group.

9. After you have completed all your updates, click Apply to save your changes.

See:Updating a Qualifier (HTML Interface) on page 2-12

Appending a Qualifier Group (HTML Interface) on page 2-15


Modifiers 3-129

Redeeming Accruals

Redeeming AccrualsYou can mark accrued price adjustments as redeemed and record redemption transaction information. In addition, you can unredeem coupons recorded as redeemed in error.

To redeem accruals:1. Navigate to the Redeem Accruals window.

Figure 3–42 Redeem Accruals window

2. Do a query to retrieve the accruals. For example, query by Customer name to find all unredeemed accruals for that customer. The window only displays accrual records that the pricing engine created.

3. Select the accrual record.

4. Do the following steps for each accrual that you want to redeem.

Note: You cannot create an accrual record in this window.

Note: You cannot mark an accrual record as partially redeemed. For example, a customer purchases a computer and accrues 100 air miles. You cannot mark 60 air miles redeemed at one time and 40 air miles redeemed at a later time.


Changing Modifier Incompatibility

5. Select the Redeemed box.

6. Enter the Transaction Reference number for the system that redeemed the accrual.

7. Enter the Payment System that issued the payment for the accrual.

8. Enter the Redeemed Date (the default is the current date).

9. Alternately, to mark a redeemed accrual record as unredeemed, clear Redeemed. Verify that the Transaction Reference, Payment System, and Redeemed Date fields are blank.

10. Save your work.

Changing Modifier IncompatibilityYou can review and change incompatibilities in the Incompatibility Groups window. For each incompatibility group within a specific phase, you can view the modifier lines assigned to one incompatibility group and then re-assign them to another.

When you create modifier lines, you assign a phase and then assign an incompatibility group. Multiple incompatibility groups can be assigned to each pricing phase. Since the pricing business rules allow the pricing engine to apply only one modifier for each incompatibility level and phase combination, it must resolve incompatibilities.

Incompatibility Processing: Precedence During the phase List Line Base Price, if the pricing engine selects more than one eligible price list line in the desired unit of measure, it resolves the incompatibility by picking the price list line having the highest precedence (lowest precedence number) and uses it as the base price of the item.

The pricing engine uses Precedence for incompatibility processing to select the list price from a price list. In the pricing phase List Line Base Price, regardless of the value of the Incompatibility code at the User level, the pricing engine picks up the list price based on Precedence only.

Note: If you are unable to access or update this window, you may not have the appropriate access privileges. Consult your Pricing Administrator.

Modifiers 3-131


Incompatibility Processing: Base Price For the phases, List Line Adjustment, All Line Adjustments, and Header Level Adjustments, if the pricing engine selects more than one eligible modifier, it resolves the incompatibility using best price processing.

Best price processing instructs the pricing engine to select the modifier that offers the lowest price to the customer. For non-monetary modifiers, the pricing engine uses the estimated general ledger value of the modifier as the value of the modifier.

During precedence processing if two or more modifiers tie based on precedence processing, then the engine resolves using best price processing WITHOUT going below the established precedence.

The following table shows an example of the pricing engine using precedence to resolve incompatibilities. The Engine Applies column indicates whether the pricing engine selects the modifier.

Freight and Special Charges modifier and Incompatibility Processing:Incompatibility processing considers all the modifier types such as Freight and Special Charges and evaluates them as a single entity. Once the incompatibility

Note: Use the Event Phases window to set the Incompatibility Resolve Code for a phase.

Table 3–25 Incompatibility Processing

Modifier PhaseIncompatibility Level Precedence Engine Applies

10% discount 30 1 260 No

$100 promotion 30 1 240 Yes

Free promotional good 30 2 260 Yes

$50 lumpsum 30 3 200 Yes

3% discount 30 3 240 No

25 currency unit deal 40 1 260 Yes

Note: Refer to the phase event mapping discussion to learn how to set phase incompatibility resolution.



processing is complete, only one modifier remains which may or may not be the Freight and Special Charge modifier type depending on the incompatibility setup.

Exclusive Modifiers and Incompatibility Processing: You can create one exclusive modifier in each pricing phase. When the pricing engine encounters an exclusive modifier, it suspends incompatibility pricing for the phase and applies only the exclusive modifier.

Note: For Freight/Special Charges: If an Incompatibility Group is not selected for the modifier line, then the pricing engine will use Best Price incompatibility processing instead of Precedence. The type of engine processing can be defined in the Incompatibility Resolve Code field in the Event Phases window.

Modifiers 3-133


To change modifier incompatibility:1. Navigate to the Incompatibility Groups window.

Figure 3–43 Incompatibility Groups window

2. Click the Search icon to display the Find Incompatibility Groups window (if you are in a blank Incompatibility Groups window). Alternately, do a search: View > Query by Example > Enter. Select your search criteria to find modifier lines associated with a particular phase or those assigned to a particular Incompatibility Group:

■ Phase Sequence

■ Phase Name

■ Incompatibility Group

3. Click Find to view the search results in the Incompatibility Groups window.

Note: If you search for a phase without specifying an Incompatibility Group, the search returns all modifier lines for this phase, even those not assigned with an incompatibility group.



4. To update the Incompatibility Group for a modifier, select a different group from the Incompatible Group column.

5. Alternately, select the modifier and click Modifier to display the modifier details in the Advanced Pricing - Define Modifier window.


6. In the Modifiers Summary tab, select a different Incompatibility Group (if desired).

7. Save your work.

Modifiers 3-135

Archiving and Purging Modifiers

Archiving and Purging Modifiers You can archive pricing entities such as modifiers and modifier lines by copying pricing data from the pricing application tables to archive tables for long-term data storage. Pricing data that is archived into the permanent pricing archive tables is deleted from the pricing application tables.

By archiving and purging records, the number of pricing records that need to be queried or processed by the pricing engine is reduced, potentially resulting in improved performance.

When the archived data is no longer required or does not need to be retained for legal retention purposes, then you can use the purge feature to purge the data from the archive tables.

See:Archiving Pricing Entities on page 6-3

Purging Pricing Entities on page 6-10


Using the Pricing Organizer

Using the Pricing OrganizerYou can manage and track your modifiers more effectively by using the Pricing Organizer to create simple or complex queries (searches). The Find Modifier window enables you to create queries using modifier setup information to find information essential to your business such as:

■ All the active automatic promotions for customer A for a given source system.

■ All the active promotions for customers within the Western region for the month of May.

■ All discounts for item A that customer B is qualified for.

■ All promotions that will end by May 31st for a given customer

■ All modifiers that use price list A as a qualifier.

■ All modifiers for my product category that customer C is eligible for if they ask for the promotion.

Once the search results are returned, you can view a modifier summary or details about a particular modifier.

The resulting query, but not the search results, can be saved as a personal query which is not shared with other users or a public query that can be shared with other users. This enables you to re-run the query without having to re-enter the query criteria.

You can also rename an existing query or delete it when it is no longer required. From the Modifiers window, you can create new modifiers as well.

See: ■ Saving a Modifier Query on page 3-164

■ Maintaining a Modifier Query on page 3-165

Process Flow for Querying and Displaying Modifiers The following process flow summarizes the main steps involved in querying and displaying modifiers:

1. Enter the query criteria in the Find Modifiers window.

If you have previous query criteria in the fields, you can clear any existing queries from all tabs by clicking Clear.

Modifiers 3-137


2. Click Find to run the query and display the results in the Modifier Organizer window.

3. The modifiers at the Header tab or the Lines tab can be selected and opened.

4. You can save the query criteria by a name in the public or private folder.

5. You can create a new modifier by selecting the New Modifier button from the Find Modifiers or Modifier Organizer window.

Creating a Query in the Find Modifiers window You can create a modifier query in the Find Modifiers window to find specific modifiers and related modifier lines. The Find Modifiers window consists of tabbed regions where you can select your search criteria. The query results display in the Headers/Lines tabs of the Modifier Organizer window.

You can query by the following search criteria:

■ Modifier Header details from the Header tab.

■ Modifier Line details from the Lines tab.

■ Other modifier line details from the Additional Lines Criteria tab.

■ Product Attribute details from the Product Attribute tab.

■ Pricing Attribute details from the Pricing Attributes tab.

■ Qualifier details from the Qualifiers tab.

Entering Query Criteria across Multiple tabsYou can select search criteria in one tab or across multiple tabs of the Find Modifiers window.

When you have completed your entries in the following tabs, click Find to start the query. After the results display in the Modifier Organizer window, select a modifier header or line detail from the Headers or Lines tab to view the modifier details. You can open a specific modifier from the Modifier Organizer window.

Note: If Pricing Security is ON, a user with View Only access privilege can view modifier information if it displays in the search results. Maintain privilege is required to make any changes.



Header tabYou can enter query criteria for modifier list details in the Header tab. This includes information such as Modifier Type, Modifier Number, Modifier Name, Version, Parent No, and Currency.

1. Select only the criteria required for your query. If a field is left blank, it is not included as a query criteria.

Figure 3–45 Find Modifiers window: Header tab

Note: You can enter you query criteria in one tab or across multiple tabs depending on your query requirements. To narrow the search results, specify additional query criteria.

Modifiers 3-139


To create a new modifier from the Pricing Organizer window:1. If the modifier you need does not exist, click New Modifier in the Find

Modifiers window to display the Advanced Pricing - Define Modifier window.

Alternately, click the New Modifier button from the Headers or Lines tab of the Modifier Organizer window to display the Advanced Pricing - Define Modifier window.

Table 3–26 Find Modifiers window: Completing Header tab information

Field Name Description

Type Query by a modifier Type such as Deal, Discount List, Freight and Special charge List, Promotion, or Surcharge List.

Parent No Query by a Parent No.

Number Query by the modifier Number.

Parent Version Defaults if Parent No is selected.

Name Query by the modifier Name.

Active Select Yes to query modifier lists that are currently Active or No to query inactive modifier lists

Version Query by a specific Version of the modifier.

Ask For Select Yes to query for modifiers that are Ask For or No for modifiers that are not Ask For.

Currency Select the Currency. If left blank, the search returns all currency modifiers. To query a non -currency defined modifier, select OPT CURR.

Source System Query for modifiers created by the selected Source System.

Last Updated By Query for modifiers last updated by the selected value.

Order Date Exist Select Yes to query for modifiers where an order is defined or No to query for modifiers without any order dates entered.

Last Update Date Query for modifiers by the last updated modifier date.

Ship Date Exist Select Yes to query for modifiers with an existing ship date is defined or No to query for modifiers without any ship dates entered

Exact Effective Date Match

When the Exact Effective Date Match is selected, only modifiers with the matching dates specified in the Effective From/To are returned.

Effective From/To Enter Effective From and To dates to query modifiers whose Effective From/To dates are within the selected date range.



2. Enter information for the new modifier.

3. Save the modifier.

Modifiers 3-141


Examples of Querying by Effective DatesThe following examples show how effective dates can be used in a query. You can enter your search criteria in the following fields:

■ Exact Match (check box)

■ Effective From

■ Effective From (High)

■ Effective To

■ Effective To (High)

If Exact Date Match is checked, the = (equal to) operator is used for the query. Otherwise >= and <= operators are used for Effective From/To and Effective From/To (High) fields respectively.

For cases other than Exact Date Match, modifiers having NULL values for Effective dates are also selected.

The following modifier setups are used in the query examples below:

Example1: Finding Modifiers by a) Exact Effective Date Match b) Effective From/To range The following examples show the query criteria and modifiers retrieved for a query by Exact Date match, and Effective From/To dates:

a) Exact Date matchSelect the Exact Effective Date Match box. The Effective From (High) and Effective To (High) fields are grayed out. You can only enter values in the Effective From and Effective To fields. For example, if you enter

Table 3–27 Querying by Effective Dates

Modifier Name Effective From Effective To

M1 10-DEC-1999 10-JAN-2001

M2 10-MAR-2001 30-MAR-2002

M3 — 30-APR-2003

M4 — —

M5 10-MAR-2001 —

M6 19-MAR-2001 10-NOV-2002



■ Effective From: 10-MAR-2001

■ Effective To: 30-MAR-2002

The modifier M2 will be returned.

b) Effective From/To range Specify the values in any or all the four fields.

■ Effective From: 01-JAN-2001

■ Effective From (High): 15-MAR-2001

■ Effective To: No Value

■ Effective To (High): 01-DEC-2002

The modifiers M2, M4 and M5 are returned.

Example 2: Finding Modifiers by a Single Date-the same date in Effective From (High) and Effective To fieldsEnter the same date in Effective From (High) and Effective To fields.

For example, to find all the modifiers effective on 10-MAR-2001, enter

■ Effective From (High): 10-MAR-2001

■ Effective To: 10-MAR-2001

The modifiers M2, M3, M4 and M5 are returned.

Example 3: Finding Modifiers by Date RangeEnter the low date range in Effective From (High) and high date range in Effective To fields. For example, to find all the modifiers effective between date range 01-JAN-2001 and 10-JAN-2001, enter:

■ Effective From (High): 01-JAN-2001

■ Effective To: 10-JAN-2001

The modifiers M1 and M4 will be returned. You can also do exact or range date matches to find modifiers by their effective dates.

Modifiers 3-143


Lines tabYou can enter query criteria for modifier lines in the Lines tab. However, you cannot query the following:

■ additional buy items for promotional goods or other item discounts

■ get items for promotional goods or other item discounts

■ price break lines details

Select only the criteria required for your query. If the field is left blank, it is not included as a query criteria.

Figure 3–46 Find Modifiers window: Lines tab

Note: You can enter query criteria in one tab or across multiple tabs depending on your query requirements.



Table 3–28 Find Modifiers window: Entering a query in the Lines tab


Modifier No Query by Modifier Line Number.

Type Query by modifier line type. When you query on Coupon Issue, only the coupon issues line is retrieved.

Level Query by the modifier line level such as Group of Lines, Line, or Order.

Pricing Phase Query lines for a specified Pricing Phase. Type the Pricing Phase ID rather than the description. Alternately, select the pricing phase from the Pricing Phase list.

Bucket Query modifier lines assigned to a particular bucket.


Query modifier lines associated for a specific Incompatibility Group.

Automatic Select Yes for modifier lines that have the Automatic box selected and No for modifier lines that do not have Automatic selected.

Override Select Yes for modifier lines with the Override box selected and No for modifier lines that do not have Override selected.

Include on Returns

Select Yes for modifier lines that have the Include on Returns box selected and No for modifier lines that do not have the Include on Returns box selected.

Accrual Select Yes for modifier lines that have the Accrual box enabled and or No for modifier lines that do not have the Accrual box enabled.

Formula Select one of the following:

■ No Formula: to query by lines that have no formula attached.

■ Any Formula: to query on modifier lines that have any formula attached regardless of the formula.

Select the formula name from the list.

Application Method

Query for modifier lines associated with an Application Method such as Percent, Amount, Lumpsum, and New Price.

Comparison Value

Query for lines for a given Comparison Value.

Value Query by modifier lines for a given value.

Break Type Query by a Break Type for the modifier lines such as point or range.

Terms Attribute Query modifier lines associated with certain terms such as Freight Terms, Shipping Terms, and Payment Terms.

Modifiers 3-145


Upgrade Item Query modifier lines by Upgraded Item.

Terms Value Query modifier lines with certain Terms Value.

Last Updated By

Query by the last user who updated the modifier.

Last Update Date

Query by the date when the modifier was last updated.

Accumulation Attribute

Query by Accumulation Attribute.

Charge Names Query by Charge such as Administration Fees, Duty Fees, Export Fees and so on.

Exact Effective Date Match

When the Exact Effective Date Match check box is enabled, only modifiers with the matching dates specified in the Effective From/To are returned.

Effective From/To

Enter Effective From/To dates to query modifiers whose Effective

From/To dates are within the selected date range.

Table 3–28 Find Modifiers window: Entering a query in the Lines tab




Additional Lines Criteria tabYou can select query criteria if Coupon Issue, Price Break Header, or Discount was selected as the Modifier Type in the Lines tab or if a modifier type is not selected in the Lines tab. Otherwise, the fields are grayed you cannot make any selections.

Select only the criteria required for your query. If a field is left blank, it is not included as a query criteria.

Figure 3–47 Find Modifiers window: Additional Lines Criteria tab

Note: You can enter query criteria in one tab or across multiple tabs depending on your query requirements.



Benefit Quantity Query by Benefit Quantity.

Modifiers 3-147


Benefit UOM Select a specified UOM such as LBS (pounds) from the list.

Expiration Date Query by Expiration Date to query modifiers with lines matching the specified expiration date.

Expiration Period Start Date

Query Expiration Start date. This is an exact date match query.

Expiration Period

Query by the Expiration Period.

Period type Query by a specified Period type.

Rebate Transaction type

Query by a Rebate Transaction type.

Accrual Conversion Rate

Query by an Accrual Conversion Rate when modifier type is Discounts for accrual.

Coupon Conversion Rate: For modifier type Coupon, this field displays the Coupon Conversion Rate.

Accrual Redemption Rate: Query by an Accrual Redemption Rate.

Coupon Redemption Rate: For modifier type Coupon, this field displays the Coupon Redemption Rate.

Coupon Modifier Number

Query by the Coupon Modifier Number if modifier type is coupon.





Product Attributes tab1. Select one of the following options from the Product Attributes tab.

Figure 3–48 Find Modifiers window: Product Attributes tab

■ Products: This enables you to query the specified fields on the window.

■ No Products: If this option is selected, the remaining fields on the window are greyed out. The query returns modifier lines that do not have any product attributes defined

■ Not Specified: If this option is selected, the remaining fields on the window are greyed out and the query ignores whether a modifier line has product attributes or not. This is the defaulted value and additional query criteria is needed for the query to execute.

2. When Product Attributes field is enabled above, query by Product Attribute.

Note: The Product Attribute Value can be entered only after a Product Attribute has been selected.

Modifiers 3-149


If you select Products in the Product Attributes field, you can also query by Exclude Items.

3. Enter one or more Exclude Items in the Exclude Items region.

The query retrieves modifiers that have that item defined as an Exclude Item. If more than one exclude product is selected, then modifiers with at least one of the Exclude Items defined are retrieved.

Note: When querying by an item, the query results will return modifier lines that specify the item number and not include modifier lines for item category.



Pricing Attributes tab1. Select the Pricing Attributes tab.

Figure 3–49 Find Modifiers window: Pricing Attributes tab

2. Select one of the following options from the Pricing Attributes field:

■ Pricing Attributes: This option enables the query fields on the window. Enables you to query by one or more combinations of Pricing Context/Attributes. For example, you could query by Volume (Pricing Context) and Total Item Quantity (Pricing Attribute). If no values are entered, the query returns only those modifiers with at least one product attribute.

■ No Pricing Attributes: If this option is selected, the remaining fields on the form are greyed out. The query will return modifier lines that do not have any pricing attributes defined.

■ Not Specified: If this option is selected, the remaining fields on the window are greyed out and the query ignores whether a modifier line has Pricing

Modifiers 3-151


Attributes or not. This is the defaulted value and additional query criteria is needed to run the query.

3. Select Pricing Attributes in the Pricing Attributes field to query by pricing context. The Pricing Attribute field is enabled if a Pricing Context is selected. The Pricing Attribute Value is enabled only after a Pricing Attribute has been selected.

4. Select an operator value such as = or BETWEEN. The Value To field is grayed out if the Operator value is =.

If the operator value is left blank or is BETWEEN, the query evaluates the values in the Value From and Value To fields to determine if there is an exact match.

5. You can specify up to 3 pricing attributes with a combination of OR/AND operators.

Examples of using AND/OR Operators to query Pricing AttributesThe following table displays modifiers named M1, M2, M3, and M4 and their pricing attributes:

The following table displays the results for a query by Pricing Attributes. The query results depend on the AND/OR operator criteria selected: Yes means the modifier is retrieved and No means it is not.

Table 3–30 Example of AND/OR Operators to Query Pricing Attributes

Modifier Name Pricing Attributes

M1 Blue, Large, and Grade A

M2 Blue

M3 Large

M4 Blue and Grade A

Table 3–31 Using AND/OR Operators to Query Pricing Attributes

ConditionsM1- Blue, Large, and Grade A M2 - Blue M3 - Large

M4 - Blue and Grade A

OR/OR Yes (Blue/ Large/grade A)

Yes (Blue) Yes (Large) Yes (Blue/Grade A)



AND/AND Yes (Blue, Large, and Grade A)

No (not Blue and Large and Grade A)



OR/AND Yes (Blue/Large and Grade A)

Yes (Blue) No (not Large and Grade A)

Yes (Blue)

AND/OR Yes (Blue and Large/Grade A)

No (not Blue and Large)

No (not Blue and Large)

Yes (Grade A)

Null PA1, And/OR

Yes (Large/Grade A) No (no PA's) Yes (Large) Yes (Blue/Grade A)

Table 3–31 Using AND/OR Operators to Query Pricing Attributes

ConditionsM1- Blue, Large, and Grade A M2 - Blue M3 - Large

M4 - Blue and Grade A

Modifiers 3-153


Qualifiers tab1. Select the Qualifiers tab.

Figure 3–50 Find Modifiers window: Qualifiers tab

2. Select one of the following options from the Qualifiers tab:

■ Qualifiers: This option enables you to query the fields on the window:

Table 3–32 Qualifier Field Names and Values

Qualifier Field Name Value

Qualifier Context Customer

Qualifier Attribute Customer Name

Operator = (exact match)

Value World of Business



■ No Qualifiers: If this option is selected, the remaining fields on the window are greyed out. The query retrieves modifier lines that do not have any qualifier attributes defined.

■ Not Specified: If this option is selected, the remaining fields on the window are greyed out and the query ignores whether a modifier line has a qualifier attribute or not. This is the defaulted value and additional query criteria is needed to run the query.

3. Select Qualifiers in the Qualifiers field to query by qualifier context. The Qualifier Attribute field is enabled if a Qualifier Context has been selected. The Qualifier Attribute value is enabled only after a qualifier attribute is selected. Otherwise, the fields are grayed out and you cannot specify any qualifier values.

4. Select one of the following operator values: =, BETWEEN, or NOT=. If you select the = or NOT= operator, the Value To field is grayed out.

5. For an exact match choose =. For a range of values, select BETWEEN. If you want to filter out values for a given range select NOT=.

If the operator is left blank or BETWEEN, the query evaluates the values in the Value From and Value To fields to determine if there is an exact match.

6. Select the Exact Effective Date Match box to retrieve modifiers with the dates specified in Effective From/To.

7. You can specify up to 3 qualifiers by selecting the OR/AND operators.

Examples of using AND/OR operators to query Pricing QualifiersYou can select up to three qualifiers by specifying the OR/AND operators:

■ Q1=Customer Name

■ Q2= Order Type

■ Q3 = Ship To

Table 3–33 Using AND/OR Operators to Query Pricing Qualifiers

Conditions

Modifier 1- Cust Name, Order Type, & Ship To

Modifier 2 - Customer Name

Modifier 3 - Order Type

Modifier 4 - Cust Name and Ship To

OR/OR Yes (Customer Name/Order Type/Ship To)

Yes (Customer Name)

Yes (Order Type) Yes (Customer Name/Ship To)

Modifiers 3-155


AND/AND Yes (Customer Name and Order Type and Ship To)

No (not Customer Name and Order Type and Ship To)



OR/AND Yes (Customer Name/Order Type and Ship To)

Yes (Customer Name)

No (Not Order Type and Ship To)

Yes (Customer Name)

AND/OR Yes (Customer Name and Order Type/Ship To)

No (not Customer Name and Order Type)

No (not Customer Name and Order Type)

Yes (Ship To)

Null Q1, And/OR

Yes (Order Type/Ship To)

No (No Q1) Yes (Order Type) Yes (Ship To)

Table 3–33 Using AND/OR Operators to Query Pricing Qualifiers

Conditions

Modifier 1- Cust Name, Order Type, & Ship To

Modifier 2 - Customer Name

Modifier 3 - Order Type

Modifier 4 - Cust Name and Ship To



Using the Pricing Organizer as Query FindFrom the Advanced Pricing - Define Modifier window, you can query modifier and qualifier information using the query fields of the Pricing Organizer. You can run queries to find:

■ Modifier lines for a product attribute or pricing attribute

■ Qualifiers for a context, attribute, attribute value, and effective dates

When you click the Find icon, the Pricing Organizer displays one or more search tabs for entering query criteria. Only the tabs and fields relevant to the query are enabled; the others are grayed out.

So, for example, if you want to query for list qualifiers, the Pricing Organizer displays the List Qualifiers tab where you can enter your search criteria.

To query modifier line information:1. Display the modifier in the Advanced Pricing - Define Modifier window.

2. Select a modifier line in the Modifiers Summary tab, and click the Find icon.

The Pricing Organizer displays the Lines tab and other tabs where you can enter the search criteria. All the tabs will be active except for the Header tab. The Qualifiers tab will now be Line Qualifiers.

Modifiers 3-157


Figure 3–51 Find Modifier Lines window: Lines tab

3. Enter your search criteria then click the Find icon.

The modifier lines matching your search criteria display in the Advanced Pricing - Define Modifier window.

To query qualifier information:1. Display the modifier in the Advanced Pricing - Define Modifier window.

2. Click the List Qualifiers or Line Qualifiers button.

The Pricing Organizer displays the Qualifiers tab where you can enter the search criteria. If you are querying from the List Qualifiers region, the List Qualifiers tab will be enabled. If you are querying from the Line Qualifiers region, the Line Qualifiers tab is enabled. The tab is the same, only the label changes.



Figure 3–52 Find List Qualifier window: Qualifiers tab

3. Enter your search criteria (up to 3 qualifiers with the OR condition) and then click the Find icon to find the qualifiers that meet your search criteria.

The qualifiers matching your search criteria display in the Qualifiers region of the Advanced Pricing - Define Modifier window.

Modifiers 3-159


Running the Modifier QueryAfter the query criteria has been selected, you can run the query to retrieve the search results. If a modifier matches all the specified search criteria, the modifier is retrieved and displayed in the Modifier Organizer window.

To run a modifier query1. From the Find Modifiers window, click Find to run the query. At least one query

criteria must be entered to run the query.

The search results display in the following tabs of the Modifier Organizer window:

■ Header tab: Displays a summary of the modifiers’ header information.

■ Lines tab: Displays a summary of modifier line details provided at least one query criteria has been entered in the Lines, Additional Lines, Products, Pricing Attributes, or Qualifiers tab.

Note: Alternately, to run a saved query, just double-click the query name. The saved query names are displayed in the Personal or Public folders in the Modifier Organizer window. For more information, see: Saving a Modifier Query on page 3-164.



Figure 3–53 Modifier Organizer window

The following table summarizes what modifier level displays (header or line) when you enter your query criteria in the tabs (Header, Lines and so on).

Table 3–34 Query Criteria and Display Results

Query Criteria Display Header Display Lines

In Header X n/a

In Lines X X

In Header and Lines

X X

Qualifiers on Header

X n/a

Qualifiers on Lines

X X

Modifiers 3-161


Qualifiers on Headers and lines

X X

Products Line X X

Pricing Attributes

X X

Table 3–34 Query Criteria and Display Results

Query Criteria Display Header Display Lines



Opening a Queried Modifier (from the Pricing Organizer)You can select a record from either the Headers or Lines tabs to view more details.

■ Select a modifier in the Headers tab, and click Open Modifier to display modifier details.

■ Select a modifier line in the Lines tab and click Open Modifier to display the current modifier for the selected modifier line.

The modifier displays in the Advanced Pricing - Define Modifier window.

Note: If you select Restrict Lines and click Open Modifier, only those lines that meet the query criteria on the Find Modifiers window are displayed. They display in the Modifiers Summary tab of the Advanced Pricing - Define Modifier window.

Modifiers 3-163


Saving a Modifier QueryIf you frequently use the same query, you can save it and rerun without re-entering the search criteria again—just double-click the saved query name.

The query can be saved as either a Personal or Public query: a Personal query is not shared while a Public query is shared with other users. When saving the query, select the Public check box to save it as a public query in the Public Folder; otherwise it is saved as a personal query in the Personal Folder.

To save a modifier query1. Do a query in the Find Modifiers window to display the search results in the

Modifier Organizer window.

Figure 3–54 Modifier Organizer window

2. Right-click the Search Results folder in the left pane to display the menu.

3. Choose Save to display the User Defined Queries window.



Figure 3–55 User Defined Queries window

4. Enter a Name for the query.

5. Select Public to save the query as a Public query that can be shared with other users. Otherwise, it is saved as a Personal query.

6. Click OK to save the query.

Maintaining a Modifier QueryOnce you have saved your queries, you can rename an existing query, move queries between Public and Personal folders, or delete a query that is no longer required.

To rename a saved modifier query:1. Find the saved query to be renamed in either the Personal Folders or Public

Folders.

2. Right-click the query name to display the menu, then choose Rename Query to display the User Defined Queries window.

3. Enter the new name and click OK.

To move a saved query between the Personal or Public folder:1. Find the saved query to be moved in either the Personal Folders or Public

Folders.

Note: A public query can be renamed, moved from Public to Personal folder, or deleted only if the value of the profile option QP: Administer Public Queries is set to Y (Yes).

Modifiers 3-165


2. Right-click the query name to display the menu, then choose Rename Query to display the User Defined Queries window.

3. Select or clear the Public box and click OK. The selected query has now moved over.

To delete a modifier query:1. Select the query to be deleted in either the Personal Folders or Public Folders.

2. Right-click the query name, then select Delete to display the Decision window.

3. In the Decision window, click Yes to delete or No to return to the Modifier Organizer window.

4. Save your work.


Overview of Promotional Limits

Overview of Promotional LimitsOracle Advanced Pricing enables you to set limits for benefits that a customer can receive for a promotion, deal, or other modifier. By limiting the amount of a benefit that can be received, you can keep promotional spending within budget and prevent promotion budget overruns.

For example, promotional limits could be used to provide a 10% discount on the first 500 units of an item sold, or a 10% discount for an item until the promotional limit is reached; for example, once the promotion reaches $100,000.

In addition to setting limits on promotional spending, you can also monitor current and cumulative promotional spending in real time, order by order.

You can set limits for a specific monetary value such as the first $500 or by a specific category such as a customer. Oracle Advanced Pricing enables you to set limits in terms of accrual units, discount cost, gross revenue, item quantity, and usage (by customer, by promotion, by promotion and customer). Within a promotion, deal, or modifier, you can also set eligibility for limits by customer, product, or other entity:

■ Customer: Define a limit by customer, a group of customers, or at any level in your customer hierarchy.

■ Product: Define a limit for a product or group of products in your product hierarchy.

If multiple organizations exist for your corporation, you can set a different limit for each sales organization, group of organizations in your company hierarchy, or give the same limit for all. When entering a limit, you can select if you want to consider to set this limit

■ By organization

■ Across all organizations

Note: To use limits, Oracle Advanced Pricing must be installed and the profile option QP: Promotional Limits Installed must be set to Yes by the System Administrator.

If you are unable to access the promotional limits windows or make updates, you may not have the appropriate access privilege. You must have at least View Only privileges to view. To make any changes or updates to the windows, you must have Maintain privileges. Consult your Pricing Administrator.

Modifiers 3-167


■ For a specific organization.

You can define a limit across the current transaction or across all transactions to which a promotion or modifier has been applied.

Note: You cannot create line limits in the following situations:

■ If the Modifier line type is Other Item Discount, Promotional Goods, Coupon Issue, Item Upgrade or Term Substitution.

■ If the Automatic box is cleared so that the modifier line must be manually applied.

■ If the Override box is selected.



Creating LimitsOracle Advanced Pricing enables you to create monetary or usage limits that a customer can receive for a promotion, deal, or other modifier.

Limits not copied to new modifier: If copying a modifier, existing limits at either the line or header level, are not copied from the original modifier to the new modifier. The promotional limits must be created again for the new modifier.

You can create limits at the:

■ Modifier header level for a promotion, deal, or modifier list.

■ Modifier line level: Limits can be applied to line modifiers and applied to a line, group of lines, or order.

■ Both Modifier header and line levels

You can define header and line level limits in terms of accrual units, discount cost, gross revenue, item quantity, and usage (by customer, by promotion, by promotion and customer). The limit can be defined by a specific value or a limit for each

Note: To use limits, Oracle Advanced Pricing must be installed and the profile option QP: Promotional Limits Installed must be set to Y (Yes) by the System Administrator.

Caution for line limits: Line limits cannot be created if the Modifier Type for the modifier line is Other Item Discount, Promotional Goods, Coupon Issue, Item Upgrade, or Term Substitution.

■ The Automatic check box for the modifier line must be enabled, and the Override Flag must be cleared otherwise you cannot enter a limit for the modifier.

■ If no Product UOM was defined for the modifier line, line limits with basis of Item Quantity will not get created. If no Benefit UOM was defined for a Modifier Line, line limits with basis as Accrual Units will not get created.

■ If no Benefit or Product UOM is defined for a modifier line, neither Item Quantity or Accrual Units displays in the Basis list of values (LOV) and line limits cannot be created for that line.

Modifiers 3-169


element that receives a promotion; for example, a limit of $100 for each customer. The following examples illustrate different ways limits can be applied:

CustomersYou can define limits for all individual customers, group of customers, or specifically named customers; for example:

■ No more than $100 of benefit to any one customer on any order from promotion Y.

■ Customer XYZ is limited to $1000 cumulative benefit from promotion X.

■ All VIP customers are limited to $2000 cumulative benefit.

Individual stock-keeping units (SKU’s) or groups of SKU’sYou can define limits for individual SKU’s or groups of SKU’s that are being promoted; for example:

■ Limit aggregate expense for promotion X to $50,000 for item 1234.

■ Limit VIP customers to $2000 cumulative benefit.

Individual or aggregated transactionsYou can define limits that apply to individual transactions or aggregated transactions; for example:

■ Limit customers so they cannot exceed $50 for any order.

■ Limit customers’ use of promotion X for either $400 cumulative discount or placing an order 3 times.

■ Limit the total expense that customers may receive from a fall promotion to $5000.

When setting up a limit, you must select a basis that defines the unit being monitored for limit checking. Available limit bases are accrual units, charge amount, cumulative discount amount, gross revenue, item quantity, and usage.

For example, if accrual units were used as the basis for monitoring units such as air miles, the limit would monitor the number of air miles accrued.



To create limits at the modifier header level or line level:1. Navigate to the Advanced Pricing - Define Modifier window.

2. Click List Limits to enter a limit at the modifier header level, or click Line Limits to enter a limit at the modifier line level.

Note: If the effective end date for a modifier has been reached, you can still attach limits. However the modifier and associated limit will not be applied if the limit date is expired.

Caution: The Automatic box for the modifier line must be enabled so that the List Limits button or Line Limits button can be clicked.

The following conditions must be fulfilled before you can enter limits for a modifier line:

■ At least one line modifier must be listed in the Modifiers Summary tab before entering a line limit. Otherwise the Line Limits button is grayed out.

■ You can only create Line limits for the following modifier types: Discount, Price Break Header, and Surcharge. Line limits cannot be created for the following Modifier Types: Other Item Discount, Promotional Goods, Coupon Issue, Item Upgrade, or Term Substitution.

■ The Automatic box for the modifier line must be selected, and the Override Flag must be cleared otherwise you cannot enter a limit for the modifier.

Modifiers 3-171


Figure 3–56 Define Limits window

The Num is a unique limit number that defaults automatically to identify the limit transaction.

3. Select the Basis for the limit. The basis defines the type of limit that is applied and how the consumption is measured. For example, if the basis is Accrual Units, the limit is calculated by the number of units accrued such as 4000 air miles. You can select from the following available bases:

■ Accrual Units: For example, each customer accrues 100 air miles for each 10 currency units spent up to a limit of 5000 air miles per customer.

■ Discount Cost: For example, when the cost of the promotion has exceeded $50,000, the promotion ends.

■ Gross Revenue: For example, each customer receives the promotion for the first $250 that they order from the website.

■ Item Quantity: For example, a customer receives $10 off a case of 12 one-gallon cans of orange juice for the first 1000 cases.

■ Usage: Usage can be based by customer, promotion, or both customer and promotion:



■ Customer: For example, each customer cannot get a promotion more than 5 times.

■ Promotion: For example, promotion is available on the first 25 orders placed.

■ Promotion and Customer: For example, promotion is available to the first 25 different customers who place an order.

When a pricing request is processed, the pricing engine checks each request against the limit to see if it exceeds the limit and applies the amount of the benefit against the limit.

4. Select how you want the limits enforced:

■ Select Across the Current Transaction if you want the pricing engine to maintain a consumption record for each order that consumes the limit.

■ Select Across All Transactions if you want the pricing engine to maintain one consumption record for all orders that consume the limit.

5. Enter the amount of the limit. You can increase or decrease an existing limit; however, you cannot decrease it lower than the amount by which the limit has been consumed. For example, if two orders each for 100 currency units have consumed the limit, you cannot lower the limit below 200.

6. The Unit field defaults to a unit of measure that corresponds to the Basis selected: for example, a currency unit such as USD (US dollars) for Gross currency.

7. Select a constraint to restrict the limit to a product or qualifier attribute:

■ Select Product Attribute to set limits for a specific product(s).

■ Select Qualifier Attribute to set limits for a qualifier such as a customer, modifier list, or order.

8. To filter limits by sales organization, select By Organization. If enabled, the organization for the transaction and modifier must match before the limit can be applied. This enables you to restrict limits to transactions for your organization.

Note: Even if the transaction is ineligible to receive the limit, it may be eligible to receive the modifier.

Modifiers 3-173


9. You can select additional criteria from the Constraint, Context, and Attribute fields to restrict eligibility for limits by certain products or qualifiers. For example, the following setup can be used to define eligibility by customer name:

10. Select Constraint 1 which can be either a product or qualifier attribute.

11. Select a Context for the product or qualifier constraint.

12. Select an Attribute for the Context. For example, if the Context is Customer, you can select Customer name as the Attribute to restrict the limit by customer name.

13. You can define additional product or qualifier attributes in the Constraint 2, Context 2, and Attribute 2 fields.

14. The When Exceeded field determines the handling action if a pricing request exceeds the promotional limit. The initial value automatically defaults from the profile option QP: Limit Exceed Action that is set up by the System Administrator. Optionally, if you do not want the default, you can select a different handling action:

■ Hard - Adjust Benefit Amount: Adjusts the order benefit amount so that the order meets but does not exceed the promotional limit. For example, if a customer close to their promotional limit places a new order that exceeds the limit amount, the customer receives the benefit only until the amount is reached.

■ Soft - Full Benefit Amount: Applies the full benefit to the order and then sends a status message to place a promotional hold on the order. For example, if a customer close to their promotional limit places a new order that exceeds their limit amount, under a soft limit the customer gets the full promotion benefit applied to the order. A status message is sent to the

Table 3–35 Example of Constraint, Context, and Attribute

Constraint Context Attribute

Qualifier Attribute Customer Customer name

Note: If you select Constraint 2, Context 2, and Attribute 2 or additional criteria, an and operator is introduced which means that all criteria must be met before the limits are applied.



calling application (such as order management) that the limit has been exceeded.

15. In the Hold? field, select one of the following hold actions:

■ Select Hold? to have a status message sent to the calling application (such as order management) when the limit is exceeded.

■ Unable the Hold? box so that the pricing engine does not place a promotional hold.

16. Save your work.

17. Optionally, click Other Attributes to display the Define Attributes window to define additional criteria.

Figure 3–57 Define Attributes window

Note: If the Soft - Full benefit amount is selected in the When Exceeded field, then the Hold? box is automatically enabled and cannot be updated.

Note: If Balances exist for a limit, the Other Attribute button is grayed out and you cannot add other attributes.

Modifiers 3-175


For example, if you have selected customer and customer name and want the limit applied to a particular customer, select the customer name from the Value field.

18. Save your work.

Note: To qualify for a limit, all the qualifier conditions must be met. Otherwise, the limit will not be applied.



Viewing Limit Balances and Transaction DetailsOracle Advanced Pricing enables you to view balances including the amounts available and consumed (used) for a selected limit or across transaction limits. For a selected balance, you can view the transactions that have consumed the balance. The available balance is calculated using the following formula:

Available balance = Limit Amount - sum of (Consumed Amounts from saved Transactions)

Manual versus Automatic Updating of Limit BalancesFor most transactions, limit balances are updated automatically when orders are re-priced or when the limit amount is changed. However, some balances must be manually updated to reflect the new balances: for example, for returned, cancelled, and deleted orders or when a manual transaction is added to adjust limit balances. To update the limit balances manually, you must click Update balances to view the updated balance.

As transactions are processed, cumulative promotional spending is subtracted from the available limit balance. The pricing engine updates the available balance for transactions that complete successfully such as a booked order line or transactions in progress; for example, a sales order line that is entered but not saved or booked.

However, if a transaction in progress was rolled back or exited abnormally from a calling application (for example, Order Management), the balance is still updated and therefore the available limit balance may not reflect the true balance. When this occurs, you must manually update the balance to reflect the true balance.

Once the order or order line is saved and booked, then the available limit balance is reduced by the amount of the completed transaction(s).

Modifiers 3-177


To view a limit balance:1. Navigate to the Define Limits window.


The limits and their balances display in the Balances region. If the limit is arranged by category such as sales organizations, product attributes, or qualifier attributes, one limit balance displays for each category.

The Available field displays the amount of the limit or sub-limit remaining. If the limit is set up by category, then the following Organization (Org) fields display:

■ Org Context: Displays the sales organization for the sub-limit balance.

■ Org Attribute: Displays the product attributes/qualifier attributes for the sub-limit balance.

Note: A limit and sub-limits only appear if transactions have posted against them.



■ Org Value: Displays the product attributes/qualifier attributes for the sub-limit balance.

■ Org Meaning

To view limit transaction details:1. Navigate to the Define Limits window.

2. In the Balances section, select the balance whose transaction details you want to view.

3. Click Transactions to display the Define Transactions window.

Figure 3–59 Define Transactions window

The following fields are defined:

■ Date Request: Display the date the transaction occurred.

■ Price Req Code: Displays the pricing code automatically for an Automatic transaction. You can enter a pricing code manually for a Manual transaction.

■ Manual: Enabled if a manual transaction has been added. You can update, delete, or add a manual transaction.

■ Amount: Displays the amount of the limit consumed.

Note: The Define Transactions window only displays if there are transactions applied against the limit. Transactions display after you save a sales order.

Modifiers 3-179


■ Request Type: Displays the name of the calling application such as Order Management.

■ Reason: Displays a reason (if applicable) for the transaction. You can enter a manual reason which is used especially in manual adjustments.

Note: In the Define Transactions window, you can choose to adjust the limit balance by manually adding new transactions or updating existing manual transactions. A limit transaction created by the Pricing engine cannot be updated or deleted. Only manual transactions can be added, update and deleted.



Updating an Existing Limit BalanceOracle Advanced Pricing provides a running available balance so you know the amount consumed (used) and available for a selected limit. Balances for limits are updated automatically when orders are re-priced or when the limit amount is changed.

In certain cases such as returned, cancelled, and deleted orders, the limit balances are not updated automatically and the balance must be manually updated using the Update balances button. If a manual transaction is added to adjust limit balances, you must click Update balance to view the new available limit balance.

To update an existing limit balance:1. Navigate to the Define Limits window.


2. Verify that the balances match the sum of the transactions. Click Update balance or run the concurrent process QP: Update Limit Balance.

Modifiers 3-181


3. Click Transactions to display the Transactions window. Confirm that the transactions are correctly applied to the balance.

4. To change the limit balance, enter a transaction in the Transactions window. Enter a positive quantity in the Amount field to lower the available balance or use a negative quantity to raise the available balance.

5. Recalculate the balances in the Define Limits window by choosing the Update balance button or by running the concurrent process QP: Update Limit Balance.



Enforcing LimitsOracle Advanced Pricing enables you to set up an enforcement policy to manage transactions if the promotional limits are exceeded. When the benefit amount for a transaction or transaction lines exceed the set limit or available limit balance, the default handling method resolves the situation.

The default limit enforcement is set up by the System Administrator in the QP: Limit Exceed Action profile option. You can accept the default or optionally, select an alternate handling method. The following limit handling methods are available:

■ Hard - Adjust Benefit Amount: Any partial benefit available will be given up to the limit. A promotion based on Usage (number of times it is given) is considered to be a hard limit.

■ Soft - Full Benefit Amount: The full benefit of the promotion is given and a message is sent to the calling application to advise that the limit has been exceeded. If a limit is exceeded, then the order header and lines need to be placed on a promotional limit hold until appropriate business processes allow progression of the entire sales order. These processes may involve adjusting the promotional limits or repricing the order.

In addition to setting hard and soft limits you can also make the following adjustments when the limit is exceeded:

■ Adjust the limit up or down while the enforcement is operating.

■ Deactivate the promotion or increase the remaining available limit.

Modifiers 3-183


Adjusting the Limit AmountYou can increase or decrease an already existing limit for a promotion, deal, or modifier and have the adjustment reflected in the available balance. However, you cannot decrease it lower than the amount by which orders have consumed it. For example, if two orders, each for $100 have consumed the limit, you cannot lower the limit below $200.

If the promotion, deal, or modifier is inactive because the limit was previously exceeded, the promotion, deal, or modifier will be re-activated once the limit is increased.

Note: A limit (header or line level) that has been created by a different source system code cannot be updated or deleted by a user who has logged in using a different source system. For example, if a limit was created for a modifier by a Trade Management user, the same limit can only get updated or deleted by a Trade Management user. A user logged in Advance Pricing can view limits for the modifier but cannot edit the existing limits.



To adjust the limit amount:1. Navigate to the Define Limits window.


2. Enter the new Amount for the limit. If decreasing the limit, you cannot decrease it lower than the amount by which orders have consumed it.

Modifiers 3-185



Form

4
Formulas
This chapter describes formulas and includes following topics:

■ Overview of Formulas on page 4-2.

■ Creating a Pricing Formula on page 4-3.

■ Finding Formula Factor Lines on page 4-12.

■ Updating Formula Prices on page 4-14.

ulas 4-1

Overview of Formulas

Overview of FormulasFormulas consist of mathematical expressions that the pricing engine evaluates to calculate the list prices of items and discounts applied to them. Formulas can be linked to a price list line or modifier line. You can use formulas to:

■ Create a price from a computation as an alternative to entering prices in a price list.

■ Calculate a price adjustment. For example, you can instruct the pricing engine to calculate a discount by attaching a formula to a discount line.

■ Set up and maintain formulas based on component types.

When you attach a formula to a price list line, you typically do not enter a price for that line because the pricing engine uses the formula to calculate the final list price of the product or service. One exception is a formula that has a list price as Formula Type: in this case, you must enter the list price (base price) for the formula to use in its calculations.

You can choose one of following methods to determine how a formula calculates the price:

■ Dynamic calculation: The list price resulting from the formula calculation is not calculated or stored anywhere until the sales order is entered with that Price List line item. When the sales order is entered, the pricing engine evaluates the formula and displays the final list price on the order.

■ Static calculation: If the formula is attached to a price list line for static calculation of the final list price, you can run a concurrent program at any time to calculate the final list price using the formula up front (not wait until order entry time) and also store it in the price list.

Seeded FormulasOracle Advanced Pricing provides seeded formulas that you can use when setting up freight charges. For more information, see the Oracle Advanced Pricing Implementation Manual.

Note: You can attach a formula that has a List Price component to price list lines and to modifier lines. For more information, see: Oracle Advanced Pricing User’s Guide, Price Lists and Modifiers chapters.


Creating a Pricing Formula

Creating a Pricing FormulaYou can set up and update formulas and formula lines in the Advanced Pricing - Pricing Formulas window. A formula is a valid mathematical expression used to determine the list prices of items and the discounts applied to those items. The formula lines provide details about each part of the formula.

A formula can contain any of the following:

■ Parentheses: for example, (and)

■ Mathematical operators: for example, +, -, /, and *

■ Built-in functions: for example, NVL, SQRT, and MOD

■ Operands: Operands are step numbers about which you provide more detail. You can use as many step numbers as you need, up to the limit of the field. You can repeat a step number in a formula, for example, 1+2*2.

For example, the valid formula (1+2*SQRT(3)) / 4 contains:

■ Operands: 1, 2, 3, and 4

■ Mathematical operators: +, *, and /

■ Built-in function: SQRT

■ Parentheses: to group the operands and operators

For each preceding step number, you need to create four formula lines since the formula has four step numbers.

Oracle Advanced Pricing uses the formula line and evaluates it to obtain the value of the operand and calculates a formula. It does not use the face value of the step number.

Note: The concurrent program Build Formula Package should be run if a new formula expression is created

Note: An operand is not a numeric constant. If you want to use a numeric constant in a formula, you must create a step number in the formula expression and then assign the numeric constant to the step number in a formula line

Formulas 4-3


You assign one of the following types to each formula line:

■ Function: The function GET_CUSTOM_PRICE retrieves a price from an external system and uses it in the formula calculation. You create the program logic to map to the external data source by developing PL/SQL program packages. The function GET_CUSTOM_PRICE returns a numeric value.

■ List price: The price of the item in a specific price list to which you have attached a formula.

■ Factor List: A list of factors that you can link to multiple pricing attributes or a range of these attributes. The pricing engine evaluates the formula, then chooses one of these factors depending into which range the actual pricing attribute of the item falls.

For example, a step in the formula may have different factors defined for different ranges of glass thickness: a glass with thickness between 0.1 and 0.3 mm has a factor of 3 and a glass with thickness between 0.4 and 0.8 mm has a factor of 5. The pricing engine determines which factor qualifies when it evaluates an order and applies this factor in the formula calculation.

You can also relate multiple factor conditions. For example, if the base pricing attribute for glass thickness is between 0.1 and 0.3 mm AND the length of the glass is between 0.5 and 2 m, apply the factor of 3 OR if the base pricing attribute for glass thickness is between 0.4 and 0.8 mm AND the length of the glass is between 0.5 and 2 m, apply the factor of 5.

■ Modifier Value: Uses the value that is entered in the Value field from the Advanced Pricing - Define Modifier window > Discounts/Charges tab.

■ Numeric Constant: A numeric value.

■ Price List Line: The price of the item in a specific line of a specific price list.

■ Pricing Attribute: The absolute value of a pricing attribute (such as thickness or height) of an item.

Pricing attributes are characteristics of products and services that you can specify when the characteristics help to determine the price of a product or service. Distance, age of a related product, customer class, product family

Note: Advanced Pricing formulas supports all the functions supported by PL/SQL. For more information on PL/SQL functions, see: Oracle9i SQL Reference, Release 2 (9.2), Functions.



group, and level of service are examples of pricing attributes. You can specify one or a combination of pricing attributes and assign them to a product or service. At order entry time, the pricing engine evaluates the attributes you have specified during formula setup to calculate the price.

You can define as many attributes as you need to meet your pricing business needs. For example, you may use the formula 1*2 to calculate the price of a glass item. Step 1 is a pricing attribute for thickness and step 2 is the list price to calculate the price of a glass item; if 100 is the base price of the glass item and 0.3 is the value of the thickness attribute of the glass then the pricing engine evaluates the formula as 0.3*100 which is 30.

Null Values in FormulasDuring formula calculation, if a step results in a null value, the formula fails. For example, in the formula 1*2, step 2 is of type Pricing Attribute, pricing attribute context is Physical Attribute, pricing attribute is Volume, and the user should supply the volume at order entry time.

Since the user may not provide a volume use the NVL expression in the formula to point to a step that evaluates to a non-null value. Change the formula to 1* NVL(2,3). In the formula line for step number 3, arrange for a non-null value, for example the numeric constant 8. If the user does not provide a value for volume, the pricing engine uses 8 in the formula calculation.

If the expression does not use NVL in the expression, and the step number evaluates to NULL, the entire expression evaluates to NULL, the formula calculation fails, and the calling application processes the failure.

GET_CUSTOM_PRICEThe following diagram illustrates the GET_CUSTOM_PRICE function. It shows several formulas which reference price lists and discounts. When the pricing engine evaluates a formula, it passes the formula, price list, and discount information to GET_CUSTOM_PRICE. GET_CUSTOM_PRICE returns a value, the pricing engine uses that value to calculate the formula and returns the formula value to the calling application.

After the diagram, the text explains the GET_CUSTOM_PRICE function in more detail.

Formulas 4-5


Figure 4–1 Get Custom Price

To use the Function formula type, modify the function GET_CUSTOM_PRICE. Write custom code in the function body that uses the standard input parameters. You can only write a function body that returns a number.

You can use the GET_CUSTOM_PRICE function in more than one formula. The formula ID is an input parameter which you can use to differentiate code logic among formulas.

To use the return value in a formula, do the following:

■ Set up a formula having a formula line of type Function.

■ Set the system profile option QP: Get Custom Price Customized to Yes at the Site level. If the pricing engine evaluates custom code within the GET_CUSTOM_PRICE function and the profile option is No, the formula calculation fails, and the calling application processes the failure.



GET_CUSTOM_PRICE is in the package QP_CUSTOM and its specification is QPXCUSTS.pls. QP_FORMULA_PRICE_CALC_PVT calls QP_CUSTOM.Get_Custom_Price().

The pricing engine passes the parameters to the function. You may not change the GET_CUSTOM_PRICE parameters which are:

■ p_price_formula_id: Primary key of the formula that uses the Get_Custom_Price function.

■ p_list_price: List price on the price list line to which the formula using Get_Custom_Price is attached. May be null.

■ p_price_effective_date: Pricing Effective Date, the date for which the pricing engine is evaluating the formula.

■ p_req_line_attrs_tbl: PL/SQL table of records containing context, attribute, and attribute value records for product and pricing attributes and a column indicating the type (Product Attribute or Pricing Attribute). The engine passes only the pricing and product Attributes of the price list line to which the formula is attached.

Formulas 4-7


To create a pricing formula:1. Navigate to the Advanced Pricing - Pricing Formulas window.

Figure 4–2 Advanced Pricing - Pricing Formulas window

2. Enter a Name and Description for the formula.

3. Enter the Effective Dates range.

4. Enter a Formula expression. A formula consists of step numbers (such as 1, 2, 3) used in an arithmetic equation such as 1*2.

A step number such as 1 in the formula expression corresponds to the formula line with the same step number in the Formula Lines region.

The Seeded box identifies if the selected formula is seeded.

5. Every time a new formula expression is created, the concurrent program Build Formula Package should be run to generate the formula package.

From the Tools menu, select Build Formula Package to run the program. Alternately, you can also run the Build Formula Package concurrent program. A



Dialog box displays a message if the formula package generation was successful.

6. Save your work.

In the Formula Lines region, you create formula lines and assign a Step number that can be used in the Formula expression. Complete the following steps for each formula line to be created.

7. Select one of the following Formula Types:

■ Function: The Component field displays GET_CUSTOM_PRICE. You must write the function in this PL/SQL package and it must return a number. See Get Custom Price on page 4-6 for an overview of GET_CUSTOM_PRICE.

■ List Price: The price of the item in a specific price list to which you have attached a formula.

■ Factor List: Select an existing factor list in Component field. Alternately, to create a new factor list, type a new name in the Component field, and press the Enter key. When you complete your entries for the formula line, click Factors to create the factor criteria in the Factors window.

■ Modifier Value: A formula which has a Modifier Value as a component cannot be attached to a price list line.

■ Numeric Constant: Enter the numeric constant in Component.

■ Price List Line: A formula which has List Price as a component and is attached to a price list line gets the list price from the Value entered in a price list line.

■ Pricing Attribute: Select the Pricing Attribute Context and Pricing Attribute.

8. Enter the Step number for the formula expression. Step numbers cannot be repeated in the Formula Lines region even though they can be repeated in the Formula expression.

The Seeded box is selected for seeded formula lines.

9. The Reqd Flag check box is currently not used by the pricing engine except if you are using custom code for tracking formula line information. If you are using custom code for this purpose, then select the Reqd Flag check box.

10. Save your work.

Formulas 4-9


To define factor list details:1. If the Formula Type is Factor List, click Factors in the Advanced Pricing -

Pricing Formulas window to display the Factors window.

Figure 4–3 Factors window

In the Base Pricing Attributes region, complete steps 2-9 for each base pricing attribute factor. See: Finding Formula Factor Lines on page 4-12 for information on searching for formula factor lines.

2. Select a value for Base Pricing Attribute Context.

If you have multiple entries, you must use the same base context in this region (to create an OR condition); the pricing engine chooses one of the entries. Use the Associate Pricing Attributes region to associate additional contexts with the base context (to create an AND condition where both attributes must be present to qualify).

3. Select a value for Base Pricing Attribute.

4. Select a comparison Operator and enter the Value From/To:



■ If you select the operator BETWEEN, you must enter a Value From. If you do not enter a value for Value To, it defaults to unlimited.

■ If you select =, you must enter Value From and you cannot enter Value To.

5. Enter the Adjustment Factor. An adjustment factor enables you to adjust the price based on the options selected. For example, if you are selling cars, you could use adjustment factors to adjust the price based on the car options the customer chooses:

■ If the car options are Standard then the price is multiplied by 1 (factor=1)

■ If the car options are Business then the price is multiplied by 1.5 (factor=1.5)

■ If the car options are Deluxe then the price is multiplied by 2 (factor=2)

If the cars you are selling are second hand, you probably want to adjust the price further based on the age of the car. For example:

■ If the car is between 0.0 and 1.0 years old, the price is multiplied by 1.

■ If the car is between 1.1 and 3.0 years old, the price is multiplied by 0.8.

■ If the car is older than 3.0 years, the price is multiplied by 0.6.

6. Enter Start/End Date range for this attribute in this factor list.

Complete the following steps for each associated pricing attribute.

7. In the Associate Pricing Attributes region, select an Associated Pricing Attribute Context and Associated Pricing Attribute to associate with the base pricing attribute context and base pricing attribute values (to create an AND condition).

8. Select a comparison Operator and enter the Value From/To:

■ If you select the operator Between, you must enter a value for Value From. If you do not enter a value for Value To, it defaults to unlimited.

■ If you select =, you must enter Value From and you cannot enter Value To.

9. Save your work.

Note: The effectivity of this pricing attribute in this factor list also applies in all other formulas that use this factor list.

Formulas 4-11

Finding Formula Factor Lines

Finding Formula Factor LinesA factor list can consist of hundreds of factor lines and associated base pricing attributes. If your business requirements require you to change the values of certain pricing attributes, it is time consuming to scroll through the entire factor list to find a required record. Instead use the Find Formula Factor Lines window to selectively retrieve the records you want.

You can narrow your search by selecting search criteria that defines the factor line you want to retrieve. You can query by Pricing Context, Pricing Attribute, Query Operator, and Pricing Attribute Value.

The query returns all those factors in the factor list which has either a base or an associated pricing attribute that meets the query criteria. The results are sorted by the Pricing Attribute Value From of the Base Pricing Attribute of the factor lines that are returned by the query.

To find formula factor lines:1. Navigate to the Find Formula Factor Lines window.

Figure 4–4 Find Formula Factor Lines window

2. Enter the Factor Pricing Attribute Context for the query such as Item.

3. Enter the Factor Pricing Attribute such as or Item Category or Customer Item.

4. Enter the Query Operator such as = or Between. The = operator returns an exact match while the Between operator returns a range of values. If the Pricing


Finding Formula Factor Lines

Context on the Query Find window is Item and the Pricing Attribute is either Item Number or Item Category, then the Query Operator is restricted to the value =.

5. Enter a Pricing Attribute Value From High/Low to define the range of values you want queried; for example, to restrict a query to a range of item numbers from 23456 to 45674. However, if the = operator is selected you can only enter a value for Pricing Attribute Value From Low.

6. Click Find to return the query results.

7. Alternately, to start a new query, click Clear to clear the current query criteria and enter your query criteria.

8. Click New to create a new Base Pricing Attribute.

Formulas 4-13

Updating Formula Prices

Updating Formula PricesUse this process to use static formulas to set list prices. When you attach a formula to a price list line, you can select from the following calculation methods:

■ Dynamic calculation: When you enter an order the pricing engine uses the formula to calculate list price.

■ Static calculation: Prior to order entry, you execute a concurrent process which calculates the list price.

To update formula prices for static calculation:1. Navigate to the Update Formula Prices window.

Figure 4–5 Update Rule Prices window

2. To calculate formula-based prices:

■ For price list lines whose formulas have been added or changed from when they were last updated by this concurrent program, select New and Modified Lines Only of Price Lists.

■ For all price list lines, clear New and Modified Lines Only of Price Lists.

3. To consider price list lines that have:

■ Any formula, select Update All Pricing Formulas for Price Lists.

■ A certain formula, select Update Individual Pricing Formula for Price Lists, and select the specific Pricing Formula.

The process applies this choice after it selects the price list lines according to the criteria for Step 2.



4. Click Submit to display the Request ID.

Formulas 4-15



Price

5
Price Lists
This chapter describes price lists and includes the following topics:

■ Overview of Price Lists on page 5-2.

■ Using Price Lists in the HTML User Interface on page 5-2.

■ Secondary Price List on page 5-4.

■ Creating a Price List on page 5-6.

■ Creating a GSA Price List on page 5-29.

■ Adding Items to a Price List on page 5-36.

■ Adjusting Prices for a Price List on page 5-39.

■ Copying a Price List on page 5-42.

■ Copying a Price List Line on page 5-45.

■ Oracle Advanced Pricing Home page (HTML Interface) on page 5-46.

■ Creating a Price List (HTML Interface) on page 5-50.

■ Creating Price List Lines (HTML Interface) on page 5-55.

■ Creating Price Breaks for a Price List Line (HTML Interface) on page 5-59.

■ Searching for Price Lists (HTML Interface) on page 5-66.

■ Updating Price List Lines (HTML Interface) on page 5-73.

■ Archiving, Deleting, and Purging Price List Information on page 5-77.

■ Using the Price List Maintenance feature (HTML Interface) on page 5-78.

■ Searching for Price Lists and Price List Lines (HTML Interface) on page 5-80.

Lists 5-1

Overview of Price Lists

Overview of Price ListsPrice 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 item and/or item category prices. Basic 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.

Using Price Lists in the HTML User InterfaceOracle 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 only using the Oracle Forms-based interface. Tasks that can be completed in HTML are identified by (HTML Interface) in the task title, for example, Creating a Price List (HTML Interface).

See:Using Oracle Advanced Pricing in the HTML Interface on page 1-6

Using Price Lists in the HTML User Interface on page 5-49

Oracle Advanced Pricing Implementation Manual, Pricing Security

Note: You can only view or update a price list for your pricing transaction entity. The profile QP: Pricing Transaction Entity must match the pricing transaction entity of the price list.

You can only view or update a price list in your source system. The profile QP: Source System Code must match the source system of the price list. Otherwise, the price list is view-only.

The profile option QP: Selling Price Rounding Options affects the rounding of adjustments. For more information on this and other profile options, see: Oracle Advanced Pricing Implementation Manual, Profile Options.



Price List TermsThe following defines common price list terms that you will see when setting up and maintaining price lists:

Effective DatesPrice lists can have starting and ending dates. This enables you to prepare price lists ahead of when they are valid and to ensure they are not used until their start dates.

Inactive Price ListsYou can temporarily or permanently inactivate a price list by clearing the Active box. For Inactive price lists, you can still do the following actions:

■ Query the inactive price list: When querying, the Active box is enabled, but the underlying value is null. To retrieve only inactive price lists, clear the Active box; to retrieve only price lists that are active, clear the Active box, then select it.

■ Update it

■ Base a formula on an inactive price list

CurrencyIf you have global customers or do pricing in different currencies, the multi-currency feature enables you to maintain a single price list for multiple currencies. See Overview of Multi-Currency Conversion Lists on page 7-2 for more information on multi-currency price lists.

Round ToThe Round To value defines the number of places to the right or left of the decimal point to which the pricing engine rounds prices from price lists and modifiers from modifier lists:

■ A positive number such as 2 indicates the number of places to the left of the decimal point. For example, a round to factor of 2 indicates rounding to the nearest hundreds so 107 rounds to 100.

Note: The pricing engine does select inactive price lists when doing a pricing request. Other applications can call an inactive price list and use relevant information.

Price Lists 5-3


■ A negative number such as -3 indicates number of places to the right of the decimal point. For example, a round to factor of -3 indicates rounding to the nearest thousands so 1.1445 rounds to 1.145.

The pricing engine rounds the base price and all discount amounts before using them in calculations.

You can limit the rounding factor value by the number of positions you specify in the extended precision format of the price list’s currency. The value returned depends on the value that was set for the profile option QP: Unit Price Precision Type:

■ Standard: The rounding factor defaults to the currency's precision value. You can override the rounding factor to any value greater than or equal to the currency's precision value.

■ Extended: The rounding factor defaults to the currency's extended precision value. You can override the rounding factor to any value greater than or equal to the currency's extended precision value.

For more information, see the Oracle Advanced Pricing Implementation Manual, Profile Options.

Secondary Price ListThe pricing engine uses secondary price lists when it cannot determine the price for an item using the price list assigned to an order. Primary and secondary price lists have the same currency.

If the item you are ordering is not in the primary price list, the pricing engine looks for the price on any attached secondary price list. If the item is found, the pricing engine uses the highest precedence secondary price list (the secondary price list with the lowest value in the precedence field).

Note: If multi-currency is enabled, the Round To field will be disabled and will reflect the Round To value defined for the Multi-Currency Conversion window.

Note: You can only add a secondary price list one you enter the currency for the primary price list. This ensures that the secondary price list has the same currency as the primary price list.



If an item appears in both the primary and a secondary price list with the same effective dates, the pricing engine uses the primary price list to price the item. If an item appears on the primary price list but is not active (the effective end date has passed), the pricing engine uses the price on the secondary price list.

Agreement Price ListOracle Advanced Pricing allows you to establish agreements with your customers that define the prices, payment terms, and freight terms that you negotiate.

There are two methods by which you can manage agreements:

■ Standard agreements which use standard price lists (PRL)

■ Pricing agreements which use agreement price lists (AGR)

Note: The pricing engine does not evaluate qualifiers on secondary price lists; however, some user setups may require them to be evaluated. In these cases, the System Administrator must change the profile QP: Qualify Secondary Price Lists to Yes. See Oracle Advanced Pricing Implementation Manual, Profile Options for more information.

Note: If you are unable to query or update the price list after saving or exiting from the window, consult with your Pricing Administrator for access privileges. Your security access privilege may not allow you to access the price list windows.

Price Lists 5-5

Creating a Price List

Creating a Price ListPrice lists contain item and item category prices. You can define and maintain multiple price lists.

You can define the following types of prices on price lists:

■ Unit price: A fixed price.

■ Percent Price: A price which is a percent of the price of another item.

■ Formula: Multiple pricing entities and constant values related by arithmetic operators. For example, you define the price of an item to be a percentage price of another price list line.

■ Price Break: If the price of an item varies with the quantity ordered, you can define bracket pricing or price breaks. The following table displays an example of a price setup:

Qualifier Grouping Number OptionsYou can attach both qualifiers and qualifier groups to a price list. When you attach qualifier groups, all the qualifiers in the qualifier group are attached. You can use qualifier grouping numbers to indicate to the pricing engine how to evaluate the qualifiers. For more information on qualifier groups, see: Using Qualifier Grouping Numbers on page 2-21 and Using Qualifier Grouping Numbers across Qualifier Groups on page 2-25.

Note: Oracle Advanced Pricing also provides an HTML-based user interface for setting up and maintaining price lists. See Creating a Price List (HTML Interface) on page 5-50.

If you are using the multi-currency conversion feature, see: Overview of Multi-Currency Conversion Lists on page 7-2.

Table 5–1 Example of Price Setup

Price Break Attribute Value Value From Value To

Unit Price

1 Item Number A11111 1 11 $50

2 Item Number A11111 12 100 $45



To create a price list:1. Navigate to the Advanced Pricing - Price Lists window.

Figure 5–1 Advanced Pricing - Price Lists window

2. Enter a Name for the price list.

3. Select the Mobile Download box if you are using an Oracle Mobile application and want to download specific price lists onto a mobile device such as a laptop computer. The default value is No.

Note: The price list Name should be unique across PTEs (Pricing Transaction Entities) otherwise an error occurs. For example, if a price list named "Corporate" is created in the Order Management PTE, an error message displays if you create a "Corporate" price list in the Purchasing PTE.

Price Lists 5-7


You can select or clear the Mobile Download box either when creating or updating a price list.

4. To activate the price list, select the Active box.

5. Enter a Description of the price list.

6. Select a price list Currency.

7. Enter a Round To value that is applied to the price list. A positive number indicates the number of places to the left of the decimal point. A negative number indicates number of places to the right of the decimal point. The default is -2. The pricing engine rounds the base price and all discount amounts before using them in calculations.

The value returned depends on the value that was set for the profile option QP: Unit Price Precision Type:

■ Standard: The rounding factor defaults to the currency's precision value. You can override the rounding factor to any value greater than or equal to the currency's precision value.

■ Extended: The rounding factor defaults to the currency's extended precision value. You can override the rounding factor to any value greater than or equal to the currency's extended precision value.

8. Enter the starting and ending Effective Dates for the price list.

The Start Date defaults to the current date.

9. Select the default Payment Terms.

10. Select the default Freight Terms.

The Global box is selected when the Pricing Security Control profile option is set to ON. This means that the price list can be used by all operating units for pricing transactions. If cleared, the price list’s use is restricted to the operating unit of the user creating the price list.

11. Select the default Freight Carrier.

12. Enter any Comments.



In the Other tab1. Select the Other tab.

Figure 5–2 Advanced Pricing - Price Lists window: Other tab

The Other tab displays the following information, and if applicable, details about the related Blanket Sales Agreement:

■ List Source Document Number: The Blanket Number of the blanket sales agreement associated with the price list.

■ List Source Code: Displays the code for the price list source. For example, BSO indicates Blanket Sales Order.

■ Pricing Transaction Entity: Displays the name of the pricing transaction entity creating the price list. This field cannot be updated.

■ Source System Code: Displays the code name for the source system creating the price list such as QP for pricing. This field cannot be updated.

Price Lists 5-9


■ Shareable box: Indicates if the modifier is shared or not. If non-shareable (the default), then this modifier is specific to that blanket and cannot be used with other blanket sales agreements.

If shared, the modifier is not exclusive to the blanket sales agreement and can be selected for use with other agreements. Source Document Number: This is the Blanket Number of the blanket sales agreement associated with the price list.

Once you have completed entries in the price list header, you can add price list lines that define the actual items and list prices for the price list.

See:Creating Price List Lines on page 5-11

Note: The Pricing Transaction Entity and Source System fields display for all price lists regardless of whether there is a related Blanket Sales Agreement.


Creating Price List Lines

Creating Price List LinesIn the List Lines tab of the price list, you can add price list lines to define the actual items on the price list and their list prices.

To create price list lines:1. Select the List Lines tab in the Advanced Pricing - Price Lists window.

Figure 5–3 Advanced Pricing - Price Lists window: List Lines tab

2. Select Item from the Product Context field.

3. Select a Product Attribute for the Item such as Item Number, Item Category, or All Items.

Note: Use All Items to apply the same price to all items in your product hierarchy.

Price Lists 5-11


4. Enter a Product Value for the selected product attribute.

5. The UOM (unit of measure) field defaults from the item master of the validation organization. You can change it to any valid unit of measure for that item.

6. Select the Primary UOM box to select the primary pricing unit of measure for the item.

For example, an item (such as item A11111) in a price list may have two price list lines: one with a UOM of Each (EA)—the primary UOM—and the other with a UOM of Boxes. The pricing engine uses the pricing Primary UOM and the Oracle Inventory UOM conversion information to price an order whose unit of measure does not have a price list line. If an order for item A11111 is placed in the unit of measure Case (CS), the pricing engine accesses the unit of measure conversion tables to convert Case to Each (EA).

7. Select one of the following Line Types:

■ Price Header: To set up price breaks for the item.

■ Price List Line: To enter a base list price for the item.

8. If you selected Price Header as the Line Type, select the Price Type:

■ Point: The pricing engine charges each unit of volume at the price of the within which the total falls.

■ Range: The pricing engine charges each unit of volume at the price of the within which it falls.

9. Choose an Application Method:

■ Block Price: This method is enabled only if Price Header is selected as the Line Type. Defines the price for the entire set of a block. See Defining Price Breaks with Block Pricing (for application method Block Price) on page 5-23 for more information on setting up and using block pricing.

■ Unit Price: Defines the price for inventory items and item categories

10. Enter a Value which is typically the base list price of the item.

Warning: If the QP: Price Rounding profile option is set to Enforce Currency Precision, and you enter a list price (in Product Value field) greater than the precision amount allows, you will be unable to save the price list. An error message only displays when you try to save the price list, not when you first enter the list price.



If Price Header is selected as the Line Type, you cannot enter the Value (price) at the list line level. Instead, click Price Breaks to enter price ranges.

11. Enter either a Static Formula or Dynamic Formula. If Price Header is selected as the Line Type, you cannot select a formula.

■ For Static Formulas, run the Build Formula Package program to calculate the value. The result of the calculation changes the Value.

■ For Dynamic Formulas, you only need to enter Value if the formula includes list price as one of the formula components. At pricing time, the pricing engine calculates the price of the item using the formula. If the formula does not return a price, the engine uses the value of Price as the price.

12. Enter the Start Date and End Dates for the price list line. The dates should be within the effective start and end dates of the price list.

This Precedence value defaults based on the product attribute selected.

The pricing engine uses precedence values to resolve conflicts if more than one price list line is selected from a price list.

13. Save your work.

See:Defining Price Breaks for a Price List Line on page 5-19

Defining Price Breaks with Block Pricing (for application method Block Price) on page 5-23

Build Formula Package program on page 10-7

Price Lists 5-13


To define pricing attributes:1. Click Pricing Attributes in the List Lines tab to display the Pricing Attributes

window.

Figure 5–4 Pricing Attributes window

2. Select a Pricing Context and Attribute for the selected product.

3. Select an Operator value: =, not=, or BETWEEN.

4. Enter Value From.

5. Enter a value for Value To, if the Operator is BETWEEN.

6. Save your work.

Note: The pricing attributes are joined as AND conditions since they apply to one price list line.



To select a secondary price list:1. In the Secondary Price List tab, select a Secondary Price List.

Figure 5–5 Advanced Pricing - Price Lists window

If the item you are ordering is not in the primary price list, the pricing engine looks for the price on any attached secondary price list. If the item is found, the pricing engine uses the highest precedence secondary price list (the secondary price list with the lowest value in the Precedence field).

2. Save your work.

Note: The pricing engine does not evaluate qualifiers on secondary price lists; however, some user setups may require them to be evaluated. In these cases, the System Administrator must change the profile QP: Qualify Secondary Price Lists to Yes. See Oracle Advanced Pricing Implementation Manual, Profile Options for more information.

Price Lists 5-15


To create qualifiers:1. Select the Qualifiers tab.

Figure 5–6 Advanced Pricing - Price Lists window: Qualifiers tab

2. Enter a qualifier Grouping Number. Qualifier lines with the same grouping number generate an AND condition and qualifiers with different grouping numbers generate an OR condition.

For more information on qualifier grouping numbers, see: Using Qualifier Grouping Numbers on page 2-21.

3. Select the Qualifier Context.

4. Select the Qualifier Attribute. For example, if you selected Qualifier Context = Volume, then all the qualifier attributes for volume are listed (except Order Amount which cannot be used).

5. Enter an Operator and Value From/To.



The Value From Meaning field displays additional details of the qualifier when you query a qualifier after saving it. For example, if the context is CUSTOMER and the attribute is Ship To, the Value From field displays the customer name and Value From Meaning field displays the site use location for the customer. If the context/attribute combination has no additional details, Value From and Value From Meaning are identical.

6. Enter a range for the Start/End Dates.

Note: Some list of values for qualifiers (such as Customer) may have large value sets that may prolong your query. To reduce the the number of items that display in the list of values, enter additional search criteria in the field.

If you do not enter search criteria and click a list of values, a Decision window advises that you have not entered search criteria and that the search may take a long time:

■ To display a reduced list of values, click No, enter search criteria, and click the list of values.

■ To display the entire list of values, click Yes.

■ If you do not want to see the list of values, click Cancel.

Set the profile option QP: Valueset Lookup Filter to avoid this message.

Price Lists 5-17


To copy qualifier groups (to the price list):1. In the Qualifiers tab (Price Lists window), click Copy Group to display the

Qualifier Groups window:


2. Select the qualifier group(s) whose qualifiers you want for the price list.

3. Select one of the grouping options: Retain Grouping Numbers Across Qualifier Groups or Generate Unique Grouping Numbers Across Qualifier Groups. For more information, see: Using Qualifier Grouping Numbers across Qualifier Groups on page 2-25.

4. Click OK to copy the qualifiers from the selected group(s) to the price list. The qualifiers display in the Qualifiers tab. The name of the originating Group associated with the qualifier displays in the Group field.

5. Save your work.

Note: After selecting the qualifier groups, confirm that the grouping numbers display the correct combination of AND and OR conditions



Defining Price Breaks for a Price List LineYou can use price breaks or "bracket pricing" to define prices that vary with the quantity ordered. For example, if you buy up to 10 items the price is $20 per item, but if you buy more that 10 items, you get a lower price per unit.

The following table displays an example of a price break setup:

When setting up price breaks, you can define price breaks as either Point or Range breaks:

Point breakDefines prices based on the price bracket in which the total quantity falls.

For example, if you ordered 16 units of Item A11111, the total quantity falls into the Price 2 bracket where the unit price is $45. So the total price is calculated as follows:

Total price = 16 * $45 each = $720

Range breakDefines prices based on the ranges of the defined price breaks. For each range, the engine calculates a price and sums across all ranges to obtain the list price.

For example, if you ordered 16 units of Item A11111, the unit price from each price (Price Breaks 1 and 2) is applied as follows:

■ Price I: For the first 11 units * $50 each (unit price from Price 1) = $550

■ Price 2: The remaining 5 units * $45 each (unit price from Price 2) = $225

Total price = $550 + $225 = $775

Note: If you define a price for an Item Category, then all items within the category are eligible for the price break.

Table 5–2 Price Breaks window setup

Price Break

Pricing Context

Pricing Attribute

Value From-To Price

Application Method

Recurring Value

1 Volume Item Quantity 1-11 $50 Unit Price -

2 Volume Item Quantity 12-99999 $45 Unit Price -

Price Lists 5-19


To define price breaks:1. Click Price Breaks in the List Lines tab of the Price Lists window to display the

Price Breaks window.

Figure 5–8 Price Breaks window

The Pricing Context is Volume (default), and the Pricing Attribute is Item Quantity. Optionally, select a different Pricing Attribute.

Complete the following steps for each price break to be defined:

2. Enter a Value From/To. To create no upper limit, enter all 9’s in Value To.

Note: Before setting up price breaks, the following must be selected in the Price Lists window:

■ Line Type: Price Header

■ Application Method: Unit Price or Block Price

Note: You cannot create overlapping price ranges in the Value From/To fields; for example, if one range is 1 to 11, you cannot have another range that is 5 to 20.



3. Enter a Price:

■ For inventory items and item categories, enter the base list price of the item.

■ For service items: If the Application Method is Unit Price, enter the base list price of the item. If Application Method is Percent Price, enter a percent of another item's price.

4. Select an Application Method:

■ Unit Price: For inventory items and item categories.

■ Percent Price: For service items. You will only see Percent Price as an Application Method if the price list line is a service item.

■ Block Price: See: Defining Price Breaks with Block Pricing (for application method Block Price) on page 5-23 for information on setting up price breaks with Block Price.

Warning: If the ordered quantity does not fall in the price range of the price list, the price is still calculated and defaulted in the sales order line. Ensure that the price ranges are set up correctly to get the pricing results you desire:

For example, suppose you create the following range price breaks for price list Item AS54888 with the Application Method of Unit Price:

■ Value From/To: 1 to 5 Price: 1.00 each

■ Value From/To: 6 to 7 Price: .75 each

If the Price Type is Point: The price is not returned if the ordered quantity does not fall in the price range of the price list.

If the Price Type is Range: A price of 0 is retrieved for the ordered quantity that does not fall in the price range.

If a Sales Order for 10 items of AS54888 were placed, the price would be calculated as follows ( Price Type is Range):

(5*1) + (2*0.75) + (3*0)/10 = 0.65 Unit Price

Notice that the last 3 items fall out of the price range and therefore a unit price of 0 is returned. Therefore it is important that the price breaks are set up correctly to get the desired price results.

Price Lists 5-21


5. Save your work.

See:Defining Price Breaks with Block Pricing (for application method Block Price) on page 5-23



Defining Price Breaks with Block Pricing (for application method Block Price)Block pricing enables you to apply a lumpsum price rather than a per unit price to a pricing line. Block pricing also provides setup flexibility where the unit of measure (UOM) of the header is different from the pricing attributes of each child line. In non-block pricing price breaks, the UOM of the child lines is the same as that of the header. In block pricing, child lines have different units of measure than the header. Lastly, block pricing also allows pricing setups that price by recurring values within blocks.

In regular breaks, lines have application method of Unit Price (for inventory items) and Percent Price (for service items only). For block pricing breaks, Unit Price is replaced by Unit Price to differentiate between the line UOM and the header UOM. Percent Price remains the same.

Like regular breaks, block pricing can be defined for either Point or Range price types. However, for Point price breaks, you can only select the Application Method = Block Price.

For Range lines where the Application Method is Price, you can define a recurring value for that block. For example, if the Recurring Value is 100, then the range is priced for every 100 items within the block.

The following examples show how price breaks with block pricing could be used:

■ Shipments between 100 and 200 lbs cost a flat rate of $50, regardless of the UOM. Without block pricing, the rate would be calculated by multiplying $50 against the unit quantity. So a 100 lb shipment would be calculated at $5000.00 (100 lbs X $50) instead of $50.00.

■ For the first 1 to 100 the price is always fixed at a total amount or lump sum. After that, charge is by the unit: for example, each hour based on a price break.

■ $10 for every hundred items until 1200. After that, $5 for every 50 items until 2000. After that, $0.30 per unit.

■ $10 for every hundred until 1200 items. After that, $30 for every hundred in addition to the cost of the first 1200. For example, with block pricing you would be able to create a price list and price setup, where the total cost for 1300 units will be $150 ($120 for the first 1200, $30 for every additional 100 units).

Note: If the recurring value does not divide evenly into the block, the resulting price is a prorated amount, not a flat rate, of the block price.

Price Lists 5-23


Example 1: Example of a Block price setup using a Recurring ValueYou can apply a block price and have the price repeat for defined intervals (the recurring value); for example, to charge $10 per 100 items up to 1000 items. In this example, the recurring value is 100.

When a recurring value is used with price breaks, the Block price repeats for every interval defined by the Recurring Value column. In this example, for the first 1200 units, the price is $10 for each 100 units up to 1200 units.

For 1201 units and more, you could create a second price to define a price of $30 for each 100 units.

So if 1300 units were purchased, the total cost would be $150 which is calculated as follows:

■ Block price 1: Price for first 1200 (1200/100= 12 X $10): $120 (first price break)

■ Block price 2: Price for each additional block of 100 units beginning with 1201 units: $30 (second price break)

This example could be set up as follows:

1. Navigate to the Advanced Pricing - Price Lists window.

2. Complete the fields in the Price Lists region.

3. In the List Lines tab, enter values for the selected Product Context (Item):

■ Product Attribute

■ Product Value

■ Product Description

■ UOM (unit of measure)

4. Select Price Header as the Line Type.

Note: The Block application method can only be selected if the price list line type is Price Header (PBH).

Note: You cannot use Recurring Value if the Price Type is Point.



5. Select Range as the Price Type. When selected, the Recurring Value column in the Price Breaks window is enabled in the Price Breaks window. You cannot use recurring value for point price break.

6. Select Block Price as the Application Method.

7. Click Price Breaks to display the Price Breaks window.

Example 2: Using Block price and Unit price with Price BreaksFor additional pricing flexibility, a Block Price and Unit Price can be applied in a price break. This is commonly found in minimum price scenarios.

Example 2a) A $100 flat price is charged for 1 to 100 minutes of cellular phone usage, after which the customer is billed a Unit Price of $1.00 per minute. This can be done by setting up a Block Price with a recurring value: for example, $10 per 100 minutes, and then applying a Unit Price of $1.00 for each minute over 100 minutes.

Example 2b)■ Block Price: $10 for every 100 units (the recurring value) up to 1200 units (first

price break)

■ Block Price: $5 for every 50 units (the recurring value) from 1201 to 2000 units (second price break)

■ Unit Price: $0.30 per unit above 2000 units (third price break)

The following tables displays the Block Price and Per Unit price setup in the Price Lists window:

Table 5–3 Price List line setup for Block price

Item UOM Line Type Price TypeApplication Method

ALL Each (EA)

Price Header

Range Block Price

Table 5–4 Price Breaks window setup: Block Price and Unit

Pricing Context

Pricing Attribute

Value From-To Price

Application Method

Recurring Value

Volume Item Quantity 1-1200 $10 Block Price 100

Price Lists 5-25


Block Price with Application Method of BLOCK PRICE and UNIT PRICEIf BLOCK PRICE is selected as the application method in the Price header for a price list (this is possible only with Range breaks), you can select the following application methods for the price lines:

■ BLOCK PRICE

■ UNIT PRICE.

When the UNIT PRICE application method is used in the line, the price specified is the unit price per attribute. For example: if the price is based on the price attribute Item Weight, the price to be specified is price per unit weight.

When setting up the price break, the price provided should be the unit attribute price. The Unit price for the ordered item is calculated by multiplying the UNIT PRICE with the sourced Volume Attribute value divided by the ordered quantity.

For example: if the Item Weight in lbs is used as the Volume Attribute in the Price breaks and the price breaks are as follows (Price $ 10 is the price per lb.):

The Item Weight is sourced from the total line weight of a sales order line. For example, if a sales order is entered for three items each weighing 2 lbs, then the unit list price returned from the preceding price would be: [10 X 6]/3 = $20. Six is the total line weight (2 x 3) lbs.

In the preceding context, the pricing attribute and its sourcing are important factors; therefore, it is important to ensure that the appropriate pricing attribute is used when setting up Unit Price lines to get the correct results.

Volume Item Quantity 1201-2000 $5 Block Price 50

Volume Item Quantity 2001-999999 $0.30 Unit Price Null

Table 5–5 Example of Unit

Pricing Attribute Value from Value to Price Application method

Item Weight 1 50 10 Unit price

Item Weight 51 100 8 Unit price

Table 5–4 Price Breaks window setup: Block Price and Unit

Pricing Context

Pricing Attribute

Value From-To Price

Application Method

Recurring Value



If any Volume attribute that sources a constant value is used, it impacts pricing in the Sales order and causes the list price to vary with the ordered quantity even though the ordered quantity falls in the same break. It is recommended to use sourced volume attributes whose value changes with the ordered quantity such as Item Weight, Item Volume, and Item Quantity.

These considerations apply when using cross order volume attributes too. For example, if the cross-order volume pricing attribute Period 1 Item Amount is used in the line, the unit price will be the price per unit period 1 amount.

Unless there is specific business requirement, it is not recommended to use Cross Order Volume attributes with BLOCK PRICE at the Header level and UNIT PRICE for the line. Instead, consider using UNIT PRICE at the Header level for such scenarios.


Price Lists 5-27

Finding Price List Lines

Finding Price List LinesWhen querying price list lines, use the Find Price List Lines query window (from the toolbar Find icon) to find specific price list lines. You provide the product attribute context (for example, Item), product attribute (for example, Item Number), and product attribute value (for example, Product A).

Note: If you search using the Find Price List Lines window instead of using a query-by-example on the Advanced Pricing - Price Lists window, you may reduce the time that you need to wait for the search results.


Creating a GSA Price List

Creating a GSA Price ListA General Services Administration (GSA) designation identifies a price list belonging to a United States government customer. For products on the GSA price list, a fixed price must be used and defined on the GSA contract.

You can create a GSA price list for your GSA customers. The items on the GSA price list cannot be sold to commercial customers for a price equal to or less than the government price. Therefore, the price offered to the government must be the minimum in the market. A GSA violation occurs when a non-United States government customer is offered a price equal to or less than the GSA Price. You can set up multiple GSA price lists that are effective during the same time period.

To create a GSA price list:1. Navigate to the Define Modifier - Define GSA Price window. In this window,

you can set up a GSA price list and GSA prices.

Figure 5–9 Define Modifier - Define GSA Price window

2. In the Main tab, select Discount List as the Type.

Price Lists 5-29


3. Enter a Number.

4. Select or clear Active.

The Global box is selected when the Pricing Security Control Profile is set to ON. This means that the price list can be used by all operating units for pricing transactions. If cleared, the price list’s use is restricted to the operating unit of the user creating the price list.

5. Enter a Name and Version for the GSA price list.

The Currency value defaults.


■ If selected, the Automatic box is also selected at the line level.

■ If cleared, then the modifier must be manually applied.

7. Enter the effective Start/End Date range.

8. Enter a Description for the GSA price list.

9. In the Modifiers Summary tab, enter a modifier number as an identifier for the GSA price list.

The Level defaults to Line, and the Modifier Type defaults to Discount.

10. Enter the Start/End Dates of this GSA price list line.

11. Select Override to enable a user to override the GSA price for the selected price list line. Clear the Override box to prevent a user from overriding the GSA price for the selected price list line.

The Pricing Phase defaults to List Line Adjustment and the Incompatibility Group defaults to Level 1 Incompatibility.

12. The Bucket defaults to 1.

13. Enter Item Number in Product Attribute.

14. Select the item in Product Attribute Value.

Note: The Start and End Dates for the discount line must be between the Start Date and End Date of the GSA price list. The pricing engine uses the discount line dates to confirm that the dates are in effect for each line.



15. Enter the Precedence value.

16. Select the corresponding Unit of Measure for the item such as Each or Carton.

17. When you have completed your entries in the Modifiers Summary tab, choose the Discounts/Charges tab.

The Application Method in the Discounts/Charges tab defaults to Newprice.

18. Enter the Value for the item. The value is related to the selected Application Method. For example, if the Application Method is New Price then the Value is expressed in currency units.

In the Other tab, you can view the following including details about any related Blanket Sales Agreement:

■ List Source Document Number: This is the Blanket Number of the blanket sales agreement.

■ List Source Code: Displays the code associated with the GSA price list. For example, BSO indicates Blanket Sales Order.

■ Pricing Transaction Entity (PTE): Displays the pricing transaction entity associated with the GSA price list. The Pricing Transaction Entity value defaults from the PTE that created the GSA price list. This field cannot be updated.

■ Source System Code: Displays the source system code such as QP for pricing.

■ Shareable box: Indicates if the GSA price list is shared or not. If non-shareable (the default), then this GSA price list is specific to that blanket and cannot be used with other blanket sales agreements.

If shared, the GSA price list is not exclusive to the blanket sales agreement and can be selected for use with other agreements.

19. Save your work.

Note: The Pricing Transaction Entity and Source System fields display if there is no related Blanket Sales Agreement.

Price Lists 5-31


To create GSA list qualifiers:To create qualifiers for a GSA price list, you can select a qualifier context such as customer and then a qualifier attribute that defines the context further such as customer name.

You can select one of the following Qualifier Contexts:

■ Customer: For this qualifier context, you can select either Customer name (GSA customers only) or site as a Qualifier Attribute.

■ Modifier List: For this qualifier context, you can select Price List as the Qualifier Attribute.

1. Click List Qualifiers.

Do steps 2-10 for each customer that is eligible for the GSA price.

2. Enter the Grouping Number.

3. Select either Customer or Modifier List for Qualifier Context.


■ If you selected Customer for the Qualifier Context, select either Customer name (GSA customers only) or site.

■ If you selected Modifier List for the Qualifier Context, select Price List as the Qualifier Attribute.

Note: You may be unable to select existing groups from the Qualifiers tab because GSA price lists restrict the type of qualifiers that can be attached.

Note: You can only attach customers only at the list (header) level. You cannot assign line level qualifiers.

Do not change the qualifier flexfield sequence for the GSA qualifier in the flexfield setup.

Note: Since Qualifier Context is Customer, make OR conditions by creating each qualifier with a different grouping number.



5. Enter Operator value and the Value From/To.

6. Enter the Start/End Date.

7. The Precedence defaults from the item segment of the descriptive flexfield.

8. Enter the customer name in Value From.

9. Enter start date and end date for the customer.

10. Save your work.


Price Lists 5-33

Maintaining Price Lists

Maintaining Price Lists You can maintain your existing price lists by adding more inventory items, adjusting prices within a single price list, or copying an existing price list to another price list.

For more complex tasks, such as searching across multiple price lists or adjusting prices for the same item across many price lists, Oracle Advanced Pricing provides a Price List Maintenance feature which enables you to:

■ Search for price list and line information across many price lists.

■ Do mass updates to price lists and price list lines.

The following provides an overview of the common tasks you can do to maintain price lists and price list lines:

Adding Inventory Items to a Price ListWhen you add inventory items to a price list, you can specify an item status, such as active or planned; an item category, such as hardware or software; or a range of items. You can request the price to be either zero or the items’ costs in a specific inventory organization. Later, you can adjust the prices to your selling price.

The process only adds items that exist in the item validation inventory organization and that are not on the price list, even if they are inactive on the price list.

To add items from an item category, you must first define the default inventory category set for Order Management. When you add items from an item category, the process adds all items of the item category to the price list; it does not add the item category.

Adjusting Price ListsYou can increase or decrease the list price of price list lines by an amount or percentage within a price list. You can adjust prices for all lines on the price list, lines that belong to an item category, lines with items of a certain status, lines created on a specified date, or lines having a range of items.

Note: You need View Only privileges to view price list and related windows. However, you must have Maintain privileges to make any updates. If you are unable to access or update this window, you may not have the appropriate access privileges. Consult your Pricing Administrator.


Maintaining Price Lists

■ For information on making simple adjustments to a single price list, see: Adjusting Prices for a Price List on page 5-39.

■ For information on making mass changes to a single price list or across price lists using the Price List Maintenance feature, see: Making Bulk Changes across a Selected Group of Lines on page 5-42.

Updating Prices (manually) for Price List Lines You can always manually change the price on an existing price list line. If you type over the existing price, the new price is effective for new orders as soon as you save your changes.

If you use price list line effectivity dates, you can maintain a historical record of your prices.

Copying Price ListsYou can quickly create a new price list by copying an existing price list. Only active price list lines (those with an effective end date later than the current date) can be copied. You can also copy active discounts and effective dates from the original price list.

Price List Maintenance feature The Price List Maintenance feature enables you to search across a single or multiple price lists, select related entities such as specific price list items, and make updates to price list or price list lines across a single price list or multiple price lists.

See:Using the Price List Maintenance feature (HTML Interface) on page 5-78

Making Detail or Bulk Changes to Price Lists (HTML Interface) on page 5-88

Searching for Price Lists (HTML Interface) on page 5-66

Archiving, Deleting, and Purging Price List Information on page 5-77

Price Lists 5-35

Adding Items to a Price List

Adding Items to a Price ListUse this process to add items from the item master file to price lists. You must define the price list header information before you can add items.

You can add inventory items to a price list by selecting:

■ A range of Items

■ Item Category Set such as Inventory Items or Purchasing

■ Item Category such as Hardware or Software

■ Item Status such as Active or Planned

You can set the price to be either zero or equal to the items’ costs from a specific inventory organization. Later, you can adjust the prices to your selling price.

The process only adds existing items from the item validation inventory organization and that are not on the price list, even if they are inactive on the price list.

To add items from an item category, you must first define the default inventory category set for Order Management. When you add items from an item category, the process adds all items of the item category to the price list; it does not add the item category.

Note: Pricing submits a concurrent process when you add inventory items. The concurrent process only adds new items to a price list; it does not replace existing items, even if the existing items are ineffective.



To add items to a price list:1. Navigate to the Add Items to Price List window.

Figure 5–10 Add Items to Price List window

2. Select the Price List to which you want to add items.

Do one or more of the following steps to select criteria of the items to be added to your price list:

3. Enter an item or range of Items to be added to the price list. You cannot use wild cards such as % when you specify the beginning and ending item numbers.

4. Select an Item Category Set.

Note: For System Items, the list of values (LOV) is not available. For any advanced add item functionality, you should use an API.

Price Lists 5-37


If you specify an Item Category Set only, then all the items which belong to specified Item Category Set will be added to the specified price list

5. To define selected items within an Item Category Set, select an Item Category.

6. Enter an Item Status to select items by their status.

7. Select the Set List Price Equal to Cost From check box if you have Oracle Inventory installed and to set the list price of the inventory item equal to its cost.

8. Enter an Inventory Organization to limit the source of the items to add to those in the organization. If you do not enter an organization, the process uses the organization specified in the profile option QP_ORGANIZATION_ID.

9. Click Submit. The Request ID can be used to track your request status.

Note: The list price becomes zero if:

■ You clear the Set List Price Equal to Cost From check box.

■ The Inventory Organization does not use the standard costing method.


Adjusting Prices for a Price List

Adjusting Prices for a Price ListUse this process to adjust the prices for a price list. You can adjust prices for the entire price list or selected items, item category sets, and item categories. You can define your criteria further by selecting the item status or creation date of the items to adjust.

For example, you can specify a category so that only the price list lines for the selected category are adjusted. If you leave any of the fields blank, pricing adjusts the price list regardless of that field.

You can adjust the price by either an amount or percent:

■ Percent: Enter a value to adjust list prices by a certain percentage. For example, when adjusting by a percentage, entering 10 raises list prices by 10 percent while -10 lowers list prices by 10 percent.

■ Amount: Enter a value to adjust list prices by a fixed amount. For example, when adjusting by an amount, entering 5 increases list prices by five whole units of currency. Entering -5 decreases list prices by five whole units of currency.

While adjusting prices:

■ If the Item Category Set is specified only, then all the items which belong to the specified Item Category Set and are present in the specified price list will get adjusted.

■ If both the Item Category Set and Item Category are specified, then all the items which belong to the specified Item Category Set and Item Category and are present in the specified price list will get adjusted.

Note: Oracle Advanced Pricing also provides an HTML-based user interface for adjusting prices on price lists. See Using the Price List Maintenance feature (HTML Interface) on page 5-78.

Price Lists 5-39


To adjust a price list:1. Navigate to the Adjust Price List window.

Figure 5–11 Adjust Price List window

2. Select the name of the Price List to adjust.

The default Currency and Description of the price list displays.

■ To adjust prices for the complete price list only, go to step 8.

■ To adjust the prices of specified items, item category sets, or item categories in a price list, complete the following steps in the Item Prices to Adjust section. Select only the criteria to adjust:

3. Enter an Item or range of Items whose prices you want to adjust. You cannot use wild cards when you specify the beginning and ending item numbers.

4. Select an Item Category Set.

Note: For System Items, the list of values (LOV) is not available. For these items, you may need to use an API.



When you select an Item Category Set only, all item prices in that category set are adjusted.

5. To restrict items within a selected Item Category Set, select additional criteria in the Item Category field.

6. Select the Item Status to include items of a specific status.

7. Enter a Creation Date to adjust the prices of items added to the price list on that date.

8. In the Adjust By field, select Percent or Amount:

■ Percent: Enter a value to adjust list prices by a certain percentage. For example, when adjusting by a percentage, entering 10 raises list prices by 10 percent while -10 lowers list prices by 10 percent.

■ Amount: Enter a value to adjust list prices by a fixed amount. For example, when adjusting by an amount, entering 5 increases list prices by five whole units of currency. Entering -5 decreases list prices by five whole units of currency.

9. Enter a Value which corresponds to the percent or amount to be adjusted.

10. Choose Submit. The request ID is displayed in the Request ID field.

Price Lists 5-41

Copying a Price List

Copying a Price ListYou can quickly create a new price list by copying an existing price list. Only active price list lines (those with an effective end date later than the current date) can be copied.

You can also copy:

■ active discounts from the original price list.

■ the effective dates from the original price list lines.

You can copy an existing Standard price list type to a new Standard price list, or an existing Agreement price list to a new Agreement price list. After the price list is copied, you can create a new agreement and attach the new price list to the agreement. Since price list names cannot be duplicated, each price list name must be unique.

Note: When you copy a price list, the new price list has the same currency as the original price list. If you are using multi-currency enabled price lists, the multi-currency conversion attached to the original will be attached to the new price list.



To copy a price list:1. Navigate to the Copy Price List window.

Figure 5–12 Copy Price List window

2. In the Copy From region, select the name of the Price List to copy. The price list can be either a Standard (PRL) or Agreement (AGR) price list.

The default Currency and Description display for the selected price list.

3. Select one of the following options:

■ To copy the entire price list, go to step 7.

■ To copy only certain items to a new price list, you can select the item or item range to copy. Enter an Item or range of Items to copy.

Note: You cannot use wild cards when you specify the beginning and ending item numbers.

For System Items, the list of values (LOV) is not available. For these items, you may need to use an API.

Price Lists 5-43


4. Select an Item Category and Item Category Set of the items to add. When you add items from an Item Category, the process adds all items of the item category to the price list; it does not add the item category.

5. Select Include Discounts to copy modifiers of type Discount List (DLT).

This is provided for backward compatibility to enable users of Release 11 to copy the modifier type of DLT (Discount List) to the new price list. When selected, only the modifier type of Discount List is copied but not any 11i modifiers.

If you are not copying modifiers from version 11, you do not need to select Include Discounts.

6. Select Retain Effective Dates so that the effective dates for the existing price list lines are copied to the new price list lines.

Even if Select Retain Effective Dates is selected, only the most current price list lines (current as defined by their effective dates) will be copied. Duplicate lines that have expired will not be copied.

7. In the Copy to region, enter a name for the new price list. It can be either a Standard (PRL) or Agreement (AGR) price list.

8. Enter a Description for the new price list.

9. Enter Effective Dates for the new price list.

10. Click Submit to copy the price list or selected lines. The request ID is displayed in the Request ID field.

Note: You must enter both Item Category Set and Item Category for this criteria to be effective.

Note: The process does not copy the effective dates of the price list, only the price list lines. You must enter effective dates for the new price list.


Copying a Price List Line

Copying a Price List LineYou can duplicate an existing price list line for a price list. This saves you time from manually re-entering a new pricing line. Although the price list information and pricing attributes are duplicated, price details from the source line are not copied.

Price list lines will be considered duplicate unless the:

■ Product value is different.

■ Effective dates are different.

■ Product attributes are different.

■ Comparison Operator Code is different.

To copy the price list line:1. Enter a new price list or query an existing price list.

2. Navigate to the line below the price list line to be copied.

3. Select one of the following to duplicate the line:

■ Select the Shift+F6 keys.

■ From the Edit menu, select Duplicate > Record Above to duplicate the price list line.

4. You can change Product Value or Effective Dates to avoid a duplicate list line error from occurring in the same price list.

5. Save your work.

Price Lists 5-45

Oracle Advanced Pricing Home page (HTML Interface)

Oracle Advanced Pricing Home page (HTML Interface) The Oracle Advanced Pricing Home page provides centralized access to your main pricing tasks. From this page, you can:

■ Search for price lists and modifier lists.

■ Use the Shortcuts links to quickly navigate to the pages that enable you to create and manage price lists and modifiers.

■ Use the Work Queue to view recently-created price lists and modifiers.

The following graphic shows the Oracle Advanced Pricing Home page featuring the Search, Shortcuts, and Work Queue regions:

Figure 5–13 Oracle Advanced Pricing Home page

The following section describes the tasks that can be completed from the home page:



To search for price lists and modifiers:1. In the Search field, select the pricing entity to search for:

■ Modifier List: To search for modifier lists.

■ Pricing List: To search for price lists.

2. Select a search category, then enter additional criteria to narrow your search results. For example, if you selected Price Lists and then Name, enter the specific name of the price list.

■ For Modifier Lists: Select Currency, Number, Type, Modifier Line Number, or Name.

■ For Price Lists: Select Name or Currency.

3. Click Go to display the search results in the Lists tab.

See:Updating a Price List (HTML Interface) on page 5-71

Updating a Modifier (HTML Interface) on page 3-123

To use the Shortcuts region:The Shortcuts region provides the following links that enable you to quickly navigate to the pricing task or feature you want. For example, click the Create Price List link to create a price list. Select from the available Shortcut links:

■ Create Price List: To create a new price list.

■ Price List Maintenance: To maintain or update one or many price lists.

■ Create Deal List: To create a Deal List.

■ Create Discount List: To create a Discount List.

■ Create Promotion List: To create a Promotion List.

■ Create Surcharge List: To create a Surcharge List.

Click the link to display the related setup or feature pages. Additional online help for each topic is available by clicking the Online Help icon in the destination page.

Note: You can only view price and modifier lists, and depending on your security privileges, update lists.

Price Lists 5-47


To use the Work Queue region:In the Work Queue region, you can view modifiers or price lists that you recently created. The Work Queue displays the price lists and modifier lists created by the user who is logged in.

1. In the Work Queue region, select the type of pricing entity to be viewed:

■ Recently Created Price Lists

■ Recently Created Modifiers

2. Click Go to display the list of recently-created modifiers or price lists. The results are displayed in chronological order (most recently completed are listed first). General information about each modifier or price list is listed in the table.

3. Optionally, click the Details icon to view additional details, or click the Update icon to update the list.

See:Using Price Lists in the HTML User Interface on page 5-2

Using Modifiers in the HTML User Interface on page 3-81


Using Price Lists in the HTML User Interface

Using Price Lists in the HTML User InterfaceOracle 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 the HTML UI to complete many of the pricing tasks that you previously completed in the Oracle Forms-based user interface such as:

■ Searching for price lists and price list lines.

■ Creating price lists.

■ Creating price list lines.

■ Maintaining price lists using the Price List Maintenance feature.

■ Creating qualifiers for price lists.

Tasks available in HTML are identified with "HTML Interface" in the task title; for example, Creating a Price List (HTML Interface).

Oracle Advanced Pricing still provides the Oracle Form-based interface for completing tasks that are currently unavailable in the HTML interface such as creating qualifier groups.

See:Using Oracle Advanced Pricing in the HTML Interface on page 1-6

Creating a Price List (HTML Interface) on page 5-50

Creating Price List Lines (HTML Interface) on page 5-55

Searching for Price Lists (HTML Interface) on page 5-66

Creating Qualifiers (HTML Interface) on page 2-6

Updating Price List Lines (HTML Interface) on page 5-73

Using the Price List Maintenance feature (HTML Interface) on page 5-78


Price Lists 5-49


Creating a Price List (HTML Interface)Price lists are essential to ordering products because each item on an order must have a price. Each price list contains basic price list information and price list lines that define the items and their list prices. Creating a price list in the HTML user interface is a flow-based process that consists of the following guided steps:

a. Enter general price list information to define general information about the price list such as the price list name, effective dates, currency, pricing controls, rounding factor, and shipping defaults.

b. Create qualifiers that define eligibility rules for the price list. You can use qualifiers to restrict the price list to certain customers by "qualifying" customers for a particular price list. For example, the customer must be a Gold class customer to receive the price list.

c. Review and then save the price list.

d. Add price list lines which define the items on your price list and their list prices.





To create a price list: 1. Navigate to the Create Price List: General Information page.

Figure 5–14 Create Price List: General Information page

2. Enter the Name and Description for this price list.

3. Select the default Freight Carrier.

4. Select the default Freight Terms.

5. Select the default Payment Terms such as Cash On Delivery (COD).

Note: The price list Name should be unique across PTEs (Pricing Transaction Entities) otherwise an error occurs. For example, if a price list named "Corporate" is created in the Order Management PTE, an error message displays if you create a "Corporate" price list in the Purchasing PTE.

Price Lists 5-51


6. The Source System and Pricing Transaction Entity values default from the profiles QP: Pricing Transaction Entity and QP: Source System Code. For example, the Source System defaults as Oracle Pricing.

7. Enter the effective Start and End Dates.

8. Select a base Currency for the price list such as USD (US dollars).

9. Select a Multicurrency-Conversion Criteria list. This field displays only if the profile QP: Multicurrency Enabled is set to Yes.


11. Enter a Round To value for the price list.

12. Select the Mobile Download box if you are using an Oracle Mobile application and want to download specific price lists onto a mobile device such as a laptop computer. The default value is No.

13. If the Pricing for Global Use box is selected, the price list can be used by all operating units for pricing transactions. If cleared, the price list’s usage is restricted to the operating unit of the user creating the price list.

Secondary Price Lists region1. Click Add Another Row to add a blank row where you can select a secondary

price list.

2. Click the Search icon, and select the price list to be attached as a Secondary Price List. The Description defaults based on the price list selected and is view-only.

The Precedence number defaults and can be updated.

Note: The Pricing for Global Use box displays only if pricing security has been turned on.

Note: If the item is listed on multiple secondary price lists, the precedence value is used to determine which secondary price list the item is selected from.

The lower the precedence number, the higher its precedence ranking; so, for example, a secondary price list with a Precedence value of 100 is selected before a precedence of 200; a value of 200 is selected before 300 and so on.



Optionally, to delete this price list as a secondary price list, click Delete, then click Apply to save your changes.

3. Click Next to display the Create Price List: Qualifiers page. Qualifiers define the eligibility rules that define who qualifies for the modifier.

Define any qualifiers for the price list. See Creating Qualifiers (HTML Interface) on page 2-6 for more information on setting up qualifiers.

4. When you have completed your entries, click Finish to skip the review page, or click Next to display the Price List Review page.

Figure 5–15 Create Price List: Review page

5. In the Price List Review page, you can review the following price list information before applying the final changes:

■ General Information

■ Secondary Price List

Price Lists 5-53


■ Qualifiers

6. If changes are required, click the Back button to return to the page and make your changes. If no changes are required, click Finish to save the price list.

A Confirmation message confirms that the price list has been created and asks if you want to add price list lines. Price list lines define the items and prices for the price list.

7. To add price list lines, click Yes. Click No, if you do not want to add price list lines now. You can add price list lines in the future.

See:Updating a Price List (HTML Interface) on page 5-71


Note: Once created, the price list remains in "Inactive" status. You must update the price list and select the Active box to activate the price list.



Creating Price List Lines (HTML Interface)You create price list lines to define the actual items on the price list and the list prices. When setting up a price list lines, you can define the prices by the following product levels:

■ All Items (price applies to

■ Item Number such as AS54888

■ Item Category such as Hardware or Software

■ iStore Section

You can use negative price, positive prices, or set the price to be zero. You can use modifiers to adjust the prices to your selling price.

See:Creating a Price List (HTML Interface) on page 5-50

Using Modifiers with Negative Unit Selling Prices on page 3-11

Note: You must define the price list header before you can add price list lines.

Price Lists 5-55


To create price list lines:1. Navigate to the Create Price List Line page.

Figure 5–16 Create Price List Line page

2. Select a Line Type. The setup for price list lines varies depending on the Line Type selected.

■ Price List Line: Select this type to assign a unit or formula-based price to a product. For example, to add a line item AS54888 with a selling price of $11 each.

■ Price Break: Select this type to create prices using a price break. Price breaks or "bracket pricing" can be used to define prices using different price tiers. For example, if ten items are ordered, the price is $10 per item, but if twelve are ordered then the price drops to $8 per item.

3. Select the Start and End Date ranges for the price list line.

Note: If navigating from the Update Price List: Price List Lines page, click Create Line to display the Create Price List Line page.



4. In the Product region, select a Product Level:

■ Item Number: Applies the price against a particular item number.

■ Item Category: Applies the same price against items in the selected item category.

■ All Items: Use All Items to apply the same price to all items in your product hierarchy.

5. Select a Product to be added to the price list.

The Product Description defaults based on the product selected.

6. Select a UOM (unit of measure) for the item.

For example, an item such as A11111 in a price list may have two price list lines: one with a UOM of Each (EA)—the primary UOM—and the other with a UOM of Boxes.

The Precedence value defaults based on the Product Level. You can change the Precedence value if desired.

7. In the Pricing Attributes region, select an Attribute for the price list line. For example, if you selected toothbrush as the product, you can use attributes to define the type or color of toothbrush to be priced. In this example, the attribute is color.

8. Select an Operator such as Is, Is Not, Between for the attribute.

9. Select Value From and, if applicable, the Value To to define the attribute values. For example, if Color is selected as an attribute, then the values could be some

Note: The pricing engine uses the pricing Primary UOM and the Oracle Inventory UOM conversion information to price an order whose unit of measure does not have a price list line. If an order for item A11111 is placed in the unit of measure Case (CS), the pricing engine accesses the unit of measure conversion tables to convert Case to Each (EA) which is the primary unit of measure.

Note: You only need to enter the pricing attributes. You do not have to enter the Context as required in the Oracle Forms-based pricing interface.

Price Lists 5-57


color such as "Red" or "White." If the operator value is Is or Is Not, then the Value To field is not displayed.

10. Click Add Another Row to add additional attributes.

11. If you selected Price as the Line Type, see To create price breaks for a price list line: on page 5-60 to complete the remaining steps. If you selected Price List Line, complete the following steps:

12. In the Price Detail region, the default Application Method is Unit Price. This is the per unit price of the item

13. Enter a list Price.

14. If using a formula to calculate prices, select a Formula Type. At pricing time, the pricing engine calculates the price of the item using the formula:

■ For Static Formulas, run the Build Formula Package program to calculate the value. The result of the calculation changes the Value.

■ For Dynamic Formulas, you only need to enter Value if the formula includes list price as one of the formula components.

15. Select a Formula name. Click the Search icon to find a formula name.

16. Click Apply to save your changes. A Confirmation message displays if the price list line was successfully created.

17. Click Create Line to create another price list line.

Note: If Price is selected as the Line Type, you cannot select a formula.



Creating Price Breaks for a Price List Line (HTML Interface)When setting up price list lines, you can create price breaks to define prices that vary with the quantity ordered ("bracket pricing").

For example, if you buy up to 10 items the price is $20 per item, but if you buy more that 10 items, you get a lower price per unit. If you define a price for an item category, all the items within the category are eligible for the price break.

When creating price breaks, you can select an Application Method in the rules region to define how the price breaks are defined.

■ Block Price: Enables you to apply a lumpsum price rather than a per unit price to a pricing line. If Block Price is selected, you can define a Recurring Value that repeats a price for a defined interval; for example, to charge $10 per 100 items up to 1000 items. In this example, the recurring value is 100. Like regular breaks, block pricing can be defined for either Point or Range price types.

■ Unit Price: Defines the price for each item.

For additional pricing flexibility, a Block Price and Break Unit Price can be applied in a price break. This is commonly found in minimum price scenarios.

Note: Block Price can be selected only if the price list line type is Price Break.

Price Lists 5-59


To create price breaks for a price list line:1. Navigate to the Break Rules region of the Create Price List Line page. These

steps are continued from the price line setup steps described in To create price list lines: on page 5-56.

Figure 5–17 Break Rules region

2. Select a Break Type such as Point or Range:

■ Point break: Price is based on the price bracket in which the total quantity falls. Point processing.

■ Range break: Price based on the ranges of the defined price breaks. For each range, the engine calculates a price and sums across all ranges to obtain the total extended price.

3. Select the Application Method to define how the is applied:

■ Block Price: Enables you to apply a lumpsum price rather than a per unit price to a pricing line. Block pricing can be used with Point or Range price types. The following example describes a situation where a Block Price method can be applied:

Shipments between 100 and 200 lbs cost a flat rate of $50, regardless of the UOM. Without block pricing, the rate would be calculated by multiplying

Note: If navigating from the Update Price List: Price List Lines page, click Create Line to display the Create Price List Line page.



$50 against the unit quantity. So a 100 lb shipment would be calculated at $5000.00 (100 lbs X $50) instead of $50.00.

■ Unit Price: Defines the price for each item.

4. If Unit Price is selected, complete these additional steps:

a. Select a Break UOM such as Each to define the unit of measure for the price break. The unit of measure (UOM) of the can be different from the pricing attributes of the child line.

b. Select a UOM Attribute.

5. Select a value for Volume Based On:

■ Item Quantity: Calculates based on the quantity of items ordered.

■ Item Amount: Calculates based on item amount.

In the Details region, define the details for each price break range. Different setup steps are required depending on the Application Method (Block Price or Unit Price) you selected in the Rules region:

■ To enter Break Details (Block Price selected in Rules region): on page 5-62

■ To enter Break Details (Unit Price selected in Rules region) on page 5-64

Price Lists 5-61


To enter Break Details (Block Price selected in Rules region):1. Navigate to the Break Rules region of the Create Price List Line page.

Figure 5–18 Break Rules region (Block Price selected)

2. Enter a break Value From/To range that defines the price break. For example, to define a break for the first 10 items ordered, create a range from 1-10. To do this, enter 1 in Value From and 10 in Break Value To.

3. Enter a Price.

4. Select an Application Method:

■ Block Price: Applies a lumpsum price rather than a per unit price to a pricing line.

■ Break Unit Price: Applies a per unit price; for example, $0.30 per unit above 2000 units.

5. Enter a Recurring Value to define a price for a defined interval. When a recurring value is used with price breaks, the defined Block Price repeats for

Note: For additional pricing flexibility, a Block Price and Break Unit Price can be applied in a price break. This is commonly found in minimum price scenarios. For example, a $100 flat price is charged for 1 to 100 minutes of cellular phone usage, after which the customer is billed a Break Unit Price of $1.00 per minute.



every interval defined in the Recurring Value field. For example, to charge $10 per 100 items up to 1000 items (the Recurring Value would be the "100" value).

6. To create additional breaks, click Add Another Row. To delete a price break, click the Delete icon.


Price Lists 5-63


To enter Break Details (Unit Price selected in Rules region)1. Navigate to the Break Details region.

Figure 5–19 Break region (Block Price selected)

2. Enter a break Value From/To range that defines the price break. For example, to define a break for the first 10 items ordered, create a range from 1-10. To do this, enter 1 in Value From and 10 in Break Value To.

3. Enter a unit Price for the break.

4. To create additional break lines, click Add Another Row. To delete a price break, click the Delete icon.




Warning: If the ordered quantity does not fall in the price range of the price list, the price is still calculated and defaulted in the sales order line. Ensure that the price ranges are set up correctly to get the pricing results you desire:

For example, suppose you create the following range price breaks for price list Item AS54888 (Application Method is Unit Price):

■ Value From/To: 1 to 5 Price: 1.00 each

■ Value From/To: 6 to 7 Price: .75 each

If Price Type is Point: The price is not returned if the ordered quantity does not fall in the price range of the price list.

If Price Type is Range: A price of 0 is retrieved for the ordered quantity that does not fall in the price range.

For example, if a Sales Order for 10 items of AS54888 were placed, the price would be calculated as follows (Price Type is Range):

(5*1) + (2*0.75) + (3*0)/10 = 0.65 Unit Price

Notice that the last 3 items fall out of the price range and therefore a unit price of 0 is returned. Therefore it is important that the price breaks are set up correctly to get the desired price results.

Price Lists 5-65


Searching for Price Lists (HTML Interface)In the Price Lists page, you can search by price list name, currency, dates, or status to find information essential to your business such as:

■ All price lists in a specific currency.

■ Specific price lists.

■ All price lists created on a specific date.

You can specify additional search criteria to narrow your results. For example, you can specify the type of currency such as USD (US dollars) to find only price lists with USD as the base currency.

Once the search results are returned, you can view a summary of price lists or select a specific price list to view additional details. In addition to viewing the price list, you can choose to update a selected price list, or create a new price list.

Note: You must be assigned Maintain privileges in pricing security to update or create a new price list. The Details icon is enabled if you have view or update privileges assigned through pricing security.



To search for price lists:1. Navigate to the Price Lists page.

Figure 5–20 Price Lists page

2. Select a search category from the Search list, then enter additional criteria (where applicable) to narrow your search results. Select from the following search categories:

■ Currency: Select a specific currency such as USD (US dollars) to find all modifier lists set up in USD.

■ Dates: Search by price list dates. These Start and End Dates must match exactly to the dates in the price list setup.

■ Price List Name: Search by the price list name. Enter a specific name or enter the Wildcard character (%) to list all price lists.

■ Status: Search by Active or Inactive price lists.

Active: Finds all Active modifier lists.

Price Lists 5-67


Inactive: Finds Inactive modifier lists.

3. Click Go to display the search results in a table.

4. Optionally, select a price list, and click Update to update the price list, or click Details to view price list details.


Updating a Price List (HTML Interface) on page 5-71

Searching for Price List Lines (HTML Interface) on page 5-69



Searching for Price List Lines (HTML Interface)You can search by the following criteria to find price list lines within a specific price list:

■ Dates: To search by a specific date range.

■ Items: To search by Item(s).

To search for price list lines:1. Navigate to the Update Price List: Price List Lines page.

Figure 5–21 Update Price List: Price List Lines page

2. Select the Search criteria:

■ Dates: To search by a specific date range. Enter the Start Date and End Dates to find price list lines within a specified date range.

Price Lists 5-69


■ Items: To search by Item(s). To define additional search criteria, select Item Number or a combination of (Item Number and UOM) or (Item Category). You cannot search just by UOM.

3. Click Go to display the price list lines related to the price list.



Updating a Price List (HTML Interface)In the Update Price List: General Information page, you can update general details about the price list such as the description, currency, active status, and other information.

To update a price list:1. Navigate to the Update Price List: General Information page.

Figure 5–22 Price List: General Information page

Warning: Pricing security can affect the View and Maintain features associated with the Update and Details icons in the HTML user interface. See Pricing Security (HTML Interface) on page 1-4 for more information. You must be assigned Maintain security privileges to update the price list, otherwise only the Details icon is enabled.

Price Lists 5-71


2. Make any required changes or corrections to the price list. You can update the following fields:

■ Freight Carrier/Terms

■ Description

■ Payment Terms

■ Currency

■ Active box: If selected, then the price list is active. If cleared, then the price list is inactive and will not be available for pricing orders.

■ Start/End Dates

■ Comments

■ Multi-currency Conversion

■ Round To

3. In the Secondary Price List region, you can update any secondary price lists. If no secondary price list is listed, click Add Another Row to add a secondary price list.

4. Click Apply to save the changes. A Confirmation note displays if the price list was updated successfully.


Updating Price List Lines (HTML Interface) on page 5-73




Updating Price List Lines (HTML Interface)Once a price list line has been created, you may need to occasionally update the information; for example, to change the price or unit of measure. The Update: Price List Lines page enables you to update information for a price list line. To update a price list line, search for the price list, display the price list lines, update selected lines and apply the changes.

To make the same change to price list lines across multiple price lists--for example, to change the price of an item listed on several price lists--consider using the price list maintenance feature. This saves you time from updating each price list separately.

In addition to updating a price list line, you can add or delete an existing line.

Note: You cannot update the Product level or Product fields. The Product Description is read-only.


Price Lists 5-73


To update price list lines:1. Navigate to the Update Price List: Price List Lines page. Price list lines related

to the price list display in a table.

Figure 5–23 Update Price List: Price List Lines page

Note: To find specific price list lines for the price list, select one of the following Search categories:

■ Dates: To search by a specific date range. Enter the Start Date and End Dates to find price list lines within a specified date range.

■ Items: To search by Item(s). To define additional search criteria, select Item Number or a combination of (Item Number and UOM) or (Item Category). You cannot search just by UOM.

Click Go to display the price list lines.



2. Select the price list line to be updated.

3. Click the Update icon to display the price list line in the Update Price List Line page.

Figure 5–24 Update Price List Line page

4. Update the information that requires changes:

■ Line Type

■ Start/End dates

■ Product level information such as the UOM (unit of measure), Primary UOM (unit of measure), and Precedence.

■ Pricing Attributes

■ Price Details (if the Line Type is Price List Line)

■ Rules (if the Line Type is Price Break)

■ UOM List Line

Price Lists 5-75


5. To delete a price list line, select the line in the Update Price List: Price List Lines page, click Delete, then click Apply to save your changes.

6. Click Apply to save the changes. A Confirmation message displays to confirm that the line was updated successfully.

See:Using the Price List Maintenance feature (HTML Interface) on page 5-78



Archiving, Deleting, and Purging Price List Information

Archiving, Deleting, and Purging Price List Information You cannot delete a price list once it has been created. However, when a price list is no longer required, you can enter an end date when the price list becomes inactive. You can delete price list lines.

For price list lines, you can use the archive feature to archive price list lines from the pricing application tables to archiving tables for long-term data storage. Once the pricing data is copied to the archive tables, it is deleted from the application tables.

When the archived data is no longer required, you can purge the data from the archive tables.



Note: Price list and modifier list header information is copied to archive tables but is not deleted from the pricing application tables.

Price Lists 5-77

Using the Price List Maintenance feature (HTML Interface)

Using the Price List Maintenance feature (HTML Interface)The Price List Maintenance feature enables you to make changes to price lists and price list lines for a single price list or across many price lists. The frequency of these changes depend largely on your business processes and how often you update your prices--daily, monthly, quarterly, or annually.

You can do Simple or Advanced searches to find price list lines within a single price list or across many price lists. You can view your search results and then do a detail change or bulk change to update the value, formula or effective dates for selected price list lines.

After applying your changes, you can review the results in the Review Changes page. This is useful for modelling your pricing scenarios before submitting the final changes.

You can use Price List Maintenance for the following tasks:

■ Searching for price lists and price list lines

■ Do simple or advanced searches for a single or multiple price lists/price list lines.

■ Display search results in a hierarchal format.

■ Making changes to price lists and price list lines

■ Do detail changes or bulk changes to change price list lines for a single price list or across price lists.

■ End date and create new line in Bulk Change.

■ Duplicate line in Detail Change.

■ Do mass maintenance across multiple price lists.

Note: You must have Maintain privileges to make any updates. If you are unable to access or update this window, you may not have the appropriate access privileges. Consult your Pricing Administrator.



Note: You can only select those price list lines with Line Type of Price List Line. Price list lines with Line Type of Price Header cannot be selected. You cannot select price lists that belong to a different pricing transaction entity (PTE) or source system.

Price Lists 5-79


Searching for Price Lists and Price List Lines (HTML Interface)Using the Price List Maintenance feature, you can do a simple or advanced search depending on your requirements:

■ Search: Search by price list name (for example, Spring price list), product attribute, product value, and product description.

■ Advanced Search: Search by price list header details, line details, pricing attribute details, qualifier details, and secondary price list details.

You can search across one price list or multiple price lists. For example:

■ Find all price lists where the price list header specifies Start Date = 12 Dec 2000 AND Price List Header End Date = 12 Feb 2002

■ Find all price lists where price list has a qualifier specifying Customer Name = Vision Operations AND where a price list line specifies Product Attribute of Item Number = telephone

■ Find all price lists where one or more of the price list lines specifies Item Category = Soda and Pricing Attribute = Diet

Viewing the Search ResultsThe search results display in the Results region of the Price List Maintenance page with the price list being the top-most node. Click the Expand icon (+) next to the price list name to view additional details nested beneath the node. For a price list, you can view related information pertaining to the selected price list such as price list lines, qualifiers and related information. To view a particular price list if more than one is listed, click the Focus icon. Use the Focus icon to select a particular entity to examine it in more detail.

Price Lists node The top node is the Price Lists node if your results include more than one price list. If you have a single price list returned in your search results, then the price list name itself is displayed as the top node.

If you click a price list node, for example, Corporate Price List, then two additional nodes display: a Lines node and a Qualifier node. Each row under this node identifies the price list name and its description.

Note: You can also search for price lists from the Price Lists Search page. See Searching for Price Lists (HTML Interface) on page 5-66.



Lines node Click the Lines node to display the price list lines (of the price list) which meet the search criteria. Each price list line displays the item number, item description, unit of measure, value, static or dynamic formula, start date and end date. If no line criteria such as lines, products and pricing attributes are entered in the search criteria, all the price list lines of the price list are displayed.

Also, if a price list line has associated price breaks or pricing attributes, the Expand icon (+) displays next to the product attribute value. Click the Expand icon (+) for the product attribute value to display the Breaks and Pricing Attributes node.

Price Breaks node Click the Price Breaks node to display all the price breaks for the product attribute value. Each row displays the individual price breaks along with the value.

Pricing Attributes node Click the Pricing Attributes node of the product attribute value to display the pricing attributes that match the query criteria. If no pricing attribute criteria is entered in the Search Criteria, all the pricing attributes of the price list line display. Each row displays the pricing attribute and pricing attribute value.

Qualifiers node Click the Qualifiers node to display all the qualifiers of the price list which meet the search criteria. If no qualifier criteria is entered in the Search Criteria, all the qualifiers of the price list are displayed. Each qualifier displays the qualifier attribute and qualifier attribute value in the Description column.

Figure 5–25 Qualifiers node

Price Lists 5-81


To do a simple search:1. Navigate to the Price List Maintenance page.

Figure 5–26 Price List Maintenance page: Search region

2. In the Search region, select only the criteria required for your search:

■ Price List Name: Select a price list name.

■ Product Attribute: Select a product attribute such as Item number or Item Category.

Note: Click the Search icon (where applicable) to display the available values for a field. Also, in some blank fields, you can use the wildcard character (%) to narrow your search results; for example, enter Co% to display all the price lists beginning with Co.

mp



■ Product Value: Select a particular product value for the selected product attribute. You must select a product attribute before you select a product value.

■ Product Description: This displays the description of the product value. The product attribute must be entered first before the Product Description can be entered.

3. When you have completed your entries, click Go to display the search results.

The search results display detailed information about each price list including price list lines, pricing attributes, and qualifiers. By clicking the Expand icon for a selected price list, you can view the price list lines and qualifiers for the price list.

Note: Only price list lines can be updated in this feature. You cannot update price lines in Price List Maintenance.

Price Lists 5-83


To do an advanced search:1. Navigate to the Price List Maintenance page.

2. Click Advanced Search to display the Advanced Search page.

Figure 5–27 Advanced Search page

3. Select your search criteria from the following regions:

Header region■ Price List Name: Select a price list name. Click the Search icon to find a

particular price list. You can use a wildcard character (%) in your search criteria; for example, enter Co% to display all the price lists beginning with Co.

■ Active: Select Yes to search by Active price lists or No to search by Inactive price lists.

Important: Click the Search icon (where applicable) to display the available values for each field.



■ Currency: Select a particular currency.

■ Start/End Dates: Click the Calendar icon to search by Start/End Dates. This date has to exactly match the price list start date active.

■ Round To: Select a Round To value to return price lists with the specified Round To value.

■ Payment Terms: Select the Payment Terms.

■ Freight Terms: Select a particular freight term.

■ Freight Carriers: Select a particular freight carrier.

Line region■ Product Attribute: Select a Produce Attribute for the price list line. You can

select an Attribute Name or Attribute Code.

■ Product Value: Select a Product Value for the selected product attribute.

■ Product Description: Select a Product Description for the selected product attribute.

■ UOM: Select a particular unit of measure.

■ Dynamic Formula: Select a particular dynamic formula. These dynamic formulas must not contain a line type as MV.

■ Static Formula: Select a particular static formula. These static formulas must not contain a line type as MV.

■ Precedence: Enter to search by product precedence.

■ Application Method: Select whether the application method is a Percent Price or Unit Price.

■ Value: Enter to search by the product value.

■ Line Type: Select Price Header or Price List Line.

■ Price Type: Select either Point or Range.

■ Primary UOM: Select Yes or No depending on if the UOM is primary or not.

■ Start Date/End Date: Click the Calendar icon to select a Start Date and/or End Date. This Start Date has to exactly match the price list line start date and the End Date has to exactly match the price list line end date active.

Price Lists 5-85


Pricing Attribute■ Pricing Context: Select a particular pricing context such as pricing attributes.

■ Pricing Attribute: Select a particular pricing attribute for the pricing context you have selected.

■ Operator: Select a particular operator such as =, BETWEEN and NOT=.

■ Value From: Select a particular Value From for the pricing attribute you have selected. For numeric Value From, enter the value in the field. For example, if the pricing attribute is Handling Cost, then the Value From is numeric. This value has to exactly match the 'pricing attribute value from' of the pricing attributes which are attached to the price list lines returned from this search.

■ Value To: Enter to search by Value To. This value has to exactly match the Pricing Attribute Value To of the pricing attributes which are attached to the price list lines returned from this search.

Qualifier region■ Qualifier Context: Select a particular qualifier context such as Customer or

Order.

■ Qualifier Attribute: Select a particular qualifier attribute for the qualifier context you have selected.

■ Operator: Select a particular operator such as =, BETWEEN and NOT=.

■ Qualifier Value From: Select a particular Qualifier Value From.

For numeric values, enter the value in the field. For example, when the Qualifier Context is VOLUME, the Qualifier Value From is numeric. This value has to exactly match the Qualifier Attribute Value From of a qualifier which is attached to the price lists returned from this search.

■ Qualifier Value To: Select a Qualifier Value To. This value has to exactly match the Qualifier Attribute Value To of a qualifier which is attached to the price lists returned from this search.

■ Start Date: Click the Calendar icon to select the effective start date. This date has to exactly match the start date of the qualifiers which are attached to the price lists returned from this search.

■ End Date: Click the Calendar icon to select the effective end date. This date has to exactly match the end date of the qualifiers which are attached to the price lists returned from this search.



Secondary Price List region■ Secondary Price List: Select a particular secondary price list. You could also use

wildcard character in your search like Co% to display all the price lists beginning with Co.

■ Description: Select a particular description.

■ Precedence: Enter to search by secondary price list precedence.

4. When your entries are complete, click Search to display the search results. The search results display in the Price List Maintenance page.

5. Select the Price List Lines for change. From the search results, select the check box next to the price list and/or price list line(s) to be changed. You can change pricing entities such as Value, Pricing Formula, and the Start and End Dates of price list lines.

When a price list is selected, all the price list lines in the search results for that price list will be available for change.

Note: You can only select those price list lines with Line Type of Price List Line. Price list lines with Line Type of Price Header cannot be selected.

You cannot select price lists that belong to a different pricing transaction entity (PTE) or source system.

Price Lists 5-87


Making Detail or Bulk Changes to Price Lists (HTML Interface)Once you have completed your search in the Price List Maintenance page and selected a price list or price list lines, you can change the values, formula, or effective dates. The changes can be made for a single price list or across multiple price lists for lines with Line Type of Price List Line.

For example, you could adjust all plastic items by 3%, metal items by 5%, and extend the end date from September 30, 2003 to December 31, 2003 for a Corporate price list. You can use either the Detail Change or Bulk Change feature to make changes depending on your business requirements.



Making Detail Changes across a Selected Group of LinesFor Detail Changes, updates must be made for each price list line separately. So, for example, to increase the price for selected items on a price list you would have to manually update each price list line separately.

If there are overlapping dates for a product on a price list, an error message displays; for example, if you end date a price list line when the item is no longer sold.

To make detail changes:1. After you have completed your search in the Price List Maintenance page,

select the price list(s) or price list lines to be changed.

2. Click Detail Change to display the Detail Change: Make Changes page.

Figure 5–28 Detail Change: Make Changes page

In this page, you can update selected price list lines. To view additional details about a price list line, click Show. For each price list line, you can make the

Price Lists 5-89


changes to the existing line. You can also click the Duplicate Line icon and then make changes to the new price list line.

3. To change the value of a price list line, for example, to increase its price, select the Type of Value Change. Select one of the following values:

■ No Change: The value of all the price list line remains the same.

■ Replace Value: The value of the price list line will be changed to the value entered in the Value Change By field.

■ Amount: The value of the price list line will be increased/decreased by the value entered in the Value Change By field.

■ Percent: The value of the price list lines will be increased/decreased by the percentage value entered in the Value Change By field.

■ Clear Value: The value of all the price list lines is changed to Null.

4. If you selected Replace Value, Amount, or Percent in the Type of Value Change field, enter a value or percentage in the Value Change By field.

The Changed Value field displays the changed value once you have completed your changes and click Refresh Data.

For example, if the original value is 100, and you enter the following:

■ Type of Value Change: Increase by Percent

■ Value Change By: 10

After you click Refresh Data, the Changed Value field displays 110.

5. Enter a Changed Start Date to replace the existing start date. You can then make further changes to the Changed Value for this price list line.

6. Enter a Changed End Date to replace the price list line end date.

If the price list line has a dynamic formula or static formula attached, the formula name is displayed in either the Static Formula or Dynamic Formula field.

7. To update or add a static or dynamic formula for a price list line, make your changes in the Static Formula or Dynamic Formula field. Select only one type of formula.



8. Click the Duplicate Line icon to duplicate the current line. You can change values of the current and the duplicated line.

9. Click Refresh Data to display the newly calculated values in the Changed Value fields.

10. Click Continue to display the Detail Change: Review Changes page.

This page displays all the price list lines that have been updated and the newly created lines.

Figure 5–29 Detail Change: Review Changes page

11. Click Finish to submit the changed lines. To return to the Detail Change page, click Back.

Note: To update or add a formula value, click the Search icon next to the Changed Static Formula or Changed Dynamic Formula fields to view the available static and dynamic formulas.

Price Lists 5-91


A Confirmation message displays that the price list lines have been updated in the Price List Maintenance page.

Example of Detail ChangeThis example shows how the Detail Change page is used to make the following changes to price list lines for a fictitious price list (Corporate):

■ Increase the price for price list line Item A by 10%.

■ Add a formula to calculate price for price list line Item B.

■ Create a new price list line for Item C and change the Start and End Dates.

1. In the Search Price Lists region of the Price List Maintenance page, do a query to find the Corporate price list.

2. Select the Corporate price list and click Detail Change to display the Detail Change page.

3. Select or enter the following values for each of the price list lines to be changed:

4. To increase the price of Item A by 10%:

■ Type of Value Change = Percent

■ Change By = 10

5. To add a formula to calculate price for price list line Item B:

■ Click the Changed Static Formula or the Changed Dynamic Formula icon to select one of the available formulas. Select one formula type or the other, not both.

6. To create a new price list line for Item C and change the Start and End Dates:

■ Click the Duplicate Line icon for Item C to duplicate the price list line. When duplicating a line, remember to end date the previous line.

■ For the new line, enter the new Start Date and optionally, the End Date. When duplicating a line, ensure that the effective dates for a price list line do not overlap. Change the effective dates of the overlapping line to make the price list line unique. The New Line box is selected to indicate new lines.

7. Click Refresh Data to view all the updated and newly created price list lines.

8. If satisfied with your changes, click Continue to go to the Detail Change: Review Changes page.



9. Click Finish to save the changes. A Confirmation message confirms if all changes to the price list lines have been saved.

Price Lists 5-93


Making Bulk Changes across a Selected Group of LinesThe Bulk Change feature enables you to make the same updates across all selected price list lines: for example, to adjust the price by $5. This saves time from updating each price list line separately. These changes are made in the Bulk Change: Make Changes page.

Unlike the Detail Change feature, which requires you to update each price list line separately, the Bulk Change feature enables you make your changes once and update all selected price list lines. For example, bulk change could be used to:

■ Adjust all lines on Corporate Price list and Spring Price List by 10%

■ Adjust all lines on VIP price list and the first two price list lines of Fall price list (out of 10 price list lines) and change the end date to 12-Dec-2002.

When making changes to the price list line, you can end date the existing line and create a new price list line with the changes. The existing line will be end-dated, and the changes are reflected only in the new line.

In Bulk Change, you can choose to make a date change by selecting either the Override option or End Date and Create New option from the Action region. When end dating and creating a new line, you can also retain the existing start/end dates. Otherwise, they can override the start/end date of the existing line.

If there are overlapping dates for a product on a price list, the system will display an error; for example, if you end date a price list line when the item is no longer sold.



To make bulk changes across a selected group of lines:1. After you have completed your search in the Price List Maintenance page, select

the price lists or price lines to update.

2. Click Bulk Change to display the Bulk Change: Make Changes page. The Bulk Change feature enables you to do the same change across all the selected lines rather than to update each line separately (Detail Change).

Figure 5–30 Bulk Change: Make Changes page

The selected price list lines display in the Price List Lines region of the Bulk Change: Make Changes page. To view additional details about a price list line, click Show.

Price Lists 5-95


In the Maintenance Criteria region, you can make changes to the effective Start and End Dates, Formula, and Value and apply theses changes to the price list lines.

Figure 5–31 Bulk Change page: Maintenance Criteria region

3. In the Action region, select one of the following options:

■ End Date and Create New: Each selected price list line is end-dated and a new price list line is created with the changes specified in the Effective Date, Formula and Value regions. The Start Date or End Date for each price list line is updated. This is useful for keeping a version history of a price list line.

If there are multiple price list lines for the same item (with different effectivity dates), the price list line with the most forward effectivity dates will be end dated and a new line will be created. Any changes will be reflected on the new line.

■ Override: Each selected price list line will be updated with the changes you specify in the Effective Date, Formula and Value regions.



4. In the Effective Date region, select the Type of Date Change:

■ No Change: The dates remain the same.

■ Change Date: The dates are changed to those entered in the Start Date, End Date, New Line Start Date, and New Line End Date.

5. If you selected Change Date in the Type of Date Change field, enter the new dates in the following fields:

■ Start date: This changes the start date of all the price list lines.

■ End date: This changes the end date of all the price list lines.

■ New Line Start Date: This date changes the start date of all the new price list lines created as a result of choosing the Action: End Date and Create New.

■ New Line End Date: This date changes the end date of all the new price list lines created as a result of choosing the Action: End Date and Create New.

■ Retain Existing Start Date box: If selected, you do not need to enter a Start Date for the existing line. If cleared, the date in the Start Date field replaces the current Start Date.

■ Retain Existing End Date check box: If selected, you do not need to enter an End Date for the existing line. If cleared, the date in the End Date field will replace the current End Date.

6. In the Formula region, select the Type of Formula Change:

■ No change: The formulas remain the same.

■ Remove Static and Dynamic Formula: You can select from Any Formula or from available formula names. If you select a particular formula, then the matching formula attached to the price list lines will be removed. If Any Formula is selected, all formulas will be removed from price list lines.

■ Replace All Formulas with Dynamic Formula: The Dynamic Formula of all the price list lines will be changed to the Formula entered in the Name field.

■ Replace All Formulas with Static Formula: The Static Formula of all the price list lines will be changed to the Formula entered in the Name field.

7. Select the Formula Name. Do not select a Formula Name if you selected No Change from the Type of Data Change list. Click the Search icon to display all the dynamic and static formulas.

Price Lists 5-97


8. In the Value region, select how the value should be changed for the selected price list lines:

■ No Change: The value of all the price list lines remains the same.

■ Replace Value: The value of all the price list lines will be changed to the value entered in the Change By field.

■ Amount: The value of all the price list lines will be increased/decreased by the value entered in the Change By field.

■ Percent: The value of all the price list lines will be increased/decreased by the percentage value entered in the Change By field.

■ Clear Value: The value of all the price list lines is changed to Null.

9. When you have completed your entries, click Refresh Data to view your changes.

The Bulk Change: Make Changes page displays both the new and original values.

10. Click Continue to review the updated price list lines:

■ Changed Value (view-only): Displays the changed value if you entered a value for Type of Value Change and Value Change By.

For example, if the original Value = 100, and you selected Type of Value Change = Increase by Percent, and Value Change By = 10 and clicked Apply, the new Changed Value that displays is 110.

■ Changed Start/End Date: Displays the changed start and end dates.

■ Changed Static Formula: Displays the changes static formula.

■ Changed Dynamic Formula: Displays the changed dynamic formula.

Note: Formulas with Modifier Value as a formula type will not be displayed in the List of Values.

Note: Any validation errors display at the top of the page. You may be able to resolve the error by changing the start and end date values for the price list line.



11. To make revisions (for Bulk Changes), change your entries in the Maintenance Criteria region and click Refresh Data to change all lines. Alternately, change the start date and end date for those lines that have errors and then click Continue.

12. If you are satisfied with your changes, click Continue to display the price list lines (existing and new lines) in the Bulk Change: Review Changes page. These price list lines display the original Value, Formulas, Start and End Dates, as well as the Changed Value, Changed Static Formula, Changed Dynamic Formula, and Changed Start Date, Changed End Date.

13. To make additional changes, click Back to return to the previous page. Only price list lines with changes display in this page.

14. Review your work and click Finish. A Confirmation message displays on the Price List Maintenance page.

Example 1: Bulk Change to increase all price list lines on Corporate Price list and Spring Price List by 10%1. In the Search Price Lists region of the Price List Maintenance page, enter your

search criteria to return the Corporate Price List and Spring Price List. For example, you could do an Advanced Search using a qualifier such as Order Type = Standard to display related price lists. Click Search to view the results.

2. Select the Corporate and Spring price lists from the results and click Bulk Change to display the Bulk Change: Make Changes page.

3. Select the following values:

■ Override box = Selected

■ Type of Value Change = Percent

■ Change By = 10

Note: Whenever you change the values in the Maintenance Criteria region and click Refresh Data, the changes are applied to the original value displayed on the price list lines in the search results, not to the price list line values which are currently in the Bulk Change Window. This means if you updated your price list by 10% from 100 to 110, and you decide you wanted to update to 20%, the price is now 120, not 132.

Price Lists 5-99


4. Click Refresh Data to view the new changes. All the price list lines of the Corporate and Spring price lists display with the changes applied as above.

5. Click Continue to display the Bulk Change: Review Changes page.

6. Click Finish to save the changes. A Confirmation message displays on the Price List Maintenance page.

Example 2: Bulk Change to override the end date for selected linesThe following example shows how Bulk Change can be used to adjust all lines on the VIP price list and the first two price list lines of the Fall price list (out of 10 price list lines). The end date of the price list lines will also be changed to 12-Dec-2003.

1. In the Advanced Search page, enter your search criteria to return the VIP and Fall price lists.

2. When you have completed your entries, click Search to display the results.

3. Select the VIP price list. For the Fall price list, click the Expand icon to view all the price list lines, then select the first two list lines.

4. Click Bulk Change to display the Bulk Change: Make Changes page. In the Maintenance Criteria region, select the following values:

5. Click Refresh Data.

All the lines of VIP price list and first two price list lines of the Fall price list are displayed in a table with the changes applied as above.

6. Click Finish to display the Bulk Change: Review Changes page.

7. Click Finish to save the changes. A confirmation message is also displayed.

Table 5–6 Example 2: Bulk Change to adjust price list lines

Field Name Value

Override box Selected

Type of Date Change Change Dates

Existing End Date December 12, 2003



Example 3: Bulk Change to change price by 10% for a specific itemThe following example shows how the bulk change feature can be used to adjust the price for an item category, for example, orange juice, for all price lists. The current prices will be end-dated by May 31st and the new prices (discounted 10%) will take effect from June 1, 2003-August 3, 2003.

1. In the Advance Search page, select the following search values:

2. Click Search to view results in the Results: Price Lists region.

3. Select all price lists and click Bulk Change to display the Bulk Change: Make Changes page.

4. In the Maintenance Criteria region, select the following values:

5. Click Apply. All the lines of the Corporate price list are displayed with the changes applied as above.

6. Click Next to go to the Bulk Change: Review Changes page.

7. Click Submit to save the changes. A confirmation message confirms that the changes have been made.

Table 5–7 Example 3: Search Price Lists region

Field Name Value

Product Attribute Item Category

Product Value Orange Juice

Table 5–8 Example 3: Maintenance Criteria region

Field Name Value

End Date and Create New Selected

Type of Date Change Change Dates

Existing End Date May 31, 2002

Retain Existing Start Date box Selected

New Start Date June 1, 2003

New End Date August 31, 2003

Type of Value Change Percent

Change By 10

Price Lists 5-101


Example 4: Bulk Change to an item to a Dynamic Formula The following example shows how Bulk Change can be used to update the price of item AS54888 on Vision Operations’ price lists to a Dynamic Formula (F1) by clearing the Value and attaching a dynamic formula.

1. In the Search Price Lists region of the Price List Maintenance page, enter the search criteria:

2. Click Go to view the results.

3. Select the Vision Operations price list and then click Bulk Change to display the Bulk Change: Make Changes page.

4. In the Maintenance Criteria region, select the following values:

5. Click Refresh Data. All the price list lines for the selected price list display with the changes applied as above.

6. Click Continue to display the Bulk Change: Review Changes page.

7. Click Finish to save the changes. A confirmation message confirms that the changes have been made.

Table 5–9 Example 4: Search Price Lists region

Field Name Value

Name Vision Operations

Product Attribute Item Number

Product Value AS54888

Table 5–10 Example 4: Maintenance Criteria region

Field Name Value

Override Selected

Type of Formula Change Replace All Formulas with Dynamic Formula

Name F1

Type of Value Change Clear Value



Viewing Validation ErrorsAny validation errors are displayed at the top of the page where the error occurred. Depending on the error, you can change the values in this price list line to resolve the error. Click Refresh Data again to ensure the error disappears.

Note: Whenever you change the maintenance criteria and click Refresh Data, the changes are applied to the price list lines, not to the price list lines values.

Price Lists 5-103



Archiving and Purging Pricing E

6
Archiving and Purging Pricing Entities
This chapter describes archiving and purging pricing entities such as price lists and modifiers and includes the following topics:

■ Overview of Archiving and Purging Pricing Entities on page 6-2.

■ Archiving Pricing Entities on page 6-3.

■ Purging Pricing Entities on page 6-10.

ntities 6-1

Overview of Archiving and Purging Pricing Entities

Overview of Archiving and Purging Pricing EntitiesArchiving pricing data enables you to copy pricing data from the pricing application tables to archive tables for long-term data storage.

You can archive price list and modifier lines. The archiving process permanently removes the lines from the related price list or modifier list into the archive tables for storage.

When the archived data is no longer required (and does not need to be retained for legal requirements), then you can use the purge feature to purge the data from the archive tables.

You can archive and purge price list lines and modifier list lines for the following price list and modifier list types:

■ Agreement Price List

■ Standard Price List

■ Deal

■ Discount List

■ Freight and Special Charge List

■ Promotion

■ Surcharge List

Archiving and purging records reduces the number of pricing records that the pricing engine queries, potentially improving processing performance.





Archiving Pricing Entities Archiving your pricing data enables you to store pricing setups that are no longer active or infrequently used. You can use the Archive Pricing Entities window to archive modifier lines and price list lines. This permanently removes the line information from the associated price list or modifier list.

The archiving process copies data from the application tables to archive tables for long-term data storage. Once the pricing data is copied to the archive tables, it is deleted from the application tables.

When the archived data is no longer required, you can use the Purge feature to purge (remove) the data from the archive tables.

By archiving and purging records, the number of pricing records that need to be queried or processed by the pricing engine is reduced, potentially resulting in improved performance.

The following scenarios show where archiving data can be useful:

■ Easier to delete pricing records created in error: If pricing records are sometimes created in error; you can delete these records.

■ Archive infrequently used pricing records: As pricing setup records accumulate, the performance of the query windows and pricing engine may decrease. If you archive historical pricing setups that are no longer active or infrequently used, the number of pricing records that the pricing engine queries or processes is reduced, potentially improving pricing engine performance.

Note: Only the lines of a pricing entity can be archived. Price list and modifier list header information is copied to archive tables but is never deleted from the pricing application tables.

Warning: You can review the selected records to be archived before submitting the archive request. Once the data is archived, it cannot be retrieved back to the pricing application tables. If you archive in error, you will have to re-create the data for the original header.

You can view the archived data using Pricing database views based on archive tables. A user interface is not available to view records of archived data.

Archiving and Purging Pricing Entities 6-3


■ Archive to retain historical pricing records: For various legal or statutory reasons, your business requirements may require you to keep pricing records for up to 10 years. If you are currently using the Inactive box for each price list and modifier to identify expired lists, you may want to use the archive feature instead. If you do not archive your data, as the number of pricing records (both active and inactive) increase in the database, performance could decrease for accessing pricing setups.

■ Purge archived records: Archived pricing data can be purged from the archive tables. The data must be archived first before it can be purged. See Purging Pricing Entities on page 6-10.

Archiving ConsiderationsOnce the pricing data is archived, it cannot be restored or retrieved to the pricing application tables. Therefore, before archiving data, it is important to consider the following archiving guidelines:

■ Price list headers and modifier list headers will not be deleted from pricing applications tables. However, a copy of price list headers and modifier list headers will be maintained in archive tables for each archive request.

■ In cases where the archiving encountered problems or could not be completed, a message is logged in the concurrent program log with information about the problem.

■ If the All Lines box in the Archive Pricing Entities window is selected, then you cannot select specific product information and all the lines in the list will be archived.

You can use the Archive Pricing Entities window to define your archiving criteria such as specifying which price list lines you want to archive. You can specify a range of product attribute values for Item Number and Item Category.

Note: You can archive and purge from the pricing source system (QP) and available source systems. The archiving and purging windows are available through the Oracle Pricing Manager responsibility. However, if pricing Security is ON, you need to be assigned Maintain Privileges to the pricing entities before you can archive and purge them.



After you have made your selections, click View Selected Records to view the records to be archived. You can either proceed with the archiving or cancel the request.



Archiving Entities ReviewedThe following table list the various pricing entities and special archiving instructions. Not all pricing entities can be archived and you should consult the following table for special instructions:

Table 6–1 Archiving Pricing Entities

Pricing entity to be archived Archiving Notes

Agreement You cannot view the data before archiving.

Excluded items Modifier has no effect on excluded items so if modifier line is archived, there is no impact.

Line accumulations For modifiers, accumulated values are stored in the calling application, not in the modifier setup. User discretion is required when archiving setup of modifier line containing range breaks.

Modifier lines When archiving modifier lines, if you leave the Product Context blank in the archive criteria, all the lines for the selected modifier that do not have product defined will be archived (if the line has been end-dated and falls within the Start/End Date Active range of the request).

Validations Any conditions that cannot be handled are logged in concurrent program log.

Coupons and related lines A coupon line and the attached benefit line will not be archived.

If the archive criteria selected either of the coupon and benefit lines, both lines will not be archived. To archive, you need to delete coupon line then delete benefit line.

Price breaks Can be archived (set up is maintained in archive table).

Price list lines (if the line has been used in a formula: Formula Type=Price List Line)

These lines cannot be archived; causes data integrity issues.

Modifiers with limits Modifiers with limits at the header level cannot be archived. Modifier lines with limits attached to them will not be archived. If the archive criteria selects multiple lines and a few lines with limits are attached, only the lines without limits will be archived.

For lines having limits, a message will be logged in the concurrent program log to indicate that the line was not archived because of limits.

Accrual redemption No Impact



To archive pricing entities:1. Navigate to the Archive Pricing Entities window.

Figure 6–1 Archive Pricing Entities window

2. Enter an Archive Name that uniquely identifies the entity to be archived.

3. Select the Entity Type to be archived:

■ Agreement Price List

Responsibility Archiving and purging is available through the Oracle Pricing Manager responsibility.

Note: Pricing entity security cannot be assigned to the archive and purge features. However, if Pricing Security is on, you must have Maintain access to an entity to archive or purge it.

Table 6–1 Archiving Pricing Entities

Pricing entity to be archived Archiving Notes



■ Freight and Special Charge List

■ Discount List

■ Standard Price List

■ Promotion

■ Surcharge List

4. Select the Source System such as Pricing associated with the entity type to be archived.

5. Select the Entity to be archived such as the price list or modifier list name.

6. In the Lines To Archive region, select one of the following:

■ To archive all lines for the selected Entity, you must first clear the "Active" box on the list header. Once the list is inactive, you can select All Lines. If All Lines is selected, then the remaining fields in the Line To Archive region are grayed out, since all of the lines will be archived.

■ To select specific archiving criteria, complete the remaining steps:

7. The Product Context of Item automatically defaults; however, you can clear the field if you do not want to enter any product information.

8. Select a Product Attribute.

Note: Modifier lists with header limits are restricted from being archived when the archive request is submitted. In addition, the following pricing entities will not archive nor will they display if you click View Selected Records before submitting the archive:

■ Lines with limits

■ Coupon/ benefit lines

■ Formula lines

Note: If you do not select product criteria in the Lines To Archive region, then all the end-dated lines falling within the date range, that do not have product specified in the price list or modifier list will be archived.



9. Select the Product Attribute Value From/To to specify a range of product attribute values for Item Number and Item Category. For all other product attributes, ranges cannot be specified. The exact product attribute value must be chosen.

10. Select the Start Date/End Date Active date range to include modifier or price list lines that are active only within this date range. If you enter a Start Date Active and End Date Active, only lines equal to or less than the Start Date Active and End Date Active will be archived. This is useful, for example, to archive lines for a specific date range, for example, from June to September.

If No Start Date Active is entered, the range is from infinity to the End Date Active.

11. Select Created By to archive records created by a particular system user.

12. Select Creation Date to archive records that were created on a particular system date.

13. After selecting the archive criteria, click View Selected Records to display the Price list or Modifier list window in query mode and review the records that meet the selected archive criteria.

14. Click Submit to archive the records. The archive will be saved using the name specified in Archive Name.

See:Overview of Archiving and Purging Pricing Entities on page 6-2


Note: You must enter a date in the End Date Active field (unless the "All Lines" box is selected).



Purging Pricing EntitiesPurging pricing entities enables you to permanently delete archived pricing data. The data is archived first to prevent the accidental purging of important data from the pricing tables.

Once the data is purged it cannot be retrieved, so it is important to ensure that the data to be purged is not required for legal or statutory retention.

To purge pricing entities:1. Navigate to the QP Purge Entity window.

Figure 6–2 QP Purge Entity window

2. Select the Source System associated with the pricing data to be purged.

3. Select one of the following combination methods to purge the archives. Complete the fields for the selected combination:

■ Archive Name /Entity Type/Entity: A named archive will be purged.

■ Entity Type/Entity: All archives of a selected entity type and entity name will be purged.

■ Archive Start/End Date: Removes all archives falling within the specified range of system archive dates. You also purge all the archives of a specified system archive date using just the End Date Archive.

4. Click Submit to purge the data.



See:Overview of Archiving and Purging Pricing Entities on page 6-2

Archiving Pricing Entities on page 6-3




Multi-Currency Conversion

7
Multi-Currency Conversion Lists
This chapter describes creating and using Multi-Currency Conversion Lists and includes the following topics:

■ Overview of Multi-Currency Conversion Lists on page 7-2.

■ Summary of Multi-Currency Changes to Price Lists and Agreements on page 7-3.

■ Creating a Multi-Currency Conversion List on page 7-5.

■ Considerations for Modifiers Using Multi-Currency Conversion List as a Qualifier on page 7-11.

■ Using Promotional Good type of Modifier Line on page 7-12.

■ Rounding Behavior during Currency Conversion Calculation on page 7-13.

■ Attaching the Multi-Currency Conversion List to a Price List or Pricing Agreement on page 7-17.

■ Updating the Multi-Currency Conversion List on page 7-20.

Lists 7-1

Overview of Multi-Currency Conversion Lists

Overview of Multi-Currency Conversion Lists If you have global customers or do pricing in different currencies, the multi-currency feature enables you to maintain a single price list for multiple currencies.

You can set up and maintain multiple currency conversion rates for a base currency in a single list which can be attached to multiple price lists or agreements. Price list maintenance is reduced because only one currency conversion definition can be attached to multiple base currency price lists. If prices change, you only need to update the base price list.

You can also specify currency-specific markup/markdown equations that are applied as a formula, percent, or fixed amount to mark up the currencies.

When a pricing request is made, the pricing engine converts the price on the base price list to the ordering currency and returns the new price in the ordering currency (including any markup values).

Note: You must have Maintain privileges to make any updates. If you are unable to access or update the multi-currency or related windows, you may not have the appropriate access privileges. Consult your Pricing Administrator.

Note: To set up the multi-currency feature, the following steps must have been completed (usually by your System Administrator or designate):

■ The profile option QP: Multi-Currency Installed must be set to Yes, and the concurrent program Update Price Lists with Multi-Currency Conversion Criteria must be run.

■ The concurrent program should only be run once. For more information, see: Update Price Lists with Multi-Currency Conversion Criteria on page 10-25.

■ Advanced Pricing must be installed and licensed.



Rounding and markup factorsYou can define markup criteria for each currency definition by specifying either a fixed value or one derived from a formula. Specific currency rounding can also be defined for the converted selling price.

Any changes to the base currency must be made in the Multi-Currency Conversion window and not the price list window.

The Base Round To value cannot be updated if the Profile QP: Price Rounding is set to Enforce Currency Precision.

Summary of Multi-Currency Changes to Price Lists and AgreementsWhen the price lists and agreements are converted to multi-currency usage, windows and fields are updated with new multi-currency fields and some existing procedures may change.

The following section summarizes the changes that occur when the multi-currency feature is implemented:

Pricing Engine ChangesThe pricing engine matches the order currency to the currencies attached to the price list at the time of selection. It then applies the conversion type, markup and rounding to the price.

Changes to Price Lists window■ New Multi-Currency Conversion field: A new field called Multi-Currency

Conversion is added to the Advanced Pricing - Price Lists window where you can select a multi-currency list which has the same base currency as the selected price list.

■ Round To procedure: The Round To field in the price list header is grayed out and can no longer be changed directly in the Advanced Pricing - Price Lists window. Instead the Round To value must be changed in the Multi-Currency Conversion window and will update the Round To in the price list header.

Agreements■ New Multi-Currency Conversion field: A new field called Multi-Currency

Conversion is added to the Pricing tab in the Agreements window where you can select a multi-currency list which has the same base currency as the selected price list.

Multi-Currency Conversion Lists 7-3


■ Round To procedure changed: The Round To field in the Pricing Tab is grayed out and can no longer be changed directly. Instead the Round To value must be changed in the Multi-Currency Conversion window and will update the Round To in the Pricing tab. The multi-currency list can be updated only for Agreement Price Lists, not for Standard Price Lists.

Warning: Once the concurrent program has been run successfully, all existing price list and agreement windows are converted to multi-currency price lists. Users should not return to NON multi-currency price lists. Changing the profile back to No may cause undesired results if conversion criteria have been used. Oracle does not support changing the setting back to No.

The following conditions apply if multi-currency is installed: if Oracle General Ledger is not installed, you cannot use the general ledger types as a conversion type.


Creating a Multi-Currency Conversion List

Creating a Multi-Currency Conversion ListA Multi-Currency Conversion List stores a list of currencies and conversion criteria which enables transactions to be converted from a base currency to other currencies. The conversion list is attached to a price list or agreement which uses the conversion criteria to convert the base list prices to the foreign currency amount.

Multiple conversion methods can be in effect at a time for a currency. For example, if converting USD (US dollars) to FRF (French francs), you could have a fixed conversion type for March and a formula conversion type for April.

If more than one multi-currency conversion list is set up for the same base currency, then each conversion list must be assigned a unique name.

Using Conversion TypesConversion types determine how the conversion rate is calculated. Some of these seeded conversion types are only available if Oracle General Ledger is installed; however, you can still link to other non-Oracle stored conversion rate information by using the formula functionality. The following seeded conversion types are available:

■ Fixed: Enter a fixed value that is used as the conversion rate. For example, if you enter a value of 1.5, the list prices from the base price list is multiplied by 1.5 to get the converted amount.

■ Formula: Attach a pricing formula and the value returned from the formula is the conversion rate. A formula with a component type of PLL (Price List Line) cannot be used as a conversion formula because the line may have a different base currency than the price list to which this currency conversion criteria is attached.

■ Transaction: Passes the conversion rate or type from the Order Management (OM) Sales Order.

The following conversion types are available only if Oracle Financials (General Ledger) is installed:

■ General Ledger sourced (Corporate, Spot, EMU Fixed, User Defined): Gets the conversion rate between the Base Currency and Currency To from Oracle General Ledger. These conversion types are available only if Oracle Financials (General Ledger) is installed.



To create a multi-currency list:1. Navigate to the Multi-Currency Conversion List window.

Figure 7–1 Multi-Currency Conversion window

All the fields in the Multi-Currency Conversion List are applicable to the base currency.

2. Enter the Base Currency Code for the currency that the price list is set up in. For example, if the price list has a base currency of US dollars, enter the code for US dollars such as USD.

3. Enter a Name to identify the multi-currency list and a Description.

4. Enter a numeric Base Round To value that rounds the selling prices to the decimal place that is entered. For example, if you entered a Base Round To value of -2, a price calculated as $9874.343 would be rounded as $9874.34.



5. Optionally, select Percent (%) or Amount as the Base Markup Operator which can be applied against the base currency. This Operator determines how the Base Markup Value is applied.

6. Enter a numeric Base Markup Value. This value is applied as either a percent or amount depending on the value defined in the Base Markup Operator field.

7. Enter a Base Markup Formula. The value returned by this formula is applied as a markup to the base currency. When entered, the Base Markup Value can be used within the Base Markup Formula. [Component type as modifier value (MV).]

8. In the Conversion Criteria Detail region, specify the criteria in the following fields to convert the base currency to the currency selected in the Currency To field:

Note: If the profile QP: Price Rounding is set to enforce currency precision, then the Base Round To value cannot be updated in the Multi-Currency Conversion List. To make a change you must first change the profile setting to Enforce Rounding Factor or NULL. Then change the Base Round To. Then change the profile setting back if desired.

Table 7–1 Completing fields in the Conversion Criteria Detail region

Field Meaning

To Currency Code Enter the currency code for a currency that a price list can be converted to using the conversion criteria setup. For example, to convert a base currency in US dollars to Canadian currency (CAD), you enter CAD as the Currency To.

Start Date Start of the currency conversion.

End Date End Date of the currency conversion.



Conversion Type Select one of the following conversion types:

■ Fixed: Enter a fixed number that is used as a fixed conversion rate.

■ Formula: For this type, the value returned by the formula becomes the conversion rate.

■ Transaction: Uses the Conversion rate or Conversion type from the Order Management Sales Order. The following conversion types are available only if Oracle Ledger is installed: Corporate, Spot, EMU Fixed, User Defined.

Fixed Value Enter a numeric conversion value if Fixed was selected as the Conversion Type.

Formula Select a pricing formula name if you selected Formula as the Conversion Type. The value returned by the Formula is the conversion rate. A formula with a component type as PLL (price list line) is not allowed in a conversion formula because the PLL line may have a different base currency than the price list to which this currency conversion criteria is attached. A formula with a component type as MV (modifier value) is also not allowed.

Conversion Date Type Select a Conversion Date Type if the Conversion Type is not Fixed, Formula or Transaction. There are two conversion date types:

■ Pricing Effectivity Date: Uses pricing effectivity date passed by the sales order

■ Fixed: Uses Conversion Date setup for this currency.

Conversion Date Enter a date if the Conversion Date type is Fixed. This date is used to retrieve the daily conversion rate from GL (Oracle General Ledger).

Attribute Type Product Attributes, Pricing Attributes, and Qualifier Attributes are valid values for this field. This specifies the type of attribute to be set up for a currency conversion. This is an optional field.

Attribute Context This is a mandatory field if you entered an Attribute Type. Enter the Attribute Context for the selected Attribute Type. For example, if the Attribute Type is Product Attribute, then its context can be ITEM.


Field Meaning



Attribute Code This field depends on the value entered for Attribute Context. For example, if Attribute Context is ITEM, this field contains its attributes like Item Number. This is a mandatory field when the Attribute Context is entered.

Attribute Value This field gives the values of the Attribute Code entered. For example, if the Attribute Code is Item Number, this field displays all the items. This is a mandatory field when the Attribute Code is entered.

Attribute Meaning This field displays the description of the Attribute Value. This is a display-only field.

Precedence Enter a numeric Precedence value if more than one conversion has the same Currency-To, Start Date, and End Date but different attribute values. See the Precedence example following the table.

The pricing engine uses the precedence value to determine selection priority. If more than one attribute passed from OM Sales Order matches with the attribute setup for currency conversions, then the one with the lowest precedence value is selected by the pricing engine for conversion.

Markup Operator Select either Percent (%) or Amount. This operator is applied to either Markup Value or Markup Formula whichever is entered.

Markup Value This is a numeric constant value that can also be used in the Markup Formula.

Markup Formula Select a formula A formula with Component Type PLL (Price List Line) cannot be used as a conversion formula because the PLL line may have a different base currency than the price list to which this currency conversion criteria is attached.

Note: Both a Markup Value and Markup Formula can be entered, provided the Markup Value is used within the Markup Formula. In this case, the final value is the value returned after computing the Markup Formula.

Conversion Rounding Factor

Enter a numeric Conversion Rounding factor that rounds the list price after the conversion and markup is applied. This rounding factor could be different for the same Currency To.


Field Meaning



Precedence exampleWhen two conversion types with different attribute codes are passed from an Order Management sales order, for example:

Country = India

Item Cat. = CD Pack

then the pricing engine selects the attribute with the highest precedence. The lower the value the higher its precedence so 1 is selected before 2 and so on. In this case, the attribute Country = India is selected by the pricing engine because its precedence value (1) is greater than the precedence value of Item Cat. = CD Pack which is 2.

Round To Enter a numeric Round To value that rounds the selling price after the modifiers are applied. This value will always be the same for a Currency To.

Note: If values for both Conversion Rounding Factor and a Round To are entered for a currency conversion, the Conversion Rounding Factor is applied first followed by the Rounding Factor. This will be applicable for every item (except for the service item) in every pricing event.

Table 7–2 Example of Using Precedence

To Currency Code

Conversion Type

Attribute Code

Attribute Value

Start Date End Date Precedence

FRF Fixed Country USA 3/1/01 3/31/01 4

FRF Fixed Country India 3/1/01 3/31/01 1

FRF Fixed Item Cat CD Pack 3/1/01 3/31/01 2

FRF Fixed — — 3/1/01 3/31/01 3


Field Meaning



Considerations for Modifiers Using Multi-Currency Conversion List as a QualifierA modifier has a single currency. You need to create currency-specific modifiers.

Modifiers can be created in different currencies. The modifier will be selected and applied when the modifier currency is the same as price list's Base or To Currency.

To attach a multi-currency price list as a qualifier for a modifier:1. Navigate to the Advanced Pricing - Define Modifier window.

2. Do a search or create a modifier and its respective currency; for example, a modifier in CAN (Canadian dollars).

3. Click List or Line Qualifiers button to display the qualifiers window.

4. Enter Modifier List in the Qualifier Context field.

5. Enter Price List in the Qualifier Attribute field.

6. Select a Price List that has Base Currency or To Currency defined with the same currency as in the modifier header.

7. Save your work.

Using a formula with component type as Price List Lines1. Navigate to the Advanced Pricing - Define Modifier window.

2. Query or create desired modifier for a discount.

3. Select a Formula. If selecting a formula with a component type as Price List Line, the base currency of the price list must be the same as the modifier currency.

4. Save the modifier record.



Using Promotional Good type of Modifier LineFor a Promotional Good (PRG) type of modifier line, in the Get Product list for the list line, you must select the price list whose currency is the same as the modifier currency.

If you create a promotion with a Get Item, you must ensure that the base currency for the modifier (promotion) price list is the same as the base currency for the Get Item price list (Header). Otherwise, the pricing engine will not select or apply the Get Item.

To use promotional good type of modifier line with multi-currency:1. Navigate to the Advanced Pricing - Define Modifier window.

2. Query or create desired modifier for the promotional good that uses the foreign currency; for example, French Francs.

3. In the Modifier Summary window, select a line with the Modifier Type of Promotional Goods.


5. In the Get region where you specify the Get Item details, select the required information about the Get Item.

6. In the Get Price field, select a price list from the Benefit Price field where the Base Currency = FRF has been defined.

7. Save the modifier record



Rounding Behavior during Currency Conversion CalculationThe following examples show you how rounding is calculated during currency conversion calculations.

If the Conversion Rounding Factor and the Round To values in the Multi-Currency Lists window are entered for a currency conversion, the conversion rounding factor will be applied first, followed by the Round To factor.

This is applicable for every item (except for the service item) in every pricing event.

Example 1

Price List Setup■ Base Currency Code = USD

■ List Price for Item A = 60.12345

Multi-Currency Conversion List attached to the Price List■ To Currency Code = CAD

■ Conversion Type = FIXED

■ Conversion Rate = 2.0

■ Conversion Rounding Factor = -2

■ Round To = -3

Sales Order Setup for a non-service item A■ Order Currency = CAD

■ Converted Price before rounding = 60.12345*2 = 120.24690

■ Price after applying conversion rounding = 120.25

■ Price after applying the Round To (final rounded price) = 120.250

■ Price displayed on the Sales Order = 120.2500 (after applying -4 currency precision for CAD)



Example 2In Service Pricing, the service item is rounded using the Round To, not the conversion rounding factor.

Price List Setup■ Base Currency = USD

■ List Price for Item B = 60.12345





■ Round To = -3

Sales Order Setup for a service item B■ Order Currency = CAD




Example 3 QP: Selling Price Rounding Options = Individual

The profile QP: Selling Price Rounding Options only affects the rounding factor. If the profile is set to Individual, then the rounding factor is applied. If it is set to No, the rounding factor is not applied. The profile QP: Round Unit Selling Price does not affect the Conversion Rounding Factor. The Conversion Rounding Factor is always applied to the list price.









■ Round To = -2



■ Price after applying conversion rounding = 120.247


■ Price displayed on the Sales Order = 120.2500(after applying -4 currency precision for CAD)

Example 4QP: Selling Price Rounding Options = N (No)







■ Round To = -2





■ Price after applying Conversion Rounding Factor = 120.247



Attaching the Multi-Currency Conversion List to a Price List or Pricing Agreement


Once you have created a multi-currency conversion list in the Multi-Currency Conversion window you can attach it to a price list or agreement. You can select the Multi-Currency Conversion List from the Currency Conversion Criteria field in the price list or agreement.

To attach the multi-currency conversion list to a price list:1. Navigate to the Advanced Pricing—Price Lists window.

Figure 7–2 Advanced Pricing - Price Lists: Multi-Currency enabled

Note: When multi-currency is first set up, a default multi-currency list without conversion criteria is automatically generated by the system and attached to price lists and agreements. You can replace the default list by selecting an alternate Multi-Currency Conversion list.



2. Select the multi-currency list from the Multi-Currency Conversion field.

The field displays all currency conversion lists where conversion criteria base currency = currency of the price list.

When multi-currency is enabled, the Round To field in the price list is grayed out and can only be updated in the Multi-Currency Conversion window.

3. Save your work.

To attach the multi-currency conversion list to an agreement:1. Navigate to the Pricing Agreements window.

Figure 7–3 Pricing Agreements window

2. Enter Agreement Type, Standard or Agreement.

For Standard Agreements, you must select a Price List. The base currency, rounding factor, and Multi-Currency Conversion attached to that price list will default to the window.



3. For Agreement price lists, in the Pricing tab, select a Multi-Currency Conversion.

For Agreement price lists, you can select lists where the base currency of the multi-currency conversion list is the same as the base currency of the agreement. When multi-currency is enabled, the Rounding Factor field in the agreement is grayed out and can only be updated in the attached Multi-Currency Conversion.

4. Save your work.


Updating the Multi-Currency Conversion List

Updating the Multi-Currency Conversion ListIf you want to change or update conversion criteria such as increasing the conversion fixed rate from 2.2 to 2.3, you can make your changes in the Multi-Currency Conversion window. You can update information at both the header and line levels.

To update the multi-currency conversion list:1. Navigate to the Multi-Currency Conversion window.

2. Complete the required changes in the Multi-Currency Conversion List or the Conversion Criteria Detail regions (header and line levels) using the suggested best practice.

If you are changing Conversion Criteria Details, and you want to prevent unexpected conversion behavior and loss of historical data enter an End Date for the detail line, and enter a new line with the desired changes and a new Start Date.

3. Save your changes.

All saved changes to a multi-currency conversion list are immediately available to all price lists and pricing agreements to which the list is attached.

Warning:

■ Header Level changes: Be cautious when updating header level information such as Markup because you will lose historical information.

■ Line Level changes: Be cautious when updating line level information in the Conversion Criteria Detail region to avoid loss of historical information. To prevent unexpected conversion behavior and loss of historical data, enter an End Date for the detail line and enter a new line with the desired changes including a new Start Date before updating any setup information.


Agreem

8
Agreements
This chapter describes agreements and includes the topics:

■ Overview of Creating Agreements on page 8-2.

■ Creating Agreements on page 8-5.

■ Revising an Existing Agreement on page 8-14.

■ Finding Agreements on page 8-17.

■ Deleting Agreements on page 8-18.

ents 8-1

Overview of Creating Agreements

Overview of Creating AgreementsOracle Advanced Pricing enables you to establish agreements with your customers that define the prices, payment terms, and freight terms that you negotiate. You can:

■ Define your agreements using customer part numbers and inventory item numbers.

■ Make revisions to the original terms and maintain these changes and their reasons under separate revision numbers.

■ Attach an already existing price list to the agreement or define new prices.

■ Assign optional price breaks by quantity. Price lists are exclusive by agreement.

■ Set effectivity dates for agreement terms.

■ Set payment terms including invoice rule and accounting rule.

■ Set freight terms including the freight carrier.

■ Apply agreement terms to sales orders by reference agreements.

Types of AgreementsThere are two types of agreement:

■ Standard Price List: Used, for example, to have one price list for all customers but to default special terms onto a sales order for a specific customer.

■ Agreement Price List: Used to offer a negotiated price for an item to a customer.

Note: If you are using the multi-currency feature with agreements, see: Attaching the Multi-Currency Conversion List to a Price List or Pricing Agreement on page 7-17.

■ You can only view or update a price list on an agreement in your pricing transaction entity. The profile QP: Pricing Transaction Entity must match the pricing transaction entity of the price list attached to the agreement.

■ You can only view or update a price list on an agreement in your source system. The profile QP: Source System Code must match the source system of the price list attached to the agreement. Otherwise, the price list on the agreement is view-only.



The following table compares the two agreement management methods:

Customer MergeWhen you merge customers in Oracle Receivables, you can merge:

■ The information from one customer (the From customer) with the information from another customer (the To customer).

■ The information from one or more customer sites of that customer (the From sites) with the site information from the other customer (the To sites).

If the From customer is party to agreements, the Oracle Receivables merge process executes an Oracle Advanced Pricing process to update the following agreements information:

■ If you merge customer: The process changes the customer name on the agreement from the From customer to the To customer. Verify this change in the Pricing Agreements window, Agreement tab, Customer, and Cust Number fields.

Table 8–1 Comparison of Standard versus Agreement Price Lists

Standard Price Lists Agreement Price Lists

Agreement lines not allowed. Agreement lines required.

Associated with standard price list (type PRL).

Associated with agreement price list (type AGR).

Maintain and view price list lines through Price List window.

Maintain and view price list lines through Agreement window.

Use each standard price list with multiple standard agreements and to price orders associated or not associated with an agreement.

Use each agreement price list with multiple pricing agreements. Not usable to price orders not associated with an agreement.

Cannot revise price list lines using agreement window.

Can revise price list lines using agreement window.

Agreement number not automatically created as a qualifier for the associated price list.

Agreement number automatically created as a qualifier for the associated price list. You can specify the pricing agreement on an order.

Agreements 8-3


■ If you merge sites: The process changes the invoice address from the From customer site to the To customer site. Verify this change in the Pricing Agreements window, Payment tabbed region, Invoice To and Address fields.

Note: Pricing Security privileges affect Pricing Agreements by inheriting the security rules associated with any Price Lists. You can select a price list to associate with an agreement at setup if your privileges authorize view access to the price list. You cannot change the price list or change its relationship to an agreement if you do not have Maintain access to the price list.

If you have access issues, consult your Pricing Administrator.



Creating AgreementsUse this process to create pricing agreements.

Security Privileges and AgreementsPricing Security privileges affect pricing agreements by inheriting the security rules associated with any Price Lists. You can select a price list to associate with an agreement at setup if your privileges authorize view access to the price list. You cannot change the price list or change its relationship to an agreement if you do not have Maintain access to the price list.

If you have access issues, consult your Pricing Administrator.

Note: The Agreement field does not display by default on the Oracle Order Management order header. You must use the Folder icon to display it.

Agreements 8-5


To create a price agreement:1. Navigate to the Pricing Agreements window.


2. Enter an Agreement Name that identifies the agreement.

3. Enter an Agreement Number if it has been assigned to the agreement.

The Revision Number defaults to 1. However, this number may change as new revisions are created; for example, from 1 to 2.

The Revision Date defaults to the current system date.

4. Enter a Customer name and Number.

5. Select an Agreement Type such as a Standard Terms And Conditions.

6. Select a Contact name.

7. Enter the Effective Date range for the agreement. If an end date is not entered, the agreement will be active for an indefinite period. However, if you are creating revisions, you will need to end the current agreement.



8. Enter a name for the Sales Person.

9. Enter the customer’s Purchase Order number.

10. Enter a Signature Date for the purchase order.

The Agreement Source field (view-only) displays the source of an agreement.

11. Select the Pricing tab.

Figure 8–2 Pricing Agreements window: Pricing tab

12. Select the Price List Type:

■ Select Standard Price List to associate a standard agreement.

■ Select Agreement Price List to associate an existing agreement price list to an agreement.

13. Select a Price List:

■ For Standard Price Lists: Select Standard Price List. The Currency, Rounding Factor, Description, and Comments fields default from the Standard price list selected. These values cannot be changed in the Pricing Agreements window.

■ For Agreement Price Lists: You can create a new price list name or select an existing Pricing Agreement price list.

Agreement price lists are maintained only in the Pricing Agreements window. Agreement price lists can be adjusted or modified unlike Standard Price Lists.

Complete the following steps if creating an Agreement Price List:

Agreements 8-7


If you choose an existing Agreement Price List, the Currency, Rounding Factor, Description, Freight Carrier, Freight Terms and Comments fields will default from the price list. However, if you change the values for any of these fields, the information will be changed for all Pricing Agreements using this price list.

14. Select a Currency.

15. Enter a Rounding Factor.

16. Enter a price list Description.

Complete the following steps for both Standard and Agreement price lists:

17. Enter a default Freight carrier.

18. Enter default Freight Terms.


20. Select the Payment tab.




21. Select the Payment Terms.

■ When you enter a sales order in Oracle Order Management and the agreement uses a Standard price list, the payment terms default from that price list. You can override the price list terms on the agreement.

■ When you enter a sales order in Oracle Order Management and the agreement uses an Agreement price list, the payment terms default from those that you enter in this field.

22. Enter the bill-to name in Invoice To.

23. Enter a bill-to Address.

24. Enter the bill-to contact in Invoice Contact.

25. In the Rules region, select a default Accounting Rule.

Agreements 8-9


26. Select the Invoicing rule.

To create agreement lines:For Standard Price Lists: The agreement line details default from the Standard Price List entered in the Price List field in the Pricing tab. These fields cannot be changed or additional lines cannot be entered from the Agreement Lines. Changes and additional price list lines must be made on the Price List from the Price List Setup window.

For Agreement Price Lists: If you attached an existing Agreement Price List, the agreement lines default from that price list. You can make changes to the agreement line details, and add additional agreement lines. Any changes or additions that you make will be reflected on the other agreements that this price list is attached to.

1. In the lowest region of the window, enter Product Value. If there is a customer item associated, the customer item number will be defaulted to the Customer Item field. Customer Item is a pricing attribute.

2. Enter a unit of measure (UOM).

3. Select Primary UOM if this price list line unit of measure is the primary pricing unit of measure for the item. The pricing engine uses the primary pricing unit of measure and the Oracle Inventory unit of measure conversion information to price an order whose unit of measure does not have a price list line. For

Note: Accounting and invoicing rules are set up in Oracle Receivables.

In the Override Flag region, the override check boxes for the Accounting and Invoicing Rules are for information only.

Caution: The defaulted values for customer item, address and address category should not be changed in this window. Changes to these should be made where the customer item relationship is maintained. Create the accounting and invoicing rules in Oracle Receivables.

When you have created a customer item relationship with an internal inventory item and you enter the inventory item product value, the customer item, address, and address category will be defaulted.



example, a price list has two price list lines for item A11111, one with unit of measure EA, the primary UOM, and one for boxes. When the pricing engine receives an order in unit of measure CS, it accesses the unit of measure conversion tables to convert CS to EA.

4. Select Price List Line in Line Type.

5. Select Unit Price for Application Method

6. Enter a base price inValue.

7. Enter the effectivity dates in Start Date and End Date. They should be within the effectivity dates of the agreement.

8. Enter the Comments.

9. Enter a Revision number.

10. Enter a Revision Date.

11. Save your work.

Note: To create list of reasons, see: Oracle Advanced Pricing Implementation Guide, Lookups.

Note: You cannot enter an item category in Product Value.

Agreements 8-11


To define pricing attributes:1. Click Pricing Attributes in the Pricing Agreements window to display the

Pricing Attributes window.

The Product Context, Product Attribute and Product Value default from the Agreement Line that you are entering.

Figure 8–4 Pricing Attributes window

2. Enter a Pricing Context.


4. Enter the Value From/To.

5. Save your work.

To define price breaks:1. Enter an agreement line with price breaks:

■ Enter Price Break Header in Line Type.

■ Enter Point or Range in Price Break Type.

2. Click Price Breaks to display the Price Breaks window. The Price Breaks button is enabled only when you select the Price Break Header in Line Type on the agreement line.

Note: The pricing attributes are joined as AND conditions since they apply to one price list line.



Figure 8–5 Price Breaks window

In the Price Breaks window, the Pricing Context defaults to Volume; Pricing Attribute defaults to Item Quantity; and the Application Method defaults to Unit Price. The Pricing Context cannot be changed.

Complete the remaining steps for each price break that you define:

3. Enter the Value From/To.

4. Enter the list Price.

5. Save your work.


Agreements 8-13


Revising an Existing AgreementIf you need to make minor changes to an existing agreement such as changing the payment terms, you can simply change the agreement terms and save the changes. This simply updates the existing agreement with your new changes.

However, if significant changes are required and you want to keep a record of previous agreements, you can create a new revision. This does not overwrite the existing agreement but creates a new version of the original agreement. This is useful if you want to track and manage multiple versions of the same agreement.

You must determine when changes warrant a new agreement version, and then manually create a new revision and revision number. For tracking purposes, a logical revision numbering system will help you better manage your agreements such as numbering the revisions 2, 3, 4 and so on.

Once the new agreement revision is created, you can update the agreement header information.

Note: You must end the current revision before creating a new revision. An agreement can have multiple revisions but the effective dates cannot overlap. Only one revision can be effective for a given range of effective dates.



To revise an existing agreement:1. Find the original agreement you want to revise.


2. Click Create Revision to display the Create Revision window.

Note: The original agreement must have an effective end date entered and saved before a new revision can be created. The end date can be past, current, or future; however the date ranges for any revisions cannot overlap. Only one revision can be in effect for a given range of effective dates.

Agreements 8-15


Figure 8–7 Create Revision window

The Agreement Name defaults from the original agreement. Although you cannot change the agreement name, you can change the revision number. The Revision Date defaults to the current date.

3. Enter the Revision Number to identify the version of the agreement you are creating. This is helpful in tracking and managing different revisions of the agreement.

4. Enter the effective start and end dates for the agreement. Date ranges cannot overlap, and only one revision can be in effect for a given range of effective dates.

5. Select a Revision Reason that describes why the agreement is being revised.

6. Click Create to display the new agreement in the Pricing Agreements window. The new revision number displays in the Revision field.

Note: Revisions to the agreement header do not revise the pricing lines for the agreement. A change to the price list lines affects all agreements that the price lines are attached to.



Finding AgreementsUse the Find Agreements windows to find agreements or agreement revisions by one or more of the following criteria: Agreement Name, Agreement Number/Revision, Invoice To, Price List, Customer, Cust Number, Agreement Type, Contact, Invoice Contact, or Sales Person.

To find agreements:1. Navigate to the Find Agreements window.

Figure 8–8 Find Agreements window

2. Enter your search criteria.

3. When you have completed your entries, choose Find to display the search results.

Note: To create a new agreement, choose the New button.

Agreements 8-17


Deleting AgreementsPricing agreements can be deleted if they have not been used in any previous order transactions. Once sales order lines have been attached to an agreement, the agreement cannot be deleted. If you attempt to delete an agreement with sales order lines attached, a warning note notifies you that the agreement cannot be deleted.

To delete agreements:1. Navigate to the Pricing Agreements window.

2. Find the Pricing Agreement to delete.

3. From the Edit menu, select Delete to delete the pricing agreement.


Pricing Engine Request V

9
Pricing Engine Request Viewer
This chapter describes using the Pricing Engine Request Viewer window to capture the pricing call from any calling application such as order management and display the inputs and outputs of the pricing call. The following topics are described:

■ Features available in the Pricing Engine Request Viewer window on page 9-2.

■ Process for the Pricing Engine Request Viewer on page 9-3.

■ Setting up the user profile options on page 9-3.

■ Viewing Information in the Pricing Engine Request Viewer on page 9-5.

iewer 9-1

Overview of the Pricing Engine Request Viewer

Overview of the Pricing Engine Request Viewer The Pricing Engine Request Viewer window captures the pricing call from any calling application such as order management and displays the inputs and outputs of the pricing call.

The information displayed by the Pricing Engine Request Viewer enables you to diagnose which lines were selected or rejected by the pricing engine to determine why certain prices and adjustments were or were not applied.

The latest pricing request is displayed. However, historical data is maintained because the Pricing Engine Request Viewer window updates the display information each time the pricing engine captures a new transaction. Previous pricing requests are saved in the pricing tables.

The Pricing Engine Request Viewer window is available from the main Advanced Pricing menu (Pricing Manager responsibility) or in Oracle Order Management using the following navigation path: Sales Orders > Tools > Pricing Engine Request Viewer.

Features available in the Pricing Engine Request Viewer windowUsing the Pricing Engine Request Viewer window, you can do the following:

■ View the pricing, qualifiers, and product attributes passed to the pricing engine along with the other data generated by the engine.

■ View which modifier lines the pricing engine applied or rejected for benefit adjustments along with the details of the modifier line. View price request line of the calling application.

■ View the relationship between order lines for promotional modifiers, price breaks, and service lines:

■ View the formula step values generated by the pricing engine used in formula calculation.

■ View the controls passed by the calling application to the pricing engine such as event, Rounding, Search and Calculate Flag, and GSA.

■ View and query fields in the Pricing Debug Log

You can view the debug log in the Pricing Engine Request Viewer window, and query the record within the debug log to display the lines directly. The results will be the 10 previous lines and the remaining lines of the debug file.

■ Delete the request(s). Navigation is Edit > Delete.



Process for the Pricing Engine Request ViewerThe following process outlines the series of activities when a pricing call is made:

1. The calling application makes a call to build qualifiers and builds the contexts through sourcing.

2. The calling application then calls the pricing engine with the attributes generated by attribute mapping.

3. The pricing engine processes the request then searches for and evaluates eligible price list and modifier lines.

4. If the profile option QP Debug is set to Request Viewer On, then the pricing engine inserts records into the permanent pricing debug tables and generates a unique request ID, storing the information from the calling application.

5. The pricing request information can then be viewed by querying the request in the Pricing Engine Request Viewer from the Order Management Sales Order Pad or through the Pricing Manager responsibility menu.

Setting up the user profile options

QP: Debug Set the value of this profile option to Request Viewer On when you want the Request Viewer to capture pricing request details into the pricing debug tables and debug log information into the debug log table. The debug log text file is also created. The default value is Request Viewer Off.

The setting is active for the transactions for the user who set this profile option—other users' transactions are not affected.

QP: Set Request Name The profile option QP: Set Request Name is used in conjunction with the QP: Debug profile option. Set QP: Set Request Name to Yes if you want the value in the Request Name field prefixed to the OrderID. For more information on setting up profile options, see: Oracle Advanced Pricing Implementation Manual, Profile Options.

Note on performance: Setting the profile QP: Debug will slow the performance of the Pricing Engine Request Viewer. The concurrent request Purge Pricing Engine Requests purges the pricing engine requests, and it should be run on a regular basis to purge the historical data from the pricing debug tables. Periodically purging the historical data will improve the performance of the Pricing Engine Request Viewer window.

Pricing Engine Request Viewer 9-3


See:Purge Pricing Engine Requests program on page 10-16



Viewing Information in the Pricing Engine Request ViewerThe Pricing Engine Request Viewer window displays detailed information about the price list lines and modifier lines that the pricing engine applied or rejected.

Figure 9–1 Pricing Engine Request window

The transaction details are displayed in one or more of the following regions in the Pricing Engine Request Viewer window:

Pricing Engine Requests regionThis region displays information about the pricing requests with its associated controls sent by the calling application to help you locate the problem.

For Request Type ONT only, the order number associated with the request is displayed.



Pricing Engine Request Lines regionThis regions shows information about the lines being priced including line number, unit price and adjusted unit price. You can view information related to service and serviceable lines in this region.

The Request Id + Line Index column maintains the master-detail relationship between the lines and line details. This block is used to change operand value, select/de-select modifiers, change manual modifiers and change buckets.

Pricing Engine Request Line Details regionThis region displays information regarding processed price list lines and modifiers lines selected and/discarded (eliminated/rejected) by the engine. The Priced box indicates which lines were finally selected for pricing by the pricing engine. The Applied check box indicates which lines were considered in calculating the selling price.

This region also displays the information for item upgrades, coupon issue, term substitution, freight and special charges, and relationships between price breaks.

Pricing Debug windowClick View Debug Log to view the debug log in the Pricing Engine Request Viewer window. You can then query a record within the debug log to display the lines directly. The results display the ten previous lines and the remaining lines of the debug file.

Note: Depending on the version of Oracle Advanced Pricing installed, the order and line numbers for orders created in prior releases may not display in the Pricing Engine Request Viewer window. However, order and line numbers created in subsequent releases can be viewed.

Note: For lines of type LINE, the Line No. field displays the appropriate line number from the Order Entry page. For lines of type ORDER, the order number associated with that request displays. For requests of type PRICE, the line number for the request lines of type LINE does not display.



Attributes windowClick the Attributes button to display all attributes for a selected line or line detail. The region displays information about the pricing attributes that the attribute mapping function passed to the pricing engine. The pricing engine uses these attributes to qualify a line or an order for price and adjustments:

■ Click Attributes from the Request Lines region to display the attributes passed to the pricing engine.

■ Click Attributes from the Request Line Details region to display the attributes related to the selected price list lines/modifier line.

Pricing Debug Related Lines windowChoose Related Lines from the Pricing Engine Request Viewer window to display the Pricing Debug Related Lines window. The cursor must be in the Engine Request Lines Details region. You can view the relationship between the Buy and Get items for Other Item Discounts and Promotional Goods.

Formula Step Values windowWhen your cursor is in the Pricing Engine Request Lines Detail region, click Step Values in the Pricing Engine Request Viewer window to display the Formula Step Values window.




Reports and Concurrent Pr

10
Reports and Concurrent Programs
This chapter describes Oracle Advanced Pricing reports and concurrent programs. A general description about the programs and submission parameters is provided for each of the following reports and concurrent programs:

■ Accrual Details report on page 10-3.

■ Attribute Mapping Rules Error report on page 10-4.

■ Build Attribute Mapping Rules program on page 10-10.

■ Build Formula Package program on page 10-5.

■ Cross Order Volume Load on page 10-8.

■ Cross Order Volume Report on page 10-10.

■ Modifier Details report on page 10-11.

■ Price Lists report on page 10-13.

■ Pricing Formulas report on page 10-15.

■ Purge Pricing Engine Requests program on page 10-16.

■ QP: Bulk Import of Price List program on page 10-17.

■ QP: Maintains the Denormalized Data in QP Qualifiers on page 10-22.

■ Qualifier Grouping report on page 10-24.

■ Update Price Lists with Multi-Currency Conversion Criteria on page 10-25.

■ Update Promotional Limit Balances program on page 10-28.

ograms 10-1

Overview of Reports and Concurrent Programs

Overview of Reports and Concurrent ProgramsOracle Advanced Pricing provides reports and concurrent programs that enable you to administer, manage, and review your pricing operations and data to:

■ Determine what pricing information has been established; for example, active price lists, formulas and qualifiers.

■ Communicate pricing information internally and externally; for example publishing price lists to internal and external users.

■ Take action based on order or pricing activity; for example, issuing a credit memo based on reported accruals.

Note: When Pricing Security is ON, security privileges determine which pricing entities can be viewed from the list of values. View or Maintain privileges determine the actions you can do in various windows.



Accrual Details reportThe Accrual Details report enables you to run a report to view modifiers that have been set up for accruals or those with associated Coupon Issue information. Using this report, you can quickly see which coupons have been issued and the coupon numbers generated for a modifier.

Report SubmissionIn the Submit Request window, Name field, select Accrual Details.

Report Parameters

Figure 10–1 Accrual Details Report

■ Modifier Name From/To: Select a range of modifier names to narrow the report to the names that fall between the specified range. For example, if you specified modifier names A to F, modifiers names G and H would not be included in the report.

■ Start/End Date Active: Select the start and end date range of the modifiers to be included in the report.

■ Qualifier Context: Select a Qualifier Context to narrow the report to only those modifiers with the selected Qualifier Context.

■ Qualifier Attribute Value From/To: Select specific qualifier attribute to further define the selected qualifier context.

Reports and Concurrent Programs 10-3


Attribute Mapping Rules Error reportThis program produces a list of all attribute mapping rules that are invalid. The program will give warning when the program completes with Attribute Mapping errors and provides other status messages:

■ Success: Program completes without Attribute Mapping errors.

■ Warning: Program completes with one or more Attribute Mapping errors.

■ Error: Program cannot complete due to some exception/runtime error. The report displays an entry in the file log for every attribute mapping rule that is invalid. The entry includes details such as the context, attribute, pricing type, request type, attribute mapping rule, and the error message produced by the invalid mapping.

You can run the report for a single Request Type such as ONT (Order Management Order) or all request types.

The number of errors displays on the log after the report is run.

Report SubmissionIn the Submit Request window, Name field, select Attribute Mapping Rules Error Report.

Report Parameters

Figure 10–2 Attribute Mapping Rules Error Report parameters

Request Type: Select a single Request Type or leave blank to run report for all request types.



Build Attribute Mapping Rules programThis program generates entries into the BUILD_CONTEXTS application program interface (API). You pre-generate entries into this API so that the pricing engine evaluates only the qualifier and pricing attributes used in the price lists, modifiers, and formulas that are relevant to each call rather than all of the attribute mapping rules.

Report SubmissionRun this program after you:

■ Make a change to the mapping rule for a specific qualifier attribute. For example, run this process after you map the Geography context to a qualifier attribute.

■ First use a qualifier in either a modifier or a price list. For example, run this process after the first time that you use Customer Class as a qualifier for a price list or modifier.

In the Submit Request window, Name field, select Build Attribute Mapping Rules.

Run the process during a time when most users are not logged onto the system. You may encounter a record locking problem if this process runs at the same time that the pricing engine is processing calls.

Report ParametersNone

RecoveryIf the process fails:

■ The QP_BUILD_SOURCING_PVT package becomes invalid.

■ All subsequent pricing calls fail.

Note: The Build Attribute Mapping Rules program will source the attributes that are used only in the active pricing setup if the profile value QP: Check For Active Flag is set to Yes. If the profile value QP: Check For Active Flag is set to No, this program sources the attributes that are used in both the active and inactive setup. The default value of the profile QP: Check For Active Flag is No and can be updated only at the site level.



To recover:1. Check the concurrent program log to view any errors. If needed, log into

SQL/PLUS and check the errors associated with compiling the QP_BUILD_SOURCING_PVT body. Problems may include:

■ You reference an API in an attribute mapping rule and the API is invalid or does not exist.

■ You have a typographical error in an attribute mapping rule that refers to an API or global structure.

2. Fix the attribute mapping rule in the Attribute Mapping window.

3. Rerun this concurrent process.



Build Formula Package programEvery time when a new formula expression is set up, the concurrent program Build Formula Package should be run to generate the formula package. Every time a new formula expression is created or updated, a Warning dialog box displays a message to run the concurrent program Build Formula Package.

This concurrent program builds the Formula Package containing statements which uses bind variables for evaluating the formula value. This generated package is called from the main engine formula package at run time to calculate the formula value.

Report SubmissionIn the Submit Request window, Name field, select Build Formula Package.


Note: If the Formula expression already exists in the current generated formula package, the Warning box does not display.



Cross Order Volume LoadRun the program Cross Order Volume Load to populate the cross order volume tables. The qualifier and pricing attribute mapping functions determine the cross order volumes for a customers and customer-item combinations.

The Cross Order Volume Load considers orders and order lines in Booked status, but does not consider returned or cancelled order lines.

The cross order volume profile options determine the order lines included in the cross order volumes.

For example:




■ Concurrent process Cross Order Volume Load, Effective Date: 31-December

■ Cross order period 1: Order lines with request date between 1-December and 31-December

■ Cross order period 2: Order lines with request date between 1-November and 31-December-2000

■ Cross order period 3: Order lines with request date between 2-October and 31-December-2000

Report SubmissionIn the Submit Request window, Name field, select Cross Order Volume Load.

Report Parameters

Figure 10–3 Cross Order Volume Report parameters



■ Operating Unit: Enter either a single operating unit or leave blank for all operating units.

■ Effective Date: Provide the load effective date; otherwise the program uses the current date.



Cross Order Volume ReportRun the Cross Order Volume Report to view the information in the cross order volume tables. The report displays the total order amount, total item amounts and total item quantities for each customer and period.

The cross order volume loader only accumulates orders for items in the Cross Order Item Amount/Quantity Summary that have modifiers using the cross order volume attributes. Similarly the engine only gives total Cross Order summaries if a cross order qualifier has been used in a modifier.

Therefore, it is necessary to run the cross order volume concurrent request after you set up any modifiers using either (a) a cross order amount qualifier that has not been used previously or (b) a cross order item amount/quantity pricing attribute for an item that has not been used previously. This ensures that all item totals are accumulated and loaded into the cross order tables.

Report SubmissionIn the Submit Request window, Name field, select Cross Order Volume Report.




Modifier Details reportThis report displays modifier information.

Report SubmissionIn the Submit Request window, Name field, select Modifier Details.

Report Parameters

Figure 10–4 Modifier Details Report parameters

■ Modifier Number From/To: Enter the range of modifier numbers for which you want the report generated.

■ Modifier Name From/To: Enter the range of modifier names.

■ Modifier Version From/To: Enter the range of modifier versions.

■ Start Date Active/End Date Active: Enter the range of dates for the active modifiers.



■ Active Modifier Only: Select Yes to display only active modifier lists and No to display all modifier lists.

■ Active Modifier Lines Only: Select Yes to display only active modifier lines or No to display all modifier lines.

■ Item Name: Select item name criteria to display modifiers for the item names you specify.

■ Item Category: Select item category criteria to display modifiers for the item categories listed.

■ Customer Name: Select customer name criteria to display modifiers associated with the specified customer names.

■ Customer Class: Select customer class criteria to display modifiers assigned to the specified customer classes.

■ Price List: Select the price list criteria to display modifiers associated with the specified price list.



Price Lists reportThis report displays the following price list information:

■ Report by price list name.

■ Options to print report for active and inactive price lists based on effectivity date. If multi-currency is enabled, prints other currency setup if the price list is multi-currency enabled.

■ Display all other header information. If price list is multi-currency enabled, report includes header information from the associated Multi-Currency Conversion list.

■ Qualifiers attached to price list.

■ Secondary price lists attached to price list.

■ Detail of list lines attached to price list.

■ Detail of item (for example, inventory item, service item).

■ Pricing attributes for item.

■ Price breaks for item.

■ Price Formulas attached to price list line.

Report SubmissionIn the Submit Request window, Name field, select Price Lists.

Report Parameters

Figure 10–5 Price List Report parameters



■ Price List From/Price List To: Enter a price list or a range of price lists.

■ Start Date Active/End Date Active: Enter a date or a range of dates.

■ Active Flag: Enter Yes to display active price lists only or No to display all price lists. The default is Yes.

■ To Currency Code: Select one Currency To multi-currency conversion list setup information or None.

If the multi-currency feature is enabled for a price lists, the names of the attached Currency Conversion Criteria, Base Markup Operator, Base Markup Value, and Base Markup Formula are returned.



Pricing Formulas reportThis report displays pricing formulas and their details, including factor lists.

Report SubmissionIn the Submit Request window, Name field, select Pricing Formulas.

Report Parameters

Figure 10–6 Pricing Formulas Report parameters

■ Formula From/To: Enter an individual formula or range of formulas.

■ Price List From/To: Enter an individual price list or a range of price lists.

■ Start Date Active/End Date Active: Enter an individual date or a range of dates.



Purge Pricing Engine Requests programThis program purges all pricing engine requests or selected requests. The program should be run on a regular basis to purge the historical data from the pricing debug tables. This improves the performance of the Pricing Engine Request Viewer window.

Report SubmissionIn the Submit Request window, Name field, select Purge Pricing Engine Requests.

Report Parameters

Figure 10–7 Purge Pricing Engine Requests parameters

This program has two input parameters:

■ Keep Last (N) Days of Requests: Enter a number of days. The pricing engine will purge requests older than the number of days entered. For example, enter 30 to keep requests created in the last 30 days. Requests older than 30 days are purged.

■ Request Name: Enter a Request Name to delete the pricing engine requests that fully or partially match the name you enter.

RecoveryNone



QP: Bulk Import of Price List programThe QP: Bulk Import of Price List program is a concurrent program that enables you to import price lists (bulk load) from interface tables into the Oracle Advanced Pricing tables.

This provides an efficient alternative to existing APIs for validating and loading large pricing data into pricing tables. To improve processing efficiency, the concurrent program can be scheduled to run at optimal times such as when no active users are on the system.

The profile option QP: Batch size for Bulk Upload(QP_BATCH_SIZE_FOR_BULK_UPLOAD) can be set to restrict the number of records read to the PL SQL tables. This helps you improve the bulk import performance. The initial value is seeded as 1000 but you can change this value to suit your hardware configuration. See the Advanced Pricing Implementation Manual, Profile Options for more information.

When to use the QP: Bulk Import of Price List programYour business practices may require that you upload price list data on a regular basis such as those described in the following scenarios:

■ When a new price list needs to be created by uploading a price change file.

■ When new products lines are created, new offerings to new channels, acquisitions of product lines or companies, new product rollout, and new price list creations.

■ When implementing a new sales territory, to bulk load existing price lists or to upload pricing from regions that may have their pricing on spreadsheets.

QP: Bulk Import of Price List enables you to complete the following tasks:

■ Do bulk validations and bulk loading.

■ Provide all validation error messages in the same run for records that were not uploaded rather than returning errors one after another.

■ Provides ability to multi-thread the interface loader similar to Order Import with the ability to multi-thread within the same price list.

Multi-threading AbilityMulti-threading occurs when the child concurrent processes are initiated after a user submits the Process Parent request. Parent process first processes the list header records, then the qualifiers records, then the value-to-ID conversions before spawning child processes. The child processes upload price list lines and attributes.



Multi-threading enables you to do the following:

■ This program only updates the IDs derived from Value-To ID conversions back to the interface tables. If a record results in errors, the record remains in the interface tables where the IDs can be viewed.

■ Use the same interface program and tables for updating the pricing data.

■ Updating price list headers, lines, pricing attributes, qualifiers, and breaks are supported using the interface tables.

■ Deleting price list lines, pricing attributes, qualifiers, and breaks is supported using the interface tables.

■ Store the interface program id in the main pricing tables so you know which batch ID updated the records.

■ Optionally, use the Process Parent parameter in the concurrent programto load list lines even if the pricing attribute validation fails. If the Option is NO, and a pricing attribute fails, both parent and child lines will not be uploaded.

■ Mark a record as being processed so that multiple processes do not pick up the same record.

■ Automatically deletes the successfully uploaded rows from the interface tables.

■ Process a specific set rather than the entire eligible data.

Report Submission In the Submit Request window, Name field, select QP: Bulk Import of Price List.



Report Parameters

Figure 10–8 QP: Bulk Import of PriceList parameters

■ Entity: Indicates which pricing entity is to be processed. This defaults as PRL (price list) because currently only price lists can be uploaded.

■ Entity Name: Enter the name of the price list to be processed. If left blank, all entities of the selected Entity type available for processing in the interface tables will be processed.

■ Process ID: This value corresponds to the process_id in the interface tables. The Process ID groups data in the interface table. You can select criteria to specify which records should be processed.

If this field is left blank, all available records for processing will be considered subject to the restrictions entered in Entity Name.

■ Process Type: This corresponds to the process type listed in the interface tables such as XML.

■ Process Parent: Select Yes (the default) or No to define if the loader should process a parent record if a child record has an error. Valid values are Yes (the default) or No.

■ No of Threads: Enter a number that indicates the total number of child processes or threads to achieve multithreading for list lines and their child records. The default value is 1.



■ Debug On: Select Yes or No (default):

■ No: Select No to improve loading performance; however error messages are not sent to the Debug log.

■ Select Yes to have all error messages sent to the Debug Log.

The Debug On parameter only controls the log files. However, error messages, number of records processed, and other related information will be written to the output file regardless of the value set for Debug On.

Considerations for runnning the program1. Errors before resubmit: For records with errors in the interface tables, set the

request_id and process status flag columns to NULL so that these records are

Note: Multi-threading can impact the length of processing time required; therefore, it is recommended that you do not exceed the number of Central Processing Units (CPUs) available when running the program. Ideally, this should be scheduled for a slow processing period or when there are few users on the system.

Table 10–1 Table and View Usage

Table Name Select Insert Update Delete

QP_INTERFACE_LIST_HEADER X - X X

QP_INTERFACE_LIST_LINES X - X X

QP_INTERFACE_QUALIFIERS X - X X

QP_INTERFACE_PRICING_ATTRIBS X - X X

QP_INTERFACE_ERRORS - X - -

QP_LIST_HEADERS_B - X X X

QP_LIST_HEADERS_TL - X X X

QP_LIST_LINES - X X X

QP_QUALIFIERS - X X X

QP_PRICING_ATTRIBUTES - X X X

QP_RLTD_MODIFIERS - X X X



picked up in the next run. When the Entity Name is specified as a Report parameter, these values do not need to be reset.

2. Data for error messages in a QP interface table: The table QP_INTERFACE_ERRORS is populated with the processing errors which are then written to the output file of the concurrent request. Occasionally, this table needs to be purged of this data.

3. Source System/Pricing Transaction Entity (PTE): The concurrent program retreives records only when the Source system code and the PTE code matches with the same profile values or null. The List Source code for BSO (Blanket Sales Order) is never retreived.

4. Importance of Log and Output file to current QP profile: The concurrent request log file provides the processing details. If you enter an Entity Name that is not unique for the eligible records, none will be picked up for processing.

5. Child Lines-parents and grandparents records must be populated for insert, update, and delete: To insert, update, or delete records, its corresponding parent and grand-parent (if applicable) records should also be in the interface table and should be eligible to get retreived by the concurrent program.



QP: Maintains the Denormalized Data in QP QualifiersThis program populates the denormalized column data in the pricing tables and fixes data corruption specific to the denormalized columns that occur from a patch application or other set-up issues. This program can be run on a periodic basis or if the pricing engine performance decreases.

This program calculates and populates modifier statistics that the pricing engine search optimizer uses to find modifiers by the most direct method. For each modifier at the list and line level, the process calculates information related to its:

■ Qualifiers: Indicates if the list or line has qualifiers

■ Directness: Indicates how specific (selective) or non-specific (non-selective) its qualifiers are. More specific qualifiers are more direct.

■ Fastest search path: The qualifiers in each modifier list and line that are the most direct become primary qualifiers and the remainder become secondary qualifiers. The pricing engine search optimizer searches the primary qualifiers first.

This program automatically runs after you add or change each modifier and recalculates some statistics for that modifier. In addition, you should run it periodically to recalculate all of the statistics for all the modifiers.

Report SubmissionIn the Submit Request window, Name field, select QP: Maintains the Denormalized Data in QP Qualifiers.

Run the program during a time when most users are not logged onto the system. You may encounter a record locking problem if this program runs at the same time that the pricing engine is processing calls.

Note: The Request log for an automatic run is not saved and cannot be viewed in My Requests if the QP: Maintains the Denormalized Data in QP Qualifiers program runs successfully. The log file is saved and can be viewed only when an exception occurs.



Report Parameters

Figure 10–9 QP: Maintains the Denormalized Data in QP Qualifiers parameters

■ List Header ID (Low/High): Enter the range of values for the modifier lists. The two parameters can be the same value but neither can be null.

■ Update Type: Select the update type such as All, Denormalized Columns, Factor Pricing Attributes, List Header Phases, Pricing Phases, or Qualification Indicator.

RecoveryNone



Qualifier Grouping reportThis report shows details for qualifier groups including grouping conditions and effective dates within the group.

Report SubmissionIn the Submit Request window, Name field, select Qualifier Grouping.

Report Parameters

Figure 10–10 Qualifier Grouping report parameters

■ Qualifier Context: Enter a qualifier context.

■ Qualifier Attribute Value From/Qualifier Attribute Value To: Enter an individual qualifier attribute value or a range of qualifier attribute values.

■ Start Date Active/End Date Active: Enter a date or a range of dates.



Update Price Lists with Multi-Currency Conversion CriteriaThis concurrent program enables you to maintain and use price lists in different currencies. There are a few prerequisite steps before running this program:

1. Apply the multi-currency patch only if you want to use the multi-currency feature.

2. Set the profile QP: Multi-Currency-Installed to Y (Yes). The valid list of values for the profile are Y and N. The default value of the profile is N.

3. Run the concurrent program Update Price Lists with Multi-Currency Conversion Criteria only once.

Report SubmissionIn the Submit Request window, Name field, select Update Price Lists with Multi-Currency Conversion Criteria.

Report Parameters

Figure 10–11 Update Price Lists with Multi-Currency Conversion Criteria

Do you want to enable Multi-Currency price lists?: Select Yes to enable multi-currency price lists.

Warning: Once the concurrent program has been run successfully, all existing price list or agreement windows will be converted to multi-currency price lists. Users should not return to NON multi-currency price lists. Changing the profile back to No may cause undesired results if conversion criteria have been used. Oracle does not support changing the setting back to No.

The program must be run initially only once to activate the multi-currency feature; otherwise, data corruption may result.



When the concurrent program Update Price Lists with Multi-Currency Conversion Criteria runs, it does the following:

■ Adds a new Multi-Currency Conversion field to the Advanced Pricing - Price Lists and Pricing Agreements windows. This field displays the name of the multi-currency list currently attached to the price list—you can select other multi-currency lists from this field; however, only one can be selected at a time.

■ Generates a default multi-currency conversion list based on the Base Currency, Currency-To, and Rounding Factor values from existing price lists. This default multi-currency conversion list does not have other currencies or conversion criteria, just the base currency from the base price list. You must add currencies to the newly created multi-currency lists or create new multi-currency conversion lists if you want to include different currencies. The multi-currency conversion list can then be attached to the respective price list.

The following example displays the setup for five price lists before conversion and the multi-currency list created after the conversion:

The concurrent program creates four currency conversion criteria based on the price list currency and rounding factor of the price lists.

Table 10–2 Price Lists before concurrent program is run

Currency Rounding

USD -2

USD -2

USD -3

FRF -1

CAD NULL

Table 10–3 Multi-Currency Conversion Lists created after concurrent program is run

Currency Currency-To Rounding

USD USD -2

USD USD -3

FRF FRF -1

CAD CAD NULL



Attach the multi-currency conversion list to the respective price list. The multi-currency conversion list can then be attached to the respective price list. You must add new currencies to the existing multi-currency lists or create new multi-currency lists with the currencies required for conversion.

RecoveryNone. Once the concurrent program has been run successfully, do not return to non-multi-currency price lists. All existing price list windows will have been converted to multi-currency price lists. Changing the profile option QP: Multi-Currency Installed back to N (No) may cause undesired results if conversion criteria have been used. Oracle does not support this.

Note: Attaching a multi-currency list to the respective price list is a mandatory step—without it the pricing engine cannot use the current price lists as multi-currency price lists.

Once the concurrent program has run, you can create additional multi-currency lists or add existing currencies to the created multi-currency lists.



Update Promotional Limit Balances programUse the Update Promotional Limit Balances program to update promotional limit balances for selected modifier lines.

Report SubmissionIn the Submit Request window, Name field, select Update Promotional Limit Balances.

Report Parameters

Figure 10–12 Update Promotional Limit Balances

■ Modifier Number: To update limits for a selected modifier, enter the modifier number.

■ Modifier Line Number: To update limits for a selected modifier line, enter the Modifier Line Number.

■ Limit Number: Enter a Limit Number.

■ Limit balance Identifier: Enter the Limit Balance Identifier.

See:Updating an Existing Limit Balance on page 3-181


Formula Scen

A
Formula Scenarios
This appendix describes formula scenarios.

arios A-1

Formula Scenarios

Formula ScenariosSplinters Glass Company manufactures windshields for cars and trucks. It sells both to wholesale customers and to retail customers.

Scenario 1To its retail customers, Splinters prices windshields based on the dimension of the sheet of glass according to the formula 3 currency units * Width * Height * Thickness Factor.

The following table shows the thickness factors.

Splinters sets up Oracle Pricing to use formula and factor-based pricing.

Step 11. In the flexfield definition window, query the pricing attributes flexfield.

2. Define three new pricing attributes flexfield segments—width, height, and thickness. Use the context Pricing Attributes.

3. Save your work and close the window.

Step 2Create a pricing formula.

1. Create a formula header.

Formula Name: Glass Pricing Formula and Formula = 1 * 2 * 3 *4

2. Create a formula line.

Formula Type: Numeric Constant

Component: 3

Step Number: 1

Table A–1 Thickness factors

Glass Thickness Thickness Factor

< 5 mm 10%

5 mm - 10 mm 15%

> 10 mm 20%

A-2 Oracle Advanced Pricing User’s Guide

Formula Scenarios

3. Create a second formula line.

Formula Type: Pricing Attributes

Pricing Attribute Context: Pricing Attributes

Pricing Attribute: Width

Step Number: 2

4. Create a third formula line.

Formula Type: Pricing Attributes

Pricing Attribute Context: Pricing Attributes

Pricing Attribute: Height

Step Number: 3

5. Create a fourth formula line.

Formula Type: Factor List

Component: Thickness Factor

Step Number: 4

6. Click Factors.

7. In the Base Pricing Attributes region, create a row.

Base Pricing Attribute: Thickness

Comparison Operator: Between

Value From: 0

Value To: 5

Adjustment Factor: 0.10

8. Create a second row in the Base Pricing Attributes region.

Base Pricing attribute: Thickness


Value From: 5

Value To: 10


9. Create a third row in the Base Pricing Attributes region.

Formula Scenarios A-3

Formula Scenarios

Base Pricing Attribute: Thickness


Value From: 10



Step 3Create a price list for retail customers, create a list line, and attach the formula.

1. Create a price list.

Name: Retail

2. Select the Qualifiers tabbed region.

3. Add a qualifier.

Context: Customer

Attribute: Customer Class

Value: Retail

4. Create a new list line.

Item: Windshield

UOM: Each

Dynamic Formula: Glass Pricing Formula

Method: Amount

Line Type: PLL



Formula Scenarios

Scenario 2 To its retail customers, Splinters charges for its windshield warranty protection plan at 10% of the cost of the replacement windshield. The formula is 10% * price of the Windshield item on the Replacement price list).

Splinters sets up Oracle Pricing to use formula-based pricing.

Step 1Create a new pricing formula.

1. Create a formula header.

Formula Name: Warranty Pricing Formula

Formula: 1*2


Formula Type: Numeric Constant

Component: 0.10

Step Number: 1

3. Create a second formula line.

Formula Type: Price List Line

Component: Windshield line of Replacement price list

Step Number: 2


Step 2Create a price list for retail customers, create a list line, and attach the formula.

1. Create a price list.

Name: Warranties

2. In the Qualifiers region, add a qualifier.

Context: Customer

Attribute: Customer Class

Value: Retail

3. Create a list line.

Formula Scenarios A-5

Formula Scenarios

Item: Protection Plan

UOM: Each

Dynamic Formula: Warranty Pricing Formula

Method: Amount

Line Type: PLL



Modifier Scen

B
Modifier Scenarios
This appendix describes modifier scenarios.

arios B-1

Modifier Scenarios

Modifier ScenariosThe following scenarios illustrate how to meet business needs by creating modifiers. The scenarios are organized by the following modifier concepts:

■ Discount

■ Surcharge

■ Price break

■ Other item discount

■ Promotional goods

■ Coupon issue

■ Item upgrade

■ Terms substitution

■ Freight and special charges

■ Newprice

Each scenario is identified by a number and the numbers do not re-start with one at the beginning of each modifier concept; they are continuous throughout the appendix.

Discount

Scenario 1If the customer is a preferred customer or customer spends more than 150 currency units, they receive 10% off the order.

1. Create a modifier.

Modifier Type: Discount

Modifier Level: Order

Application Method: Percent

Value: 10

2. In the Line Qualifiers window, create two line qualifiers.

Grouping Number: 1

Qualifier Context: Volume

B-2 Oracle Advanced Pricing User’s Guide

Modifier Scenarios

Qualifier Attribute: Order Amount

Operator: Between

Value From: 150

Grouping Number: 2

Qualifier Context: Customer

Qualifier Attribute: Customer Class

Operator: =

Value From: Preferred

Scenario 2For any ten compact discs purchased by April 2000, the customer receives 2 currency units off.

Create a modifier.


Modifier Level: Line

End Date: 30 April 2000

Product Attribute: Item Category

Product Attribute Value: CD

Volume Type: Item Quantity

Break Type: Recurring

Value From: 10

Application Method: Lumpsum

Value: 2

Scenario 3For every eight currency units spent on cat food, the customer accrues five shopper points.

Create a modifier.



Modifier Scenarios B-3

Modifier Scenarios


Product Attribute Value: Cat Food

Volume Type: Item Amount


Value From: 8

Select Accrue

Benefit Quantity: 5

Benefit UOM: Shopper Point

Scenario 4Customers mentioning the Summer Special Promotion (an "Ask For" promotion) get $5 off of any tennis racket except the FastFireIII model.


In Modifiers Summary tab

Modifier No: SUMMER SPECIAL



Automatic box: Selected


Product Attribute Value: Tennis Rackets

In Discounts/Charges tab

Application Method: Amount

Value: 5

In Advanced tab

Ask for box: Select. Instructs the pricing engine to apply this modifier only if the customer asks for it.

2. Click Exclude. In the Exclude Items window, create an excluded item:

Product Attribute: Item

Product Value: FastFire III


Modifier Scenarios

Exclude box: Select

Scenario 5Customers who buy two bottles of shampoo receive one currency unit off of the third bottle of shampoo.

Create a modifier.




Product Attribute Value: Shampoo



UOM: Each

Value From: 3


Value: 1

Surcharge

Scenario 6Customers in the National Accounts territory who spends less than 1000 currency units per order receives a 2% surcharge.


Modifier Type: Surcharge



Value: 10

2. In the Line Qualifiers window, create two line qualifiers for the modifier.

Grouping Number: 1



Modifier Scenarios


Operator: Between

Value To: 1000

Grouping Number: 1


Qualifier Attribute: Customer Class

Operator: =

Value From: National Accounts

Scenario 7Any customer placing a rush order (delivery required within two days) for replacement motors receives a 50 currency unit surcharge.


Modifier Type: Surcharge



Product Attribute Value: Motors, Spare


Value: 50

2. In the Line Qualifiers window, create a qualifier for the modifier. You have created qualifier attribute Days to Requested Delivery and created the appropriate sourcing rules for this attribute.

Grouping Number: 1

Qualifier Context: Order

Qualifier Attribute: Days to Requested Delivery

Operator: Between

Value To: 2


Modifier Scenarios

Price Break

Scenario 8All employees in Company ABC’s mobile phone plan receive per minute discounts based on minutes used, as follows:

■ 0-120 minutes: 0.5 currency units per minute



■ > 421 minutes: 0.15 currency units per minute

A customer who uses 150 minutes receives the following discounts:

■ 0.5 currency unit per minute discount on 120 minutes

■ 0.10 currency unit per minute discount on 30 minutes


Modifier Type: Price Break Header



Product Attribute Value: Minutes


Break Type: Range

Adjustment Type: Discount

2. In the Price Break Lines region, enter the break lines.

Value From: 0

Value To: 120


Value: 5

Value From: 121

Value To: 240



Modifier Scenarios

Value: 10

Value From: 241

Value To: 420


Value: 12

Value From: 421


Value: 15

3. In the Line Qualifiers window, create a qualifier for the price break modifier.

Grouping Number: 1


Qualifier Attribute: Customer Name

Operator: =

Value From: ABC

Scenario 9Customers who buy cases of TY brand products across an order receive a percent rebate per case as follows:

■ 1 - 500 cases: 2% rebate per case

■ 501 - 1000 cases: 3% rebate per case

■ > 1000 cases: 5% rebate per case


Modifier Type: Price Break Header

Modifier Level: Group of Lines


Product Attribute Value: TY


Break Type: Point

UOM: Case


Modifier Scenarios

Adjustment Type: Discount

Select Accrue

2. In the Price Break Lines window, enter the break lines.

Value From: 1

Value To: 500


Value: 2

Value From: 501

Value To: 1000


Value: 3

Value From: 1001


Value: 5

Other Item Discount

Scenario 10Customers who buy more than three meters of fabric across an order receive 10% off thermal curtain linings and 5% off drapery services.


Modifier Type: Other Item Discount

Modifier Level: Group of Lines


Product Attribute Value: Fabric


Break Type: Point

UOM: Yard

Value From: 10


Modifier Scenarios

2. In the modifier details, enter the get products.


Product Value: Thermal Linings


Value: 10


Product Value: Drapery Services


Value: 5

Scenario 11Customers who buy six chairs and a coffee table or six chairs and 2 standard lamps, will get $400 off a dining table assuming the dining table is on the order as well.


Modifier Type: Other Item Discount



Product Attribute Value: Dining Chair


Break Type: Point

UOM: Each

Value From: 6

2. In the modifier details, enter the related product.

Group No: 1


Product Value: Coffee Table

UOM: Each

Group No: 2



Modifier Scenarios

Product Value: Standard Lamp

Pricing Attribute: Item Quantity

Operator: Between

Value From: 2

UOM: Each

3. In the modifier details, enter the get product.


Product Value: Dining Table


Value: 400

Promotional Goods

Scenario 12Customers who buy one bottle of shampoo receive a free bottle of conditioner.


Modifier Type: Promotional Goods






UOM: Each

Value From: 1



Note: Promotional Goods modifiers are not supported at the Order level.


Modifier Scenarios

Product Value: Conditioner

Get Quantity: 1

Get Price: <price list line for conditioner>

Get UOM: Each


Value: 100

Scenario 13Customers who buy two bottles of shampoo receive 10% off the purchase of a third bottle of shampoo.








UOM: Each

Value From: 2



Product Value: Shampoo

Get Quantity: 1

Get Price: <price list line for shampoo>

Get UOM: Each


Value: 10


Modifier Scenarios

Scenario 14A customer who spends between $45 to $100 on an order line receives a free cosmetic bag.

1. Create a modifier line.



2. In the Line Qualifiers window, create a qualifier.

Grouping Number: -1


Qualifier Attribute: Line Volume

Operator: Between

Value From: 45

Value To: 100

3. In the Modifier Summary region, select the product that the customer must order to get the free cosmetic bag.

4. Click Define Details to display the Products tab. In the Get region, define the item the customer gets when the Buy item is ordered:

Get Product Attribute: Item

Get Product Value: Cosmetic Bag

Get Quantity: 1

Get Price: <price list line for cosmetic bag>.

Get UOM: Each


Value: 100


Modifier Scenarios

Coupon Issue

Scenario 15Customers who buy any product in the Chubo brand receive 10% off any item in the Chubo brand on their next order.

1. Create a modifier list. In the Main tab:

Type: Promotion

Number: Coupon15

Select Active

Name: Coupon15

Clear Automatic

2. Create a modifier line for the discount.

In the Modifiers Summary tab




Product Attribute Value: Chubo

In the Discounts/Charges tab


Value: 10

3. Create a second modifier line for the coupon issue and assign it for the modifier line created in step 2.

Modifier Type: Coupon Issue



Product Attribute Value: Chubo

Coupon Modifier: <discount modifier from previous step>


Modifier Scenarios

Scenario 16Customers ordering from the website receive a coupon for 10% off a future order.

1. Modifier List Type: Promotion

Create a modifier line.




Value: 10

2. Create a second modifier line for the coupon issue and assign it to the modifier line created in step 1.



Coupon Modifier: <modifier from step 1>

3. In the Line Qualifiers window, create a qualifier for the Coupon Issue modifier line from step 2. You have created the qualifier attribute Website Domain and created the appropriate sourcing rules for it.

Grouping Number: 1


Qualifier Attribute: Website Domain

Operator: =

Value From: co.uk

Scenario 17With any order, receive a coupon for two free bags of coffee on a future order.

1. Create a modifier line.


Modifier Level: Group of Lines, All Items



Product Value: Coffee


Modifier Scenarios

Get Quantity: 2

Get Price: <price list line for bag of coffee>

Get UOM: Bag


Value: 100

3. Create a second modifier line for the coupon issue and assign it to the modifier from step 1.



Coupon Modifier: <modifier from step 1>

Item Upgrade

Scenario 18Customers who order a standard video recorder before end of April 2000 receive a deluxe video recorder for the same price.


Type: Promotion or Deal

Date Type: Requested Ship Date

End Date: 31 April 2000

2. Assign a modifier line to the modifier list in Step 1. You have defined the item relationship between the standard video recorder and deluxe video recorder.

Modifier Type: Item Upgrade



Product Attribute Value: Video Recorder Standard

Upgrade Item: Video Recorder Deluxe

Scenario 19Customers who buy a shirt receive the shirt and a tie for the shirt price.


Modifier Scenarios

Create a modifier. You have defined the item relationship between the shirt and the marketing bill shirt and tie pack.

Modifier Type: Item Upgrade



Product Attribute Value: Shirt

Upgrade Item: Marketing item shirt and tie pack

Terms Substitution

Scenario 20Customers who spend more than 1000 currency units on a sofa pay nothing for shipping.

Create a modifier.

Modifier Type: Terms Substitution



Product Attribute Value: Sofa

Volume Type: Item Amount

Break Type: Point

UOM: Each

Value From: 1000

Terms Attribute: Shipping Terms

Terms Value: No Charge

Scenario 21Customers who buy more than 100 currency units of one item on an order receive terms of 2% 30/NET 60.


Modifier Type: Terms Substitution


Modifier Scenarios


Terms Attribute: Payment Terms

Terms Value: 2% 30/NET 60

2. In the Line Qualifiers window, create a qualifier.

Grouping Number: 1



Operator: Between

Value From: 100

Freight and Special Charges

Scenario 22For all low priority shipments, calculate shipping charges by order line total weight as follows:

■ 0 - 500 kg: 2.50 currency units

■ 501 - 1000 kg: 3.50 currency units

■ > 1000 kg: 5.00 currency units

Profile Option QP: Line Weight UOM Code is kg.


Modifier Type: Freight Charge



Value: 2.50

2. In the Line Qualifiers window, create a qualifier for the modifier from step 1.

Grouping Number: 1


Qualifier Attribute: Shipment Priority

Operator: =


Modifier Scenarios

Value From: Low

Grouping Number: 1


Qualifier Attribute: Line Weight

Operator: =

Value From: 0

Value To: 500

3. Create a second modifier.




Value: 3.50

4. In the Line Qualifiers window, create a qualifier for the second modifier from step 3.

Grouping Number: 1



Operator: =

Value From: Low

Grouping Number: 1



Operator: =

Value From: 501

Value To:1000

5. Create a third modifier.




Modifier Scenarios


Value: 3.50

6. In the Line Qualifiers window, create a qualifier for the third modifier from step 5.

Grouping Number: 1



Operator: =

Value From: Low

Grouping Number: 1



Operator: =

Value From: 1001

Scenario 23Calculate freight handling charge as a 10% markup of actual handling cost.

1. Create a formula.

Formula Name: Handling Cost

Formula: 1 * 2


Formula Line Type: Pricing Attribute

Pricing Attribute Context: Pricing Attribute

Pricing Attribute: Handling Cost Amount

Step: 1

Formula Line Type: Constant

Component: 1.1

Step: 2



Modifier Scenarios




Formula: <reference formula Handling Cost from step 1>

4. In the Line Qualifiers window, create a qualifier for the third modifier from step 2.

Grouping Number: 1


Qualifier Attribute: Freight Cost Type

Operator: =

Value From: Handling

Newprice

Scenario 24The following table states the scenario for this newprice example. Following the table, the text analyzes the scenario:

Within the same incompatibility group, when all of the lines have the same Precedence, the pricing engine performs best price processing. The final selling price is in line 2, 25 currency units. In this scenario, the bucket is not important to the result.


Table B–1 Newprice Scenario: List Price 1000, Selling Price 25

Incompatibility Level Precedence Bucket Operator Value Engine Selects

1 10 1 NEWPRICE 30 No

1 10 1 NEWPRICE 25 Yes

1 10 1 NEWPRICE 40 Yes


Modifier Scenarios

With different incompatibility levels, the pricing engine evaluates the lines according to buckets. Since all of the lines are in the same bucket, the pricing engine calculates Adjusted Amount from the list price. It calculates the selling price as follows:

List Price - Sum of the Adjusted Amounts

1000 - (970 + 975 + 960) = 1000 - 2095 = -1905


With different incompatibility levels, the pricing engine evaluates the lines according to buckets. Since each line is in a different bucket, the pricing engine calculates Adjusted Amount from the base price of the previous bucket (list price is in bucket 0). It calculates the selling price as follows:

List Price - Sum of the Adjusted Amounts

1000 - (970 + 5 - 15) = 1000 - 960 = 40

As the pricing engine evaluates the eligible list lines, it resolves incompatibilities in all phases. You can set up your modifiers such that the

Table B–2 Newprice Scenario: List Price 1000, Selling Price -1005

Incompatibility Level Precedence Bucket Operator Value

Engine Selects

Adjusted Amount

1 10 1 NEWPRICE 30 Yes -970



Table B–3 Newprice Scenario 3: List Price 1000, Selling Price 40

Incompatibility Level Precedence Bucket Operator Value

Engine Selects Adjusted Amount

1 10 1 NEWPRICE 30 Yes -970 (Base price: 1000)

2 10 2 NEWPRICE 25 Yes -5 (Base price: 30)

3 10 3 NEWPRICE 40 Yes 15 (Base price: 25)


Modifier Scenarios

pricing engine determines most of the list line eligibility at the search stage. Then, the pricing engine calculates the final selling price bucket by bucket.


Modifier Scenarios


Windows and Navigator P

C
Windows and Navigator Paths
This appendix shows the default navigator paths for Oracle Pricing application.

Windows and Navigator PathsRefer to the following sources for other window and application information:

■ Oracle Order Management User’s Guide

■ Oracle Application User’s Guide

The Window Names and Navigation Paths table lists the navigation path for each window or HTML page. The conventions and short names used in the table are described as follows:

■ HTML UI and SSWA (Self Service Web Application): Identifies a navigation path in the HTML user interface.

■ []: Square brackets indicate a [button name or link] that must be clicked to display the window or HTML page.

■ [T}: Square brackets around the letter "T" indicates that you must click a tab.

Table C–1 Window Names and Navigation Paths

Window Name Navigation Path

Add Items to Price List Price Lists > Add Items to Price List

Adjust Price List Price Lists > Adjust Price List

Advanced Pricing - Define Modifier

Modifiers > Modifier Setup

Advanced Pricing - Define Modifier (alternate)

Modifiers > Modifier Incompatibility Setup > [Modifiers]

aths C-1


Advanced Pricing: Home Page

SSWA > Oracle Pricing User responsibility > Home

Advanced Pricing - Price Lists

Price Lists > Price List Setup

Advanced Pricing - Pricing Formulas

Pricing Formulas > Formulas Setup

Advanced Search SSWA > Oracle Pricing User >Price List Maintenance > [Advanced Search]

Alternate: SSWA > Oracle Pricing Administrator >Price List Maintenance > [Advanced Search]

Archive Pricing Entities Archive Purge Pricing Entities > Archive Entity

Assign Attributes Setup > Attribute Management > Attribute Linking and Mapping > [Assign Attributes]

Attribute Defaulting Rules Setup > Attribute Mapping > [Defaulting Rules...]

Attribute Mapping, Setup > Attribute Linking and Mapping > [Link Attributes] > Link Attributes window > [Attribute Mapping]

Bulk Change SSWA > Oracle Pricing User > Price List Maintenance > [Advanced Search] > [Search] > From Advanced Search page > [Bulk Change]

Alternate: SSWA > Oracle Pricing User or Oracle Pricing Administrator > Price List Maintenance > (Do Search) >[Bulk Change]

Bulk Create Privileges SSWA > Oracle Pricing Administrator Responsibility > Security > Privileges > [Bulk Create Privileges]

Bulk Update Entity Usage SSWA > Oracle Pricing Administrator Responsibility > Security> Entity Usage > [Bulk Update Entity Usage]

Context Setup Setup > Attribute Mapping > Context and Attributes

Copy Modifiers Modifiers > Copy Modifiers

Copy Price List Price Lists > Copy Price List

Create Entity Set SSWA > Oracle Pricing Administrator Responsibility > Security > Entity Sets > [Create Entity Set]



C-2 Oracle Advanced Pricing User’s Guide


Create Line page (modifier) (HTML UI)

SSWA > Oracle Pricing User responsibility > Home page > Shortcuts > Create (Modifier Type) List > (Create modifier) > Next > Update Discount List: Modifier Lines > [Create Line]

Create Price List: General Information (HTML UI)

SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page [Shortcuts: Create Price List]

Alternate: SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page [Lists tab] > Create List

Create Price List: Qualifiers (HTML UI)

SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page [Shortcuts: Create Price List] > Create Price List: General Information > [Next]

Alternate: SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page [Lists tab] > Create List > Create Price List: General Information page [Next]

Defaulting Condition Validation Templates

Setup > Attribute Mapping > [Defaulting Condition Templates...]

Defaulting Setup Setup > Attribute Mapping

Define Limits Modifiers > Modifier Setup > Define Modifier (W) > [List Limits] >

Define Modifier Modifiers > Modifier Setup

Define Modifier - Define GSA price

Price Lists > GSA Pricing Setup

Define Modifier Details Modifiers > Modifier Setup > [Define Details*]

Descriptive Flexfield Segments

Setup > FlexFields

Detail Change (HTML UI) SSWA > Oracle Pricing User > Price List Maintenance > [Advanced Search] > From Advanced Search page > [Detail Change]

Alternate: SSWA > Oracle Pricing User or Oracle Pricing Administrator > Price List Maintenance > (Do Search) >[Detail Change]



Windows and Navigator Paths C-3


Entity Set Details (HTML UI) SSWA > Oracle Pricing Administrator Responsibility > Security > Entity Sets > [Set Id]

Entity Sets SSWA > Oracle Pricing Administrator Responsibility > Security > Entity Sets

Entity Usage SSWA > Oracle Pricing Administrator Responsibility > Security > Entity Usage

Event Phases Setup > Event Phases

Exclude Items Modifiers > Modifier Setup > [Exclude]

Express Create Privilege SSWA > Oracle Pricing Administrator Responsibility > Security > Privileges > [Express Create Privilege]

Factors Pricing Formulas > Formulas Setup > [Factors]

Find Personal Profile Values Setup > Profiles

Find Modifiers Pricing Organizer

Find Requests View Concurrent Requests

Find Requests (alternate) View Concurrent Requests > [Find] > [Find Requests]

Find Formula Factor Lines Pricing Formulas > Formulas Setup > Advanced Pricing - Pricing Formulas > (Query Formula Name) > Select Formula line > [Factors] > Factors window > Select line which contains the value > [Search icon]

GSA Qualifiers Price Lists > GSA Pricing Setup > [List Qualifiers]

Incompatibility Groups Modifiers > Modifier Incompatibility Setup

Link Attributes Setup > Attribute Linking and Mapping > [Link Attributes]

Log file: request id View Concurrent Requests > [Find] > [View Log...]

Modifier Lists SSWA > Oracle Pricing User > Home > Lists {T}, Administrator Responsibility > Modifier Lists

Modifier Lists Search (HTML UI)

SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page > [List tab] > Modifier Lists

Modifier Organizer Pricing Organizer

More Pricing Attributes Modifiers > Modifier Setup > [Pricing Attributes]





Multi-Currency Conversion List

Price Lists > Multi-Currency Conversion Setup

Oracle Pricing Lookups Setup > Lookups

Personal Profile Values Setup > Profiles > [Find]

Price Breaks Pricing Agreements > Price Breaks

Price Breaks (alternate 1) Modifiers > Modifier Setup > [Define Details*] > Price Breaks

Price Breaks (alternate 2) Price Lists > Price List Setup > [Price Breaks]

Price List Maintenance (HTML UI)

SSWA > Oracle Pricing Administrator Responsibility > Price List Maintenance

Alternate: Oracle Pricing User > Price List > Maintenance

Price Lists Search (HTML UI) SSWA > Oracle Pricing User responsibility > Home > Oracle Advanced Pricing: Home page > [List tab] > Price Lists

Pricing Agreements Pricing Agreements

Pricing Attributes Pricing Agreements > [Pricing Attributes]

Pricing Attributes (alternate) Price Lists > Price List Setup > [Pricing Attributes]



Pricing Formulas Pricing Formulas > Formulas Setup

Pricing Organizer Pricing Organizer

Pricing Transaction Entity-Attribute Linking

Setup > Attribute Management > Attribute Linking and Mapping

Privileges SSWA > Oracle Pricing Administrator Responsibility > Security > Privileges

Privileges Summary SSWA > Oracle Pricing Administrator Responsibility > Security> Privileges > [Bulk Create Privileges] > Complete Bulk Create Privileges Step 1 to 3 > [Submit]

Purge Pricing Entities Archive Purge Pricing Entities > Purge Entity

QUALIFIER - Header Level Qualifiers

Modifiers > Modifier Setup > [List Qualifiers] > [Cancel]





QUALIFIER - Line Level Qualifiers

Modifiers > Modifier Setup > [Line Qualifiers] > [Cancel]

Qualifier Group Qualifier Setup

Qualifier Groups - List Modifiers > Modifier Setup > [List Qualifiers]

Qualifier Groups - Line Modifiers > Modifier Setup > [Line Qualifiers]

Qualifiers (HTML UI) SSWA > Oracle Pricing User responsibility > Find or create Modifer/Price List > List Qualifiers > Qualifiers page [Append Group]

Alternate: SSWA > Oracle Pricing User responsibility > Find or create modifer line/price list line> List Qualifiers > Qualifiers page [Append Group]

Qualifiers: Append Group (HTML UI)

SSWA > Oracle Pricing User responsibility > Qualifiers page [Append Group]

Redeem Accruals Modifiers > Accrual Redemption

Report: request id View Concurrent Requests > [Find] > [View Output]

Request Detail View Concurrent Requests > [Find] > [View Details...]

Request Diagnostics View Concurrent Requests > [Find] > [Diagnostics]

Requests View Concurrent Requests > [Find]

Segments Summary (Attachment context)

Setup > FlexFields > [Segments]

Segments Summary (alternate 1)

Setups > FlexFields > [Segments] > [New]

Segments Summary (alternate 2)

Setups > FlexFields > [Segments] > [Open]

Source Systems Setups > Source Systems

Submit a New Request Reports

Submit a New Request (alternate)

View Concurrent Requests > [Submit a New Request...]

Submit Request Reports > OK

Update Formula Prices Pricing Formulas > Update Formula Prices





Update Line (modifier) (HTML UI)

SSWA > Oracle Pricing User responsibility > Lists > Modifier Lists > Modifier Lists Search page (complete search for modifier) > [Update] > Modifier Lines (from Navigation bar) > [Update]

Alternate: SSWA > Oracle Pricing User responsibility > Home page (Recently Created Modifier Lists) > [Update] > Modifier Lines (from Navigation bar) > [Update]

Update (Modifier Type): Modifier Lines (HTML UI)

SSWA > Oracle Pricing User responsibility > Lists > Modifier Lists > Modifier Lists Search page (complete search for modifier) > [Update] > Modifier Lines (from Navigation bar)

Alternate: SSWA > Oracle Pricing User responsibility > Home page (Recently Created Modifier Lists) > [Update] > Modifier Lines (from Navigation bar)

Update (Modifier Type): General Information (HTML UI)

SSWA > Oracle Pricing User responsibility > Modifier Lists Search page (after completing a search) > [Update]

Alternate: SSWA > Oracle Pricing User responsibility > Home page (Recently Created Modifier Lists) > [Update]

Value Sets Setups > FlexFields > [Segments] > [Value Set]

Value Sets (alternate 1) Setups > FlexFields > [Segments] > [New] > [Value Set]

Value Sets (alternate 2) Setups > FlexFields > [Segments] > [Open] > [Value Set]






Glossary

A

accrual

In Oracle Advanced Pricing are monetary or non-monetary units that are earned and accumulated for later remittance in a form of a monetary or non-monetary payment. Remittance settlement is based on a predefined basis for performance.

accumulation attribute

A volume accumulation attribute enables the pricing engine to source the attributes and the accumulation values from the custom API. The value from the accumulation attribute is sourced from the pricing request when evaluating accumulated range price breaks for modifiers. Advanced Pricing does not store these accumulated values.

ask for modifier

A promotion modifier type that requires a customer to specifically request the promotion on the order.

attribute

A basic data element used by Oracle Advanced Pricing to control pricing activity. For example, Pricing uses attributes to define the eligibility of a customer order to receive a particular price or modifier. In Oracle Advanced Pricing, individual attributes are obtained from data sources that are called contexts. Pricing attributes may also be used as elements of a pricing formula.

attribute mapping

Glossary-1

attribute management

The Attribute Management feature enables you to create new contexts and attributes, update existing contexts/attribute properties, or disable existing attributes.

automatic modifier

In Oracle Advanced Pricing, a control that allows you to specify that the Pricing Engine apply a modifier automatically to a transaction, assuming that the transactions meets the qualifier eligibility.

B

base price

The original price for an item obtained from the Price List; the price before any price adjustments are applied. Also known as List Price.

benefits

In Oracle Advanced Pricing, modifiers that result in non-monetary adjustments to an order. Types of benefits include: Item upgrade, free items, change in payment or shipment terms. See also Price Adjustments.

best price

■ The modifier which gives the lowest price or most advantageous price to the customer on the given pricing line will be applied.

■ An alternative method to precedence which is used to determine which modifier should be selected when multiple modifiers in the same exclusivity or incompatibility group are eligible to be applied to the same pricing line within a pricing phase. The modifier which gives the lowest price or most advantageous price to the customer on the given pricing line will be applied. See also Precedence.

break UOM

When creating price breaks, you can select a Break UOM (unit of measure) to define in what UOM the break for the defined product will be calculated.

buckets (pricing)

A feature in Oracle Advanced Pricing that determines how modifier price adjustments are applied to the list price of an item to calculate the selling price. Modifiers use the previous buckets sub-total for percentage calculation. Modifiers

Glossary-2

within the same bucket are Additive i.e. added together, and subtracted from the previous buckets total. The user can create an unlimited amount of buckets to calculate selling price. For example, discounts associated with bucket 0 use list price as their calculation basis. Bucket 1 prices use the subtotal resulting from subtracting bucket 0 discounts from list price as their calculation. Bucket 2 uses the subtotal remaining after subtracting bucket 1 discounts from the bucket 0 subtotal, and so forth.

C

calculation engine

In Oracle Advanced Pricing the calculation engine is a part of pricing engine. It returns the price of an item/service.

compound discounts

Discounts that are applied on top of already discounted prices. See buckets, pricing.

context

A data source used by Oracle Advanced Pricing to obtain attributes. For example, Oracle Advanced Pricing considers the customer order itself to be a context. Various attributes from the order, such as order date, can be used by Pricing to control the selection of a price or modifier. Oracle Advanced Pricing does not limit the number of contexts that can be defined. Any single context can supply up to 100 pricing attributes. See also Dimension.

customer class

A method to classify and group your customers. For example, you could group them by their business type, size, or location. You can create an unlimited number of customer classes.

D

deal

A Modifier List type in Oracle Advanced Pricing that is a child of the modifier list type Promotion. A Deal is a group of modifiers that share the same header level qualifications and are reported together. A Deal is tied to a Promotion for reporting purposes only.

Glossary-3

discounts

Is a Modifier type in Oracle Advanced Pricing that creates Pricing Adjustments which allows Pricing Engine to extend a reduced price for an order, specific line item, or group of lines.

E

effective dates

Start date and end date that a price, discount, surcharge, deal, promotion, or change is active.

exclusivity

A feature in Oracle Advanced Pricing that determines if an order qualifies for multiple modifiers on an order, and if one of the modifiers is exclusive, then only the exclusive modifier is applied.

F

factor list

In Oracle Advanced Pricing Formulas, factor lists may be linked to multiple pricing attributes or range of these attributes. For example, a glass with thickness between 0.1 to 0.3 mm will have a factor of 3 and a glass with thickness between 0.4 to 0.8 mm will have a factor of 5. The choice of factors from the factor list is made by the Pricing engine at the time the formula is computed. See formula.

formula

A mathematical formula used in Oracle Advanced Pricing to define item pricing or modifier adjustments. You create a pricing formula by combining pricing components and assigning a value to the components.

G

GSA (General Services Administration)

GSA (General Services Administration): a customer classification that indicates the customer is a U.S. government customer. For products on the GSA price list, a fixed price must be used, defined on the GSA contract. The items contained on the GSA price list cannot be sold to commercial customers for the same or less price than the government price. In other terms, the price offered to the government must be the minimum in the market.

Glossary-4

incompatibility

A feature in Oracle Advanced Pricing that allows you to define groups of modifiers where the modifiers in a group are incompatible with each other. Modifiers in the same incompatibility group may not be used together on the same transaction. See Precedence.

L

list price (price lists)

In Oracle Advanced Pricing, the base selling price per unit of the item, item category or service offered. You define the list price on a price list. All price adjustments are applied against the list price.

list price (Pricing Formula)

A Formula type used in Oracle Advanced Pricing to notify the pricing engine to use the Price on the line that the formula is attached to for calculating the formula.

M

modifier

Defines the terms of how Oracle Advanced Pricing will make adjustments. For example, a modifier can take the form of: discounts, or surcharges. In Oracle Advanced Pricing, when you setup modifiers, you define the adjustments your customers may receive. You control the application of modifiers by the pricing engine by also setting up rules that specify qualifiers and attributes governing their use.

modifier list

A grouping of modifiers in Oracle Advanced Pricing.

P

precedence

Used by Oracle Advanced Pricing to resolve Incompatibility. Precedence controls the priority of modifiers and price lists. If a customer qualifies for multiple modifiers that are incompatible with each other, precedence determines the discount that the customer is eligible for based on the precedence level of the modifier. See also incompatibility.

Glossary-5

price adjustments

In Oracle Advanced Pricing, modifiers that result in monetary adjustments to an order. Types of benefits include: discount in %, amount or new price, discounts on other items, surcharges. See benefits.

price breaks

A quantity delimiters to which are associated prices or discounts by range of quantity and amount. These breaks may occur at either the line item level or at the total order level and associated with a item/ item group.

price list

A list containing the base selling price per unit for a group of items, item categories or service offered. All prices in a price list are for the same currency.

pricing date

In Oracle Advanced Pricing, the date according to which selling price will be calculated. Pricing Date can be Order Date, Ship Date or sysdate.

pricing event

A point in the process flow of a Pricing Line, e.g. Order, Contract etc. at which a call is made to the Pricing Engine to fully or partially price the Order or Contract. A pricing event is analogous to a Workflow event; for example, Booking Order, Reprice Order, Shipping Order.

pricing phase

A user-defined control that can be applied to Price Lists, Discount Lists, Promotions, Deals, etc. In Oracle Advanced Pricing, the Pricing Engine looks at the phase when deciding which lists should be considered in a Pricing Event. See Pricing Event.

pricing request structure

In Oracle Advanced Pricing the Pricing Request Structure is the parameter information that is passed to the Pricing Engine for calculating the final price which is inclusive of all the modifiers that the customer is eligible for.

pricing transaction entity (PTE)

Oracle Pricing provides seeded pricing transaction entities (PTEs) that consist of a group of applications that point to the same setup data and attributes, and includes Request Types and Source Systems.

Glossary-6

During the attribute mapping process, once you have created the context and its attributes, you can link an attribute grouping to a specific PTE. For a given PTE, this combination becomes available in the pricing setup windows. Each PTE has its own unique combination of attributes.

product pricing attributes

In Oracle Advanced Pricing, these define the products referenced in a deal, discount, promotion, or price list.

promotion

A Modifier List type in Oracle Advanced Pricing. A Promotion is a group of modifiers that share the same header level qualifications and are reported together.

Q

qualifier

Used in Oracle Advanced Pricing to determine eligibility for a price, price adjustment or benefit.

■ unique qualifier: Each separate qualifier created for a modifier or price list is called a unique qualifier. Unique qualifiers are evaluated by an "OR" condition; for example, either Qualifier 1 OR Qualifier 2 can qualify before the price list or modifier is applied.

■ common qualifier: A common qualifier is used to create a mandatory condition across all qualifiers. A common qualifier consists of conditions which are joined by AND to all qualifiers in a table.

qualifier condition

A qualifier condition defines an eligibility rule, for example, the customer name must be Vision Operations. You can set up one or more conditions for a single qualifier.

R

request type

Used by Oracle Advanced Pricing to identify the transaction system which calls the Pricing Engine for calculation of the price. Ex: Order Management, Order Capture, Oracle Service, Contracts etc.

Glossary-7

S

selection engine

In Oracle Advanced Pricing the selection engine is a part of pricing engine. Selection engine is responsible for selecting price lists and modifiers based on the Pricing Request.

selling price

Selling Price is defined as the price derived after applying price adjustments to the list price.

source transaction system

The source application that populates the pricing tables with information using the Pricing APIs. These include Order Management, iMarketing, Trade Management, Contracts, etc.

Glossary-8

Index
Aaccruals
in modifiers, 3-13redeeming, 3-130

addingitems to a price list, 5-37

adjusting. See changingadjustment method (modifiers), 3-7agreement price lists, 5-5agreements

creating, 8-5defining

price breaks, 8-12pricing attributes, 8-12

deleting, 8-18finding, 8-17overview, 8-2revising, 8-14types

Pricing, 8-2Standard, 8-2

appending qualifier groups (HTML UI), 2-15application method (modifiers), 3-7archiving

considerations, 6-4modifiers and modifier information, 3-136overview, 6-2price lists, 5-77pricing entities, 6-3

attachingpricing attributes to modifier lines, 3-69

Attribute Mapping Rules Error Report, 10-4

Bblock pricing

price breaks (HTML UI), 5-62recurring value, 5-25

buckets (modifiers), 3-12, 3-96Build Attribute Mapping Rules program, 10-5Build Formula Package program, 10-7

Cchanging

prices, 1-13common qualifiers (HTML UI), 2-7concurrent programs. See reportscopying

modifier line, 3-80modifiers, 3-77price list lines, 5-45price lists, 5-43

creatingagreement revisions, 8-14agreements, 8-6GSA list qualifiers, 5-32GSA price list, 5-29limits, 3-169modifier lines, 3-33modifier lines (HTML UI), 3-92modifiers, 3-23modifiers (HTML UI), 3-83price breaks (price list line), 5-19, 8-12price breaks for modifiers, 3-59price breaks for modifiers (HTML UI), 3-104price breaks for price list lines (HTML UI), 5-59

Index-1

price list lines, 5-11price list lines (HTML UI), 5-55price lists, 5-6price lists (HTML UI), 5-50pricing attributes for price list lines, 5-14pricing attributes in agreements, 8-12pricing formulas, 4-3qualifier groups, 2-17qualifiers, 5-16qualifiers (HTML UI), 2-6qualifiers, line level, 3-74qualifiers, list level, 3-29secondary price lists, 5-15

Cross Order Volume Load Report, 10-8Cross Order Volume Report, 10-10cross order volume, in modifiers, 3-15currency

in cross orders, 3-17modifiers, 3-84optional currency, 3-84price lists, 5-3

Ddefining. See creatingdeleting

agreements, 8-18modifier query, 3-166price breaks for modifier lines (HTML

UI), 3-110price breaks for price list lines (HTML UI), 5-64price list lines (HTML UI), 5-76qualifier groups, 2-29qualifiers, 3-30qualifiers (HTML UI), 2-14secondary price lists (HTML UI), 5-53

discounts/charges (modifier lines), 3-43duplicating. See copying

Eeffective dates (price list), 5-3enforcing limits, 3-183entering

coupon issue information, 3-51

freight charge information, 3-46item upgrade information, 3-48other item discount and promotions

information, 3-54price break information, 3-59terms substitution information, 3-50

events (modifiers), 3-13excluding items from modifier, 3-72excluding items from modifier (HTML UI), 3-113exclusive modifiers, 3-133

Ffactor lines (formula), finding, 4-12finding. See searchingformulas. See pricing formulas

GGeneral Services Administration (GSA) price lists,

creating, 5-29Global box

modifiers, 3-24, 5-30price lists, 5-8

grouping numbers, 2-21

HHTML UI (user interface) in pricing

accessing, 1-6Home page, 5-46modifier lists and modifiers, 3-3overview, 1-6price list maintenance feature, 5-78price lists and price list lines, 5-2, 5-49qualifier groups, 2-15qualifiers, 2-6

Iimplementation planning, 1-19inactive price lists, 5-3incompatibility processing (modifiers), 3-12item upgrade information, entering, 3-48

Index-2

Llimits

adjusting limit amounts, 3-185balances

updating, 3-181viewing, 3-177

changing amounts, 3-184creating, 3-169enforcing, 3-183overview, 3-167viewing transaction details, 3-177

line level qualifiers. See qualifierslist price

determining, 1-14

MMobile Download box

setting up for price lists, 5-7Modifier Details report, 10-11modifier lines

See also modifier lines (HTML UI)archiving, 3-136, 6-3attaching pricing attributes, 3-69copying, 3-80creating, 3-33, 3-36

coupon issue information, 3-51discounts/charges, 3-43freight and special charges, 3-46item upgrade, 3-48price break information, 3-59

excluding items, 3-71lumpsum application method, 3-9purging, 3-136, 6-10

modifier lines (HTML UI)See also modifier linesAdvanced Pricing Home page (HTML), 5-46archiving, 6-3controls

buckets, 3-96defining, 3-95incompatibility, 3-97modifier level, 3-95phases, 3-96

creating, 3-92discount, 3-99price break, 3-104promotional goods, 3-111surcharge, 3-116

purging, 6-10updating, 3-125

modifier lists. See modifiersmodifier scenarios

coupon issue, D-14discount, D-2freight and special charges, D-18item upgrade, D-16new price, D-21other item discounts (OID), D-9price break, D-7promotional goods, D-11surcharge, D-5term substitution, D-17

modifiersSee also modifiers (HTML UI)accruals, 3-13archiving, 5-77, 6-3concepts, 3-5

adjustment (application) method, 3-7buckets, 3-12events, 3-13incompatibility processing, 3-12

copying, 3-77creating modifier lists, 3-22

deal, 3-22discount list, 3-22freight and special charge list, 3-22promotion, 3-22surcharge list, 3-22

cross order volume, 3-15defined, 1-13, 1-15Global box, 3-24, 5-30incompatibility level, 3-97negative selling prices, 3-11optional currency, 3-84overview, 3-3pricing organizer, 3-137promotional limits. See limits.purging, 3-136, 5-77, 6-10

Index-3

qualifier grouping numbers, 2-21qualifiers (list level), 3-29terms substitution information, 3-50types, 3-6, 3-22using qualifiers, 2-5using with negative unit selling prices, 3-11

modifiers (HTML UI)See also modifiersAdvanced Pricing Home page (HTML), 5-46archiving, 6-3concepts, 3-84creating, 3-83

deal, 3-83discount list, 3-83promotion, 3-83surcharge list, 3-83

fieldsCustomer Must Ask For List box, 3-86Pricing for Global Use box, 3-86

optional currency, 3-84overview, 3-81purging, 6-10qualifier groups, 2-15qualifiers, 2-6searching, 3-120types, 3-84updating, 3-123

multi-currency conversion listsas qualifier, 7-11attaching to price lists or agreements, 7-17creating, 7-5overview, 7-2rounding, 7-13updating, 7-20

Nnavigator paths and windows, E-1negative prices

in modifiers, 3-11in price lists, 5-4, 5-55

Ooptional currency, 3-84

Oracle Pricing Administrator responsibility, in pricing security, 1-4

other item discount and promotions information, in modifiers, 3-54

overviewmodifiers, 3-3Oracle Advanced Pricing, 1-2price lists, 5-2pricing formulas, 4-2reports and concurrent programs, 10-2

Ppoint price breaks, 5-19price and modifier adjustments, applying, 1-14price breaks

agreements, 8-12block pricing, 5-23, 5-25block pricing for price lists (HTML UI), 5-62break unit pricing, 5-25defining, 5-19deleting (HTML UI), 3-110, 5-63modifier type, 3-59point, 5-19price lists (HTML UI), 5-59range, 5-19

price list linesSee also price list lines (HTML UI)attributes, 5-14changing

Bulk change, 5-88Detail change, 5-88

copying, 5-45creating, 5-11

price breaks, Block price, 5-23price breaks, 5-19qualifier groups, 5-18qualifiers, 5-16

price list lines (HTML UI)See also price list linesdeleting, 5-76price breaks

creating, 5-59deleting, 5-63

searching, 5-69, 5-80

Index-4

updating, 5-73updating with Price List maintenance

feature, 5-88Price List Maintenance feature, 5-78price list maintenance feature (HTML UI)

making detail and bulk changes, 5-88overview, 5-78searching, 5-80

price listsSee also price lists (HTML UI)adding items, 5-36adjusting, 5-34, 5-39agreement price lists, 5-5archiving, 5-77changing

Advanced change, 5-88Bulk change, 5-88

copying, 5-42creating, 5-6defined, 1-15deleting, 5-77fields

Active box, 5-3currency, 5-3Effective Dates, 5-3Global box, 5-8Mobile Download box, 5-7Round To, 5-3

GSA (General Services Administration), 5-29inactive, 5-3maintaining, 5-34purging, 5-77secondary price lists, 5-4, 5-15selecting, 1-14types of prices

Formula, 5-6percent price, 5-6Price Break, 5-6unit price, 5-6

using qualifiers, 2-5using the Price List Maintenance feature, 5-78

price lists (HTML UI)See also price listsAdvanced Pricing Home page (HTML), 5-46introduction, 5-2

qualifier groups, 2-17qualifiers, 2-6searching, 5-66, 5-80updating, 5-71updating with Price List maintenance

feature, 5-88using the Price List Maintenance feature, 5-78

price request structure, 1-14price request structure, defining, 1-14pricing

pricing attributes, 1-13product hierarchy, 1-13product hierarchy, defined, 1-13qualifiers, defined, 1-13

pricing agreements. See agreementspricing attributes

defining, 1-15, 5-14, 8-12pricing components

overview, 1-15price lists, 1-15pricing attributes, 1-15qualifier groups, 1-15qualifiers, 1-15service items, 1-17

pricing engine, 1-13Pricing for Global Use box (modifiers), 3-86pricing formula

creating, 4-3pricing formulas

defined, 1-16defining factor list details, 4-3overview, 4-2scenarios, C-2searching for formula factor lines, 4-12updating prices, 4-14

Pricing Formulas report, 10-15pricing organizer, 3-137pricing security, 1-4

Oracle Pricing Administrator, 1-4profile options, 1-19promotional limits. See limitspurging

modifiers and related modifier information, 3-136

pricing entities, 6-10

Index-5

QQP_Bulk Import of Price List program, 10-17QP_Maintains the Denormalized Data in QP

Qualifiers program, 10-22QP_Purge Pricing Engine Requests program, 10-16QP_Update Price Lists with Multi-Currency

Conversion Criteria program, 10-25qualifier grouping numbers, 2-21Qualifier Grouping report, 10-24qualifier groups

creating, 2-17defined, 1-15deleting, 2-29, 3-30modifying, 2-29searching, 2-28

qualifier groups (HTML UI)appending, 2-15

qualifiersSee also qualifiers (HTML UI)context, 2-2defined, 1-13, 1-15line level, creating, 3-74modifiers, creating, 3-29overview, 2-2price list lines, 5-16using with modifiers, 2-5using with price lists, 2-14value, 2-3

qualifiers (HTML UI)See also qualifiersappending a qualifier group, 2-15common qualifiers, 2-7creating, 2-6deleting, 2-14qualifier conditions, 2-6unique qualifiers, 2-6updating, 2-12

querying. See searching

Rrange price breaks, 5-19recurring value, in block pricing, 5-25redeeming accruals, 3-130

reports and concurrent programsAttribute Mapping Rules Error Report, 10-4Build Attribute Mapping Rules program, 10-5Build Formula Package program, 10-7Cross Order Volume Load Report, 10-8Cross Order Volume Report, 10-10Modifier Details report, 10-11overview, 10-2Price Lists report, 10-13Pricing Formulas report, 10-15Purge Pricing Engine Requests program, 10-16QP_Bulk Import of Price List program, 10-17QP_Maintains the Denormalized Data in QP

Qualifiers program, 10-22Qualifier Grouping report, 10-24Update Price Lists with Multi-Currency

Conversion Criteria program, 10-25Update Promotional Limit Balances

program, 10-28round to value (price lists), 5-3

Ssearching

agreements, 8-17modifier lists (HTML UI), 3-120price list lines (HTML UI), 5-69price lists (HTML UI), 5-66pricing formula factor lines, 4-12qualifier groups, 2-28using pricing organizer (modifiers), 3-137

secondary price lists, 5-4, 5-15deleting (HTML UI), 5-53

security privilegesmodifiers, 3-23, 3-77, 3-138multi-currency lists, 7-2price lists, 5-5reports, 10-2

service items, pricing, 1-17

Uunique qualifiers (HTML UI), 2-6Update Promotional Limit Balances

program, 10-28

Index-6

updatingbalances, 3-181formula prices, 4-14limit amounts, 3-184modifier incompatibility, 3-134modifier lines (HTML UI), 3-125modifiers (HTML UI), 3-123price list lines (HTML UI), 5-73price list prices, 5-34, 5-40price lists (HTML UI), 5-71prices for price list lines, 5-35prices for pricing formula, 4-14qualifiers (HTML UI), 2-12

updating, agreements, 8-14

Vviewing

limit balances, 3-177limit transaction details, 3-177

Wwindows and navigator paths, E-1

Index-7

Index-8

Date post:	18-Sep-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

User’s Guide Release 11i...viii QP: Bulk Import of Price List program..... 10-17 QP: Maintains the...

Documents