Open APIs

 View Only
  • 1.  TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 05, 2019 11:12
    Hello,

    The TMF641 orders or order items state can be "Failed" or "Partial", but there is apparently no attribute to convey the reason of the service ordering failure (e.g. "reason", "error message", else ...). Is it implementation specific or can it be standardized and added in a next TMF641 specification version?

    Thanks
    Alexandre

    ------------------------------
    Alexandre Meynaud
    Hewlett Packard Enterprise
    ------------------------------


  • 2.  RE: TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 05, 2019 15:44
    Hi Alexandre
    Subject to correction by @Ludovic Robert - sprint leader for API release 19.5, I don't believe we have any substantial corrections planned for TMF641 Service Order management in this release.
    You can certainly add the failure reasons in your own extensions to the API (using the defined extension pattern), and you could open a CR for correction in the standard spec in the future.
    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: TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 06, 2019 04:04
    We faced the same requirement to convey the reason code/desc and we re-used eventId and eventDescription for this purpose to remain compliant to API specs.


    BR,
    Kailash Mali
    T-Mobile NL


    ------------------------------
    Kailash Mali
    Ericsson Inc.
    ------------------------------



  • 4.  RE: TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 06, 2019 05:54
    Thanks for the hint Kailash. We can indeed reuse/recycle other attributes for another purpose, as long as both the client and server apps agree on the new semantic (which is btw the role of a standard). Your example is for notification events (ServiceOrderStateChangeNotification), but I was more thinking about the ServiceOrder GET result. Did you also reuse one of the TMF Order attribute (e.g. "description") to put the order rejection reason: "Order rejected - No free lines available"?
    Cheers
    Alexandre

    ------------------------------
    Alexandre Meynaud
    Hewlett Packard Enterprise
    ------------------------------



  • 5.  RE: TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 06, 2019 06:50
    Hi Alexandre, For GET operation, we will indeed need an additional attribute to share the reason (code/description) to the consumer. We did not implement a GET operation with reason so far.

    BR,
    Kailash

    ------------------------------
    Kailash Mali
    Ericsson Inc.
    ------------------------------



  • 6.  RE: TMF641 reason/message for a failed order

    TM Forum Member
    Posted Nov 06, 2019 11:17
    Hello
    We got same requirement in the ONAP/External API component and we add an orderMessage structure.
    But then we reported this 'extension' to TMF but not get an approval to add this because it could bring confusion with note that already exist.
    Probably - and like mentioned by @Jonathan Goldberg- you can leverage the polymorphic extension.

    If we have to do it it again in ONAP/extAPI we will probably create an orderMessage structure as a note specialization and use note.@type as discriminator to rout to standard note or to orderMessage structure.

    Hope it helps
    Ludovic


    ------------------------------
    Ludovic Robert
    Orange
    My answer are my own & don't represent necessarily my company or the TMF
    ------------------------------