Hi Jacques,

From the PSO perspective, the xml definition received for the shift data simply needs to specify a value of true for the split_allowed attribute.  This is listed in the PSO documentation (Scheduling Schema.pdf) in the “Entity: Shift (Input)” section.

I can’t say how you would control that value being passed in from your SAP integration though.  Perhaps someone else in the community might be able to help on that part.

Thanks,
   Carl

For the specific Tasks that you’re sending in, make sure you see the ‘Allow Multiple Visits’ parameter being set to true against them. I’d question why you’re using the RES_SHIFT attributes for splitting activities, as long as the data is correct that’s being sent from Cloud, you shouldn’t need this parameter set as having the Task is usually enough.

Can you try this?

I used a very low level of shift type, so this will apply to all templates using this shift type (and to all resources with any of these templates).

Thanks Alex!

The customer had already set all the activity types to have this variable set to YES, as it is more obvious when creating activity types.  I have changed it as you suggest in Resource Shift Type in the customer’s environment and I will find out today if this solves their problem with unscheduled tasks.

I set up some data in the customer’s cfg environment and the PSO scheduled the tasks by splitting the tasks over multiple days.  Another case closed!  Thank you so much!