1. Integration Platform Technologies: Siebel Enterprise Application Integration Guide
  2. Validation of Integration Component Fields and Picklists

Validation of Integration Component Fields and Picklists

If an integration component field is created for a Siebel business component field, and the business component field is based on a picklist, then the EAI Siebel Adapter or the Object Manager validates the field. To have the validation done using the EAI Siebel Adapter, the integration component field has a user property with the name PICKLIST and a value of Y; otherwise, validation is done by the Object Manager.

If the EAI Siebel Adapter validates the integration component field, and if the pickmap for the picklist contains more than one field, then, when designing the integration object, you must decide the following:

  • Which of the fields to use as a search criterion

  • Which fields to simply update if input values are different from those in the picklist (provided that the picklist allows updates)

Note: Using the PICKLIST user property on an integration component field causes truncation to 30 characters (the length of the VAL column in the S_LST_OF_VAL Table) of the input value for searching the static picklist data.

Do not use the PICKLIST property on custom integration component fields. It is designed for static picklists, based on longer columns of the S_LST_OF_VAL table. Any input value provided in the input integration component field for search in picklist fields based on columns such as DESC_TEXT (Description field of the Picklist Generic business component) or NAME (Name field of the Picklist Generic business component) will deliver no result or an incorrect result because the string in the search expression will be truncated to 30 characters.