This chapter provides an overview of Enterprise Pricer implementation and discusses how to:
(Optional) Set up Enterprise Pricer.
Establish pricing options.
The following diagram provides an overview of the pricing setup tasks that includes the Enterprise Pricer setup process and defining the price-by keys, price list fields, pricing variables and the pricing dates.
Overview of Pricing setup tasks
The setup for Enterprise Pricer is separated into two parts: performing setup tasks and establishing pricing options. Setup tasks involve configuring the pricing features available in your pricing implementation. It may also be used by developers and others who intend to customize the Enterprise Pricer module by adding price-by fields to the list of delivered fields or by adding transactions to be priced. Pricing options are tasks performed to initially configure your system to establish pricing variables, fields you will use to perform your pricing, dates to be used in mathematical equations, and fields to use as Price List business objects.
Note. The general Enterprise Pricer user should not have access to the setup pages. These pages are available to the Enterprise Pricer developer to modify the Enterprise Pricer system data and to modify the pricing features available to the users. You can configure the Enterprise Pricer data entry pages and restrict which price-by fields are available to the general Enterprise Pricer user, but this is not required for a standard implementation of Enterprise Pricer. The system data described in this chapter are delivered for each pricing transaction implementation.
Setup Tasks
A predetermined set of price-by key fields and price list fields are delivered as part of the standard pricing implementation, but the person administering Enterprise Pricer should know that these areas are available for customizations. If a new pricing key is added, the developer must also customize both online and batch pricing to use the new key. In general, these pages are not accessed; however, it is important that you understand how these pages are used to create a pricing structure. Setup tasks, such as expanding the list of price-by keys or expanding the list of price list fields, are considerably more complex. Only a knowledgeable PeopleSoft application developer or information technology person should perform these tasks.
The implementation options are:
Set up Price-by Keys: The All Price-by Key Fieldnames page contains the standard list of available fields that are used when defining price rule conditions at the line level.
All delivered price-by keys are available at implementation. Here you can add fields that are considered for price list determination and price rule creation.
Set up Transaction Code Options: The options for each transaction are delivered as system data and appear on the online pricing pages.
They also determine how Enterprise Pricer prices each transaction. Changes to these pages are considered a customization and are not supported by PeopleSoft.
Warning! The Enterprise Pricer application is delivered with standard setup data for the supported applications. Any changes made to the standard delivered data, or customer created pricing variables and dates, and custom mathematical expressions created by the customer are considered system customization and are not supported.
The basic setup options task are:
Set up system pricing keys on the All Price-by Fieldnames page.
This defines the list of record fields that are used by the system.
Set up the application on the Price Transaction Code page.
This sets up the options for the application by defining the acceptable transaction codes.
Set up the price-by keys for the application using the Transaction Price-By Keys page.
This identifies the price-by keys used by the application when defining price lists and price rules.
Note. If a price-by field is currently assigned to a price rule or an arbitration plan, you cannot remove it from the list of values assigned to the pricing transaction.
Set up the pricing dates for the application on the Pricing Variables page.
This defines the pricing date variables used in the creation of price rules and arbitration plans. The dates are used to create breaks on the formula and select price lists.
Set up the pricing variables for the application on the Pricing Dates page.
This defines the pricing variables used for price formulas when creating price rules. The Pricing Variables page is used to establish the variables to use for calculating the net price using mathematical expressions.
This section provides an overview of transaction code options and discusses how to:
Set up price-by key fields.
Set up transaction code options.
Note. If you are not modifying standard setup data in PeopleSoft Enterprise Pricer, you do not need to complete the tasks discussed in this section. You can continue to the next implementation step. Adding or deleting price-by fields to the standard setup data is considered a customization and is not supported.
The options for each transaction are delivered as system data and appear in the online pricing pages. They also determine how PeopleSoft Enterpriser Pricer is used to price each transaction. You can customize your pricing definition by selecting the appropriate pricing actions for your organization. This table lists the setup options available for each transaction:
Differences in Pricing Methods Between PeopleSoft CRM and PeopleSoft SCM
In addition to the options defined for each transaction code that defines how Enterprise Pricer prices the transaction, PeopleSoft SCM and PeopleSoft CRM use the system differently. We discuss these differences so that you can determine the best method to use for pricing.
PeopleSoft CRM uses the recurring and frequency flags when defining the price list.
CRM use product notes on the price list. These options are not available in PeopleSoft SCM.
In PeopleSoft CRM, the order capture transaction code appears by default.
In PeopleSoft SCM, you can choose the transaction code when you are setting up a price rule, price list, or arbitration plan.
Discounts in PeopleSoft CRM are only off-invoice.
PeopleSoft SCM uses off-invoice and bill-back adjustments.
PeopleSoft CRM does not use payment terms and distribution accounting when pricing transactions.
PeopleSoft CRM uses the Lookup in Priority Order option and PeopleSoft SCM uses the Consider All Prices Price List Lookup option.
Page Name |
Definition Name |
Navigation |
Usage |
EOEP_KEYFLDS |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, All Price-by Key Fieldnames |
Set up price-by key fields for all Enterprise Pricer implementations. These values are delivered as system data during installation. |
|
EOEP_APP_CODE |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Price Transaction Code |
Set up transaction code options, which set up the data entry pages for each transaction code and relate the transaction to another transaction. |
Access the All Price-by Key Fields page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, All Price-by Key Fieldnames, All Price-by Key Fields).
Note. Adding data here is considered a customization.
Record |
Select the transaction record name for the price-by key field. When adding a new record, click the Look up Record button to add new values. |
Field Name |
Select the transaction field name for the price-by key field. If a new Record is added, click the Look up Field Name button to add corresponding fields. |
Access the Transaction Code page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Price Transaction Code).
This section provides an overview of pricing options, lists common elements, and discusses how to:
Select price-by keys.
Select price list fields.
Set up pricing dates.
Set up pricing variables.
Enterprise Pricer pricing options are defined by pricing managers and other users who control and manage the pricing setup for the organization. Pricing options will be created and updated at implementation and possibly occasionally as the pricing requirements change. The things defined here are used to support those who will define the arbitration plans and price rules for the organization. Enterprise Pricer allows you to create custom variables, mathematical expressions, and dates.
Variables are used to establish the fields to use for calculating the net price using mathematical expressions.
The actual expressions are added to the price formula. The expression is validated by the system and tested before the formula is saved.
This table describes the pricing variables that are supported for both Contracts and Order Management:
Contract |
Sales Order |
Weight and Volume Pricing |
|
|
|
This table lists the only operators and functions that are supported by Enterprise Pricer for use in creating customized mathematical expressions:
Operator/Function |
Description |
Example |
Notes |
+ |
Add |
1 + 2 = 3 or 2 + –1 = 1 |
If you use negative numbers, do not enter a space between the negative sign and the number. |
− |
Subtract |
2 – 1 = 1 |
|
* |
Multiply |
2 * 3 = 6 |
|
/ |
Divide |
6 / 3 = 2 |
|
** |
Exponential |
2 ** 3 = 8 |
|
( ) |
Parenthesis |
(1 + 2) * 3 = 9 |
You can use operation grouping. |
Truncate(a,b) |
Truncate |
Truncate(123.45,1) = 123.4 |
You must enter a value for both a and b, and b cannot be a negative number. |
Round(a,b) |
Round |
Round(123.45,1) = 123.5 |
You must enter a value for both a and b, and b cannot be a negative number. |
In this example, variables are set up for list price (LIST_PRICE), product cost (PROD_COST), rollup quantity (ROLLUP_QTY, sum of the quantity of the schedules that match the price rule), and current net price (NET_PRICE). This table lists and describes examples of valid mathematical expressions:
Mathematical Expression |
Description |
1000 |
Replace price with 1000. |
LIST_PRICE * 0.95 |
Apply a five percent discount to the list price. This expression is also valid but not as efficient: LIST_PRICE * (100 – 5) / 100. |
NET_PRICE - 10 |
Reduce the current net price (amount) by 10. |
TRUNCATE(ROLLUP_QTY / 3, 0) |
For a product add, calculate the quantity as buy 3 and get 1. |
ROUND(PROD_COST * 1.30 * (1 - TRUNCATE( (ROLLUP_QTY – 900) / 100, 0) * 0.05), 2) |
This formula defines a break between 1000 and 1500 units. The net price is calculated as:
This kind of expression can reduce the need to create multiple formulas. However, you should set the formula break so that the calculation is valid. For example, if this example is applied to quantities greater than 2900, then the result can become negative. Note. Enterprise Pricer does not allow a negative net price. If the calculation results in a negative, it is set to 0. |
Pricing dates are the dates that Enterprise Pricer uses to select price lists and price formulas. They are set up by application. This table describes the dates used for Contract and Order Management:
Contract |
Sales Order, Weight, and Volume Pricing |
Effective Date |
|
Note. If you add a new pricing date, as long as it is not a user-defined date, (for example, you are simply changing the label of the date) then it is not considered a custom date and, therefore, does not require additional custom coding.
Transaction to be Priced |
Determines the appropriate list of price-by keys to use to price transactions. Values are: BA (buying agreement): Used to price buying agreement transactions in PeopleSoft Order Management. CA (contract): Used to price contact transactions in PeopleSoft Contracts. OC (order capture): Used to price transactions in PeopleSoft Order Capture. Note. This transaction does not appear in PeopleSoft Supply Chain Management. SO (sales order): Used to price online sales order and quote transactions in PeopleSoft Order Management. SOBT (sales order batch): Used to price batch sales orders and quote transactions in PeopleSoft Order Management. LP (weight and volume pricing): Used for weight and volume pricing on the sales order and quote in PeopleSoft Order Management. LPBT (weight and volume batch): Used for batch weight and volume pricing on the sales order and quote in PeopleSoft Order Management. RMA (customer returns): Used to price customer returns in PeopleSoft Order Management. |
Page Name |
Definition Name |
Navigation |
Usage |
EOEP_APPKEY_FIELD |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Transaction Price-by Keys, Price By Key Field |
Select the price-by fields that are used to price the transaction. |
|
EOEP_APPLIST_FLDS |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Transaction Price-by Keys, Price List Fields |
Select valid price-list-related business objects that are used when creating price lists and when defining the price list lookup method. |
|
EOEP_DATE_VAR |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Pricing Dates |
Set up dates used for pricing process. |
|
EOEP_PRICE_VAR |
Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Pricing Variables |
Set up variables that are used in price rule formulas when defining mathematical expressions. |
Access the Price-by Key Field page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Transaction Price-by Keys).
Price-by Key Fields |
View the current price-by fields for the transaction. You can delete fields from this list to remove them from use in pricing the transaction. |
Build Price-by Key Fields |
Click to add fields to the Price-by Key Fields grid after selecting them from the Select Price-by Key Fields grid. Note. If a price-by field is currently assigned to a price rule or an arbitration plan, you cannot remove it from the list of values assigned to the pricing transaction. |
Select Price-by Key Fields |
Select additional price-by fields.
Note. The number of pricing keys that you can define is
not limited; however, system performance slows when the number of keys increases.
In addition, you might need to change the application code to pass the value
to the Enterprise Pricer. For example, if you add a new field for sales orders,
you must add code to the sales order to pass the value of the new field when
calling Enterprise Pricer. You must perform this customization for both online
and batch pricing. |
Access the Price List Fields page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Transaction Price-by Keys, Price List Fields).
Select how you want the system to perform price list lookup. Values are: Consider all prices: The system considers all matching price lists based on the related business objects and price rules that you have attached to the price lists. It then selects the lowest price for the product. Lookup in priority order: The system establishes the order for the price list lookup based on the values in the Price-by Key Fieldnames Priority section. Use this method to establish a hierarchical method for selecting the list price for the transaction. The system selects the first active price it finds. Note. If the price list and related objects do not require the definition of a complex price condition, we recommend that you use the price list related objects. |
|
Key Field Code |
Select price-by keys to define the valid related business objects for a price list. These values are available as related business objects on the Price List Related Object page. They are a subset of the Price-by Key Fields for the transaction. |
Priority |
Establish a hierarchical order to price list lookups by entering a numeric value. This field is available only if you select the Lookup in priority order option in the Price List Lookup field. |
Access the Pricing Dates page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Pricing Dates).
Date Name |
Enter a date variable name. The name must:
|
Select the date type. Values are: Requested Arrival Date: The date that the customer wants the order to arrive on site. This option is used only by PeopleSoft Supply Chain Management installations. Effective Date: The date the transaction takes place, for example, the order date in OM. Order Date: The date that the order header is created. The system uses the current date as the default date on a sales order header, but you can enter another date. Price Date: The date specified on the arbitration plan. For example, on the price formula, you can specify Price Date <= January 1, 2005. If the arbitration plan used specifies Price Date = Scheduled Ship Date. When the price formula is evaluated, Scheduled Ship Date <= January 1, 2005 is evaluated. Schedule Ship Date: The date the order line is scheduled to ship. The system calculates this date from the requested arrival date, using the transit lead time and exception ship dates. You can, however, enter another date. This option is used only by PeopleSoft Supply Chain Management installations. System Date: The current server date, that is, the system variable %Date. User Date: A customer-defined date. Note. This PeopleSoft application does not automatically support a defined User Date. Implementation requires that the transaction pass the value for each user date when Enterprise Pricer is called. For example, if you add a user date for sales order, then you also must add code in sales order to pass the values. For sales orders, we have created an API for you to easily implement required logic. See example implementation class SCM_OM_API:Sample:SamplePricerInputLine for more information. The same API is used to pass customer-defined pricing variables. |
|
Description |
Provide a description for the pricing date. Used when selecting the pricing dates. |
Record |
Select the record from which you wish to pull the date value. Applies only when the pricing variable selected is User Date. |
Field Name |
Select the field from which you want to pull the date value. Applies only when the pricing variable selected is User Date. Note. Enterprise Pricer does not use Record and Field Name to automatically retrieve the value for the user date. These fields are only for the convenience of the implementation of user dates. For example, you can use the values in these fields to automatically retrieve the value for the user date and pass them to the Enterprise Pricer. |
Access the Pricing Variables page (Set Up Financials/Supply Chain, Common Definitions, Pricing Registration, Pricing Variables).
Pricing Variable Name |
Enter a variable name. The format of the name is the same as pricing dates. |
Select a variable type. All of the variable types, except User Variable, are Pricer variables whose values are known to Enterprise Pricer, either because the values are computed by the Enterprise Pricer (for example, the current net price) or because they are explicitly passed from the transaction (for example, the product cost by sales order). The variable types are: Alternate Product Cost: The alternate product cost of the transaction line. If not provided, value of Product Cost is used. Base Price: The base price used in the pricing calculation. Select from list price, product cost or alternative product cost, buying agreement price. Index Start Value: Price index start value. It is automatically retrieved by Enterprise Pricer based on the index start date specified by the transaction. Index End Value: Price index end value. It is automatically retrieved by Enterprise Pricer based on the index end date specified by the transaction. Index Start Amount: The start amount to apply the index adjustment. The amount is passed from transaction (for example, Contracts). If it is not provided, then the value of Base Price is used. Net Price: The current calculated net price (running net price). List Price: The list price of the transaction line. Product Cost: The product cost of the transaction line. Buying Agreement Price: The buying agreement price is used in the pricing calculation. Rollup Quantity: The rolled-up quantity of the transaction lines that match the price rule. This value is used to select the price formula breaks. Rollup Amount: The rolled-up amount of the transaction lines that match the price rule. This value is used to select the price formula breaks. Rollup Weight: The rolled-up weight of the transaction lines that match the price rule. This value is used to select the price formula breaks. Rollup Volume: The rolled-up volume of the transaction lines that match the price rule. This value is used to select the price formula breaks. Note. Index Start Amount, Index Start Value, and Index End Value are currently only used by Contracts. Trans Extended Base Price: Sum of the extended base price for the entire transaction. Trans Extended List Price: Sum of the extended list price for the entire transaction. Trans Extended Net Price: Sum of the extended net price for the entire transaction. Trans Extended Product Cost: Sum of the extended product cost for the entire transaction. User Variable: Customer-defined variable. Note. Not all variables are available in all situations. |
|
Record |
Select the record from which you want to pull the variable value. Applicable only when the pricing variable selected is User Variable. |
Field Name |
Select the numeric field from which you want to pull the variable value. Applicable only when the pricing variable selected is User Variable. Note. Enterprise Pricer does not use Record and Field Name to automatically retrieve the value for the user variable. These fields are only for the convenience of the implementation of user variables. For example, you can use the values in these fields to automatically retrieve the value for the user variable and pass them to the Enterprise Pricer. |