Translate to reporting currency asking to translate a prior locked period
Summary: When user tries to run a translation on P10 it fails with a reference to P5 2022 needing to be translated.
It can be fixed by running a forced translate for Period 10 - however our users don't have access to that rule.
P5 is locked but is down as system changed - there are no issues with the standard consol - has anyone come across anything similar before? It happens again even after the job is run when a user loads data to P10 and tries to translate after running the consol. I've checked the data status for P5 and all appears fine.