Products > PSOP > Documentation Why do I have to make sure nobody else is working on the project PSOP is leveling? If other users are working on a project that PSOP is leveling, data corruption can occur. PSOP reads project data from the P3e database before it starts leveling. If the project changes while PSOP is working, the schedule PSOP exports to P3e might not correspond to the project now in the P3e database. This can cause data corruption. Furthermore, when changes are made to a project in P3e they are not immediately saved to the Primavera database. Primavera does not provide a way to programmatically read the schedule visible to the user, so PSOP reads directly out of the P3e database. As a result, PSOP will not see any changes that were made to the project but have not yet been committed to the database. After leveling, PSOP can push its schedule into the P3e database, but the schedule changes made by PSOP will not be visible in P3e until the user refreshes the data. If PSOP exported a schedule that does not correspond to the project visible in P3e, Primavera will try to merge the new data with the data visible to the user and this can cause data corruption. Data corruption can occur even when only small changes, such as changing the start time of a single activity, have occurred. It is imperative that nobody on the network has an open copy of the project PSOP is leveling. Similarly, it is important that you close Primavera before PSOP starts leveling and that you do not open it again until the leveling process has completed (more information...). Back to FAQ