Open APIs

Expand all | Collapse all

Migrating to TMF648 - Quote Management

  • 1.  Migrating to TMF648 - Quote Management

    Posted Nov 30, 2020 01:24

    Hello Members!

    Is it possible to migrate our existing inhouse APIs to TMF648 Specs without considering other TMF specs like catalog, productOfferingQualification, serviceOfferingQualification, agreementManagement, etc,.

    Basically we are looking at migrating our Quote systems alone to TMF specs and not to disturb the other systems for time being (Atleast now!)

    PS: I referred the TMF648 specs and found other systems like catalog, product & service offering, agreement, billing management APIs are interconnected with the Quote requests & so I came up with this question.



    ------------------------------
    Eswar Babu
    Verizon Communications
    ------------------------------


  • 2.  RE: Migrating to TMF648 - Quote Management

    TM Forum Member
    Posted Nov 30, 2020 05:03
    Hi Eswar
    The Open APIs are interrelated in the sense that we use a common data schema to generate the swaggers and user guides. So (for example) entities in the Quote Management API may well have references to entities (Customer, Product Offering, etc.) that are managed by other APIs.
    However the swagger for each API is self-contained, there are no unresolved references to other swagger files.
    You could migrate your inhouse API for quotes to the TMF648 API using the published swagger, your challenge would be how to fill the entity references for the other entities - so you would need to at least understand how these entities map into your other systems and use (for example) the primary key as the id in the ref structures. You would presumably not be able to populate the hrefs (e.g. for customer) with an actionable uri since you are not implementing the other APIs. Similarly you would not be able to support the depth query string directive to expand other entities.
    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: Migrating to TMF648 - Quote Management

    Posted Dec 01, 2020 06:46

    Hi Jonathan
    Yes I agree with your points. It certainly helps. In our case, we do follow a completely different business process than what needs to be there for TMF standards. For example, agreement, billingAccount & productOfferingQualification entity needs to be created (before quote) and the corresponding entity id should be specified in the Quote request. But we do have a different approach where those entities are created as an internal part of quoting process rather than as a separate entity. 

    Further, on exploring TMF648 API, quoteItem is the only mandatory attribute of the request, so can I extend the request with attributes (not available in TMF) which is required for our inhouse API? so, this would help us to follow our internal business process as well as the TMF standard.

    Is my assumptions correct?



    ------------------------------
    Eswar Babu Kutuva Naraynamoorthy
    Verizon Communications
    ------------------------------



  • 4.  RE: Migrating to TMF648 - Quote Management

    TM Forum Member
    Posted Dec 01, 2020 13:00
    You can certainly extend your implementation of the API as per your business needs - see the design guidelines document set TMF630 for more details on how to do this while maintaining conformance.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------