In this article we are going to focus on the challenges during the EIM merge process.
The EIM merge is a lovely process offered by the Siebel, We can have detail understanding of the merge process at the backend by studying the log of any EIM merge process. It provide the detailed information of all processing at the backend. The merge process functionality can be achieved using scripts but it will be a tedious job.

Sometime we have to go for creating a custom business component because no existing business component is suitable or match or requirement and alos have to decide whether to go with existing table or create a new one. It will always be preferred to use the custom table for the functionality because of some of the below reasons :

Sometime we configure Immediate Post Changes property on the BusComp field object equal to TRUE while no server processing is required in the configuration. This is  an inappropriate Use of Immediate Post Changes for BusComp Fields in Siebel.
Brief introduction of Immediate Post Changes : Immediate Post Changes is an optional property of BusComp field. It has a TRUE or FALSE value.
Definition by Siebel Bookshelf “Field data is posted to the server when the focus moves off of the field and then the data is refreshed. Causes an immediate roundtrip to the …

We are adding a new tag "Siebel Best Practice" for our readers, which will cover Siebel best practice for all categories.
first article in this series. Custom Foreign Key Columns Differ in Length from Destinations Custom Foreign Keys do not have the same length as the destination columns to which they are joined.
Impacted space:  Data Integrity, Runtime Error