Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Translate to reporting currency asking to translate a prior locked period — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Translate to reporting currency asking to translate a prior locked period

Received Response
16
Views
3
Comments
edited Nov 2, 2022 7:05PM in Financial Consolidation and Close 3 comments

Summary: When user tries to run a translation on P10 it fails with a reference to P5 2022 needing to be translated.


Content (required):

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.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!