---
schema_version: "1"
id: d51263b210129be02bf727d44092ea4c4c8ad3877387460b599e2f7b5796b879
title: Handle Cost Components in Assets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_handle_cost_components_in_assets.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_handle_cost_components_in_assets.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9873b751f52662c29d2c93e3e007f4de66797b20704f436c1144c5186b3bdeef
description: When you retrieve Assets to present to an Energy customer, typically for tariff details, it's a best practice to ensure that parent Assets and cost components nest properly.
products:
  - Communications
  - Media
  - Energy and Utilities
release: "264"
---
# Handle Cost Components in Assets

When you retrieve Assets to present to an Energy customer, typically for tariff details, it's a best practice to ensure that parent Assets and cost components nest properly.

This Omistudio Data Mapper Extract shows how to exclude cost components from the parent level using this filter:

```
vlocity_cmt__LineNumber__c NOT LIKE "."
```

And include them at the child level using this filter:

```
vlocity_cmt__LineNumber__c LIKE "."
```

![Asset Details](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-comms_media_energy_managed-264-0-0-production-enus/ff4079f6-a384-475c-b863-578bbbb0ef9b/resources-product/images/drgetassetdetails.png)

You can use a similar structure to nest cost components when presenting Opportunities, Quotes, and Orders.