tag:blogger.com,1999:blog-7650953985627040991.post3986557686278375881..comments2024-02-14T05:30:55.538-05:00Comments on Cameron's Blog For Essbase Hackers: Calculation Manager, BSO Planning, and ASO Planning combine for an awesome ASO Essbase procedural calculation hack -- Part 2Cameron Lackpourhttp://www.blogger.com/profile/07701786303677521318noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-7650953985627040991.post-1992355895027081202016-03-01T13:26:02.849-05:002016-03-01T13:26:02.849-05:00Has someone been able to get around the level 0 re...Has someone been able to get around the level 0 restriction in PBCS? Is there a way to make it work in PBCS?LuigiOhttps://www.blogger.com/profile/02707354122094325570noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-34276889731233037442015-04-15T09:56:28.355-04:002015-04-15T09:56:28.355-04:00Just curious. Is there security so the users canno... Just curious. Is there security so the users cannot see the accounts calculated at each level with the MDX formula that gets copied to the stored member? We do similar logic in BSO Workforce so we can utilize dynamic calcs but want to only run on level 0 without the weight of relying on calc scripts. We have to hide these "driver" accounts to eliminate confusion.Leannenoreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-36913024333031188962014-11-17T15:03:45.818-05:002014-11-17T15:03:45.818-05:00Thanks for the excellent post Cameron.
This is wha...Thanks for the excellent post Cameron.<br />This is what exactly I did around 2 years back for one of the implementation where we did a BSO to ASO conversion and we came up with all possible options...Reading your post brought me back those memories...we had sleepless nights working on this conversion :)<br /><br />But the only difference that we had was we didn't use the procedural calcs but rather used it purely with dynamic scenariosamarnathhttps://www.blogger.com/profile/12749240552285136096noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-37710806336931489552014-08-01T13:11:49.353-04:002014-08-01T13:11:49.353-04:00I have created a bug with the Essbase folks and se...I have created a bug with the Essbase folks and see how long will they take to resolve this. <br /><br />Sree MenonSreehttps://www.blogger.com/profile/13222298378972730836noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-73259154592707698352014-07-31T12:53:53.103-04:002014-07-31T12:53:53.103-04:00Thanks for the excellent post and response.
Unfor...Thanks for the excellent post and response.<br /><br />Unfortunately, I'll not be able to do so with few accounts.<br /><br />It was much faster when I used partitioning to transfer the data from the BSO (level0) for the entire set of accounts. The entire data set went within 1 min and tied out. <br /><br />Regards,<br />Sathish RadhakrishnanSathish Musichttps://www.blogger.com/profile/14264346173273471204noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-16017545573905018582014-07-30T13:05:12.080-04:002014-07-30T13:05:12.080-04:00
Satish,
I had the same problem when I expanded... <br />Satish, <br /><br />I had the same problem when I expanded the range of Accounts. <br /><br />At least in the case of my test database, it seemed to be a function of how many Accounts (so dynamic compression dimension) were accessed. <br /><br />What I did was take the logic and simply repeat it about 7 times (yes, really) always going after a different tree in Accounts. <br /><br />Believe it or not, that was really quite fast although profoundly ugly. <br /><br />Sometimes ugly wins. :) <br /><br />Regards, <br /><br />Cameron Lackpour Cameron Lackpourhttps://www.blogger.com/profile/07701786303677521318noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-39960915893698869152014-07-29T23:48:26.741-04:002014-07-29T23:48:26.741-04:00Hi Cameron,
I tried exactly the same stuffs as a ...Hi Cameron,<br /><br />I tried exactly the same stuffs as a part of POC (using NONEMPTYTUPLE on the member formula) and calling it through allocation process.<br /><br />I submitted the POC to my client about a month ago. Unfortunately, I dropped this procedure due to a performance degradation, since it was executed at all the accounts level. Is there any specific parameters or set of accounts you are using to execute this procedure or is it getting executed at the entire DB level? Please clarify<br /><br />Thanks,<br />Sathish RadhakrishnanSathish Musichttps://www.blogger.com/profile/14264346173273471204noreply@blogger.comtag:blogger.com,1999:blog-7650953985627040991.post-32203808363251325862014-07-29T23:47:24.823-04:002014-07-29T23:47:24.823-04:00Hi Cameron,
I tried exactly the same stuffs as a ...Hi Cameron,<br /><br />I tried exactly the same stuffs as a part of POC (using NONEMPTYTUPLE on the member formula) and calling it through allocation process.<br /><br />I submitted the POC to my client about a month ago. Unfortunately, I dropped this procedure due to a performance degradation, since it was executed at all the accounts level. Is there any specific parameters or set of accounts you are using to execute this procedure or is it getting executed at the entire DB level? Please clarify<br /><br />Thanks,<br />Sathish RadhakrishnanSathish Musichttps://www.blogger.com/profile/14264346173273471204noreply@blogger.com