Self-solved: Assets not created for Operating Eq and Facility Hardware CIs - on import and manually.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2024 03:59 AM - edited 02-18-2025 03:55 AM
Hey Asset and CMDB superstars,
We're importing CIs into cmdb_ci_facility_hardware and cmdb_ci_oe among other classes. For these two, oddly, assets are not getting created. Not just from the import but also when I create CIs manually or use Create Assets button on Model categories. No issues with assets from CIs that point to alm_hardware table.
I've done hours of debugging - below is what I've checked. Where else would you check? Is there a way to see what is causing the error or why the asset creation failed exactly (below is also what Asset Creation Queue is telling me.
Asset creation debugging checklist:
| cmdb_ci_facility_hardware | cmdb_ci_oe |
Model category exists for the CI Class | yes | Yes |
Two model categories exist for the same CI class | No | No |
Asset class defined in the model category | Yes | Yes |
Correct asset class defined in the model category | yes | Yes |
On model category, Enforce CI verification is false | Is false | Is false |
Model of the CI is NOT set to Do not create assets | Leave to category | Leave to category |
Create Asset on Insert BR are AssetandCI SI are active and not modified | BR: Active and never updated | BR: Active and never updated |
Asset is inserted by values are empty | No – there is no asset at all | No – there is no asset at all |
Update: A colleague of mine realized the client didn't have HAM Pro or EAM license. As a result, for non-standard model categories based on oe and facility hardware model, assets were not being created. The solution was to reclassify them to Hardware models and use baseline models / tables.