Enable relationship aggregation The Process Last Month CI Costs scheduled job processes costs of configuration items. To start aggregating expenses to parents, identify the relationships to use for aggregation. Because there are many options for CMDB relationships, using all available paths for aggregation is generally not efficient. About this task You can have multiple relationships for each child class. For example, to enable only certain relationships or parent classes, create a new record for each type and class combination paired with the child class. When an expense line is generated from a configuration item cost, the parents of the configuration item are evaluated. The parent class and relationship type are compared to the list of relationship path records to see if there is a match to use for aggregation. If there is a match, an expense line is generated for the parent configuration item. The process repeats for all parents until there are either no parent relationships or the relationships in place do not meet the criteria defined in the relationship path records. Procedure Navigate to Cost > Administration > Relationship Paths. Click New. Fill in the fields, as appropriate. Field Description Active Check box that indicates whether the relationship path is enabled. Child class The child configuration item class. This class is the source of the expense generated during configuration item cost processing. All parent classes Check box that indicates whether relationships to all parent classes are processed. Parent class A valid parent CI class for the selected child class. Available only if All parent classes is selected. All relationships Check box that indicates whether all relationship types between the child and parent classes are processed. Relationship type The type of relationship to process between the child and parent classes. Available only if All relationships is selected. What to do next When a configuration item has multiple parents that have valid relationship paths, the amount aggregated to each parent is split to prevent over-aggregation of a item cost. When evaluating parent relationships to active relationship paths, the aggregation counts the total number of valid relationships. The expense line amount from the child configuration item is evenly divided among the number valid paths and that amount is used when creating the inherited expense line for the parent.