Siebel Community

Welcome to Siebel Community. In this place you can find all the topics related to Siebel. This place is dedicated to provide information about how to implement Siebel CRM application. Siebel Technical/Functional consultants can get information from basics of Siebel CRM to advanced topics like EAI, EIM, eScripting, Workflows, Assignment Manager, Actuate Reports, Territory Management. This place also included Forums and Blogs to help you further.

Wednesday, June 20, 2012

Pick List User Keys

In case of dynamic picklists, pick map may bring many fields,One of the tasks the integration object designer needs to perform is to determine which of these fields is used to identify the required field.


For example:
Consider a field Accout which is a dynamic picklist and contains many fields such as Account, Account Location, Account Integration Id, Currency Code,Price List, and so on

If the PicklistUserKeys user property on the integration component field that is mapped to the field with the picklist (in the example above: Account) is not defined, then any integration component fields that are mapped to columns in the U1 index of business component's base table, and are present in the pickmap will be used by the EAI Siebel Adapter to find the matching record in the picklist. (In the example above, this would be Account and Account Location.)

In cases where the default user key for the picklist does not satisfy your business requirements (for example, Account Integration Id should be solely used instead of the default user key to pick an Account), or you want to make the user key explicit for performance reasons, then use the

PicklistUserKeys user property.

Syntax for Integration component Field User Property:

Name: PicklistUserKeys Value : PickmapFieldname

Eg: Name: PicklistUserKeys Value : Account Integration Id

No comments:

Post a Comment