Open APIs

 View Only
  • 1.  TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Feb 20, 2020 02:31
    Dear All,

    I am going through the TMF622 Product Ordering API and need clarifications on the following parameters:
    • orderTotalPrice - Where ordertotalprice is used? What is the underlying UC ?
    • requestedCancellationDate - Is this intended for future dated cancellation of an order ? What's the CSP usecase for this ?
    • effectiveCancellationDate - What is the underlying usecase ?
    Thanks in advance !

    ------------------------------
    Chandra Bommanaveni
    Oracle Corporation
    ------------------------------


  • 2.  RE: TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Feb 20, 2020 08:55
    Hi Chandra
    OrderTotalPrice is used to describe price at Order level. From my perspective the UC is very limited: it could be when you want to provide some discount at order level and not at order item level. If for example I award you a 11% discount on your order total - because of rounding for example - it is probably better to handle this via the orderTotalPrice.

    For the 2 Cancellation date attributes they are part of the CancelProductOrder.
    requestedCancellationDate is the datetime when the request for cancelling an order has been created (I see it as a timestamp for this request)
    effectiveCancellationDate is the datetime when vendor/supplier accept the request for cancellation (and cancels the order).

    Hope it helps

    Ludovic


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



  • 3.  RE: TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Feb 25, 2021 18:10
    Edited by Rati Mehrotra Feb 25, 2021 21:48
    Hi @Ludovic Robert, @Kamal Maghsoudlou

     Looking at TMF 641 , the definition of CancelServiceOrder.effectiveCancellationDate is "Date when the order is cancelled". Since the cancelServiceOrder task is for assessment of cancellation, the definition does not look correct.

    The definition that you have provided "effectiveCancellationDate is the datetime when vendor/supplier accept the request for cancellation" looks correct.

    This the same definition in TMF 622- Product Ordering API. Screenshot below :


    Please confirm. 

    Thanks,
    Rati
    cc : @Uma Lakshman

    ​​

    ------------------------------
    Rati Mehrotra
    Telstra Corporation
    ------------------------------



  • 4.  RE: TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Feb 26, 2021 03:10
    Hello Rati

    We has some exchange within the team since my post on this one year ago. The CancerServiceOrder is a task to" cancel an order" (and not "a request to cancel an order"). This change some attribute meaning and the lifecycle. With this pattern then the CancelServiceOrder.effectiveCancellationDate is the date when the service order has been cancelled - and not as I stated one year ago the date when vendor/supplier accept the request for cancellation. Same will aply on the lifecycle --> this is a state to track cancelling progress (and fail means that server side deny the cancel).

    Hope it is clear now (and simpler).

    Ludovic

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



  • 5.  RE: TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Feb 28, 2021 19:52
    Hi @Ludovic Robert,

    Thanks for your response.  So as per the definition provided by you , the cancelServiceOrder task is for 'cancelling the task' and not an 'assessment ​for cancellation'  as is mentioned in the document for TMF 641 v4.1

    Two queries for the above :
    • In which version of the user guide will  the definition for cancelServiceOrder task be updated.
    • Does this mean that the cancelServiceOrder  state change event with state=Done will be sent after serviceOrder state change event for state =cancelled is sent.  In  some scenarios  cancellation assessment could be completed earlier but the order cancellation might take longer time (like requiring  manual intervention).  In this case, does the provider  need to hold on to the cancel service order task until the service order is actually cancelled.

    Thanks again for your support.
    cc: @Kamal Maghsoudlou

    Rati
    @Uma Lakshman​​​​

    ------------------------------
    Rati Mehrotra
    Telstra Corporation
    ------------------------------



  • 6.  RE: TMF622 Product Ordering API clarifications needed

    TM Forum Member
    Posted Mar 01, 2021 12:00
    Hello Rati,
    For the first point probably we dropped the ball with release 4.1 to not fix this. Because all new feature were on the serviceOrder itself we did not looked on cancelServiceOrder. I will check open Jira and add one if required.

    For the second case I guess yes. My view:
    We have a ServiceOrder inProgress
    1. A cancel Service Order is triggerred --> CancelServiceOrder Accepted
    2. Back end begin to check if service order could be cancelled:
      1. ServiceOrder shiftes to AssessingCancellation
      2. CancelServiceOrder shiftes to InProgress
    3. (alternate 4) - Back end could not cancel:
      1. ServiceOrder shiftes back to inProgress
      2. CancelServiceOrder shiftes to TerminatedWithError
    4. (alternate 3)- Back end OK to cancel
      1. ServiceOrder shiftes to PendingCancellation
    5. Service Order cancelled
      1. ServiceOrder shiftes to Cancelled
      2. CancelServiceOrder shiftes to Done
    Seems to me that combinaison of CancelServiceOrder/ServiceOrder state provide us the way to distinguish at which step we are.
    Looking for your feedback

    Hope it helps
    Ludovic

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