Documente Academic
Documente Profesional
Documente Cultură
Fundamentals
Student Guide - Volume 3
O
e
y
l
n
I
A
&
l
a
n
r
te
D17037GC20
Edition 2.0
n
I
e
December 2004
D40111
r
O
l
c
a
s
U
Author
John Salvini
y
l
n
Manoj Arya, David Barnacle, Amit Batra, Steven Best, Vanessa Graziano, Vivek Gulati, Anwar
Hussain, Jeff Lee, Vivian Y. Lee, Maria Viglionese Matheny, Abhijit Prasad, David Reitan,
Kalyani Subramanyan, Pius Sebastian, Nancy Szeto, Giri Tippireddy, Li Yang, Rebecca
Zarchikoff
O
e
&
l
a
n
r
te
r
O
l
c
a
n
I
e
I
A
oracletutor
s
U
Table of Contents
Overview of Advanced Pricing .......................................................................................................................1-1
Overview of Advanced Pricing .....................................................................................................................1-2
Objectives ......................................................................................................................................................1-3
Agenda...........................................................................................................................................................1-5
What is Oracle Advanced Pricing..................................................................................................................1-6
Benefits of Advanced Pricing........................................................................................................................1-8
Overview of Advanced Pricing in the Order to Cash Process .......................................................................1-9
Agenda...........................................................................................................................................................1-10
From Basic Pricing to Advanced ...................................................................................................................1-11
Advanced Pricing ..........................................................................................................................................1-12
Basic/Advanced Pricing Summary: Pricing Security ....................................................................................1-15
Basic/Advanced Pricing Summary: Price Lists .............................................................................................1-16
Basic/Advanced Pricing Summary: Agreements...........................................................................................1-18
Basic/Advanced Pricing Summary: Formulas ...............................................................................................1-19
Basic/Advanced Pricing Summary: Modifiers ..............................................................................................1-20
Agenda...........................................................................................................................................................1-24
Pricing Engine Overview...............................................................................................................................1-25
Pricing Engine ...............................................................................................................................................1-28
Pricing Engine Process ..................................................................................................................................1-30
Agenda...........................................................................................................................................................1-32
Advanced Pricing Features ............................................................................................................................1-33
The Advanced Pricing Process ......................................................................................................................1-34
Qualifiers .......................................................................................................................................................1-35
Qualifier Groups ............................................................................................................................................1-36
Modifiers .......................................................................................................................................................1-37
Accruals.........................................................................................................................................................1-39
Formulas ........................................................................................................................................................1-40
Price Lists ......................................................................................................................................................1-42
Pricing Attributes...........................................................................................................................................1-43
Contexts.........................................................................................................................................................1-44
Attribute Management...................................................................................................................................1-45
Responsibility Levels ....................................................................................................................................1-46
Oracle Pricing Administrator.........................................................................................................................1-47
Oracle Pricing Manager.................................................................................................................................1-48
Oracle Pricing User .......................................................................................................................................1-49
Agenda...........................................................................................................................................................1-50
Oracle Advanced Pricing HTML User Interface (UI) ...................................................................................1-51
Description of Major Changes.......................................................................................................................1-52
Pricing Home Page (HTML UI) ....................................................................................................................1-53
Modifier Setup (HTML UI)...........................................................................................................................1-54
Shortcut Region from HTML Home page.....................................................................................................1-56
Shortcut Region (HTML Home page) ...........................................................................................................1-57
Summary........................................................................................................................................................1-58
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Agenda...........................................................................................................................................................3-47
Security Implementation Steps Setting up Default Security Profile Options .............................................3-48
Security Implementation Steps Turning Security On .................................................................................3-50
After the Security Upgrade: Impact of Changes............................................................................................3-52
Summary........................................................................................................................................................3-53
Qualifiers and Qualifier Groups ....................................................................................................................4-1
Qualifiers and Qualifier Groups ....................................................................................................................4-2
Objectives ......................................................................................................................................................4-3
Agenda...........................................................................................................................................................4-5
Overview of Qualifiers ..................................................................................................................................4-6
Agenda...........................................................................................................................................................4-8
Creating Qualifiers for Price Lists or Modifiers ............................................................................................4-9
Creating List Qualifiers in Creation Flow (HTML UI) .................................................................................4-10
Creating Line Qualifiers in Creation Flow (HTML UI) ................................................................................4-11
Typical Qualifier Setup (HTML UI) .............................................................................................................4-12
Agenda...........................................................................................................................................................4-13
Qualifier Terminology...................................................................................................................................4-14
Example of Qualifier Hierarchy ....................................................................................................................4-15
Qualifiers (HTML UI) ...................................................................................................................................4-16
Unique Qualifiers (HTML UI) ......................................................................................................................4-17
Common Qualifiers (HTML UI) ...................................................................................................................4-18
Agenda...........................................................................................................................................................4-19
Creating Qualifier Groups .............................................................................................................................4-20
Qualifier Grouping Number ..........................................................................................................................4-21
Practice - Create a Qualifier Group ...........................................................................................................4-23
Solution Create a Qualifier Group ..........................................................................................................4-25
Agenda...........................................................................................................................................................4-29
Appending Qualifier Groups .........................................................................................................................4-30
Agenda...........................................................................................................................................................4-31
Entering Qualifier Information (Forms UI) ...................................................................................................4-32
Qualifier Grouping Number (Forms UI) .......................................................................................................4-34
Selected Qualifier Groups..............................................................................................................................4-35
Agenda...........................................................................................................................................................4-36
Appending Qualifier Groups (Forms UI) ......................................................................................................4-37
Retaining Grouping Numbers Across Qualifier Groups................................................................................4-38
Generating Unique Grouping Numbers Across Qualifier Groups.................................................................4-39
Summary........................................................................................................................................................4-40
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
Formulas...........................................................................................................................................................6-1
Formulas ........................................................................................................................................................6-2
Objectives ......................................................................................................................................................6-3
Agenda...........................................................................................................................................................6-5
Overview of Formulas ...................................................................................................................................6-6
Formulas ........................................................................................................................................................6-7
Component Types..........................................................................................................................................6-8
Agenda...........................................................................................................................................................6-10
Types of Formulas .........................................................................................................................................6-11
Static Calculation...........................................................................................................................................6-12
Dynamic Calculation .....................................................................................................................................6-13
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management....................................................................................................................................8-1
Attribute Management...................................................................................................................................8-2
Objectives ......................................................................................................................................................8-3
Agenda...........................................................................................................................................................8-4
What is Attribute Management? ....................................................................................................................8-5
Common Terms .............................................................................................................................................8-7
Attributes in Advanced Pricing .....................................................................................................................8-9
Attributes and Contexts .................................................................................................................................8-10
How Can Attributes Control Pricing Actions? ..............................................................................................8-11
Steps in Creating Attributes...........................................................................................................................8-12
Agenda...........................................................................................................................................................8-13
Overview of Pricing Transaction Entity (PTE) .............................................................................................8-14
Components of a Pricing Transaction Entity .................................................................................................8-16
Source Systems and Request Types...............................................................................................................8-18
Example: Order Fulfillment PTE...................................................................................................................8-19
Reviewing Available PTEs............................................................................................................................8-20
Role of PTEs in Attribute Management ........................................................................................................8-21
PTE in Attribute Creation Process.................................................................................................................8-22
Linking Attributes to a PTE...........................................................................................................................8-23
Creating a New Pricing Transaction Entity ...................................................................................................8-25
Defining Pricing Transaction Entity Associations.........................................................................................8-27
Agenda...........................................................................................................................................................8-28
What is a Context?.........................................................................................................................................8-29
Context Examples..........................................................................................................................................8-30
Understanding Contexts ................................................................................................................................8-31
Contexts.........................................................................................................................................................8-32
Qualifier Contexts..........................................................................................................................................8-34
Qualifier Context Examples ..........................................................................................................................8-35
Product Contexts............................................................................................................................................8-36
Pricing Contexts ............................................................................................................................................8-37
Agenda...........................................................................................................................................................8-38
Context/Attribute Creation Process ...............................................................................................................8-39
Creating Attributes for Contexts....................................................................................................................8-40
Attribute Selection: Pricing Engine Processing.............................................................................................8-41
Pricing Attributes and Flexfields ...................................................................................................................8-42
Pricing Attributes...........................................................................................................................................8-43
Practice - Create a Pricing Qualifier Context and Attributes.....................................................................8-46
Solution Create a Pricing Qualifier Context and Attributes.....................................................................8-48
Agenda...........................................................................................................................................................8-52
Overview of Attribute Mapping Methods .....................................................................................................8-53
Stages in Attribute Creation...........................................................................................................................8-54
Linking Attributes to a Pricing Transaction Entity........................................................................................8-55
Advanced PricingPTEAttribute Linking Window.....................................................................................8-56
Setting Attribute Levels.................................................................................................................................8-58
Attribute Levels .............................................................................................................................................8-60
Attributes and Pricing Window LOVs...........................................................................................................8-61
Disabling an Attribute from a PTE ................................................................................................................8-63
Practice - Link Attributes to a Pricing Transaction Entity (PTE) ..............................................................8-64
Solution Link the Attribute to a Pricing Transaction Entity (PTE).........................................................8-66
Agenda...........................................................................................................................................................8-69
Assigning an Attribute Mapping Method ......................................................................................................8-70
Attribute Mapping .........................................................................................................................................8-72
Setting Up a New Mapping Rule for a Qualifier/Pricing Attribute ...............................................................8-73
Attribute Mapping Window...........................................................................................................................8-75
Practice - Use Attribute Mapping to Define an Attribute ..........................................................................8-77
Solution Use Attribute Mapping to Define an Attribute.........................................................................8-80
Agenda...........................................................................................................................................................8-86
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
Prerequisites
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Related Publications
Oracle Publications
Title
Part Number
B14385_01
B13966-01
A95861_03
A88765_05
Additional Publications
Read-me files
Oracle Magazine
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Typographic Conventions
Typographic Conventions in Text
Convention
Bold italic
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Italic
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Quotation
marks
Uppercase
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.
For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
Arrow
Brackets
Commas
Plus signs
l
c
a
n
I
e
r
O
Key combinations
Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
Syntax variables
O
e
y
l
n
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
3.
Notations:
(N) = Navigator
n
r
te
(M) = Menu
n
I
e
(T) = Tab
(B) = Button
&
l
a
I
A
s
U
l
c
a
(I) = Icon
r
O
(H) = Hyperlink
(ST) = Sub Tab
Copyright Oracle Corporation, 2004. All rights reserved.
In the navigation frame of the help system window, expand the General Ledger entry.
2.
3.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 1
Modifiers
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 2
Objectives
y
l
n
O
e
s
U
Lesson Aim
This lesson explains how to set up and use modifiers in Oracle Advanced Pricing. Modifiers
enable you to set up price adjustments such as discounts and surcharges; benefits such as free
goods or 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 3
Objectives
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 4
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 5
Overview
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 6
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 7
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 8
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 9
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 10
Modifier Components
y
l
n
O
e
s
U
Modifier Components
Each modifier list that you set up consists of modifier lines--both are set up in the modifier
setup window.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 11
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 12
Modifier Setup
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 13
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 14
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 15
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
Discount List
n
I
e
Promotion
Surcharge List
l
c
a
For each list type that you define, you can associate certain line type modifiers.
r
O
Modifiers
Chapter 7 - Page 16
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 17
Currency
y
l
n
O
e
s
U
Currency
Select a Currency for the modifier. Alternately, you can select Optional Currency to make the
modifier list available to all currencies.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 18
Optional Currency
y
l
n
O
e
s
U
Optional Currency
You can set up a modifier list that can be applied to any transaction regardless of currency. No
currency conversion is done by these modifiers. For example, this type of modifier could be
used to give a world-wide discount of 10% without creating a modifier in each of the
transaction currencies in which you do business.
It can be used with all application methods and modifier types.
This feature is supported in both Forms and HTML, and is available for both Basic and
Advanced Pricing users.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 19
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 20
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 21
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 22
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 23
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 24
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 25
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 26
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 27
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 28
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 29
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 30
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 31
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 32
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 33
Discount Modifier
y
l
n
O
e
s
U
Discount Modifier
A discount can be a percentage of a basic value. For example, a corporate customer can be
offered a 15-percent discount. A discount can also be a fixed amount. For example, a discount
of $10 can be offered to a customer who spends more than $300.
Scenario 1
If a customer is a preferred customer or customer spends more than $150, they receive 10% off
the order.
Scenario 2
For any 10 compact discs purchased by April 2000, the customer receives $2 off.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 34
Assumptions
Oracle Pricing User and Order Management Super User, Vision Operations
responsibility
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
y
l
n
O
e
s
U
1.
2.
&
l
a
I
A
n
r
te
3.
4.
5.
6.
7.
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 35
Click Yes to confirm that you want to save your changes, and add modifier lines.
The Update Discount List: Modifier Lines page displays.
9.
Click Create Line to create a new modifier line. The modifier line defines details about the
actual discount to be applied:
Modifier Type = Discount
Start Date = Current
y
l
n
O
e
s
U
You will have a discount of 5% for all products ordered if one of the following conditions
exists (as defined by the conditions of the Qualifier Group attached to the modifier):
[Customer = Business World AND Price List = Corporate] OR
[Customer Name = ABC Application Software] OR
[Price List = Web Special]
I
A
&
l
a
15. Click Next to display Qualifiers page, but do not select any line qualifiers.
16. Click Finish to save your changes.
n
r
te
17. Important: After creating the modifier, query it in the Home Page, select the Active box to
activate it, and click Apply to save the changes. This enables the modifier to be applied to
the sales order.
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 36
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 37
(N) Oracle Pricing User > Home > Advanced Pricing Home page
y
l
n
O
e
I
A
&
l
a
s
U
2.
3.
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 38
4.
y
l
n
(B) Next.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 39
y
l
n
6.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 40
7.
y
l
n
(B) Apply
This appends the qualifier group to the modifier defined in the General Information page.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 41
8.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 42
9.
(B) Finish.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 43
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 44
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 45
Define Controls
y
l
n
&
l
a
O
e
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 46
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 47
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 48
Define Qualifiers
y
l
n
If you click Create Qualifier or Append Qualifier, you can create a new qualifier that would
qualify for just this modifier line (not all modifier lines in the list). We will not add a
Modifier Line level qualifier.
O
e
I
A
&
l
a
s
U
22. Important: After creating the modifier, query it in the Home Page, select the Active box to
activate it, and click Apply to save the changes. This enables the modifier to be applied to
the sales order.
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 49
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 50
25.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 51
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 52
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 53
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 54
Surcharge Modifier
y
l
n
O
e
s
U
Surcharge Modifier
A Surcharge modifier increases the cost of an item. It can be applied using the following
application methods:
Percent
Amount
New price
Lump sum
A surcharge can be used to apply taxes, handling charges, and other special costs in the price.
Scenario 1
Customers in the National Accounts territory who spends less than $1000 per order receives a
2-percent surcharge.
Scenario 2
Any customer placing a rush order (delivery required within two days) has to pay a $50
surcharge for special handling.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 55
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Define General Information for the Surcharge Modifier
1.
2.
3.
e
l
c
Price List
Customer Name
6.
I
A
s
U
&
l
a
n
r
te
5.
O
e
Create Qualifiers
4.
y
l
n
a
r
O
In
Operator
Value From
Is
XX-Price List1
Is
Click Apply, then click Next to add a surcharge modifier line. The modifier line defines
details about the actual surcharge to be applied.
Click Create Line to create a new modifier line:
Copyright Oracle Corporation, 2004. All rights reserved.
Modifiers
Chapter 7 - Page 56
9.
Enter Controls:
Modifier Level = Line
Pricing Phase = All Lines Adjustment
Bucket = Pricing Adjustments Bucket 1
Incompatibility = Blank
Automatically Apply = Selected
10. Click Next to display the Create Surcharge Line: Product and Benefit page.
Create Surcharge Line: Product and Benefit
11. Enter product and benefit information:
Product Level = All Items
UOM = Ea
12. In Benefit region:
Value = 10
Adjustment Method = Percent
y
l
n
You now have a surcharge of 10% for all products ordered, only when
The customer is XX-Big City Electronics and
The price list used for the order is XX-Price List1
I
A
O
e
s
U
13. Click Next to display Qualifiers page, but do not select any line qualifiers.
14. Click Apply to save your changes.
&
l
a
n
r
te
15. Enter a Sales Order for XX-Big City Electronics. At the sales order line level enter item
AS54888 with a quantity of 1.
n
I
e
l
c
a
17. After saving the order, there should be a surcharge of 10% added to your lines.
r
O
Modifiers
Chapter 7 - Page 57
(N) Oracle Pricing User > Home > Advanced Pricing Home page > Create Surcharge
List
y
l
n
O
e
I
A
2.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 58
3.
y
l
n
(B) Next.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 59
4.
Create Qualifiers
5.
Enter the following qualifiers. After adding the first qualifier, click Add Another Row to
enter the second qualifier:
Attribute
Operator
Value From
Price List
Is
XX-Price List1
Customer Name
Is
y
l
n
O
e
I
A
6.
&
l
a
s
U
n
r
te
(B) Apply.
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 60
7.
y
l
n
(B) Finish.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 61
8.
(B) Yes.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 62
y
l
n
&
l
a
O
e
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 63
y
l
n
(B) Next.
Enter Product and Benefit information
Product Level = All Items
UOM = Ea
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 64
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
Note: If you click Create Qualifier or Append Qualifier, you can create a new qualifier that
would qualify for just this modifier line (not all modifier lines in the list). Instead, select (B)
Finish. We will not add a Modifier Line level qualifier.
l
c
a
r
O
Modifiers
Chapter 7 - Page 65
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 66
(B) Apply.
16. Save your work.
Enter a Sales Order
17. Navigate to the Sales Order window.
18.
19. Enter a Sales Order for XX-Big City Electronics. At the sales order line level enter item
AS54888 with a quantity of 1.
y
l
n
O
e
I
A
&
l
a
Ordered Item
ra
XX-Standard Phone
XX-Palm Pilot
n
r
te
n
I
e
cl
s
U
Quantity
3
5
Modifiers
Chapter 7 - Page 67
y
l
n
O
e
22. After saving the order, there should be a surcharge of 10% added to your lines.
23. (B) Actions > View Adjustments. View your price adjustments and see which modifier
attached.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 68
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 69
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 70
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 71
A Modifier List with four line modifiers that determine how to use the formulas
Note: For freight charge modifiers, you can apply freight charges of one Charge Name only
(such as "Freight Costs") once even if more number of charges qualifies.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
y
l
n
Tasks
O
e
2.
n
r
te
Volume
n
I
e
Numeric Constant
3.
&
l
a
Pricing Attribute
Context
N/A
I
A
s
U
Pricing
Attribute
Component
Step
Item Amount
N/A
N/A
.01
l
c
a
r
O
Place your cursor on the Formula name field, clear the record, and enter the next formula:
Name = XX-Handling
Description = Item Quantity x Constant .05
Copyright Oracle Corporation, 2004. All rights reserved.
Modifiers
Chapter 7 - Page 72
Formula = 1*2
Formula Type
Pricing Attribute
Context
Pricing
Attribute
Component
Step
Pricing Attribute
Volume
Item Quantity
N/A
Numeric Constant
N/A
N/A
.05
5.
7.
8.
y
l
n
9.
Qualifier
Context
Qualifier
Attribute
Precedence
Modifier List
Price List
Defaults
Order
Order Type
Defaults
Click OK.
&
l
a
Operator
=
I
A
=
s
U
O
e
Value From
XX-Price List1
Mixed
10. In the Modifiers Summary tab, enter the following modifier line information:
n
r
te
Modifier
Number
Level
Modifier Type
Line
Freight/Special
Charge
l
c
a
n
I
e
Start/End Dates
Optional
Automatic
Selected
Pricing Phase
50 (Line
Charges)
r
O
Charge Name
Freight Costs
Formula
XX-Freight
Application Method
Lumpsum
Modifiers
Chapter 7 - Page 73
Bucket
Value
(blank)
12. Click Line Qualifiers and enter the following qualifier data:
Group
Number
1
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
Precedence
Defaults
Operator
BETWEEN
Value
From
0
Value
To
10000
Level
Order
Modifier Type
Freight/Special
Charge
Start/End
Dates
Optional
Automatic
Selected
Pricing Phase
70 (Charges:
Header/All Lines)
Bucket
(blank)
Application Method
Lumpsum
Value
750
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
Precedence
Defaults
Operator
BETWEEN
Modifier Type
Freight/Special
Charge
n
r
te
Formula
XX-Handling
y
l
n
10000
s
U
Automatic
Selected
&
l
a
n
I
e
l
c
a
I
A
Start/End
Dates
Optional
Value To
O
e
Modifier
Number
3
Value
From
Pricing Phase
50 (Line Charges)
Application Method
Lumpsum
Bucket
1
Value
Blank
r
O
Group
Number
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
Precedence
Operator
Defaults
BETWEEN
Modifiers
Chapter 7 - Page 74
Value
From
0
Value
To
10000
Level
Modifier Type
Order
Freight/Special
Charge
Start/End
Dates
Optional
Automatic
Pricing Phase
Bucket
Selected
70 (Charges:
Header/All Lines)
(blank)
Application Method
Handling Costs
Value
Lumpsum
50
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
Precedence
Operator
Defaults
BETWEEN
Value
From
10001
Value
To
999999
9
y
l
n
26. Return to the Main tab of the Modifier header and select the Active check box.
O
e
Enter a Sales Order Using the Freight and Handling Charge Modifier
28. Navigate to the Sales Orders window.
29. In the
I
A
s
U
Main tab:
Customer = XX-Big City Electronics
Required Header information defaults from your customer setup
Price List = XX-Price List1
&
l
a
n
r
te
n
I
e
31. Save your work and note the order number ---------------.
l
c
a
32. Click Actions > Charges and Freight Costs to view your charges. You should have charges
for both Freight Costs and Handling Costs. Close the window
r
O
33. In the Order Information tab, click Actions > Charges. Should see a $750 lumpsum.
Modifiers
Chapter 7 - Page 75
34. Increase the order line to a dollar amount greater than $10,000 (quantity 15)
35. Save your work.
36. Click Actions > Select Charges to view your charges. There should be none (provided
Order Total is above $10,000).
37. Close the window and select the Order Information tab.
38. Click Actions > Charges. There should be only one line for Handling Costs of $50 and no
Freight Costs (provided the Order Total is greater than $10,000).
39. Save your work.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 76
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 77
Formula Type
Pricing Attribute
Context
Pricing
Attribute
Component
Step
Pricing Attribute
Volume
Item Amount
N/A
Numeric Constant
N/A
N/A
.01
y
l
n
O
e
3.
I
A
(I) Save.
5.
&
l
a
s
U
n
I
e
n
r
te
Formula Type
l
c
a
Pricing Attribute
Context
Pricing
Attribute
Component
Step
Pricing Attribute
Volume
Item Quantity
N/A
Numeric Constant
N/A
N/A
.05
r
O
Modifiers
Chapter 7 - Page 78
6.
y
l
n
O
e
Note: For freight charge modifiers, you can apply freight charges of one Charge Name (such as
"Freight Costs") only once even if more number of charges qualifies.
7.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 79
y
l
n
8.
(T) Main.
9.
&
l
a
O
e
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 80
y
l
n
Qualifier
Context
Qualifier
Attribute
Precedence
Modifier List
Price List
Defaults
Order
Order Type
Defaults
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 81
O
e
Operator
Value From
XX-Price List1
Mixed
Level
Line
Modifier Type
Freight/Special
Charge
Start/End
Dates
Automatic
Pricing Phase
Bucket
Optional
Selected
50 (Line Charges)
y
l
n
O
e
I
A
e
l
c
&
l
a
Formula
rn
XX-Freight
e
t
In
s
U
Application Method
Lumpsum
a
r
O
Modifiers
Chapter 7 - Page 82
Value
(blank)
y
l
n
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
Operator
Value
From
Value
To
Defaults
BETWEEN
10000
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
O
e
Precedence
Modifiers
Chapter 7 - Page 83
Level
Modifier Type
Order
Freight/Special
Charge
Start/End
Dates
Optional
Automatic
Pricing Phase
Bucket
Selected
70 (Charges:
Header/All Lines)
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 84
(blank)
y
l
n
Application Method
Freight Costs
Lumpsum
750
I
A
Qualifier
Context
Volume
e
l
c
Qualifier
Attribute
a
n
r
l&
Order Amount
O
e
Value
Precedence
Defaults
s
U
Operator
BETWEEN
e
t
In
a
r
O
Modifiers
Chapter 7 - Page 85
Value
From
Value
To
10000
Level
Modifier Type
Line
Freight/Special
Charge
Start/End
Dates
Optional
Automatic
Pricing Phase
Selected
50 (Line Charges)
I
A
s
U
Charge Name
Formula
Application Method
Value
Handling Costs
XX-Handling
Lumpsum
Blank
&
l
a
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
Modifiers
Chapter 7 - Page 86
Bucket
1
y
l
n
O
e
Group
Number
Qualifier
Context
Qualifier
Attribute
Precedence
Operator
Value
From
Value
To
Volume
Order
Amount
Defaults
BETWEEN
10000
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 87
Level
Modifier Type
Start/End
Dates
Automatic
Pricing Phase
Order
Freight/Special
Charge
Optional
Selected
70 (Charges:
Header/All Lines)
y
l
n
O
e
Application Method
Value
Handling Costs
Lumpsum
50
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Bucket
Modifiers
Chapter 7 - Page 88
(blank)
y
l
n
Qualifier
Context
Volume
Qualifier
Attribute
Order Amount
I
A
&
l
a
s
U
BETWEEN
n
r
te
n
I
e
l
c
a
r
O
O
e
Operator
Precedence
Defaults
Modifiers
Chapter 7 - Page 89
Value
From
10001
Value To
9999999
y
l
n
O
e
Enter a Sales Order Using the Freight and Special Charge Modifier
31. Navigate to the Sales Orders window.
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 90
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 91
y
l
n
34. (I) Save your work and note the order number ______________.
O
e
36. (B) Actions > Charges and Freight Costs to view your charges. You should have charges
for both Freight Costs and Handling Costs.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 92
y
l
n
O
e
s
U
39. (B) Actions > Charges. Should see the $750 lumpsum freight costs applied.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 93
y
l
n
O
e
41. Increase the quantity ordered (such as quantity 15) of the order line so that the ordered
amount exceeds $10,000.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 94
y
l
n
O
e
44. (B) Actions > Charges and Freight Costs to view your charges. There should be none
(provided Order Total is above $10,000).
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 95
y
l
n
O
e
I
A
s
U
There should be only one line for Handling Costs of $50 and no Freight Costs (provided the
Order Total is greater than $10,000).
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 96
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 97
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 98
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Define the Promotional Goods Modifier
1.
2.
y
l
n
O
e
I
A
3.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
Grouping No.
r
O
1
1
Context
Attribute
Operator
Value From
Customer
Customer Name
Modifier
List
Price List
XX-Price List5
Modifiers
Chapter 7 - Page 99
5.
Click OK.
6.
In the Modifiers Summary tab, enter the following modifier line information:
Modifier
No.
Level
XXPromo
Line
Modifier
Type
Start
Date
End
Date
Promotional Today
Goods
One
week
from
today
Automatic
Selected
Override
Cleared
7.
8.
9.
Group
No.
Product
Attribute
Item
Number
Product
Value
I
A
XX-Phone
Card
Pricing
Attribute
Item Quantity
&
l
a
Pricing
Phase
30 (All Lines
Adjustment)
y
l
n
O
e
s
U
Operator
Value From
Between
Value To
999999999
Get
Product
Attribute
Item
Number
n
I
e
cl
a
r
O
Get
Product
Value
n
r
te
XX-Palm
Pilot
UOM
Ea
Get Quantity
Get Price***
XX-Price List5
Application
Method
Percent
Value
100
***This field is used to enter the price list that you would like the value of the get item to
default from. The value will default into this field.
Copyright Oracle Corporation, 2004. All rights reserved.
Modifiers
Chapter 7 - Page 100
Ordered Item
Quantity
XX-Standard Phone
XX-Phone Card
y
l
n
O
e
You should receive the following message. A new line has been created for item XX-Palm
Pilot and for Quantity 1.
s
U
18. Go to the line that was automatically added, that is, the line for the XX-Palm Pilot.
I
A
19. Click Actions > View Adjustments. You will see the details of the modifier you applied.
20. Click Related Details. Note that the XX-Standard Phone is listed as the related line.
&
l
a
n
r
te
22. Click Actions > View Adjustments. View the details of the modifier you applied.
23. Click Related Details. Note the XX-Palm Pilot as the related item.
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 101
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 102
2.
O
e
y
l
n
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 103
3.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 104
y
l
n
O
e
I
A
&
l
a
4.
s
U
n
r
te
n
I
e
r
O
l
c
a
Grouping No.
1
1
Context
Attribute
Operator
Value From
Customer
Customer Name
Modifier List
Price List
XX-Price List5
Modifiers
Chapter 7 - Page 105
5.
(B} OK.
6.
7.
Modifier
No.
Level
Modifier
Type
Start
Date
XXPromo
Line
Promotional
Goods
Today
End
Date
One
week
from
today
Automatic
Override
Selected
Cleared
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 106
y
l
n
30 (All Lines
Adjustment)
O
e
s
U
Pricing
Phase
y
l
n
O
e
Product
Attribute
Item
Number
Product
Value
XX-Phone
Card
Pricing
Attribute
Item
Quantity
&
l
a
I
A
s
U
Operator
Between
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 107
Value
From
1
Value To
999999999
y
l
n
O
e
Get
Product
Value
XX-Palm
Pilot
UOM
Get
Quantity
Ea
Get Price***
I
A
XX-Price List5
&
l
a
s
U
Application
Method
Percent
Value
100
***This field is used to enter the price list that you would like the value of the get item to
default from. The value will default into this field.
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 108
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 109
O
e
y
l
n
I
A
Ordered Item
XX-Standard Phone
Quantity
&
l
a
s
U
n
r
te
XX-Phone Card
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 110
y
l
n
O
e
18. You should receive the following message. A new line has been created for item XX-Palm
Pilot and for Quantity 1.
I
A
&
l
a
s
U
n
r
te
19. (B) OK
20. Go to the line that was automatically added, that is, the line for the XX-Palm Pilot
n
I
e
21. (B) Actions > View Adjustments. You will see the details of the modifier you applied.
l
c
a
r
O
Modifiers
Chapter 7 - Page 111
y
l
n
22. (B) Related Details. Note that the XX-Standard Phone is listed as the related line.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
24. (B) Actions > View Adjustments. View the details of the modifier you applied.
Modifiers
Chapter 7 - Page 112
y
l
n
25. (B) Related Details. Note the XX-Palm Pilot as the related item.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 113
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 114
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Create a Terms Substitution Modifier
1.
2.
3.
4.
&
l
a
y
l
n
O
e
s
U
I
A
Level
Defaults
Line
Modifier
Type
I
e
l
c
a
r
O
e
t
n
rn
Term
Substitution
Automatic
Override
Selected
Cleared
Pricing
Phase
Modifiers
Chapter 7 - Page 115
Incomp.
Group
Bucket
Blank
5.
Qualifier
Context
Qualifier
Attribute
Customer
Customer Name
Volume
Order Amount
Operator
Value
From
BETWEEN
Value To
End Date
XX-Big
City
Electronics
Grayed
Out
Tomorrow
3000
99999999 Blank
7.
Click OK.
8.
Return to the Header (main tab) and select the Active checkbox.
9.
10. Now enter an order to confirm that the terms substitution modifier is applied.
Create a Sales Order
y
l
n
O
e
&
l
a
Quantity
4
I
A
s
U
n
r
te
n
I
e
15. Save the order line and note the order number ___________.
l
c
a
16. In the Pricing tab, the Payment Terms field should now change to Net 90.
r
O
Modifiers
Chapter 7 - Page 116
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
(T) Main:
Type = Promotion
Name = XX-Terms
Currency =Defaults
Description = Enter a meaningful description
Number = XX-Terms
Version = 1
Start Date = Default
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 117
Modifier
Number
Level
Modifier
Type
Automatic
Override
Defaults
Line
Term
Substitution
Selected
Cleared
&
l
a
I
A
y
l
n
s
U
Pricing Phase
30 (All Lines
Adjustment)
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 118
O
e
Incom.
Group
Bucket
Blank
Blank
3.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 119
y
l
n
O
e
Qualifier
Context
Qualifier
Attribute
Customer
Customer
Name
Volume
Order
Amount
e
l
c
Operator
=
a
n
r
l&
I
A
BETWEEN
s
U
Value
From
XX-Big
Grayed
City
Out
Electronics
3000
e
t
In
a
r
O
Modifiers
Chapter 7 - Page 120
Value To
End Date
Tomorrow
99999999 Blank
5.
Click OK.
6.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
7.
r
O
Modifiers
Chapter 7 - Page 121
y
l
n
9.
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 122
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 123
y
l
n
O
e
13. In the Pricing tab, the Payment Terms field should now change to Net 90.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 124
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 125
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 126
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 127
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Create an Item Relationship For the Upgrade
You first must define the item upgrade relationship.
1.
Navigate to the Item Relationships window. If the Organizations window opens, select M1.
In the Find Item Relationships window, press the New button.
2.
y
l
n
O
e
3.
4.
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 128
5.
Context
Attribute
Customer
Operator
Customer Name
Value From
XX-Big City
Electronics
6.
Click OK.
7.
8.
In the Promotion Upgrades tab, select the Upgrade Item = XX-WAP Phone.
9.
O
e
s
U
Now enter an order to confirm that the item gets upgraded to the XX-WAP Phone.
I
A
&
l
a
n
r
te
n
I
e
r
O
l
c
a
1.1
y
l
n
Ordered Item
XX-Standard Phone
Quantity
1
Modifiers
Chapter 7 - Page 129
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 130
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 131
2.
3.
O
e
y
l
n
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 132
5.
&
l
a
y
l
n
O
e
I
A
s
U
n
r
te
cl
Grouping
No.
a
r
O
1
n
I
e
Qualifier
Context
Customer
Qualifier Attribute
Operator
Customer Name
Modifiers
Chapter 7 - Page 133
Value From
XX-Big City Electronics
7.
Click OK.
Enter Modifier Line Details for the Item that you must buy to get the Upgrade
8.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
9.
r
O
Modifiers
Chapter 7 - Page 134
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 135
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 136
y
l
n
Ordered Item
O
e
Quantity
XX-Standard Phone
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 137
y
l
n
O
e
You should see the details of the upgrade modifier that you applied.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 138
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 139
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 140
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 141
Assumptions
y
l
n
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
O
e
Tasks
I
A
s
U
You first must create the benefit (such as a discount) that the customer receives when the
coupon is redeemed.
&
l
a
1.
2.
3.
n
r
te
n
I
e
l
c
a
In the Modifiers Summary tab, enter the following modifier line information:
Modifier No = XX-CoupD (where XX are your initials and CoupD stands for
Coupon Discount)
Level = Line
r
O
Modifiers
Chapter 7 - Page 142
4.
5.
Now you have to create the Coupon Issue modifier line (this is the coupon that will be generated
for the customer).
6.
7.
In the Modifiers Summary tab, enter the following modifier line information:
Modifier No = XX-Coup (where XX are your initials).
When issuing coupons, the system generates coupon numbers based on the
modifier number. So the first coupon to be issued based on the Modifier No. The
customer will quote the modifier number when redeeming the coupon so it is very
important that the modifier number (Modifier No) enables you to recognize the
type of coupon.
Level = Line
Modifier Type = Coupon Issue
Automatic = Yes
Pricing Phase = All Lines Adjustment
y
l
n
8.
O
e
I
A
s
U
&
l
a
Note: The Redemption Rate field (Coupons tab) is used in situations where it is necessary to
convert the value in the Benefit UOM field to the primary currency. For example, if one air
mile is 0.50 currency units, redemption rate is 0.50.
n
r
te
Although Expiration fields are not used in this practice they are useful for setting redemption
dates for the coupon. The pricing engine will take as a start date the first day a coupon is
issued. The pricing engine will then calculate the expiration end date using the values entered
for Expiration Period and Expiration Period Type (or Expiration Date only if that was used).
9.
n
I
e
l
c
a
The coupon is issued when the customer places an order from $1000. To create this, you
must create a qualifier for the modifier Coupon Issue.
r
O
10. Click the Line Qualifiers button to display the Qualifier-Line Level Qualifiers window.
Modifiers
Chapter 7 - Page 143
y
l
n
O
e
19. To confirm that a coupon has been issued, click the Action button then select View
Adjustments.
I
A
s
U
At the order level, you will see the most recent coupon number that was issued. Go to the
first line on the sales order, click the Action button, select View Adjustments. You will see
that a coupon has been issued with number XX-Coup### (where # is the number generated).
At the order line level, you can see the first coupon being issued.
&
l
a
The pricing engine has created additional qualifiers to ensure that the discount is only
applied when one of the created coupon numbers is quoted.
n
r
te
n
I
e
20. Enter a new sales order for XX-Big City Electronics. At the sales order line level, enter the
item eligible for the discount AS54888.
l
c
a
r
O
Modifiers
Chapter 7 - Page 144
23. Select the Coupon tab. From the list of values, select the coupon number that was issued
XX-Coup### and click Apply.
The line price should be decreased by $20.
24. Book the sales order.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 145
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 146
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 147
3.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 148
4.
y
l
n
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 149
O
e
5.
y
l
n
O
e
Now you have to create the Coupon Issue modifier (the actual coupon that the customer can
redeem).
Create the Coupon Issue Modifier line
6.
I
A
s
U
&
l
a
n
r
te
Note: When issuing coupons, the system generates coupon numbers based on the modifier
number. So the first coupon to be issued will be number XX-Coup### (where ### are the
generated numbers). The customer will quote the modifier number when redeeming the
coupon so it is important that the Modifier No enables you to recognize the type of coupon.
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 150
7.
y
l
n
(T) Coupons
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 151
y
l
n
Note: The Redemption Rate field (Coupons tab) is used in situations where it is necessary to
convert the value in the Benefit UOM field to the primary currency. For example, if one air
mile is 0.50 currency units, redemption rate is 0.50.
O
e
Although Expiration fields are not used in this practice they are useful for setting
redemption dates for the coupon. The pricing engine will take as a start date the first day a
coupon is issued. The pricing engine will then calculate the expiration end date using the
values entered for Expiration Period and Expiration Period Type (or Expiration Date only if
that was used).
I
A
8.
&
l
a
s
U
The coupon is only issued when the customer orders more than $1000. To enforce this, you
must create a qualifier for XX-Coup.
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 152
12. When you have completed your entries, click on the next qualifier line to enter a second
qualifier based on customer name:
Grouping Number = -1
Qualifier Context = Customer
Qualifier Attribute = Customer Name
Operator = =
Value From = XX-Big City Electronics (or if thats not available use the XXCustomer New--the customer you created earlier in the practice where XX are your
initials)
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 153
15.
y
l
n
O
e
I
A
s
U
16. Enter a Sales Order for XX-Big City Electronics. At the sales order line level enter item
AS54888 with a quantity that ensures the resulting sales order line amount is more than
$1000.
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 154
y
l
n
O
e
18. (B) Actions > View Adjustments. Confirm that a coupon has been issued:
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 155
y
l
n
In the Adjustments tab, you will see the coupon number (XX-Coup141) that was issued
based on your modifier XX-CoupD.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 156
y
l
n
The pricing engine has created additional qualifiers for the Discount modifier line to ensure
that the discount is only applied when one of the created coupon numbers is quoted.
O
e
s
U
20. Enter a new sales order for XX-Customer New. At the sales order line level, enter the item
eligible for the discount item AS54888. Enter a quantity that ensures the sales order line
amount is more than $2000.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 157
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 158
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 159
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 160
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 161
y
l
n
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 162
O
e
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 163
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 164
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 165
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 166
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 167
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 168
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 169
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 170
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Define the Point and Range Break Modifier Header Information
1.
2.
y
l
n
O
e
I
A
3.
4.
5.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
7.
Modifiers
Chapter 7 - Page 171
8.
Enter Controls:
Modifier Level: Line
Pricing Phase: Modifiers for BOOK Event
Bucket: Pricing Adjustments Bucket 1
Incompatibility: Blank
9.
Click Next to display the Create Price Break Line: Products page.
y
l
n
14. In the Benefits region, enter the following Price Break Line Benefits information. Click Add
Another Row to add each row.
Value From
Value To
O
e
Adjustment Value
s
U
Adjustment Method
I
A
100
Amount
101
400
50
Amount
401
700
100
701
999999
150
Amount
l&
Amount
a
n
r
15. Click Next to display Qualifiers page, but do not select any line qualifiers.
e
t
In
16. Click Next to review your entries in the Create Price Break Line: Review page.
17. Click Finish.
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 172
y
l
n
25. Click Next to display the Create Price Break Line: Benefits page.
O
e
26. In the Benefits region, enter the following Price Break Line Benefits information. Click Add
Another Row to add each row.
Value From
Value To
Adjustment Value
I
A
Adjustment Method
100
Percent
101
400
Percent
401
700
10
701
999999
15
l&
r
e
nt
na
s
U
Percent
Percent
27. Click Next to display Qualifiers page, but do not select any line qualifiers.
I
e
28. Click Next to review your entries in the Create Price Break Line: Review page.
l
c
a
r
O
30. Navigate to the Update Discount List: General Information page, and select the Active
check box to make the modifier active.
Modifiers
Chapter 7 - Page 173
32.
Ordered Item
Quantity
UOM
1.1
XX-Palm Pilot
400
Ea
$700.00 (Range)
2.1
XX- Pager
400
Ea
$700.00 (Point)
y
l
n
Note on Calculation:
The XX-Palm Pilot used the Range Point Break. The first 100 units receive a discount
of zero. The Modifier calculation is based on the applicable volume of 300 divided by
the quantity ordered (400). In other words X 50 = 37.50 discount per item
The XX-Pager used the Point Price Break. The calculation for the Pager simply applies
5% of the list price based on the order point of 400 or $35.00 per unit
O
e
&
l
a
I
A
s
U
35. Click Book Order. Book your order and note that since these modifiers are at the Book
pricing event, the unit prices will change at booking based on the calculations above:
XX-Palm Pilot $662.50
XX-Pager
$665.00
n
r
te
n
I
e
36. To view the adjustments, click Actions > View Adjustments for each list line:
l
c
a
37. Click OK. From the Adjustments window, click Related Details to view additional details
about how the price break was applied.
r
O
Modifiers
Chapter 7 - Page 174
(N) Oracle Pricing User > Home > Advanced Pricing Home page
y
l
n
O
e
I
A
&
l
a
s
U
3.
3.
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 175
4.
(B) Next.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 176
y
l
n
O
e
6.
I
A
(B) Apply.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 177
7.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 178
8.
9.
(B) Finish.
y
l
n
(B) Yes.
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 179
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 180
Define Controls
y
l
n
&
l
a
O
e
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 181
Define Products
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
Define Benefits
r
O
Modifiers
Chapter 7 - Page 182
Value From
Value To
Adjustment Value
100
Amount
101
400
50
Amount
401
700
100
Amount
701
999999
150
Amount
I
A
&
l
a
n
I
e
l
c
a
Modifiers
Chapter 7 - Page 183
O
e
s
U
n
r
te
r
O
y
l
n
Adjustment Method
22. Do not select any line qualifiers in the Create Price Break Line: Qualifiers page.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 184
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 185
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 186
Define Controls
y
l
n
&
l
a
O
e
I
A
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 187
Define Products
y
l
n
O
e
&
l
a
I
A
s
U
n
r
te
n
I
e
l
c
a
Define Benefits
r
O
35. Enter the following values in the Benefits page. Click Add Another Row to create each new
line:
Modifiers
Chapter 7 - Page 188
Value
From
Value To
Adjustment Value
Adjustment
Method
100
Percent
101
400
Percent
401
700
10
Percent
701
999999
15
Percent
36. (B) Next. Do not select any line qualifiers in the Create Price Break Line: Qualifiers page.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 189
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 190
y
l
n
O
e
41.
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 191
y
l
n
Ordered Item
Quantity
O
e
UOM
s
U
1.1
XX-Palm Pilot
400
Ea
$700.00 (Range)
2.1
XX- Pager
400
Ea
$700.00 (Point)
&
l
a
I
A
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 192
y
l
n
Note on Calculation:
O
e
The XX-Palm Pilot used the Range Point Break. The first 100 units receive a discount
of zero. The Modifier calculation is based on the applicable volume of 300 divided by
the quantity ordered (400). In other words X 50 = 37.50 discount per item
The XX-Pager used the Point Price Break. The calculation for the Pager simply applies
5% of the list price based on the order point of 400 or $35.00 per unit
&
l
a
I
A
s
U
44. (B)Book Order. Book your order and note that since these modifiers are at the Book pricing
event, the unit prices will change at booking based on the calculations above:
XX-Palm Pilot $662.50
XX-Pager
$665.00
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 193
y
l
n
45. To view the adjustments, click Actions > View Adjustments for each list line:
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 194
46. (B) OK. From the Adjustments window, click Related Details to view additional details
about how the price break was applied.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 195
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 196
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 197
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 198
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 199
Controls
y
l
n
O
e
s
U
Select Controls
Select Controls in the Controls page (HTML UI). These are set rules that can be used to
control how pricing applies actions. For example, effective dates can be used to control when
rules are in effect and when they are not.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 200
y
l
n
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 201
O
e
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 202
y
l
n
O
e
s
U
Pricing Controls
The pricing engine makes control selections from the top down. The engine processes each
pricing request in the following sequence:
1. Events from the calling application.
2. Phases for the specified events.
3. Selects appropriate lines for the phase.
4. Selects price list and modifiers that match qualifiers and pricing attributes rules.
5. Resolves incompatibility between price lists and modifier lists using precedence, best
price, or exclusivity.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 203
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 204
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 205
y
l
n
O
e
s
U
Seeded Phases
The following table outlines the seeded phases for pricing. All price lists are hard coded to be
automatically placed in the seeded phase sequence 0 which is the List Line Base Price. Price
lists cannot be assigned to any other phase.
Accessibility Description
The table describes the types of seeded phases, their names, and levels.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 206
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 207
Events
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 208
Events
y
l
n
O
e
s
U
Events
A pricing event is the point in a process at which the pricing engine is invoked. For example,
the following events in Order Management invoke the pricing engine: enter order line, book
order, and reprice order.
The above events are seeded lookup codes that integrate with Oracle Order Management (other
events are associated with different Oracle applications). Each event represents a point in the
order process flow at which the pricing engine is called to return a base price, price
adjustments, freight charges, promotions, benefits, etc. The following outlines the function
which calls each event:
Price Event: Called after user enters item, quality, and unit of measure
Line event: Called when the user exits the order line
Order event: Called when the user saves the order
Book event: Called when the user books the order
Ship event: Called by OM after the order is ship confirmed--when the field-shipped
quantity on the order line is updated with a value
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 209
Reprice line: An event which the user inserts into the workflow activity. It is seeded in
Pricing to occur after the order is shipped but before the order is invoiced. This event takes
place after the Ship event. Potentially, the user could set this up to run anytime during the
workflow.
Note
In this release it is not possible to create new pricing Events.
Reprice Line: This event always passes just one order line that is being worked on to the
engine. That means any order level/liner group kind of discounts cannot be given in this event.
Accessibility Description
The table describes the relationship between events and their actions.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 210
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 211
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 212
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 213
Event Phases
y
l
n
O
e
s
U
Event Phases
When a certain event occurs, a call is made to the pricing engine. All the phases that are
mapped to that event are executed at that time and returned to the requesting application. The
information returned by pricing can include base prices, price adjustments, promotions, or
freight charges depending on the event and the phases associated with that event.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 214
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 215
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 216
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 217
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 218
Controls: Buckets
y
l
n
O
e
s
U
Controls: Buckets
A bucket is a level introduced at each step of pricing. You assign different modifiers to various
bucket levels to create cascading price adjustments. The modifiers assigned at each bucket
level are applied on the resultant amount of the previous bucket.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 219
Controls: Buckets
y
l
n
O
e
s
U
Controls: Buckets
Consider an example where Vision Operations offers a 20-percent discount to its distributors.
It imposes a 10-percent surcharge on the order amount. If a distributor places an order for an
item priced $1,000, the price specified for the distributor is $800.
When the Surcharge modifier is assigned to a Level-2 bucket, the pricing engine first applies
the Level-1 bucket modifier (order total of $800) then applies the Level-2 bucket modifier
(10% surcharge on the $800 order so the distributor pays $880).
If both modifiers are contained within the same Level-1 bucket, the pricing engine applies each
modifier to the original base pricenot the discounted price. This is how the final order cost of
the single bucket use is calculated:
Level-1 bucket: Order amount ($1000) * Discount modifier (20%) = $800
Level-1 bucket: Surcharge modifier (10%) * order amount ($1000) = $100
Total of buckets = $900
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 220
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 221
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 222
Null Buckets
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 223
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 224
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 225
Controls: Incompatibility
y
l
n
O
e
s
U
Controls: Incompatibility
Incompatible modifiers are modifiers that you do not want a pricing engine to apply together to
an order. For example, Vision operations applies a 5-percent surcharge to distributors paying
after 30 days but it also offers a 10-percent discount to distributors who place an order amount
greater than $50,000. A distributor could be given either the surcharge or the discount if the
distributor pays after 30 days AND places an order more than $50,000.
To prevent the application of incompatible modifiers to an order, you assign incompatible
modifiers to different incompatibility levels. A pricing engine applies modifiers in a single
incompatibility level to an order.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 226
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 227
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 228
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 229
Exclusivity
y
l
n
O
e
s
U
Exclusivity
If a modifier is marked exclusive, a pricing engine ignores the precedence and the best price
and applied only the exclusive modifier. Pricing engine uses the Best Price method if there is
more than one modifier with the lowest precedence number. In these situations the pricing
engine selects the modifier that provides the best price to the customer.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 230
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 231
Best Price
y
l
n
O
e
s
U
Best Price
You can use the Best Price method to have the pricing engine select the modifier that provides
the best price to the customer.
Enter a numeric value in the Comparison Value field in the Modifier window for best price
resolution for Promotional Goods,Other Item Discount, Item Upgrade,Coupon Issue, and Term
Substitution.
Notes on Best price:
Can only be used when the monetary value is easily estimated
Cannot be used for price list lines
Cannot be used with the following order-level modifier list types:
Discount
Surcharge
Freight and Special Charges
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 232
Best Price
y
l
n
O
e
s
U
Best Price
If there is more than one modifier with the lowest precedence in an Incompatibility level, the
pricing engine Pricing engine uses the Best Price method if there is more than one modifier
with the lowest precedence number. In these situations the pricing engine selects the modifier
that provides the best price to the customer.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 233
Create Product
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 234
Define Product
y
l
n
O
e
s
U
Define Product
On the Product page (HTML UI), you can define the product to be evaluated for the benefit.
You can specify any pricing attributes or volume requirements (if applicable) for the product.
Depending on the modifier line type, the product and benefit information is set up on the same
page, or on separate pages (first the Product page, followed by the Benefit page). After
defining the product, you can define the benefit.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 235
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 236
Precedence Value
y
l
n
O
e
s
U
Precedence
Using precedence, a pricing engine applies the modifier with the highest precedence to a
pricing request. Precedence is the sequence in which a pricing engine retrieves modifiers. The
lower the numeric value, the higher its precedence.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 237
Precedence Number
y
l
n
O
e
s
U
Precedence Number
Precedence number is the value for Precedence that displays in the:
Define Modifier window (Forms-based UI)
Products page (HTML UI)
If a modifier is assigned the precedence number 200 and another modifier is assigned 50, then
the pricing engine applies the modifier with the precedence 50.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 238
Define Benefit
y
l
n
O
e
s
U
Define Benefit
After defining the product, you can define the benefit. Depending on the modifier line type, the
benefit may be set up in a single page or two separate pages (HTML UI).
This may be the discount or surcharge adjustment, free good products, or price break. After
defining the benefit, you have the option to add line qualifiers to the modifier by assigning
existing qualifier groups or adding qualifiers. On the last page of the flow, you can review all
your setup before saving the line.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 239
Adjustment Methods
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 240
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 241
Note: Not all modifier types can be applied to all levels. Refer to the Oracle Advanced Pricing
Implementation Manual for more information on the application methods that can be used with
various modifier levels.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 242
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 243
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 244
Limit Types
y
l
n
O
e
s
U
Limit Types
If the limit is defined as a hard limit, and the benefit amount exceeds the available
balance, the pricing engine will adjust the benefit amount on the transaction by the
remaining available balance at which time no further benefit is available to anyone.
If the limit is defined as a soft limit, and the benefit amount exceeds the available
balance, the pricing engine will apply the full amount of the benefit to the transaction but
indicate to the calling application that the benefit has been exceeded.
You will be able to specify whether it is a hard or soft limit by setting the profile QP: Limit
Exceed Action to either Hard Adjust Benefit Amount or Soft Full Benefit Amount.
This profile can be set at the user level.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 245
Hard Limit
y
l
n
O
e
s
U
Hard Limit
If the limit is defined as a hard limit, and the benefit amount exceeds the available balance,
the pricing engine will adjust the benefit amount on the transaction by the remaining available
balance at which time no further benefit is available to anyone.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 246
Soft Limit
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 247
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 248
Transaction Date
Source Application, e.g. Contract, Order Management, Order Capture etc.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 249
Limits: Exceptions
y
l
n
O
e
s
U
Limits: Exceptions
For a Modifier List to have a List limit, it must have at least one Modifier line for which a line
limit can be created.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 250
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Define the Modifier
y
l
n
You first must define the promotion by setting up the promotion modifier.
1.
2.
I
A
&
l
a
s
U
n
r
te
n
I
e
O
e
l
c
a
r
O
Grouping
Number
Qualifier
Context
Qualifier
Attribute
Modifier List
Price List
Operator
Value From
XX-Price List 1
Modifiers
Chapter 7 - Page 251
4.
Click OK.
5.
In the Modifiers Summary tab, enter the following modifier line information:
Modifier No = 1
Level = Order
Modifier Type = Discount
Start Date/End Date = Optional
Automatic = Selected
Pricing Phase = All Lines Adjustment
Note: The Override check box should not be selected for limits.
6.
7.
8.
9.
Enforced
Amount
Constraint 1
Context 1
Attribute 1
Usage
Across All
Transactions
Qualifier
Attribute
Customer
Customer
Name
Usage
Across All
Transactions
25
Qualifier
Attribute
Order
Request
Date
I
A
y
l
n
When
Exceeded
O
e
s
U
Hard-Adjust Benefit
Amount
Hard-Adjust Benefit
Amount
Enter a Sales Order Using the Discount Modifier With Promotional Limits
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 252
Ordered Item
Quantity
1.1
2.1
AS54888
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 253
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 254
y
l
n
O
e
Qualifier
Context
Qualifier
Attribute
Precedence
I
A
Defaults
&
l
a
s
U
Operator
=
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 255
Value From
XX-Price List 1
4.
(B) OK.
5.
y
l
n
O
e
I
A
6.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 256
7.
y
l
n
O
e
s
U
(B) List Limits (at the modifier list header). Enter the following limits:
Basis
Enforced
Usage
Usage
I
A
Amount
Constraint
1
Context 1
Across All
Transactions
Qualifier
Attribute
Customer
Customer
Name
Hard-Adjust
Benefit Amount
Across All
Transactions
25
Qualifier
Attribute
Order
Request
Date
Hard-Adjust
Benefit Amount
e
l
c
l&
e
t
In
a
n
r
Attribute 1
a
r
O
Modifiers
Chapter 7 - Page 257
When Exceeded
9.
y
l
n
O
e
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 258
y
l
n
O
e
Ordered Item
Quantity
1.1
2.1
AS54888
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 259
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 260
y
l
n
16. Repeat steps 11 to 14 to create a new order for the same customer. Because of the
promotional limits, the customer should not receive the 10% discount on this second order.
A customer can only get the discount once as defined in the limits setup. We also set a limit
of 25 total orders (one per customer) but we will not test that.
O
e
s
U
Note: Review the balances to confirm that each customer has consumed the limit.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 261
Summary
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 262
Summary
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 263
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Modifiers
Chapter 7 - Page 264
Attribute Management
Chapter 8
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 1
Attribute Management
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 2
Objectives
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 3
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 4
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 5
properties, or disable Attribute Mapping rules at various levels such as PTE-Attribute link level
or at Order at line level.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 6
Common Terms
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 7
Common Terms
y
l
n
O
e
s
U
Common Terms
A Pricing Transaction Entity (PTE) consists of a group of applications sharing the same setup
data. A Pricing Transaction Entity consists of multiple source systems and request types.
Note: Source systems can be shared between PTEs.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 8
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 9
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 10
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 11
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 12
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 13
y
l
n
O
e
Overview
I
A
s
U
A new entity has been created in Advanced Pricing called a Pricing Transaction Entity. A
Pricing Transaction Entity (PTE) is an ordering structure that has associated Request Types
and Source Systems. Different applications may have different request structures when they
make requests to the pricing engine. For example, Istore and Order Management can be part
of the Order Fulfillment PTE because they are both Order Fulfillment systems and share the
same setup data
&
l
a
n
r
te
Note: The QP: Pricing Transaction Entity profile option can be set at the site or application
level using the System Administrator responsibility. This profile options value indicates
the current Pricing Transaction Entity in use.
Only those contexts and attributes assigned to the current Pricing Transaction Entity will be
available in the list of values (LOVs) on the setup forms. Likewise, querying up setup data
(Price list lines, Modifiers, Qualifiers, etc.) will cause the description to be shown only for
those contexts and attributes that are assigned to the current Pricing Transaction Entity.
Therefore it is important to set this profile option to the right value before creating or
querying any setup data in the Pricing Application.
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 14
The QP: Pricing Transaction Entity profile is set to Order Fulfillment by default.
Therefore, for example, Logistics users must change this profile to point to Logistics
PTE so that they can look at the attributes that are linked to Logistics PTE.
This profile can be set at site or application level only and cannot be set at user level. The
value of this profile must be correctly set for applications that are different from Order
Management.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 15
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 16
All source systems belonging to the same PTE will return the same price and adjustments for
all request types.
Request Type
The Request Type identifies the type of transaction that is being priced. Different applications
make requests to the pricing engine. Request types of these applications may be different.
Some applications may share their request types.
For example: iStore and Order Capture share the same request type. On the other hand, Order
Management and iStore have different request structures.
Advanced Pricing provides seeded Pricing Transaction Entities (PTEs); however, you can
define additional PTEs.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 17
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 18
y
l
n
O
e
s
U
I
A
&
l
a
Accessibility Description
The graphic displays the Pricing Transaction Entity - Order Fulfillment.
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 19
y
l
n
O
e
I
A
s
U
View existing PTEs in the Pricing Transaction Entity Source System and Request Types
window.
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 20
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 21
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 22
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 23
behave the same way. All seeded attributes will have this flag selected so that all seeded
attributes will be available in the list of values (LOVs) of the setup windows.
If you select the mapping method as attribute mapping, then you must select the attribute
mapping enabled box. Otherwise, the mapping rule will not work properly.
The Attribute Mapping Status box will not be selected initially after you create the mapping
rule. It will only get selected if the attribute has been used in a pricing setup and you have run
the build attribute mapping rules program (which we will go into later).
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 24
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 25
The Pricing Transaction Entity that you created must also be attached to a new Request Type.
Without a new Request type, you cannot attach Attribute Mapping rules to that Pricing
Transaction Entity. In other words, a Pricing Transaction Entity without Request type cannot be
attribute mapped, because of the absence of Request types.
Note: This is not applicable to Basic Pricing where the Pricing Transaction Entity you just
created displays in the Pricing Transaction Entity LOV, as Attribute Mapping method is
User Entered whenever new PTE-Attributes links are created.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 26
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 27
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 28
What is a Context?
y
l
n
O
e
s
U
What is a Context?
Qualifier Contexts and its attributes can be used to create qualifiers that determine eligibility
for a modifier (who is eligible to receive the modifier). Qualifiers can be attached to price lists
(only in Advanced Pricing) and modifiers.
Product Contexts and its attributes define the product hierarchy and are related to product
information. For example, the product context Item may consist of attributes such as Item
Number and Item Category.
Note
Pricing Contexts are associated with pricing attributes. They further define eligibility for a
price list line or modifier. They can be used for a price list line, as a formula component, or in
Modifiers.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 29
Context Examples
y
l
n
Accessibility Description
The table describes the three Context Types and their names.
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 30
O
e
Understanding Contexts
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 31
Contexts
y
l
n
O
e
s
U
Contexts
Oracle Pricing Manager Responsibility
(N) Pricing > Setup > Attribute Management > Context and Attributes > Context Setup
Advanced Pricing
Contexts are a group of related pricing elements that can have attributes linked to them. Once
the context is defined, you can create its attributes. Attributes determine the specific values in
which you define pricing rules. For example, customer hierarchy can include pricing
characteristics such as customer name = Customer ABC.
Context/attribute combinations are available for use in the Pricing Setup windows once they
are created and linked to a specific Pricing Transaction Entity (PTE).
Code
Short name for a context. Once defined and saved , user can not modify it later.
Name
Name of a context. It will be displayed in the context LOVs available in
Qualifier/Modifier/formula screens. User can modify it if needed.
Description
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 32
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 33
Qualifier Contexts
y
l
n
O
e
s
U
Qualifier Contexts
Predefined (seeded) qualifier contexts and associated qualifier attributes that use Oracle
Application database tables as the data source wherever applicable are provided.
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. The following are common qualifier terms:
Qualifier Contexts
Qualifier contexts are flattened hierarchies where similar qualifying attributes can be grouped
into logical categories.
Qualifiers
Qualifiers are specific attributes that assist Oracle Advanced Pricing with limiting the who for
benefit or price eligibility.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 34
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 35
Product Contexts
y
l
n
O
e
s
U
Product Contexts
Product Contexts and its attributes define the product hierarchy and are related to product
information. For example, the product context Item may consist of attributes such as Item
Number and Item Category.
Warning
You cannot add new contexts of Product Context type. However, you can add attributes to the
existing Product Context Item.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 36
Pricing Contexts
y
l
n
O
e
s
U
Pricing Contexts
Pricing Contexts are associated with pricing attributes. They further define eligibility for a
price list line or modifier. They can be used for a price list line, as a formula component, or in
modifiers.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 37
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 38
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 39
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 40
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 41
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 42
Pricing Attributes
y
l
n
O
e
s
U
Pricing Attributes
Pricing attributes control what is being priced or modified on a price list or modifier list.
Creating Context and Attributes to be used for Pricing Setup Windows
Contexts are a group of related pricing elements that can have attributes linked to them. Once
the context is defined, you can create its attributes. Attributes determine the specific values in
which you define pricing rules. For example, customer hierarchy can include pricing
characteristics such as customer name = Customer ABC.
Creating Contexts
In Attribute Management, you can set up three types of contexts:
Qualifier Contexts and its attributes can be used to create qualifiers that determine
eligibility for a modifier (who is eligible to receive the modifier). Qualifiers can be attached
to price lists (only in Advanced Pricing) and modifiers.
Product Contexts and its attributes define the product hierarchy and are related to product
information. For example, the product context Item may consist of attributes such as Item
Number and Item Category. You cannot add new contexts of Product Context type.
However, you can add attributes to the existing Product Context Item.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 43
Pricing Contexts are associated with pricing attributes. They further define eligibility for a
price list line or modifier. They can be used for a price list line, as a formula component, or
in Modifiers.
For example, a product context such as Item can be further categorized by attributes such as
Item Name and Item Number while a qualifier context such as Customer can consist of
attributes such Customer Name and Customer ID.
Creating Attributes
The pricing engine evaluates attributes during engine run time to determine which price lists
and modifiers are eligible for the transaction. Attribute values can be derived at the order level,
line level, or for both order and line levels.
You must create all new attributes using the Attribute Management setup windows. Oracle
Pricing Manager Responsibility > Setup > Attribute Management > Context and Attributes.
With the Attribute Management feature, you can define attributes for a given context,
determine how they are sourced, decide which attributes can be selected from a list in the
Pricing Setup windows, and determine which ones are used in promotional limits.
Pricing Attributes
The following are examples of pricing attributes used to specify conditions of a product or
service that affects the price:
Product ID = HMO Plan 15; Pricing Attribute = State = Connecticut; List Price = $200.00
per month.
Product = HMO Plan 15; Pricing Attribute = State = New York; List Price = $250.00 per
month.
Product ID = Motor Oil; Pricing Attribute = Grade = Regular; List Price = $3.50 per Quart
Product ID = Motor Oil; Pricing Attribute = Grade = Premium; List Price = $4.25 per quart
Product ID = Usage Charge; Pricing Attribute = Time of Day = Evening (7:00pm to
11:00pm); list price =.08 per minute
Product ID = Usage Charge; Pricing Attribute = Time of Day = Late night (6:00am to
5:30am) list price =.05 per minute
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 44
Pricing Attributes
y
l
n
O
e
s
U
Pricing Attributes
Order Management Super User Responsibility
(N) Pricing > Price Lists > Price List Setup (T) List Lines (B) Pricing Attributes
1.
Choose Pricing Attributes in the List Lines tab to display the Pricing Attributes window.
2.
Enter a pricing context.
3. Enter a pricing attribute.
4. Select = or BETWEEN for Operator.
5.
Enter Value From.
6.
If the Operator is BETWEEN, enter Value To.
Note: The pricing attributes are joined as AND conditions since they apply to one price list
line.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 45
These new qualifier contexts and attributes can be used to create qualifier groups. The
qualifying groups can used to determine who qualifies for certain pricelists and discounts.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
I
A
Tasks
Define a New Qualifier Context
&
l
a
y
l
n
O
e
s
U
n
r
te
1.
2.
3.
Enter QPPM-PA in the Code field. This is the short name for the context.
Once it has been saved, it cannot be changed.
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 46
4.
5.
Topic
Name
Description
When you have completed your entries for the context, you can enter information to create the
attribute.
Creating a New Pricing Attribute
6.
In the Attributes region of the Context Setup window, enter the following information:
Field Name
Topic
Code
QPPM
Name
QPXXs Age
Precedence
300
Application Name
Oracle Pricing
Column Mapped
PRICING_ATTRIBUTES35
y
l
n
Value Set
Datatype
7.
O
e
s
U
The columns PRICING_ATTRIBUTES1 through 30 of each context are reserved for seeded
pricing attributes. You can select from PRICING_ATTRIBUTES31 through 100.
I
A
8.
Select the Value Set QP: Number to define a value set for the attribute. In this field, you can
define a new value set or use an existing value set.
9.
&
l
a
n
r
te
You can create additional attributes for a context. In the Attributes region, tab to the second row
to create a second attribute for this qualifier context.
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 47
y
l
n
O
e
I
A
2.
&
l
a
n
r
te
s
U
e
l
c
Type
Code
a
r
O
Name
In
Value
Pricing Context
QPPM-PA
QPPMs Pricing Context
Description
Enabled box
Selected
Copyright Oracle Corporation, 2004. All rights reserved.
Attribute Management
Chapter 8 - Page 48
y
l
n
In the Attributes region of the Context Setup window, enter the following information:
Field Name
O
e
Topic
Code
QPPM
Name
QPXXs Age
I
A
s
U
Note: The XX in QPXX represents your initials. Type your initials in the place of the XX.
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 49
4.
Enter a Precedence value such as 300. This decides the processing sequence of qualifier
attributes. For Pricing Attributes, this value is not taken into consideration.
5.
Select Oracle Pricing (the default) as the Application Name. This identifies the name of the
application creating this attribute.
6.
y
l
n
I
A
O
e
s
U
The columns PRICING_ATTRIBUTES1 through 30 of each context are reserved for seeded
pricing attributes. You can select from PRICING_ATTRIBUTES31 through 100.
7.
&
l
a
The value set define the values that can be used for the selected attribute such as the
maximum number of In this case, numbers. You can view additional information or create a
new value set by clicking the Value Sets button.
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 50
Since the Validation Type for QPXXs Age value set is set to None, values are not required.
By entering a minimum and maximum value in the QPXXs Age value set, you determine
that the age must fall between 0 and 110 years.
8.
9.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 51
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 52
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 53
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 54
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 55
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 56
All seeded attributes will have this check box selected so that all seeded attributes will be
available in the LOVs of the setup windows.
If you select the mapping method as Attribute Mapping, then you should select the Attribute
Mapping Enabled box. Otherwise, the mapping rule will not work properly.
The Attribute Mapping Status check box will not be selected initially after you create the
mapping rule. It will only get selected if the attribute has been used in a pricing setup and you
have run the build attribute mapping rules program.
Note: If the attribute is not assigned, it will not be available in pricing setups
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 57
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 58
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 59
Attribute Levels
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 60
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 61
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 62
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 63
In this guided practice you will link the attribute created to an existing PTE and assign an
attribute mapping method to the attribute.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
y
l
n
Tasks
Link the Attribute to a PTE
O
e
s
U
1.
2.
3.
In the Context Type field, select Pricing to display the contexts defined for the Pricing
Context Type. If the context is currently assigned to the Order Fulfillment PTE, then the
Assigned to PTE box will be selected.
4.
Find the context you created by searching the Code column in the Contexts region.
Seeded contexts will have the seeded box selected.
5.
Select the Enabled box so that the context displays in the list of values for pricing setups.
6.
Select the context from the Contexts region in the Pricing Transaction Entity-Attribute
Linking window.
7.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Click the Link Attributes button to display the Link Attributes window. In this window, you
can link this attribute to the Pricing Transaction Entity: Order Fulfillment.
Attribute Management
Chapter 8 - Page 64
9.
Select the Level for the attribute. A Level is used to selectively display pricing attributes and
qualifiers in the list of values from the pricing setup windows.
Attributes can be set at the LINE, ORDER or BOTH levels. Select LINE.
10. Select ATTRIBUTE MAPPING as the Attribute Mapping Method. The choices for attribute
mapping are: USER ENTERED, CUSTOM SOURCED, ATTRIBUTE MAPPING, and
RUNTIME SOURCED (this should only be selected for accumulation attributes).
y
l
n
O
e
12. Select Use in Limits box if you want this attribute to show up in the Attribute list of values
in the Limits setup window.
s
U
The following steps apply if ATTRIBUTE MAPPING is selected as the Attribute Mapping
Method:
I
A
13. Select the Attribute Mapping Enabled box if you want this attribute to be mapped.
&
l
a
The Attribute Mapping Status box is selected automatically by the Build Mapping Rules
program which generates the Build Context API for mapping. The Build Mapping Rules
program must be run after you have completed attribute mapping.
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 65
y
l
n
O
e
I
A
&
l
a
s
U
2.
3.
In the Context Type field, select Pricing to display the contexts defined for the Pricing
Context Type. Contexts currently assigned to the Order Fulfillment PTE will have the
Assigned to PTE box selected.
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 66
4.
y
l
n
The Assigned to PTE box will be selected automatically once the attribute has been
successfully created and mapped (the mapping process is required only for attributes that
have ATTRIBUTE MAPPING in the Attribute Mapping Method field).
O
e
5.
6.
I
A
s
U
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 67
7.
8.
Value
LOV Enabled
Selected
Use in Limits
Selected
Selected
Column Mapped
PRICING_ATTRIBUTE58
Cleared
y
l
n
(I) Save.
O
e
I
A
s
U
Attribute Mapping is required because ATTRIBUTE MAPPING has been selected for this
attribute. If USER ENTERED or CUSTOM SOURCED had been selected as the attribute
mapping method, then attribute mapping would not be required and the attribute would be
ready for use in the pricing setup windows.
9.
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 68
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 69
y
l
n
O
e
I
A
s
U
Attributes Mapping is a mandatory step before any pricing element is used by the pricing
engine. The pricing engine also provides flexibility that a transaction area can define the
attributes mapping specific for its use.
&
l
a
n
r
te
After linking the context/attribute combination, you must select an attribute mapping method
that determines how the attribute is sourced:
Select one of the following Attribute Mapping Methods to determine how the attribute is
mapped:
Attribute Mapping: If this is selected, attribute mapping is required.
Custom Sourced: User provides a code
Runtime Sourced: Sourced in the pricing engine by a Custom API. This is used to source
an accumulation attribute at runtime. During accumulated range break calculations, the
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 70
pricing engine calls the Runtime Sourcing API to acquire an accumulation value for the
accumulation attribute
User Entered: Attribute value is entered by user, therefore attribute mapping is not required
If you select User Entered or Custom Sourcing as the Attribute Mapping Method, you
have finished assigning the attribute. You can now use it in a pricing setup
Note: You will not have to run the Build Attribute Mapping rules program for User entered or
Custom sourced attributes.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 71
Attribute Mapping
y
l
n
O
e
s
U
Attribute Mapping
Complete your entries, if Attribute Mapping is selected as the Attribute Mapping Method then
click the Attribute Mapping button to define the Attribute Mapping rules for the selected
attribute.
If Custom Sourced, Runtime Sourced, or User Entered is the Attribute Mapping Method, then
the process is complete-- you do not have to run the Build Attribute Mapping rules program for
these attributes.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 72
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
6. Click Attribute Mapping to display the Attribute Mapping window: Context, Attribute are
display-only fields.
n
I
e
l
c
a
8. Enter information in Header Level or Line Level region, or both the regions, depending on
the Level of the attribute in the previous window.
r
O
The Global structure/view name is already displayed for that Request type chosen.
9. Select the user source type from LOV.
10. Enter a User Value String.
Copyright Oracle Corporation, 2004. All rights reserved.
Attribute Management
Chapter 8 - Page 73
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 74
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 75
PL/SQL API: Attribute can be sourced directly from a global structure defined for the
given source system. The following flexfield window will pop up. For OM all the
record structures are defined in the package OE_ORDER_PUB. For example , if you
want to use payment term id as the source value for the new segment that you have
defined , enter G_LINE.payment_term_id in the function name. You have two record
structures available. OE_ORDER_PUB.G_LINE contains all the possible values of a
sales order line. OE_ORDER_PUB.G_HDR contains Fields from Order headers.
Structure of the Line_rec_type and header_rec_type can be obtained from the
Manufacturing Open Interface Manual. (For IStore/OC the equivalent global structures
are defined in the package ASO_PRICING_INT.
PL/SQL API Multi-Record: You can write a custom API (must be a function) that
returns multiple values. The output of your function can only be a table of
VARCHAR2s: for example, to get the inventory categories for an item. The flexfield
window above displays. For more information, see seeded sourcing for Item Categories
or customer class as an example of multi-Value pl/sql API.
Package: Enter the PL/SQL package name.
Function: Enter the function name.
Constant Value: Constant: Enter a constant value that will always
be mapped to this attribute for the given condition.
System Variable: Enter the system variable that will be mapped to
the attribute for the given condition such as SYSDATE.
Seeded Source type: It will have value if the record is seeded. This field is protected against
update. If user wants to modify seeded mapping, user can enter data into corresponding
user field (user source type).
Value String (user and seeded): It is a value of the source type. Seeded value string will
have seeded value. This field is protected against update. If user wants to modify seeded
mapping, user can enter data into corresponding user field (user value string).
Seeded: This is a non-navigable field indicating, whether the mapping rule is seeded or not.
Line level region
You can enter data here if the level ( defined in assign attribute form ) of the attribute is
Line or Both . This region will be grayed out if the Segment level in the previous screen is
Order. Rest of the fields are the same as the Header level region.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 76
In this guided practice, you will use attribute mapping to map the attribute QPPM and
then run the Build Attribute Mapping Rules program.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
I
A
&
l
a
O
e
s
U
1.
2.
3.
4.
Click the Link Attributes button to display the Link Attributes window.
5.
6.
y
l
n
n
r
te
n
I
e
l
c
a
r
O
Ensure that ATTRIBUTE MAPPING is selected in the Attribute Mapping Method field and
that the checkbox for the following fields is selected: LOV Enabled, Use in Limits, and
Attribute Mapping Enabled.
Attribute Management
Chapter 8 - Page 77
7.
Click the Attribute Mapping button to display the Attribute Mapping window.
8.
The Attribute Mapping Status box is automatically selected once the Build Attribute
Mapping Rules program which generates the Build_Contexts API for mapping runs
successfully.
In this window, you can define the attribute mapping rule for each request type listed in
the Request Types region.
Enter Oracle Pricing in the Application name field for the ONT Request Type.
The Application Name indicates the application creating the attribute mapping rule.
Now you will define the attribute mapping rule for the ONT request type.
Since the Level for this attribute is Both, fields in the Header Level and Line Levels
regions are enabled.
For seeded attributes, you can view the Source Type and Value String in the Seeded
fields. To change the seeded attribute mapping rules, enter data in the corresponding
User fields.
y
l
n
O
e
I
A
s
U
Note: The following warning message may appear: Warning You must source this
Attribute for all the Request types.
&
l
a
This message appears if attribute mapping rules have not been defined for all the request
types in the Request Types region. Defining attribute mapping rules for all requesting types
ensures that all the requesting applications that look at the same set of data receives the same
price.
n
r
te
n
I
e
13. Once you have completed your entries, save your work.
l
c
a
r
O
For improved system performance, it is recommended that you run the Build Attribute Mapping
Rules concurrent program after you define your mapping rules (although it is not mandatory,
since dynamic attribute mapping is supported). Running the Build Attribute Mapping Rules
program generates the mapping rules for attributes with the following conditions: 1) Attribute
Copyright Oracle Corporation, 2004. All rights reserved.
Attribute Management
Chapter 8 - Page 78
Mapping Enabled box is selected and 2) ATTRIBUTE MAPPING is selected as the Attribute
Mapping Method.
14. To run the Build Attribute Mapping Rules program, select Build Attribute Mapping Rules
from the Tools menu.
A Message box appears to indicate that the attribute mapping was successful.
The Assigned to PTE box is selected in the Pricing Transaction Entity-Contexts window
because the attributes and properties are now linked to the Pricing Transaction EntityOrder Fulfillment.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 79
(N) Setup > Attribute Management > Attribute Linking and Mapping
y
l
n
O
e
I
A
2.
3.
&
l
a
s
U
n
r
te
n
I
e
l
c
a
Contexts region:
Select Code = QPPM-PA
r
O
Attribute Management
Chapter 8 - Page 80
4.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 81
5.
Ensure that ATTRIBUTE MAPPING is selected in the Attribute Mapping Method field and
that the checkbox for the following fields is selected: LOV Enabled, Use in Limits, and
Attribute Mapping Enabled.
6.
The Attribute Mapping Status box is automatically selected once the Build Attribute
Mapping Rules program which generates the Build_Contexts API for mapping runs
successfully.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 82
7.
y
l
n
O
e
This indicates that Oracle Pricing is the application creating the attribute mapping rule. You
can then define the attribute mapping rule for the ONT request type.
I
A
s
U
Since the Level for this attribute is Both, the Header Level and Line Levels regions are
enabled:
Header Level:
User Source Type = PL/SQL API
User Value String = QP_SOURCING_API_PUB.
&
l
a
n
r
te
For seeded attributes, you can view the Source Type and Value String in the Seeded fields.
To change the seeded attribute mapping rules, enter data in the corresponding User fields.
n
I
e
Line Level:
User Source Type = PL/SQL API.
User Value String = B.G.HDR.sold_to_org_id
l
c
a
r
O
Attribute Management
Chapter 8 - Page 83
y
l
n
Note: If the following message displays if attribute mapping rules have not been defined for
all the request types in the Request Types region. Defining attribute mapping rules for all
requesting types ensures that all the requesting applications that look at the same set of data
receives the same price.
O
e
I
A
&
l
a
s
U
n
r
te
10. Once you have completed your entries, save your work.
n
I
e
l
c
a
For improved system performance, it is recommended that you run the Build Attribute Mapping
Rules concurrent program after you define your mapping rules (although it is not mandatory,
since dynamic attribute mapping is supported).
r
O
Attribute Management
Chapter 8 - Page 84
The Build Attribute Mapping Rules program generates mapping rules only for attributes with the
Attribute Mapping Enabled box selected and ATTRIBUTE MAPPING selected as the Attribute
Mapping Method.
11. (M) Tools >Build Attribute Mapping Rules
y
l
n
O
e
I
A
s
U
After the program has run, a Message box confirms if the attribute mapping was successful.
&
l
a
The Assigned to PTE box is selected in the Pricing Transaction Entity-Contexts window
because the attributes and properties are now linked to the Pricing Transaction EntityOrder Fulfillment.
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 85
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 86
y
l
n
O
e
I
A
s
U
The Build Attribute Mapping Rules program will map 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 will map the attributes that are used
in both the active and inactive setup.
&
l
a
The program Build Attribute Mapping Rules dynamically generates the package
QP_BUILD_SOURCING_PVT, which contains attribute mapping calls to build attribute
mapping rules for Attributes. The package QP_BUILD_SOURCING_PVT is generated when
the concurrent program is run. This package contains only the rules of used attributes
(Qualifiers/Pricing Attributes used in any pricing setup) that can be mapped at run-time. This
means anytime you use a new attribute (one that has not been used by any other modifier, price
list, formula), you will need to run the program Build Attribute Mapping Rules accessible in
the Oracle Pricing Manager Responsibility or from the Tools Menu of the Attribute Linking
and Mapping windows. Also anytime you change any attribute mapping rules you will need to
run this program.
n
r
te
n
I
e
l
c
a
r
O
The program generates the attribute mapping rules for all the attributes that have the Attribute
Mapping Enabled box selected. When the Build Attribute Mapping Rules program runs
Copyright Oracle Corporation, 2004. All rights reserved.
Attribute Management
Chapter 8 - Page 87
successfully, the Attribute Mapping Status is checked for those attributes for which an attribute
mapping rule is generated.
The Build Attribute Mapping Rules reports back success or failure to the user. If the Attribute
Mapping Status box changes to selected status for the attributes that were successfully mapped
then it was successful. The window automatically re-queries the database if the Build Attribute
Mapping Rules process is successful and moves focus to the Attribute Mapping Status box.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 88
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 89
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 90
Restoring Defaults
y
l
n
O
e
s
U
Restoring Defaults
The Restore Defaults button replaces values with their original seeded values.
Sourcing Rules
For all seeded sourcing rules, Restore Defaults button will restore back the seeded Source type
and the seeded Value string as User source type and User value string respectively. If the
seeded Source type and the seeded Value string are same as user Source type and user Value
string, the Restore Defaults button will be grayed out.
You can restore the default seeded settings in the following windows:
Context Setup
Link Attributes
Context Setup
Contexts
For contexts, the Restore Default button restores the context to the original seeded values. So
even if a seeded context has been changed, the values are restored to their original condition.
The Name and Description fields display the seeded values rather than the user-entered values.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 91
For seeded contexts, the Name and Description fields display their seeded values. However if
these seeded values are changed, these fields show the user-entered values and the seeded
values will be preserved in seeded name, seeded description fields respectively. These seeded
fields will always be hidden.
Attributes
For attributes, the Restore Default button restores the original seeded values. So if a seeded
attribute has been changed, the values can be restored to their original condition. Precedence,
name, valueset, datatype window fields display the seeded values in place of user entered
values.
For seeded attributes, the precedence, name, valueset, and datatype fields display their seeded
values. However, if you change the seeded values, these fields display the user-entered values
and the seeded values will be preserved in separate fields named as seeded precedence, seeded
name, seeded valueset, seeded datatype. These seeded fields will always be hidden.
Link Attributes
For seeded attributes, the Attribute Mapping Method column displays the seeded value of the
attribute. However, if you change the attribute mapping method, this field displays the userentered value; the seeded value will be preserved in a separate field named as seeded Attribute
Mapping Method. This seeded Attribute Mapping Method field will always be hidden.
The Restore Default button restores the original seeded attribute mapping method for an
attribute. If you overwrite a seeded attribute and later want to restore the original seeded
values, click the Restore Default button to restore the seeded values.
This button will be grayed out for non-seeded attributes. However, the button remains 'grayed
out' for seeded attributes, if the user-entered Attribute Mapping method is the same as the
seeded Attribute Mapping method.
Attribute Mapping
For all seeded Attribute Mapping rules, the Restore Defaults button restores the seeded Source
type and the seeded Value string as User source type and User value string respectively. If the
seeded Source type and the seeded Value string are same as user Source type and user Value
string, the Restore Defaults button will be grayed out.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 92
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 93
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 94
If you do not want to differentiate between applications or prevent update of modifiers created
by different applications, then no specific setup is required. In this case, all modifiers are
created with same value for source system code (assuming the value of this profile is set only
at site level by default or same value if set for all applications which create modifiers).
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 95
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 96
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 97
The default value should only be changed if the source of the pricing data is any application
other than Oracle Advanced Pricing. Set this to the source system lookup code of the
application which is interfacing the pricing data.
After Attribute Mapping Manger is installed, this profile can be set at Site, Application and
User level. The default value for this profile at the time of installation at the Site level is Oracle
Pricing. The seeded value of this profile for various applications is shown in the table below:
Application Name
Default Value
Site Level Profile Value
Oracle Pricing (QP)
Oracle Transportation (FTE)
Oracle Transportation (FTE)
Oracle Inventory (INV)
Oracle Inventory (INV)
Oracle Marketing (AMS)
Oracle Marketing (AMS)
All other Applications
Defaulted from Site
Note: Set the QP: Source System Code Profile to the source system lookup code of the
application from which the QP Setup or other application setup windows are called.
Values
QP: Oracle Pricing (and other source system lookup codes of related applications).
This profile option can be updated at the site and responsibility levels.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 98
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 99
The default value should only be changed if the source of the pricing data is any application
other than Oracle Advanced Pricing. Set this to the source system lookup code of the
application which is interfacing the pricing data.
After Attribute Mapping Manger is installed, this profile can be set at Site, Application and
User level. The default value for this profile at the time of installation at the Site level is Oracle
Pricing. The seeded value of this profile for various applications is shown in the table below:
Application Name
Default Value
Site Level Profile Value
Oracle Pricing (QP)
Oracle Transportation (FTE)
Oracle Transportation (FTE)
Oracle Inventory (INV)
Oracle Inventory (INV)
Oracle Marketing (AMS)
Oracle Marketing (AMS)
All other Applications
Defaulted from Site
Note: Set the QP: Source System Code Profile to the source system lookup code of the
application from which the QP Setup or other application setup windows are called.
Values
QP: Oracle Pricing (and other source system lookup codes of related applications).
This profile option can be updated at the site and responsibility levels.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 100
Summary
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 101
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Attribute Management
Chapter 8 - Page 102
Diagnostics and
Troubleshooting
Chapter 9
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Objectives
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
5. The pricing request information can then be viewed by querying the request in the Pricing
Engine Request Viewer from the OM Sales Order Pad or through the Pricing Manager
responsibility menu.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
s
U
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Agenda
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
Summary
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O