Actually, even if the Navdata have changed meanwhile, it shouldn't be a problem since the restriction is coded '-FL200' at the relevant waypoint. It means, the plane can cross the waypoint at or below the restricted altitude. However, the FMC does interpret the restriction as 'at' only which causes the problems to reach the subsequent altitudes and restrictions in this particular case. So, the FMC always interprets the 'at or below' restriction as an 'at' restriction which causes the problems. That's why I asked somebody from PMDG to comment on the subject to clarify this.

This is a known bug. I think it was confirmed by PMDG some years ago but I don't know where.

 

As a workaround just delete the at or below constraints a check wheter it calculates an altitude below the original constraint. If not reenter the at or below constraint to be at least at the altitude and not at or above.

 

 

Jan-Paul