OSM Improvement proposal - Improvement of date setting IP/IL

"It seems that the dating of IP/IL in COW is most often not actively used. This is stupid and means that you have poorer control and overview than necessary. Work is being done with other digital tools that will happen data flow from COW which depends on the is there order in the isolations that are pending approval and that are active. I have given it some thought and am now wondering if it would have been possible to automatically set the data span on IP/IL from associated WOs. And if you have several WOs associated with that you then get the date from the earliest basic start and latest finish date of these. That COW then updates the date on the IP/IL if the WO is rescheduled (and dates are changed) as long as the IP/IL is not active. Then you have to make a correction as you do today. It must also be possible to override the date manually as an addition if you have additional needs. I think this could be a fix that could provide gains in increased control over IP/IL here so that you can filter on dates as well --- Extra info from Ronny: In addition, I believe that this requires an extension of the interface to SAP as we do not currently receive the dates from SAP. Possibly the IP dates and must be set from the scheduling app in SAP, i.e. there must be an API on the CoW side that can receive IP dates from an external source."