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

Archiving applications for 7 years with Different Metadata Structures

Received Response
33
Views
4
Comments

Summary:

We have a requirement with our customer that every year the metadata or the hierarchies gets updated, and we need to retain the data for 7 years but based on different metadata structures every year.

Content (please ensure you mask any confidential information):

Our customers in Current Essbase models have different applications in Essbase saying ROMA20, ROMA21, ROMA22, ROMA23, ROMA24, etc. So if they want to report data year wise, they connect to that specific application and do SmartView retrievals.

In EPM also they are expecting to do the same, meaning if they want to see 2021 structure and data, they should be able to retrieve that and 2023 should carry its own structures. Between years there would be lot of movements, deletions between and within the hierarchies as well. So having a single archival application with multiple databases, is this kind of reporting structures not possible we believe. For example, in 2022 they have a member say X and in 2023 they deleted it. when they select 2022 database, they should see X and when they select 2023 database,

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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