Open APIs

 View Only

  • 1.  Trigger API endpoint for submitting TMF648 Quoting platform to TMF622 Ordering platform

    Posted 20 days ago

    Our TMF648 compliant Quote Management platform has POST-Quote and PATCH-Quote APIs. 

    • POST-Quote is used for creation of TMF648 compliant Quote,
    • PATCH-Quote is used for configuration of TMF648 compliant Quote. 

    TMF622 compliant Order Management platform has POST-ProductOrder endpoint that accepts TMF622 compliant Order.

    But we are trying to understand what is the TMF648 endpoint that accepts the id/payload of a TMF648 compliant Quote object, converts it into a TMF622 compliant Order object and finally calls the POST-ProductOrder endpoint.

    Currently we have a POST-SubmitQuote API. It is not TMF compliant. But this API accepts the id of a Quote object, converts it to an OSSJ Order object and finally submit to Order Management via a TMF non-compliant API. 

    We can spawn a TMF compliant variant of existing POST-SubmitQuote API. This API will only accepts the id of a TMF compliant Quote, converts it to a TMF622 compliant Order object and finally submit to TMF622 compliant POST-ProductOrder API. Is this the standard industry practice? 

    Thanks, Mujtaba. 



    ------------------------------
    Mujtaba Nowshad
    Hansen Technologies
    ------------------------------


  • 2.  RE: Trigger API endpoint for submitting TMF648 Quoting platform to TMF622 Ordering platform

    Posted 15 days ago

    Hi Mujtaba, This is a standard and widely adopted practice.

    TMF648 (Quote Management) and TMF622 (Product Order Management) are intentionally separated by design. The conversion of a compliant Quote into a compliant ProductOrder and invoking POST /productOrder (TMF622) is typically handled through an orchestration layer or via an implementation-specific action on the Quote domain.

    There is no mandated "native" TMF648 endpoint that performs the conversion automatically. So introducing a TMF-aligned variant of your existing POST-SubmitQuote (that accepts a TMF648 Quote ID, maps it to a TMF622 ProductOrder payload, and invokes the compliant TMF622 endpoint) is aligned with common industry implementation patterns.

    Thanks



    ------------------------------
    Goutham Babu
    API Product Owner
    TM Forum
    ------------------------------

    Original Message


  • 3.  RE: Trigger API endpoint for submitting TMF648 Quoting platform to TMF622 Ordering platform

    Posted 12 days ago
    Edited by Mujtaba Nowshad 12 days ago

    Hello Goutham, thanks for your response.

    For a synchronous flow, spawning a TMF compliant variant of POST-SubmitQuote API that accepts ID on TMF648 Quote, internally coverts to TMF622 Order and finally submits to TMF622 compliant POST-ProductOrder API sound like decent plan, thanks for confirming that synchronous flow will align with common industry implementation patterns.

    For an async flow, this is the solution I would propose - 

    Once customer accepts/approves a Quote, TMF648 complaint PATCH-Quote API is used to change TMF648 Quote's "state" field to approved/accepted. This state change will raise a "QuoteStateChanged" kafka event. We will develop a listener-microservice that will convert the TMF648-Quote to a TMF622-Order and also call the TMF622 compliant POST-ProductOrder API. Finally, upon successful submission, Order capture platform will need to call TMF648 complaint PATCH-Quote API to update Quote.state to "submitted".

    Is this the standard async industry practice? 

    Thanks.



    ------------------------------
    Mujtaba Nowshad
    Hansen Technologies
    ------------------------------

    Original Message


Related Content