We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
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

Expected migration behaviour - Converting period and movement for an existing application to dense

Received Response
1
Views
1
Comments

Summary:

We would like to clarify what the expected behaviour ("result") is when migrating an application that had control to-date view storage enabled and that were subsequently converted to period and movement dense.

Content (required):

Our existing Production application were initially set with control to-date view storage on and account dense. We then converted the period and movement to dense. Based on the documentation we expected the consolidate / translate "selected view" rules to be available and they are. We also now expect, as per the documentation, that any of consolidate or translate rules will only generate periodic data. We migrated a Production snapshot (full nightly Oracle backup) to test (after recreating the test environment using EPMAutomate). We now see the following in the Test environment:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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