Hardware Asset Management - "License Opt in" shows NA for product models mapped only to a custom child model category<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Table of Contents IssueSymptomsCauseHow the field is evaluated (OOB logic)Why custom child categories without a OOB parent category show NACommon misconceptions (and clarifications) "NA means the model is not eligible for HAM.""Normalization won’t work when the field shows NA." ResolutionRelated links Issue When a hardware product model is mapped only to a custom model category that is a child of an opted‑in OOB parent model category, the License Opt in field (norm_license_opt_in) on the product model shows NA instead of Yes. Removing the OOB parent category from the product model and leaving only its custom child category causes norm_license_opt_in to change from Y to NA. Even though license opt in displays NA for the custom model category, HAM licensing and normalization features continue to include models whose effective eligibility comes via the opted‑in OOB parent category. Symptoms Map a product model only to a custom child category that lacks resource_category, save, and observe norm_license_opt_in → NA.Add the opted‑in parent category and save again → Y. Cause This is working as designed. The License Opt in field on the product model reflects only the direct resource‑category association of the mapped model categories. It does not inherit from parent categories. If the mapped custom model category itself does not have a resource_category populated, the product model’s norm_license_opt_in evaluates to NA, even when the parent model category is opted in. How the field is evaluated (OOB logic) The logic is performed by the following script include: HAMUtils Single model category mappedIf the product model has one model category, the platform fetches that category and returns: Y if the category’s resource_category.opt_in == trueN if the category’s resource_category.opt_in == falseNA if the category has no resource_category set. Multiple model categories mapped Y if any mapped category has resource_category.opt_in == trueNA if any mapped category has no resource_categoryN if any mapped category has resource_category.opt_in == falseDefault NA A custom child category without resource_category therefore forces NA unless another mapped category explicitly returns Y or N first. Why custom child categories without a OOB parent category show NA Custom child categories typically do not have resource_category populated OOB. When a product model is mapped only to such a custom child category, the logic above evaluates to NA. This does not negate the effective eligibility via the opted‑in parent; it only reflects that the direct association is missing on the child. Common misconceptions (and clarifications) "NA means the model is not eligible for HAM." Eligibility via hierarchy (opted‑in parent) still applies even when the field shows NA. "Normalization won’t work when the field shows NA." Normalization and HAM workflows consider effective licensing through parent categories; the field’s NA does not, by itself, block those flows. Resolution Keep the opted‑in parent OOB model category mapped to the product model. If you would like the License Opt in field to display Y for operational/reporting purposes, keep (or add back) the parent OOB category alongside the custom child category so that the logic discussed above sees a category with resource_category.opt_in == true. Related links Hardware Asset Management licensing Opt-in or opt-out of HAM license resource categories