I call this Part III, and concluding part of a series of my posts on the Merge Records functionality in Siebel CRM. You may want to take a look at the previous 2 parts below:
Siebel – Merge Records functionality
Siebel – Automating Merging Records by script – II
Though this looks like a very interesting and useful utility from the face of it, it can be dangerous too.
Siebel List of Values is probably the most commonly used entity in almost all the Siebel EAI projects. I have seen people use LOVs for all sorts of crazy things – storing Language Translations (most common use!), reverse translations, holding Pricing Information, identifying incoming interfaces, setting up a list of allowed values (for eg. in an incoming XML tag), using the Description field to increase the max length that can be stored and what not!
Siebel List of Values have found such profound use and application, possibly because of the famous LookUpValue() function, which can quickly pick out values from the S_LST_OF_VAL table. The LOVs are cached which make this function work even faster and helps Performance. It does have its own set of pains, however.
Now this is strange. I had been running into some problems when I was checking out objects in my Siebel Tools. What used to happen was that I would set an object for check-out. It would show it fine for some time. all the extracts being done fine, all the tables being checked out one by one et al. All of a sudden, the operation would hang.