When setting Ticket Status mapped to Requestor Action, field Completion is auto filled with a date. You expect it to stay blank because the Ticket is now on customer's side and not completed yet.
SAP Cloud For Customer
Reproducing the Issue
Prerequisite: You have already configured SLA setup and there is a Ticket Status mapped to Requestor Action in the system.
- Go to the Service work center.
- Go to the Tickets view.
- Click New.
- Fill mandatory fields.
- Click Save and Open.
- Notice that completion field is blank.
- Click Edit.
- Go to field Status and select any status that is mapped to Requestor Action.
- Click Save.
- Completion field is auto filled with a date.
You have set the Ticket to Requestor Action status.
This is expected system behavior. The Completion field is updated when the assignment status changes from Processor Action to Requestor Action. When status is set to Requestor Action, then from a Technician/Agent's point of view there is no further processing to do and Ticket is completed for now. Furthermore, when status changes from Processor Action to Requestor Action (status is in customer action), SLA clock is paused. Once Customer responds, SLA clock will resume and due dates are updated. This is applicable for Completion Due, Resolution Due and On-Site Arrival.
- Knowledge Base Article 2656925 - SLA Calculation Varies with Reaction Time Maintained in SLA Setup Service Levels.
- SAP Cloud for Customer User Stories > Tickets > Working with Tickets > Resolving and Responding to Customer Issues > Pause SLA Clock.
- Solution Guide for SAP Cloud for Service > Tickets > manage Tickets > Set Up Service Level Agreements for Tickets.
Ticket, SLA, Completion , KBA , LOD-CRM-SRP , Service Request Processing , Problem