Open APIs

 View Only

  • 1.  TMF620 - productOfferingTerm&productSpecification

    Posted Aug 01, 2023 10:40
    Hello,
     
    We have an usecase where a productOffering can have multiple productOfferingTerms. This is already supported by the TMF620.
     
    However, due to our techincal data model (already in place), a the productSpecification associated with the productOffering may variate accordingly with the productOfferingTerm. Meaning that a productOffering can have more then one productSpecification.
     
    Since the api only allows to have a relation of 1to1 between the productOffering and the productSpecification, there's another way to solve this issue?
     
    Regards,
     
    Pedro Martins
    Celfocus


    ------------------------------
    Pedro Martins
    Celfocus
    ------------------------------


  • 2.  RE: TMF620 - productOfferingTerm&productSpecification

    Posted Aug 03, 2023 06:58

    Hi,

    Since the api only allows to have a relation of 1to1 between the productOffering and the productSpecification, there's another way to solve this issue?

    Actually, the relationship is 1:M between PS and PO not 1:1.

    we have the same situation with our BSS and it's already supported by TMF information framework using the composite entity pattern. GB922 - Product guide has examples, search for CompositeProductSpecification.

    the representation of CompositeProductSpecification is available in TMF620, but they changed the name to:  bundledProductSpecification

    alternatively, if you need a non-composite bundle of PS, you can use productSpecificationRelationship, which has an extra and very usefull attribute called relationshipType



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

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

    Original Message


  • 3.  RE: TMF620 - productOfferingTerm&productSpecification

    Posted Aug 04, 2023 10:37
    Hi,
     
    You are right, the relation is 1:N.
     
    For our usecase is not possible to use the composite PS because a compositePS implies that all the PS are to be used for one PO.
     
    In our case we need to return a different PS according to the PO term.
    But, for example, if one request requires one specific PO, without specifiyng the term, it is not possible to return the multiple PS that may be associated with the PO. 
     
    It is possible to use the relationship between PS to solve this? how can we map a relationship between PS accordingly to the PO term?
     
    Regards,
     
    Pedro Martins
    Celfocus


    ------------------------------
    Pedro Martins
    Celfocus
    ------------------------------

    Original Message


  • 4.  RE: TMF620 - productOfferingTerm&productSpecification

    Posted Aug 07, 2023 04:31
    Edited by Matthieu Hattab Aug 07, 2023 04:30

    I don't know what your terms are. I use terms in the sense is was defined by TM Forum in the Information model. and Terms should only be associated to PO and POP.

    I don't quite understand "if one request requires one specific PO, without specifiyng the term".

    end of the day, If your PO has a Term, then requesting a specific PO will always return the associated Term, you don't need to specify the term.

    again, there is no direct link between term and PS, since a (simple) PO must have a PS and PO have terms, you have a indirect relationship (via PO) between the PS and the Term.

    If you have multiple PS and they depends on the Term, you could implement multiple PO, one per PS.



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

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

    Original Message


Related Content