Bookshelf Home | Contents | Index | Search | PDF

Pricing Administration Guide > Script-Based Pricing Factors > The Process of Implementing Script-Based Pricing Factors >

Defining User Properties for the Script

---

A script-based pricing factor uses a business service or any process that can be called through a business service interface, such as a workflow process. These can be deployed either by being compiled into the SRF or as data in the Siebel database.

The purpose of defining user properties on the business service is to specify the information that is passed by Pricer to the business service.

The purpose of passing only the required information to the business service is to improve the performance of the pricing process by minimizing the amount of data that is transferred.

The format for business services requires you to define user properties to support:

Attributes
Customizable products
Information about the current state of business components, such as the Account for the Quote or the Part # for the Product.

For every business service used as a pricing factor, one user property is required, as shown in Table 34.

Table 34.  Property for Business Services Used as Pricing Factor

Name	Value
Use Variable Map	Y

In addition, properties similar to the ones shown in Table 35 can be used to specify information passed to the script.

Table 35.  Properties Used to Pass Information to the Script

Name	Value
Field 1	Quote.Name
Field 2	Quote.Currency Code
Field 3	Quote Item.Product
Parameter 4	Quote Item XA.Color

When you are defining the properties used to pass information to the script, follow these recommended naming conventions:

The properties must be named using sequential integers. These numbers are the keys you will use to pass parameters into the script.
For the header (such as Quote) and item (such as Quote Item) business components, use a name composed of "Field" followed by an integer.
For the XA business component (such as Quote Item XA), use a name composed of "Parameter" followed by an integer.
Specify the values for the header and item using the syntax BusComp.Field, as shown in the examples in Table 35.
Specify the values for the XA buscomp using the syntax XABusComp.AttributeName, as shown in the examples in Table 35.

The following properties are always present in the inputs property set to the script factor, supplied by the pricing engine. You should not set user properties for these inputs.

Purchase Price
Current Price
Adjustment Value
Target Price
Source Price
MSRP Price
Cost
Base Price
Reason
Type of Calculation

For a complete list of user properties, see Siebel ePricer Deployment and Integration.

Creating the User Properties

Before you write the script, create a business service and define the user properties that the script will reference.

To define user properties for the script

From the application level menu, choose View > Site Map > Business Service Administration > Business Service Details.
In the new record in the Business Service list, enter a name for the business service and optionally enter a comment describing the business service.
Add new records to the User Properties list, and enter the user properties, as described earlier.

Bookshelf Home | Contents | Index | Search | PDF