Siebel Pricing Administration Guide > Creating Attribute Adjustments > Single and Multiple Type Attribute Adjustments >

Using Wildcards in Attribute Adjustments


Selecting the Allow Any check box in a Dimension record lets you enter a blank instead of entering every different domain value for that dimension. This blank is called a null value wildcard. It represents all possible values in the given attribute's domain.

For example, you sell T-shirts that come in the colors white, gray, and red, and also come in the sizes small, medium, large, and extra-large, with the pricing shown in Table 7.

Table 7. Attribute Pricing for Each Combination of Attributes
Color
Size
Adjustment Type
Adjustment Amount

Red

Small

Markup Amount

$2.00

Red

Medium

Markup Amount

$2.00

Red

Large

Markup Amount

$2.00

Red

Extra-Large

Markup Amount

$5.00

There is no markup for any color except red. The red T-shirts are marked up $2, except for the extra-large size, which is marked up $5. Instead of the long list shown in Table 7, you can represent this with the short list shown in Table 8.

Table 8. Attribute Pricing Using a Null Wildcard
Color
Size
Adjustment Type
Adjustment Amount

Red

 

Markup Amount

$2.00

Red

Extra Large

Markup Amount

$5.00

In Table 8, the first row represents all the colors except red, and the second row represents all the sizes of red except extra-large.

The null value wildcard can reduce the work of creating a large attribute pricing table, but be careful to avoid the problems that it can create:

  • If you are using the attribute adjustment for attribute pricing, you may mistakenly enter wildcards that allow the user to choose invalid combinations of products.
  • You may also mistakenly create several rules that represent the same combination of condition dimensions. Make sure that every combination of condition tables is unique.

If you do create several rules that represent the same combination of condition dimensions, the application uses the rule with the most exact matches (not blanks) in the condition dimensions as the highest priority for processing. Priority is specified using the Sort Order field of the dimension.

Avoid using null value wildcards in the columns with the highest priority for processing. This increases the processing task for Siebel Pricer and causes the processing to take longer.

NOTE:  If you use wildcards, it is especially important to test your results after creating the attribute pricing table.

Siebel Pricing Administration Guide Copyright © 2006, Oracle. All rights reserved.