Open APIs

 View Only

  • 1.  GB922_Product_v21.5

    Posted Jul 18, 2023 08:07

    Hi,

    I have been going through product management GB922 and stuck at the below two items:

    1. ProductSpecificationRelationship
    2. Product Specification grouped into below:
      1. product line
      2. product category

    I don't clearly understood the idea of the above features. Can you help to give me the real time use case of how to use the above features and how should we design the database model. Apologies if my question doesn't make sense. I am happy to reply back for any further questions.



    ------------------------------
    Mahesh Kothamasu
    SP Telecommunications Pte Ltd
    ------------------------------


  • 2.  RE: GB922_Product_v21.5

    Posted Jul 19, 2023 05:11

    Hey there,

    For your first point, check out IG1228. Take a look at the product model described in section 6.3.1 (Global Catalog view). You'll find ProdSpec relationships there. For example, the TV channel ProdSpec requires the Connectivity ProdSpec, which means you need internet connectivity to watch TV.

    These rules are stored in the product catalog. Your offer configurator, CPQ, "order capture application" should read these rules from the catalog and enforce them. This ensures that customers can't buy a TV without internet, you know?

    Oh, and just so you know, TV and Internet ProdSpec don't have to be bundled. We have a rule that enforces it whether they are sold separately or in a bundle. Also, they don't have to be bought together in the same order. Someone could get Internet last year and then buy a TV this year.

    As for your second question, SID mentions that sometimes it's necessary to group product specifications. But honestly, I've never felt the need for it. We've never had enough ProdSpec to warrant grouping. And by the way, the product catalog API doesn't support it either. Instead, they group product offerings (not prodSpec) in "product categories."

    Lastly, I suggest using the Excel version of GB922. It's much easier to find entities, their definitions, and all that stuff compared to the Word document.

    Hope that helps!



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Lyse Platform
    ------------------------------

    Original Message


  • 3.  RE: GB922_Product_v21.5

    Posted Jul 19, 2023 22:17
    Edited by Mahesh Kothamasu Jul 19, 2023 22:20

    For point 1,

    So, IG1228 6.3.1 shows TV Channel requires Connectivity. Keyword here is 'requires' which is a type of ProductSpecificationRelationship.

    As per GB922, there are different types of ProductSpecificationRelationships : migration, exlusivity, dependency, substitution. Can we treat 'requires' as the sub type of 'dependency' type ?

    And data model will be something like below ? 

    relationship_type from above will be something like 'requires'. 

    For point 2,

    Understood. Thanks for your insights.



    ------------------------------
    Mahesh Kothamasu
    SP Telecommunications Pte Ltd
    ------------------------------

    Original Message


  • 4.  RE: GB922_Product_v21.5

    Posted Jul 21, 2023 06:31

    Hi,

    Different people write different document (IG1228, TMF620 etc) and sometimes they like to use their own words.
    "depends on", "requires" "prerequisite", "dependency" are all the same.
    There is no sub-type, just type but if you want to extend your model or API, feel free to do so.
    so use "requires" if you want, as long as the service that will consume this data understands it.



    ------------------------------
    Kind regards,

    Matthieu Hattab
    Lyse Platform
    ------------------------------

    Original Message


Related Content