Standard identification and precedence rules for reconciliation jobs
- Configuring standard identification rules for reconciliation
- Configuring standard precedence rules for reconciliation
Standard identification and precedence rules can simplify the process of creating reconciliation jobs.
These standard rules work with all classes in the Common Data Model (CDM) and BMC extensions. They identify each class using attributes that typically have unique values, and they merge based on precedences set for BMC datasets. Standard reconciliation jobs always use these standard rules, but you can also use them when you create a custom reconciliation job.
The standard identification rules use BMC.ASSET as the production dataset, and they assign a priority level to one or more unique attributes for each class. If the Reconciliation Engine cannot match a CI based on the first attribute, then it uses the secondary attributes. If a class has no standard identification rule, the Reconciliation Engine uses the BMC_BaseElement attributes.
For example, for the BMC_Product class, TokenId is the primary attribute used to identify identical CIs in different datasets. If the Reconciliation Engine cannot find a match among CI instances using the TokenId attribute, the Reconciliation Engine uses Model and MarketVersion. If no match is found using the Model and MarketVersion attributes, the Reconciliation Engine uses VersionNumber and Name.
Examples of attribute priorities
Attribute | Priority |
|---|---|
| 1 |
| 2 |
| 2 |
| 3 |
Name | 3 |
When a new dataset is created a precedence of 100 is assigned to the dataset.
For example, in the BMC Configuration Import dataset, the BMC_Memory class has a precedence of 800. Because all datasets have a precedence of 100 and no other dataset has a precedence defined for BMC_Memory, data from BMC Configuration Import overwrites data from other datasets when merging BMC_Memory instances.
Comments