Your
benefit
Multi-system landscapes with parallel maintenance/project lines make it possible to decouple operative maintenance from longer-term developments as well as several development projects from each other: departments can develop and test new releases on their own project systems without the operative maintenance line and thus the consistency and availability of productive SAP – jeopardize systems.
It is important to synchronize the basis of these project strands in the same way as the maintenance landscape, so that
- Always set up projects on the current, valid system basis
- Errors that have already been corrected in maintenance operations do not get back into the productive system during the later release roll-out.
Compared to manual synchronization work, a proven average of 70-80% of the effort can be saved with U:R4-Synch – with the available automation methods, all developers and administrators can concentrate on their actual work again.
As with all TIA-based tools, the average error rate for U:R4-SYNCH in the customer environment is well below 0.1%.