Open APIs

Hi,

When we are associating characteristic to a product specification, what is the best practice ? creating a copy of characteristic in the product_specification_characteristic relation (or) instead of copying, just referring to the characteristic via the id ?

When we take first approach, every time there is any change to a given characteristic, there requires updation to all the specifications that uses this characteristic, which otherwise is not a problem when we are just using the reference.

When we take second approach, when ever we need a change to the definition of the characteristic, but don't want this change for a given set of specifications that are using this characteristic, this referencing might be a problem.

Any suggestions please ?

I am not sure if I understand your question correctly.

ProductSpecification "contains" CharacteristicSpecification (composite relationship). So, I think it is always by value. Isn't it?

On the other hand, if we are using ProductOffering, it can refer to CharacteristicSpecification from another ProductSpecification. So, my idea was to define a universal ProductSpecification to just define all common the characteristics here. We can refer to them from PO using the "ProductSpecificationCharacteristicValueUse" field.

This is a good trade-off as it allows you to use only the required values in the PO while allowing you to expand the list in the common PS as and when you want.

Hi,

I'm also not sure if I understand your question in the context of TMF620.  I can confirm is that both approaches are perfectly fine for TMF620.

you may want to look in the ODA community, it has years of discussions on PSR product catalogue modelling, many of them have links to TMF documentation, video, guide, best practices etc. But you have to do a lot of reading to find the right discussion. You can also ask Aiva, which also check content from the communities.