Siebel Sequential Merge and Standard Merge

Sequential Merge and Standard Merge

Siebel provides options for matching and merging the duplicate records to maintain high quality data in the application. Matching (also called as DeDuplication) can be done using Data Quality functionality provided out of the box. After the potential duplicate records are identified using Data Quality functionality, they can be merged using Sequential Merge.
There can be instances where duplicates can be identified manually and required to be merged. This can be done using Standard Merge.

Take a note of following points:

·    Sequential Merge can be done only from Administration – Data Quality Screen where as Standard Merge can be performed against standard entities like Account/Contact from their respective screens.
·    Sequential Merge merges fields at the Parent level wherein Standard Merge Parent level fields are not merged. e.g. if Contact mobile number is populated on Losing record and not populated on Winning record, it will not be carried to the Winning record in Standard Merge.
·    Only exposed and force active fields are merged in Sequential Merge
·    If hidden fields are to be merged, set list column user property as ForceActive Y
·    In Sequential Merge, record with lowest sequence number is Winning record whereas last selected record is the Winning record in Standard Merge
·    If there are any business validations before Merge, those can be put on PreInvokeMethod of the applet
·    If there is any processing after Merge, it can be put on InvokeMethod of the applet
·    It is recommended to skip all code on respective entities in all events while Merge is happening. This can be achieved through setting profile attribute on PreInvokeMethod and resetting it in error handling and InvokeMethod

Siebel Loyalty : Changing Transaction Status

Loyalty : Changing Transaction Status

If the transactions are created in the batch mode by the Loyalty engine, the status of the transactions will be in "Queued" status. When you click on the process button manually, this will not be processed. This OOTB behavior can be modified by changing the user property OrderToTxn:Transaction Status as below.

Business Service Name: LOY Customer Action Business Service

Business Service User Property:
   
    Old Value: LOY_TXN_STATUS_CD|Queued
   
    New Value: LOY_TXN_STATUS_CD|Acceptable

Use:
This allows us to manually process the Loyalty Transactions which are created by the batch mode.