7 Replies Latest reply: Jul 10, 2012 4:24 AM by Dhananjay Singh Sengar RSS

Merge Precedence group and sets in reconciliation engine

Dhananjay Singh Sengar

Hi Everyone,

 

Can anyone please let me know the significance and usage of Precedenace Group and Dataset Merge Precedence Set as I am not able to understand their individual usage and collective roles in reconciliation process.

 

Can anyone explain this concept in detail.

 

Thanks.

Dhananjay

  • 1. Re: Merge Precedence group and sets in reconciliation engine
    Devendra Yadav

    Will Suggest to go through “Reconciliation and Normalization Guide”.

    I will give you an idea about precedence.  Recon Engine merges data from various sources into single Golden Dataset (BMC.ASSET), while doing merge which value from which dataset needs to be considered for golden data set is decided based upon Dataset Merge Precedence. Data with higher precedence value goes in Golden dataset . Precedence can configured at CLASS / ATTRIBUTE label as well.

     

     

    Thanks & Regards,

    Devendra Yadav | BMC Software |Phone: +91-20-40175390 |Fax: +91-20-40175001

  • 2. Merge Precedence group and sets in reconciliation engine
    Dhananjay Singh Sengar

    Hi Devendra,

     

    Thanks for the response.

     

    If there is only one data source i.e. Dataset then do we need to create precedence group and precedence set?.

     

    Thanks $ Regards,

    Dhananjay Singh Sengar

  • 3. Merge Precedence group and sets in reconciliation engine
    Nikhil Warrier

    Hi Dhananjay,

     

    Even in the case, you have one source dataset, you would still need the precedence groups and sets.

    To illustrate,

     

    If you have a source dataset called Source1, and you have the dataset precedence set to 100 (This is the default value). BMC.ASSET (normally the target for reconciliation activities) also has a default precedence of 100.

    If the precedence value is greater or equal to the target precedence, values are copied from the source to the target.

     

    Now,

    You may want to restrict the copy of certain attributes, to the Target.

    For e.g. You may set the value of Manufacturer as 10, in the Source Precedence Group.

    This will mean that all values from Source1 except Manufacturer will get copied to the target.

     

    So the way you would have the Precedence configured is

    Precedence Association set > which can have multiple Precedence Sets (Also called Precedence groups in the User tool terminology) > which in turn is a collection of Precedence rules mapped to a dataset.

     

    If there is a specific configuration you would want to achieve, please describe it and we can build the precedence set and rules.

     

    Thanks,

    Nikhil.

  • 4. Merge Precedence group and sets in reconciliation engine
    Dhananjay Singh Sengar

    hi Nikhil,

     

    Thanks for the response.

     

     

     

    We have two source datasets - say Source1 and Source2

     

    We have two attributes "Temp_Char1" and "Temp_Char2" in both the datasets.

     

    Now I want to copy Temp_Char1 from Source1 into BMC.ASSET and Temp_Char2 from Source2 into BMC.ASSET then what should be my precedences in the respective Dataset.

     

    What is the difference between group precedence value and attribute/class level precedence?. On what basis these values are compared?

     

    Thanks $ Regards,

    Dhananjay Singh Sengar

  • 5. Merge Precedence group and sets in reconciliation engine
    Amey Bagwe

    Hi Dhananjay,

     

    I think Nikhil has described it perfectly ...more help below...might help you understand better..

     

    https://communities.bmc.com/communities/thread/39084

     

     

    -Amey.

  • 6. Re: Merge Precedence group and sets in reconciliation engine
    Nikhil Warrier

    Precedence can be set at 3 levels and are compared against the target dataset in a reconciliation job.

    So if Source1 is source and BMC.ASSET is target, then values are compared between Source1 and BMC.ASSET

    The top level is at dataset precedence value- meaning everything in the dataset will obey this value

    Reconciliation Engine also enables a user more granularity in setting rules, with the lower level values overriding the top level ones.

    The next level is Class Precedence level - meaning that even if Dataset has a particular value, you can override it with a different value for a particular class. e.g. Dataset can have value 100, but you can chose a ComputerSystem class to have value 800, to ensure it is copied even if Target is 200. (Since 100 < 200, but 800 > 200)

    You can still go one step further to set attribute level precedence, for e.g. MarketVersion Attribute for a Product class. This value of attribute precedence will override the values of Class and Dataset precedence. If there are no class and attribute level precedences defined, then the top level precedence value will apply.

     

    Now for the scenario you wish to achieve,

     

    Sample Precedence values can be

     


    Source1Source2BMC.ASSET
    Dataset Precedence Value100100100
    Temp_Char1 Attribute Precedence Value80010Not defined (Meaning Dataset Precedence value above will take effect)
    Temp_Char2 Attribute Precedence Value10800Not defined (Meaning Dataset Precedence value above will take effect)