SAP FSM - Deprecation of old "Checkout" flow

30th June - Deprecating the old "Checkout" flow

As SAP continues to invest in the workflow driven checkout, SAP has decided it is now time to deprecate the old checkout screens on Android, iOS and Windows. By the old checkout screens SAP means the checkout that is triggered with the overflow menu as shown below:

 

old_checkout.png

 

Customers who would like to keep using the checkout should use the workflow step "checkout" or the "report" and leverage the UI improvements SAP has added to these screens, such as HTML reporting and grouped activities based on checkout status (Ready for Checkout, Not Ready, Already checked out).

 

Example for checkout status:

mceclip0.png

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

4 comments
  • Hi Karsten, thanks for the info! What is "checkout status"? Where can I read more about it? I was only be able to find the mention here: https://help.sap.com/viewer/fsm_release_notes/Cloud/en-US for 2102 release. But wondering if more info exists?

    0
    Comment actions Permalink
  • Hi Andrei,

    the activities visible to the technician while doing the group checkout are sorted by the checkout status.
    Some activities might already be ready for checkout while others are already checked out or not ready for checkout at all, depending on the process of the customer.
    I've added you an example screenshot above.

    Please let us know if you need further explanation. 

     

    Cheers
    Karsten

    0
    Comment actions Permalink
  • Hi Karsten,
    Thanks for the explanation. I think I understand now what you call "checkout status". This is the one that can be additionally controlled via company setting CoreSystems.ResourcePlanner.ServiceAssignmentCheckoutCondition.

    0
    Comment actions Permalink
  • Hi Andrei,

    CoreSystems.ResourcePlanner.ServiceAssignmentCheckoutCondition is a company setting designed to give you the ability to force technicians to complete certain tasks before being able to checkout any activity.
    For example you can force technicians to fill a UDF or TimeEffort before being able to checkout.

    The checkout status on the other hand refers to the Group Checkout where more than one technician works on a service call.
    While regular technicians will only mark their activity as "Ready for Checkout", one leading technician will then do the actual checkout for all activities.
    Therefore the sorting for the checkout status, so the leading technician can easily identify the activities marked as "Ready for Checkout" and can also see if some technician missed to mark their activity so far, leading to the activity being shown as "Not Ready".
    You can read more about Group Checkouts here:
    https://help.sap.com/viewer/fsm_mobile/Cloud/en-US/group-checkout.html?q=Group%20Checkout

    Cheers
    Karsten

    0
    Comment actions Permalink

Please sign in to leave a comment.