SW Model.Product Type = Child as opposed to Suite Component

[Brigham]

What is the difference between Product type = Child and making a SW Model a suite component of another SW Model?

I get that being a suite component we can readily see the relationship to the suite parent SW Model. And despite having Product type = Child, there is nothing to show what the product is a child of.

Child is not considered in reconciliation and Suite Components are generally licensed under their Suite Parent (though there are certainly exceptions where a suite component may also be licensed independently.

Real world example, bos.mh (IBM Mail Handler) is installed as part of bos.rte (IBM AIX operating system), but IBM Mail Handler is Product Type = Non Licensable (not Child) and further Content Library does not make bos.mh and suite component of bos.rte.

Setting aside reconciliation, there is also consideration for the Restricted flag which triggers Reclamation Candidate tasks. But if I set IBM AIX to Restricted = TRUE, that does nothing about IBM Mail Handler, and there is no way for me to see that I should be aware of Mail Handler as a child or suite component of IBM AIX.

Looking for ideas on how to solve this or if I am missing something within SN that should handle this kind of situation. Thanks

[Engelica Adalia · Accepted solution]

@Brigham That's right. Child is not considered in reconciliation and Suite components are licensed under the Parent (this is where you set the inference percent) or if a component can be licensed separately. Content Library only identifies the product type (child, licensable, not licensable, driver, patch etc.) but it will not show you the other components that comes bundled with a particular product - you have to identify this manually when you create your model.

In your example, I would add the IBM Mail Handler as a suite component of IBM AIX and marked both records as Restricted. Again, since the other one is just a child, it will not be included in the reconciliation result.