Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Product Administration Guide > Product and Promotion Eligibility and Compatibility > Defining Eligibility for Product AttributesYou can define the eligibility for individual attributes of products. For example, only customers living in certain countries are eligible to buy a shirt in a specific color. All customers are able to buy the same shirt in any other color. When a configuration session is started, all the possible attribute values belonging to the attributes marked as requiring an eligibility check are evaluated:
When an attribute value is changed, only the new selection is evaluated for eligibility (post-pick). The ineligibility reason is used by the Siebel Configurator UI in the messaging. You must create custom PSP procedures to evaluate the attributes. The framework that calls these custom procedures and communicates with the user is delivered as part of the application, including:
Saving the Result of Attribute EligibilityAttribute eligibility status and reason are not saved to the quote or order objects when a configuration session is completed. It is not possible to save these with the configuration changes alone, because the values are not saved to the CxObject in memory. However, it is possible to save these results using the BatchValidate API for Siebel Configurator, described in BatchValidate Method. This API can run attribute eligibility. The ineligible attributes are sent to a log file. The output property that is set from this API contains information on the ineligible attributes. It is possible to add a custom step to the Sales Order verify process that calls the batch validate API. This step can update the custom fields on the Order XA business component indicating an attribute value as being ineligible. The Order Validation engine then checks that field to confirm that no ineligible values are selected. Attribute Eligibility ArchitectureAttribute eligibility checking uses the following architecture:
Setting Up Attribute Eligibility CheckingThis topic describes the high-level steps for setting up attribute eligibility checking. Writing a Custom PSP Procedure to Check EligibilityYou can use a given procedure to evaluate one attribute or many attributes:
Typically, the custom procedure includes the following steps:
Creating the Attribute and Assigning It to a Product ClassCreate the attribute and assign it to a product class in the usual way, described in Process of Creating Products with Attributes. In the Administration - Product, Product Classes, Version, and then the Attributes view:
Changing the Context and Rowset Variable MapsYou can change the context and rowset variable maps used by the attribute eligibility procedure. The variable map is set as a parameter in the LoadInstance signal and the SetInstance signal. The name of the parameter is Context Variable Map. By default, it has a value of Cfg Eligibility Variable Map - Context. The rowset for attribute eligibility is generated without a variable map. It contains only one property: value. Using Different Display Modes for Attribute and Product EligibilityYou can have different display modes for Attribute eligibility and for Product eligibility. Change the display mode for attribute eligibility by adding the EligiblityDisplayMode parameter to the SetInstance and LoadInstance signals and giving it the value of 0, 1, or 2. This overrides the application's EligibilityDisplayMode setting. |
![]() ![]() |
Siebel Product Administration Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |