on 02-07-2017 8:03 AM
Hi experts,
I have the problem that since release 1702 the release for scheduling in the test system is not working. I got the error message: Item - 10 not marked as Scheduling relevant, although the item processing code is assigned to Service.
Before the upgrade 1702 the release for scheduling worked with the item processing time we use, so don't know what I should/can change.
Thanks for help.
Best regards,
Deborah
Hi all,
I now got the response from SAP.
Since release 1702 there is a new functinality called "scheduling method" (with the values: appointment, auto dispatch, manual). The flag in the ticket items "scheduling relevant" is hidden and read-only by default, because this should no longer be used. If you chose a scheduling method before releasing for scheduling, then the error won't occur. This scheduling method can be maintained for every item processing code in the fine tuning activity: tickets for customer- maintain item processing codes.
However, for me this change is not really good documented in the admin guide...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any updates? Not clear how we can work with the Resource Scheduler.
Please share any documentation step-by-step on how to work with Resource Scheduler.
BR,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any progress`? I got the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The same problem we experience here.
The checkbox with "Relevant for scheduling" on items is hidden since the update (we made it visible via edit master lay-out), and is greyed out wherefore we can't edit relevancy for scheduling
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Deborah,
We have not identified any such upgrade related regression. Please report an incident to Support for further investigation.
I have also tested in our internal 1702 tenants and the feature works fine.
Thank you.
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.