Forum Stats

  • 3,852,432 Users
  • 2,264,103 Discussions
  • 7,905,062 Comments

Discussions

DM to Cloud ASO

Ian50
Ian50 Member Posts: 15
edited Aug 29, 2019 6:49PM in Financial Data Management

Hello

We are exporting to an ASO cube using Cloud DM with Target Type "Essbase" and Deployment Mode "Classic". PBCS version is 19.08.67.

Export with Export Mode "Store Data" is successful.

However, export with Export Mode "Replace Data" fails with:

2019-08-28 06:31:55,962 INFO  [AIF]: Building and executing replace data script...

2019-08-28 06:31:55,971 INFO  [AIF]: Replace data script:

CROSSJOIN({[Years].[FY20]},CROSSJOIN({[Period].[Jul]},CROSSJOIN({[Scenario].[Actual]},CROSSJOIN({[Version].[Working]},{[Company].[JV_201001]}))))

2019-08-28 06:31:55,978 INFO  [AIF]: The load buffer [1] has been closed (finally clause).

2019-08-28 06:31:55,978 ERROR [AIF]: Cannot Clear Partial Data. Essbase Error(1260046): Unknown Member [Period].[Jul] used in query

Not sure why it's unhappy about "Jul", as this does exist in the Period dimension. Something obvious that we've missed?

Suggestions very welcome.

Thanks

Ian

SH_INT

Best Answer

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited Aug 29, 2019 9:09AM Answer ✓
    Ian50 wrote:But does this mean we can't export to an ASO cube that has shared members?

    The problem exists when you use the replace export function, Data Management creates an MDX statement to clear data, the problem is with the way Data Management creates the MDX, it concatenates the dimension name and this causes a problem with shared members.

    One way to get around this would be to add an application period mapping so the fully qualified name is generated, so instead of being mapped to Jul you could try [YearTotal].[Jul], this means the MDX generated will be [Period].[YearTotal].[Jul] and it should be valid.

    SH_INT

Answers

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited Aug 29, 2019 2:08AM

    Do you have shared members in your period dimension as I know that sometimes can cause issues, what does your period dimension look like.

    Cheers

    John

  • Ian50
    Ian50 Member Posts: 15
    edited Aug 29, 2019 5:47AM

    Thanks John. I suspect we do...

    Period

      BegBalance

      YearTotal

        Jul

        Aug

        Sep

        Oct

        Nov

        Dec

        Jan

        Feb

        Mar

        Apr

        May

        Jun

      Total Year

        Q1

          Jul

          Aug

          Sep

        Q2

          Oct

          Nov

          Dec

        Q3

          Jan

          Feb

          Mar

        Q4

          Apr 

          May 

          Jun

    I saw a note about shared members on a related question, but didn't make the association. I'll have our Period dimension simplified and see how we go.

    But does this mean we can't export to an ASO cube that has shared members?

    Cheers

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited Aug 29, 2019 9:09AM Answer ✓
    Ian50 wrote:But does this mean we can't export to an ASO cube that has shared members?

    The problem exists when you use the replace export function, Data Management creates an MDX statement to clear data, the problem is with the way Data Management creates the MDX, it concatenates the dimension name and this causes a problem with shared members.

    One way to get around this would be to add an application period mapping so the fully qualified name is generated, so instead of being mapped to Jul you could try [YearTotal].[Jul], this means the MDX generated will be [Period].[YearTotal].[Jul] and it should be valid.

    SH_INT
  • Ian50
    Ian50 Member Posts: 15
    edited Aug 29, 2019 6:49PM

    Works beautifully! Thanks John.