Implementing PeopleSoft Enterprise Pricer

This chapter provides an overview of the PeopleSoft Enterprise Pricer implementation and discusses how to:

• Set up Enterprise Pricer.

• Establish pricing options and values.

• Add price-by key fields.

Understanding PeopleSoft Enterprise Pricer Implementation

The setup for Enterprise Pricer is separated into two segments: performing setup tasks and establishing pricing options and values. Setup tasks are optional and are more complex and involve adding additional fields and completing significantly more complex tasks. As for pricing options tasks, they are simpler tasks that involve defining key fields appropriate to the enterprise.

Warning! The Enterprise Pricer application is delivered with standard setup for the Order Capture transaction. Changes made to certain delivered data, such as adding a new price transaction code, adding a price-by key for a record that's not already being used by Enterprise Pricer, and creating custom mathematical expressions, are considered system customizations and are not supported by the Global Support Center.

Setup Tasks

Perform setup tasks if you wish to modify Enterprise Pricer system data and alter how the application works in a standard implementation.

Available setup tasks include addition of price-by fields and transaction-specific options. Note that these tasks require customization to the application. For example, if a new pricing key for a record that is not already being used in Enterprise Pricer is added on a setup page, the developer must also customize both online and batch pricing to use the new key.

Setup tasks are optional in a standard pricing implementation because it delivers a predetermined set of price-by key fields and price list fields as well as ready-to-use pricing settings for the Order Capture transaction.

These setup tasks are:

• Set up new 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 the Order Capture transaction are delivered as system data and appear on the online pricing pages.

Pricing Options and Values

After the price-by keys and transaction code options are defined and specified, an Enterprise Pricer implementer or information technology person can perform these steps to set up other pricing options and values for use in defining price lists, price rules and arbitration plans:

1. Specify price-by keys to be used by a transaction on the Transaction Price-By Keys component.

   This identifies the price-by keys used by the application when defining price lists and price rules for a transaction. Enterprise Pricer delivers price-by keys for the Order Capture transaction.

2. Set up the pricing dates for the application on the Pricing Dates page.

   This defines the 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. Delivered values are available.

3. Set up the pricing variables for the application on the Pricing Variables 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 be used for calculating net prices using mathematical expressions. Delivered values are available.

4. Set up a rounding rule to be used to round up pricing adjustments or net prices if needed.

   Enterprise Pricer delivers a rounding rule called standard for use in Order Capture transactions.

Setting Up Enterprise Pricer

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. Tasks in this section are optional; skip this section if there is no need to modify the delivered price-by key fields and transaction code options.

Understanding Transaction Code Options

Each transaction that Enterprise Pricer supports is associated transaction code options, which determines the values and functionality that are available when you define price rules or arbitration plans for the transaction, or when Enterprise Pricer performs arbitrations or calculates pricing.

This table lists the setup options that are delivered as system data for the Order Capture transaction:

Pages Used to Set Up Enterprise Pricer

Setting Up Price-by Key Fields

Access the All Price-by Key Fieldnames page (Set Up CRM, Product Related, Enterprise Pricer, All Price-by Key Fieldnames, All Price-by Key Fieldnames).

Entries on this page are delivered as system data. The system identifies the record and field name for each price-by key specified on this page.

Note. Addition of new price-by key fields on this page for records that are not already being used by Enterprise Pricer is considered a customization.

Setting Up Price Transaction Code Options

Access the Price Transaction Code page (Set Up CRM, Product Related, Enterprise Pricer, Price Transaction Code, Price Transaction Code).

The transaction code setup for the Order Capture transaction is delivered as part of the standard Enterprise Pricer implementation.

Valid Action Types

Valid Adjustment Methods

Valid Price Types

Transaction Code Options

Establishing Pricing Options and Values

To define pricing dates, pricing variables, and price rounding rules, use the Pricing Dates, Pricing Variables, and Price Rounding Rules components.

Use the EOEP_DATE_VAR_CI, EOEP_PRICE_VAR_CI, and EOEP_ROUND_RULE_CI component interfaces to load data into the tables for these components.

The section provides an overview of pricing options and values, and discusses how to:

• Specify price-by keys for the Order Capture transaction.

• Specify price list fields for the Order Capture transaction.

• Set up pricing dates.

• Set up pricing variables.

• Set up price rounding rules.

Understanding Pricing Options and Values

Price lists and price rules are two important elements in the pricing process; price lists are used to determine list prices and price rules used for computing the price adjustments when applied. Prior to defining price lists and price rules, you establish components that are referenced in price lists and price rules for a number of purposes: setting up related objects in price lists, building rule conditions, specifying date ranges and mathematical expressions in rule formulas, as well as the rounding option for use in price rules.

Transaction Price-by Keys

Transaction price-by keys are used in defining conditions in price rules. When Enterprise Pricer is called to compute pricing for an order, it looks for all price rules with conditions that match the order lines for applying price adjustments and price lists (in case when a price list is specified in a price rule).

Price List Fields

Price list fields are used in defining related objects in price lists and are a subset of transaction price-by keys. When Enterprise Pricer finds a list price of the product on an order line that is not list price protected, it retrieves all price lists with related objects that match the order. If multiple matching price lists are available, you can set up to either take the best (lowest) product list price found among these price lists, or to use the product list price that comes from the price list with the highest priority score.

Pricing Variables

Pricing variables are used for calculating the net price using mathematical expressions. This table lists the pricing variables that Enterprise Pricer delivers and specifies the ones that are enabled for the Order Capture transaction:

Mathematical Expressions

Enterprise Pricer supports the use of these operators and functions when creating custom mathematical expressions:

Enterprise Pricer provides the ability to validate the syntax of mathematical expressions and evaluate them with the inputs you provide.

Pricing Dates

Pricing dates are used in arbitration plans and in defining date breaks that are referenced in price rule formulas for Order Capture transactions. This table lists the pricing dates that Enterprise Pricer delivers and specifies the ones that are enabled for the Order Capture transaction:

Rounding Rules

Price rounding rules identify the number of decimal points to use based on the base price that is used in the pricing calculation. You can associate each price rule with a rounding rule or use the default rounding rule from the arbitration plan. You can also define whether each adjustment is rounded before it is applied, the net price is rounded after adjustments are applied, or both.

Use the Price Rounding Rules page to specify rounding rules. If rounding rules are not established, the system rounds according to how each application uses Enterprise Pricer. In the case of PeopleSoft Enterprise CRM, prices are rounded by currency.

Pages Used to Establish Pricing Options and Values

Specifying Price-by Keys for the Order Capture Transaction

Access the Price Key Fields page (Set Up CRM, Product Related, Enterprise Pricer, Transaction Price-by Keys, Price Key Fields).

Price-by Key Fields

This section lists the price-by fields that can be selected for use in the specified OC transaction.

Select Price-by Key Fields

This section lists price-by key fields that are currently selected for the transaction, as well as the ones that can be added to the list. For example, if you add a new field to the All Price-by Key Fieldnames page, it is added automatically to this list.

Note. You can define an unlimited number of pricing keys; however, system performance is affected as the number of keys increases.

Specifying Price List Fields for the Order Capture Transaction

Access the Price List Fields page (Set Up CRM, Product Related, Enterprise Pricer, Transaction Price-by Keys, Price List Fields).

Price List Lookup	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 Field Names by Priority section. Use this method to establish a hierarchical method for selecting the list price for the transaction. Note. When using the hierarchical method, price rules tied to price lists are not used, unless a price is not found using the hierarchical method.
Key Field code	Select price-by keys to define the valid related business objects for a price list. These values are available to you as related business objects on the Related Objects page of the Price List component.
Priority	Establish a hierarchical order to price list lookups by entering a numeric value. This field is available only if you select Lookup in priority order in the Price List Lookup field.

Setting Up Pricing Dates

Access the Pricing Dates page (Set Up CRM, Product Related, Enterprise Pricer, Pricing Dates, Pricing Dates).

Use this page to define valid dates that can be used by price rules to create date breaks in rule formulas. Delivered pricing dates are available. You can define multiple rule formulas using multiple date breaks in a price rule.

Setting Up Pricing Variables

Access the Pricing Variables page (Set Up CRM, Product Related, Enterprise Pricer, Pricing Variables, Pricing Variables).

Use this page to specify valid variables that can be used in mathematical expressions for calculating pricing adjustments. Delivered pricing variables are available.

Setting Up Price Rounding Rules

Access the Price Rounding Rule page (Set Up CRM, Product Related, Enterprise Pricer, Price Rounding Rule, Price Rounding Rule).

Use this page to specify the rule that is used for rounding during net price calculation.

A rounding rule cannot be deleted if it's currently used by an arbitration plan.

Adding Price-by Key Fields

You might need to add more price by keys than those delivered with the system data. The following steps provide an example of how to add item weight using the All Price-by Key Fieldnames page. You can follow the same steps to add other fields.

Note. Adding price by key fields for records that are not already being used by Enterprise Pricer is considered a customization.

Follow these steps to add item weight as a pricing key to PeopleSoft Enterprise Pricer:

1. Add the INV_ITEM_UOM record and the SHIPPING_WEIGHT field on the All Price-by Key Fieldnames page.

2. Assign the new SHIPPING_WEIGHT field to the transaction code that you are using on the Price Key Fields page.

   Select the new SHIPPING_WEIGHT field from the list at the bottom of the page. Click the Build Price-by Key fields button to associate the new field to the transaction code.

3. If the new field requires a table to prompt for valid values when the pricing key is used on the price rule, create a view and assign the prompt table to the pricing key on the Price Key Fields page.

   This is the same page you used in step 2.

   If no prompt table is assigned to a pricing key, you can enter any value on the price rule for that field.

You may need to modify the PeopleCode to recognize the new pricing key. When a new pricing key is added to the list of available keys and it is assigned to a transaction code, it may require a change to the PeopleCode method used to pass a value to that new pricing key. The following method in PeopleSoft Enterprise CRM contains the logic used to pass a value for each pricing key defined for the Order Capture transaction code. If a new pricing key is added to the transaction code, you should review the following PeopleCode program to make sure that the pricing key is used by the system:

• Application Package: RB_PRICER:PricingUtil:InputList

• Method: CreatePricingKeysLocal( )

This method is used to assign a value from PeopleSoft Enterprise Order Capture to each pricing key defined for the Order Capture transaction code. If multiple pricing keys are defined for the same record, you modify the PeopleCode only once. Subsequently, you can select any field from that record as a pricing key without having to modify the code. You can modify the code in CreatePricingKeysLocal( ) to handle all the fields from a specific record without having to specify the field name.

In other cases, the value for a field will require more logic to determine what value to assign to the pricing key. If you must add a new record for which all the fields can be used as pricing keys to the PeopleCode, you use the same logic and add a new condition to the Evaluate logic. For example, if you need to add multiple fields from record INV_ITEM_UOM to the list of pricing keys, you can add the following condition:

  When Record.INV_ITEM_UOM
            &recItemUom = createrecord(RECORD.INV_ITEM_UOM);
            &recItemUom.SETID.value = %Super.ProductSetid;
            &recItemUom.INV_ITEM_ID.value = %This.GetInvItemId(&recLine.PRODUCT_⇒
ID.Value);
            &recItemUom.UNIT_OF_MEASURE.value = &recLine.UNIT_OF_MEASURE.value;⇒
         
            &recItemUom.SelectByKey();
            &strValue = &recItemUom.GetField(@("FIELD." | &strFieldname)).Value;
            Break;

You can add the PeopleCode once and then use any field from record INV_ITEM_UOM as a pricing key.

Example

The following example shows the code that you need when more logic is needed in order to determine the value for a specific pricing key. When the pricing key is INV_ITEM_UOM.SHIPPING_WEIGHT, you can run the GetWeight( ) method to calculate the weight for the item:

When Record.INV_ITEM_UOM
         Evaluate &strFieldname
         When Field.SHIPPING_WEIGHT
            &strValue = %This.GetWeight(&recLine.PRODUCT_ID.value, &recLine.UNIT_⇒
OF_MEASURE.value);
            Break;

This is the existing and new code for the customization:

rem ==================================================================
rem  Method:       CreatePricingKeysLocal
rem
rem  Description:  Pass the pricing key information to the engine.
rem ==================================================================;
method CreatePricingKeysLocal
   /+ &objLine as EOEP_PRICER:DataStructure:Line, +/
   /+ &recLine as Record +/
   Local integer &iCount, &iCount2;
   Local Record &recAppkeyFld, &recDestination;
   Local string &strFieldname, &strValue, &strVoid;
   Local number &numBO, &numShipToBoid, &numProfileSeq;
   Local boolean &bRetVal;
   Local RO_CAPTURE:BusinessLogic:Records:Destination &objDestination;
   Local array of string &arrReturn;
   
   
   For &iCount = 1 To &c_rsPricingKeys.ActiveRowCount
      &recAppkeyFld = (&c_rsPricingKeys)(&iCount).PW_PRCKEY_VW;
      &strFieldname = &recAppkeyFld.FIELDNAME.Value;
      &strValue = "";      

      When Record.RO_HEADER
         rem -----------------------------------------------------------;
         rem Copy key value from header                                 ;
         rem -----------------------------------------------------------;
         &strValue = %Super.HeaderRec.GetField(@("FIELD." | &strFieldname)).Value;
         Break;

      When Record.INV_ITEM_UOM
         rem -----------------------------------------------------------;
         rem Copy key value from Inventory Item UOM                     ;
         rem -----------------------------------------------------------;
         &recItemUom = createrecord(RECORD.INV_ITEM_UOM);
         &recItemUom.SETID.value = %Super.ProductSetid;
         &recItemUom.INV_ITEM_ID.value = %This.GetInvItemId(&recLine.PRODUCT_⇒
ID.Value);
         &recItemUom.UNIT_OF_MEASURE.value = &recLine.UNIT_OF_MEASURE.value;⇒
      
         &recItemUom.SelectByKey();
         &strValue = &recItemUom.GetField(@("FIELD." | &strFieldname)).Value;
         Break;
      .
      .
      . 

      End-Evaluate;
      
      If &strValue <> "" Then
         %This.AddPricingKey(&objLine, &recAppkeyFld.EOEP_KEY_FLD_CD.Value, &str⇒
Value);
      End-If;
   End-For;

This is the new code for the customization to retrieve values from the table and pass them to the pricing engine:

When Record.INV_ITEM_UOM
         rem -----------------------------------------------------------;
         rem Copy key value from Inventory Item UOM                     ;
         rem -----------------------------------------------------------;
         &recItemUom = createrecord(RECORD.INV_ITEM_UOM);
         &recItemUom.SETID.value = %Super.ProductSetid;
         &recItemUom.INV_ITEM_ID.value = %This.GetInvItemId(&recLine.PRODUCT_⇒
ID.Value);
         &recItemUom.UNIT_OF_MEASURE.value = &recLine.UNIT_OF_MEASURE.value;⇒
      
         &recItemUom.SelectByKey();
         &strValue = &recItemUom.GetField(@("FIELD." | &strFieldname)).Value;
         Break;
      .
      .
      . 

      End-Evaluate;