ESSBASE: Issues Concerning BSO New Data Block Creation

Comments

Post a Comment

Popular posts from this blog

ESSBASE: When to Use FIX vs. IF

Hyperion developers love FIX and IF, both are powerful tools and interchangeable in usage in certain circumncetances. There are also differences between the two. Let's take a look. FIX...ENFIX Usages and Rules Every FIX must be ended with ENDFIX. But it is optional to end the statement by ";" FIX Mbr can be any comma-delimited list of members, or member set functions FIX Mbr argument can be a combination of members from multiple dimensions           FIX(@CHILDREN(Qtr1),"Actual")                 Calc Dim(Accounts);           ENDFIX FIX Mbr list from the same dimension means "OR", cross dimensions means "AND" FIX cannot be used inside of formulas in outline, they can ONLY be used in calc scripts Cannot consolidate a dimension that is FIXed on. Following will generate an erro...
Read more

HFM: IC Configuration and Partner Code

Image
HFM is very powerful in dealing with InterCompany Transactions and elimination. (add more notes how HFM dealing with ICP) Our current General Ledger (GL) uses "hard coded" IC accounts. Ex. 1231 (IC receivable CA), 1232 (IC receivable BA), etc. Each receivable account plus entity will require an IC account! This is not only inefficient, but also hard to maintain in FDM mapping (see below). To correct this backward design of GL, NAV team added Partner Code as a new attribute / dimension of accounts, see below. This will appear in the very last column of GL extracts for HFM. Here are steps what need to be done to add new location and ICP mapping. Step1)  Add a new location After LOCALCURRICP is added, we need to ensure the entries in General and Workflow Behaviors are correct. This requires to create a new Import Format LOCALCURRICP Now we can copy the mappings from LOCALCURR to LOCALCURRICP. Make sure copy both Types of "Explicit"...
Read more

Essbase Dynamic Member With Self-Reference

Image
Planning/Essbase professional like to use Dynamic member formulas. One of advantages is to take no data storage, therefore to improve overall performance. Second, it improve the correctness of calculation and can be easily and quickly verified, without waiting for calc scripts to run (some may rely on aggregation). When you have multiple Dynamic Calc members, whether within a dimension or cross dimensions, you would have to understand the ordering between Dynamic Calc members. 1) Dynamic Calc order within a dimension follows the outline order. 2) Dynamic Calc on Sparse dimensions will come before Dynamic Calc on Dense dimensions. The reason for this is that the Block Storage need be VIRTUALLY created first before it can perform calculation. 3) Dynamic Calc on Dense dimensions will come after Dynamic Calc on Sparse dimensions. (is this just a repetition of #2 in an opposite way?) Among the dense members, Account and Time will be calculate first, following by other Dense dimensions...
Read more