Professional Documents
Culture Documents
OM Freight Caln
OM Freight Caln
ii
EXECUTIVE SUMMARY
Businesses that charge their customers for freight and other special charges often
need to calculate those charges in a variety of ways. Oracle Advanced Pricing
provides the functionality and the flexibility to tailor the calculation of freight and
special charges to specific business needs.
INTRODUCTION
This paper steps the reader through setting up freight charges as both a lump sum
based upon a range of total order amounts, and also as a percentage of the order
amount. This paper is written for the 11i.8 version of Advanced Pricing. The
functionality is the same in earlier versions, the navigation and setup forms are
different.
BUSINESS SCENARIO
An enterprise charges its customer for freight based on a tier, a flat rate lump sum
for certain amount tiers, followed by a percentage of order amount above a certain
tier.
Example:
Order Amount (in dollars, currency unit is immaterial)
Freight Charge
1
100
15
101 200
20
201 300
25
over
300
6 % of order amount
Functional Issue
Oracle Advanced Pricing only supports Lumpsum order level freight charges.
Solution Background
Define a Pricing Attribute for Order Amount, create a pricing formula with the
formula 1 * 2 where 1 is the pricing attribute Order Amount and 2 is the numeric
constant (0.06 in this example). Since there is a seeded Qualifier Attribute for
Order Amount, the following steps will outline how to copy the existing mapping
rules to create the pricing attribute and formula:
Attribute Management
Using Attribute Management, locate the attribute mapping for the qualifier context
Volume, attribute Order Amount.
Copy the Pl/SQL API information from the Qualifier attribute to the
Pricing Attribute
Select the User Value String for the header level, and Ctrl-C to copy
Click on your new code, and click the button Link Attributes.
Enter Oracle Pricing as the application name for request type ONT
(you will need to map the other entities as well if you wish to use this
attribute in Contracts or Quoting, etc.) Select Header Level, User
Source Type (if you are mapping an attribute for Order or Both), and
paste the User Value String from earlier. Return to the mapping form
for the qualifier context Order Amount, and repeat the steps, copying
to the Line Level value string (if you are mapping a qualifier for Line or
Both).
This creates the Attribute Mapping for your new Pricing Attribute of
Order Amount. After you use this attribute in a modifier or formula, you
will have to run the Build Attribute Mapping Rules concurrent program,
detailed later in this procedure.
Give your formula a name, description and effective dates (if desired)
Enter the formula as NVL ((1*2),3). Using NVL (Null Value) ensures that
if for some reason the pricing engine encounters a null value in one of the
formula steps, it will return a value, not an error. In this example, factor 3 is
a numeric constant, value 0.
Formula Line 3, Type Numeric Constant. This is the value you want
returned if the pricing engine encounters a Null value. In this example we
chose zero (0)
Define Modifier
Click on Qualifiers to assign any list level qualifiers, if desired (e.g. specific
customers, customer classes, order types)
Assign a line number, or accept the default. This modifier will assign a
lump sum freight charge of 15 for order amounts from 1 to 100
Level: Order
Repeat this process for the other lines that are a lump sum for an amount
range, as illustrated in the business example above.
Create a line for the percent based freight repeat setup steps from above
until you click on the Discounts and Charges tab. Choose your Charge
name.
Application Lumpsum
Click OK.
There are two ways to run this program, via Reports, Single Request, or
from the Tools menu in the Attribute Mapping form.
A WORD OF CAUTION
In the 11.5.8 release (Family Pack H) and earlier, this method may produce
undesired results if an order line is split, or order lines do not ship together. Until
this issue is resolved by development, this method works best with an order type
which has Header Level Invoicing.
CONCLUSION