(Optional) Setting Up Enterprise Pricer

All Price-by Key Fields Page

EOEP_KEYFLDS

Set up price-by key fields for all Enterprise Pricer implementations. These values are delivered as system data during installation.

Price Transaction Code Page

EOEP_APP_CODE

Set up transaction code options, which set up the data entry pages for each transaction code and relate the transaction to another transaction.

Valid Action Types

• Discount/Surcharge

• Price Override

• Minimum/Maximum Target Discount

• Min/Max Target Price

• Min/Max Target Surcharge

• Related Business Objects

• Discount/Surcharge

• Pricing Base

• Rollup Only Rule

• Minimum/Maximum Margin

• Price Override

• Product Add

• Total Order Discount/Surcharge

• Minimum/Maximum Target Discount

• Minimum/Maximum Target Price

• Minimum/Maximum Target Surcharge

• Price List Only Condition

• Related Business Objects

Discount/Surcharge

Valid Adjustment Methods

• Cascading

• Summed

• Cascading

• Summed

Summed

Valid Price Types

• Extended Price

• Quantity

• Extended Price

• Quantity

• Volume

• Weight

Transaction Code Options

Use Price Index

• Use Alter Cost Based Pricing

• Use Buying Agreement

• Use Cost Based Pricing

• Use Exclusive Pricing

• Use External Application Class

• Use KVI/NDP (known value items/non-discountable products) Products

• Use mathematical Expression

• Use Maximum Quantity

• Use Mutually Exclusive Rule

• Use One-Time Only Price Rule

• Use Payment Terms on Formula

• Use Period-to-Date

• Use Quantity in Price List

• Use Rule Distribution Accounts

• Used Tiered Pricing

• Use Trade Promotions

• Use Rule Distribution Accounts

• Use Payment Terms on Formula

• Use One-Time Only Price Rule

• Use Mutually Exclusive Rule

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.

Transaction

Available transaction codes are:

• BA — Buying Agreements. In Order Management, the Buying Agreement can leverage the power of Enterprise Pricer by referencing a Price Rule as the basis for Pricing for the duration of the Buying Agreement.

• CA — Contract Billing: Order Management integrates with the Contracts module to provide advanced pricing capabilities for revenue and billing by product. The CA transaction code is used to identify product prices for billing.

• LP — Weight and Volume Pricing calculated online: When calculating freight and associated charges during transaction entry, Enterprise Pricer Price Rules can be leveraged for calculating freight charges based on various fields on the business objects and documents where freight needs to be charged.

• LPBT — Weight and Volume Pricing calculated in a batch process: When calculating freight and associated charges during batch processing (i.e. Order Completion), Enterprise Pricer Price Rules can be leveraged for calculating freight charges based on various fields on the business objects and documents where freight needs to be charged. It is suggested the same transaction pricing options for Online be used for batch processing.

• OMPB — Order Management Customer Price Book: The Price Book options should match those of the Sales Order so that when you generate a Price Book for a customer, the same sort of options are displayed/printed for the Customer-specific Pricing options.

• RMA — Returned Material Authorization Pricing: This setup allows you to determine how orders returned for replacement and credit are to be calculated using Price Rules and Formulas. You may have a different set of criteria for pricing returned material than you would for Sales Orders/Quotes.

• RP — Contract Revenue Pricing: Product prices setup using the RP transaction code are used in the Contracts module for revenue recognition.

• SO: Sales Order and Quotes: This setup allows you to determine how orders and Quotes will leverage Enterprise Pricer options and how Orders and Quotes will be priced when doing online data entry.

• SOBT: Sales Order and Quote Batch Processing: This setup allows you to determine how Orders and Quotes will leverage Enterprise Pricer options and how Orders and Quotes will be priced when doing processing batch (i.e.: Order Completion, Reprice Orders). It is suggested the same transaction pricing options for online be used for batch processing.

Parent

If you want to use the options from another transaction, select that transaction as the parent. For example, Buying Agreement uses the same options as Sales Order. Therefore, you would select Sales Order as the parent of Buying Agreement, and no options would be set up under Buying Agreement.

Pricing Data Used

Select a value that indicates if the price rule should be inherited by child transactions. Values are:

System Default: Child application uses pricing data of parent application. This is the default option.

Parent Application: A child application uses the pricing data of the parent application; however, a child application is allowed to flag price rules set up for the parent application so that they cannot be used in the child application.

Price Rule Usage Processor

Enter the name of the application class that returns and displays price rule usage for the transaction. The application class implements interface EOEP_API:RuleUsageChecker to return the price rule usage data during the pricing calculation and to display the price rule data on the Price Rule page. For example, SCM_OM_PRICER:EOEP_API:SORuleUsageChecker is used for sales order.

This value is required if the transaction uses these types of price rules: one-time only, maximum quantity, period-to-date.

Valid Action Types

Select valid price action types for the transaction and limit the available options during price rule and arbitration plan entry. The values that you select are available for the price rule price action type. Values are:

Discount/Surcharge: Applies a discount or surcharge to the line.

Min/Max Margin: When the price rule has a match, the order is put on hold, as in the case of PeopleSoft Order Management. A schedule is on hold if it hits any Min/Max Margin price rules. The hold is removed automatically when repricing occurs if the order schedule no longer matches any of the Min/Max Margin price rules.

Min/Max Target Discount: Compares the total discount adjustment and, if it is outside the specified amount, applies a target discount.

Min/Max Target Price: Compares the price adjustment and, if it is outside the specified range, applies a target price.

Min/Max Target Surcharge: Compares the total surcharge adjustment and, if it is outside the specified range, applies a target surcharge.

Price List Only Condition: Attaches price lists to a transaction. The formula does not specify price breaks.

Price Override: Applies a new price.

Pricing Base: Selects the base or the starting point for pricing calculation. The pricing base action type does not have associated formulas, but it has a flag that indicates the base used if the transaction line matches this price rule.

Product Add: In previous releases, this was a giveaway action type. Now, you can indicate the discount, surcharge, or price in addition to the quantity of the giveaway. The list price of the giveaway product is used to calculate the net price. For online sales orders in PeopleSoft Order Management, the product adds (or giveaways) appear on a separate page or grid so that you can choose the ones to add to the order. For batch orders, the product adds are added to the order automatically.

Rollup Only Rule: Rolls up the quantity or amount. Only conditions are used for this type of rule (no breaks are needed). This type of price rule is used by other price rules, such as Discount/Surcharge price rules, to select price formulas.

Total Order Discount/Surcharge: Applies a discount or surcharge to the entire order.

Valid Adjustment Methods

Select how the system applies the adjustment for the Discount/Surcharge price action type from these values:

Cascading: Applied as they are found. A second discount is applied to the previously discounted price, a third discount is applied to a price that already was discounted twice, and so on. For example, if the system encounters two discounts, 10 percent and 20 percent off the list price of 100.00 USD, then the system applies the discounts in this manner: 10 percent off of 100.00 USD and 20 percent off of 90.00 USD. Thus, the unit price for the order schedule line is 72.00 USD.

Summed: When the system finds multiple discounts, it adds them together and applies the discounts once. Thus, for the summed example, the system would apply discounts in this manner: the 10 percent and 20 percent discounts for 30 percent off of 100.00 USD, which results in a unit price for the order schedule line of 70.00 USD.

Valid Price Types

Select the price types whose values you want to price by. Choose from: Extended Price, Quantity, Weight, and Volume.

Transaction Code Options

Select the features that the transaction supports. These options will control the pricing data setup pages and the pricing process. Possible values are:

No Price List Auto Conversion: Select this option to disallow price list in base currency from being used if no price list in transaction currency is found. If this option is not selected, price list in base currency will be converted to transaction currency and used if no matching price list in transaction currency is found.

Use Alt Cost Based Pricing (use alternate cost based pricing): Select to indicate whether or not the specified transaction uses the Alter Cost Based Pricing feature. Enabling this option results in the Applicable to Alternate Cost Base option appearing on the Conditions page when you define a price rule.

Alternate cost and product cost are different. For example, in Order Management, the alternate cost is product cost with an alternate cost adjustment factor applied.

Use Buying Agreement: Select to indicate whether or not the specified transaction uses the Buying Agreement feature. When this option is selected, the transaction can set up price rules that are applied to the buying agreement price, and the Applicable to Buying Agreement option appears on the Conditions page when you define a price rule.

Use Cost Based Pricing: Select to indicate whether or not the specified transaction uses the Cost Based Pricing feature. Enabling this option results in the Applicable to Cost Base option appearing on the Conditions page when you define a price rule.

Use Exclusive Pricing: Select to indicate whether or not the specified transaction uses the Mutually Exclusive pricing feature. With multiple exclusive price rules, if one or more of these rules is matched, then only one of them is applied and all other rules, whether they are mutually exclusive or regular rules, are ignored.

Use External Application Class: Select to indicate whether or not the specified transaction enables user-defined application classes to calculate the net price.

Use KVI/NDP Products: (use known value items/nondiscountable products): Select to indicate whether or not the specified transaction supports KVI/NDP products. For KVI products, Enterprise Pricer does not apply any adjustment to the price of the product. For NDP products, Enterprise Pricer does not apply discounts to the product price that would result in a net price that is less than the starting price (for example, list price or cost plus the first surcharge). In addition, you can select to exclude them from the price rule rollup for price formula matching.

Use mathematical Expression: Select to indicate whether or not the specified transaction enables Enterprise Pricer to create adjustments using user-defined mathematical expressions on the Price Formula page. You must set up pricing variables so that the system knows what variables are used in the pricing calculation.

Use Maximum Quantity: Select to indicate whether or not the specified transaction supports the ability to define price rules that are used until the applied quantity specified is reached.

Use Mutually Exclusive Rule: Select to indicate whether or not the specified transaction supports the ability to define price rules that are mutually exclusive. With multiple exclusive prices rules, if one or more of these rules is matched, only one of them is applied and all other rules, whether they are mutually exclusive or regular rules, are ignored.

Use One-Time Only Price Rule: Select to indicate whether or not the specified transaction supports the ability to define limited use price rules. On the Price Formula page, you can indicate that the rule is valid only for one time per rule or one time per customer. This option is valid only for Discount/Surcharge, Price Override, Giveaway/Product Adds, and Total Order Discount/Surcharge price rules.

Use Payment Terms on Formula: Select to indicate whether or not the specified transaction supports the ability to define price rules that select the payment for each adjustment that has the longest day or month increment from the list of values on the Payment Terms page in PeopleSoft Billing. If the order or schedule has more than one price rule with a payment term that qualifies for the order, then the system selects the most favorable terms for the customer.

Use Period-to-date: Select to indicate whether or not the specified transaction uses the Period-to-date Pricing feature. Enabling this option will result in the system using period-to-date pricing to calculate price adjustments based on transactions across a predefined time frame, rather then individual transactions.

Use Price Index: Select to indicate whether or not the specified transaction uses an index, such as the Consumer Price Index (CPI), from an external source for price calculations. The price index feature uses the pricing variables and mathematical expression.

Use Quantity in Price List: Select to indicate whether or not the specified transaction is allowed to use quantity breaks within the price list.

Use Rule Distribution Accounts: Select to indicate whether or not the specified transaction is allowed to view and create accounting distribution details for the adjustments in the price rule.

Use Tiered Pricing: Select to indicate whether or not the specified transaction supports the tiered pricing feature. With tiered pricing price rules, you can set up price rules that apply different adjustments to different ranges in the same transaction line.

Use Trade Promotions: Select to indicate that the transaction supports the Trade Promotion feature.