Picklist Validation
Siebel CRM has two classes of picklists: static picklists based on lists of values and dynamic picklists based on joins.
Setting the property PICKLIST to Y in the integration object field directs the EAI Siebel Adapter to validate that all operations conform to the picklist specified in the field. For dynamic picklists, this setting is essential to make sure the joins are resolved properly. However, for unbounded static picklists, this validation might be unnecessary and can be turned off by setting the PICKLIST property to N. Even for bounded static picklists, you can turn off validation in the adapter, because the Object Manager can perform the validation. Turning off the validation at the EAI Siebel Adapter level means that picklist-related warnings and debugging messages do not show up along with other EAI Siebel Adapter messages. This also means that bounded picklist errors will not be ignored, even if Ignore Bounded Picklist is set to Y.
As well as certain warnings and messages not appearing, setting the integration component field user property PICKLIST to N can also cause fields to be auto-completed. Providing only part of the value for a particular field causes the field to be auto-filled with the first matching entry in the picklist. This occurs especially when the picklist is based on a multilingual list of values (MLOV). For example, if the incoming message contains the string "On-" and there exists an entry "On-Hold," then the field will be set to "On-Hold."
If the EAI Siebel Adapter performs the validation (PICKLIST is set to Y), auto-filling of the field does not occur. In this case, the EAI Siebel Adapter supports only an exact match for the particular field (in the previous example, the value "On-" will fail; only "On-Hold" will pass).