Open APIs

Product Characteristics: TMF 620 vs GB922 Product

  • 1.  Product Characteristics: TMF 620 vs GB922 Product

    TM Forum Member
    Posted 10 days ago
    Edited by Igor Veliev 8 days ago
    Hi team,

    GB 922 Product R19, page 39 shows ProductSpecCharacteristic as an entity separated from a ProductSpecification and even reusable for different ProductSpecCharUse objects in same ProductSpecification or in different ProductSpecifications.
    It make sense for example when we have same Characteristic in many different ProductSpecifications and we want to use single association of OfferingPrice with specific value of such a common Characteristic by it's ID.
    With this approach ProductSpecCharacteristic became more like ProductCharacteristicSpecification reusable from different ProductSpecifications.
    So if we need parameters of this ProductCharacteristicSpecification bit tuned in specific ProductSpecification we may reload it with new values in ProductSpecCharUse.



    TMF 620 R19 shows absolutely different approach. ProductSpecificationCharacteristic is not SID's ProductSpecCharUse or ProductSpecCharacteristic (don't be fooled with the same name of composition).
    It is something different which belongs to only one particular ProductSpecifcation and it doesn't have any references (ID) to be associated with common prototype.
    ProductSpecCharacteristic does not have ID of characteristicSpecification.
    Moreover we can see same ProductSpecificationCharacteristicValue in composition under ProductSpecificationCharacteristicValueUse (which looks like SID's ProdSpecCharUse and exists only in Offerings and Prices).
    ProductOfferingPrice is not associated with particular Value but associated with prodSpecCharUse (it's not SID's prodSpecCharValueUse, because it doesn't even have isDefault flag)



    Please help me answer the following questions:
    1. How can we avoid multiple excessive duplicates of characteristic data in Product Catalog with this approach? For example 'color' with dozens of charValues?
    2. How can we avoid multiple excessive OfferingPrice associations with each particular ProductSpecCharacteristicValue via ProdSpecCharValueUse in the meaning of TMF 620?


    ------------------------------
    Igor Veliev
    Netcracker Technology
    ------------------------------