Writeback of plan updates in Maintain to SAP

Hello @Liv Hagen! This is a much requested feature and part of Maintains strategy to support. Curios to hear more about the writeback scenarios voters here would be most interested in!

@Marius Biermann The objective is to avoid having to use two systems to accomplish detailed planning : SAP & MAINTAIN. SAP remains the ‘source of truth’ for much of the data, but detailed planning should happen in MAINTAIN where other contextualized information is available. The Notification - Work Order creation - detailed planning /scheduling - execution - recording of time spent & materials used workflow needs careful consideration due to a lot of master data residing in SAP which influences ‘what planning can be done in which system’ unless a lot of master data is synced between systems. Perhaps a general philosophy needs to be defined as a first step to define the broad split in functionality between SAP & MAINTAIN.

Got it. My current take is that we should focus on areas where multiple data sources can come together to improve this workflow, which is typically where we see pain points too - detailed planning being one of them, and that we write back as a result of having improved the workflow (alleviating the user having to jump systems).

Would be great to discuss this further in more detail!