EPMA 11.1.2.1 dimension build from FlatFile to EPMA to EssbaseASO using ODI, member sorting order issues

We are building our EssbaseASO cube using FlatFiles which are pushed to EPMA via interface tables and then the EPMA Essbase app is deployed to Essbase, this entire job is done through a ODI interface/package. The problem I am facing is the Order in which members in EPMA appear, even though the FlatFile has the right sorting order, by the time the hierarchies arrive into the EPMA interface table the sort order is changed randomly.
I am using the File to SQL control append IKM in ODI and some where on the way I saw a suggestion to add a new option to insert "ORDER BY" into the IKM. I successfully did this and it did change the sort order but even this is not the right order(order in which my flatfile has the dimensions).
I can't understand why Oracle/ODI needs to randomize the rows without being asked to do so! Please let me know if anyone has faced this issue before and if they were able to resolve it.

The EPMA interface tables have a SORTORDER column. Make sure this is populated with numeric values sequencing the order you want your members to appear in the EPMA hierarchies and when you import from the interface tables this order will be respected. Prior to this feature being introduced the workaround was to create a view referencing the interface tables imposing the required ORDER BY clause but this isn't required in 11.1.2.1 just use the SORTORDER column

Similar Messages

EPMA-Loading metadata using Interface tabes-Member sort order-Property?

Hi,
Any help would be greatly appreciated.
Version: 11.1.1.2
Loading metadata for planning app in EPMA using interface tables.
What property ( table , column) do I set to set the SORT ORDER for members within a dimension. I can arrange them manually by reordering children i nthe UI. The SYSTEM>sort order property does change manually after the metadata is loaded.
Thanks.
Edited by: user1658817 on Jun 26, 2009 9:06 AM

Some more info
I am loading members into Acount Dimension.
I am using following tables as source tables.
hs_account_hierarchy
hs_account_member
hs_account_property
hs_account_propertyArray
I use hs_account_propertyArray to load member Alias and member sort order.
Alias loads rightly. Sort order is not taken taken into account at all while loading. The sort order after the dimension is loaded is Alphabetical.
Sample records in my propertyArray table look like
Property Name Key Value
Order Common Stock Default 2
Order Warrants and Options Default 3
Order Additional Paid in Capital Default 4
Order Cumulative translation adj Default 5
Order Retained earnings (loss) Default 6
In the Load profile, I associate this Order property with Order property for shared library.
When the import is done, everything gets loaded properly, except for the SORT ORDER. The sort order is alphabetical. So the above members look like this
Additional Paid in Capital
Common Stock
Cumulative translation adj
Retained earnings (loss)
Warrants and Options
instead of being in the sort order mentioned above.
Thanks.

Hyperion Planning- Account dimension - Sort Order Issue with ODI 11.1.1.5

Hello Experts,
First of all, I thank you everybody in this forum for posting their valuable suggestions.
I am facing a strange issue with ODI (Version 11.1.1.5) while loading metadata to Planning ACCOUNT dimension (Version 11.1.2.x). I am using a Oracle view to load metadata to this dimension. I have defined the sort order in the view and enabled SORT_ORDER_BY_INPUT. For the fresh load to the dimension, everything is working fine. But, when I move a member from one parent to another parent, and define it as the top member of new parent, it is missing its sort order.
But it is working fine if you define it as the second, third...or last member under new parent. I have tried all the possible ways by flipping all the properties but unable to fix it.
Please help me here to resolve this issue.
Your help is greatly appreciated!!
Thanks
Edited by: user11965311 on Sep 20, 2011 7:07 PM

To be honest I think you are best logging it with Oracle because it sounds like you are doing everything correctly so it could be a bug.
Have you tested this on any previous versions of ODI or is it a new installation?
If it does get logged with Oracle please keep me informed of the outcome as I would be interested to hear.
Cheers
John
http://john-goodwin.blogspot.com/

How to load empty column from flatfiles to tables in oracle using aql*loade

HI,,
i am trying to load data from flat files to oracle tables using sql*loader. i got empty column to load. while i am trying it is throwing an error as null colums canot load...
plz help me with this...
Thanks in adavnce..

I believe you need to use 'trailing nullcols' as a parameter in your sql loader command.
See example below:
LOAD DATA
INFILE *
INTO TABLE load_delimited_data
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
( data1,
data2
BEGINDATA
11111,AAAAAAAAAA
22222,"A,B,C,D,"
{code}

Call ODI 11g scenario from Essbase calc script/business rule using ODI SDK

I am looking for any hints on how to use the ODI 11g SDK. I want to call a java application (CDF) that runs an ODI scenario using RUNJAVA in Essbase which I have successfully done in the 10g environment.
The java application has the odi-core.jar included in the project and registers OK with Essbase and I have replicated code from the Oracle sample code site. When I run the application in a calc script I get the following error:
EssbaseCluster-1.EFTS.EFTS.odi     Execute calculation script     June 17, 2011 10:20:40 AM NZST     Failed
Error: 1200456 Problem running [indigo.essbase.odi.RunODIScenario]: [java.lang.NoClassDefFoundError: org/springframework/util/StringUtils]
When I comment out the code that calls the creates the OdiInstance then the java app executes fine - i.e. writes something to the Essbase log.
The research I have done so far indicates that a classpath is incorrect. If that is the case where do I start looking to correct the classpath? Is it the ODI classpath or the Essabase classpath?
Any tips would be grateful.
Thanks.

You need to import more jars to execute this
following are the jars
1)     bsf.jar
2)     bsh-2.0b2.jar
3)     commons-collections-3.2.jar
4)     eclipselink.jar
5)     odi-core.jar
6)     ojdl.jar
7)     oracle.ucp_11.1.0.jar
8)     persistence.jar
9)     spring-beans.jar
10)     spring-core.jar
11)     spring-dao.jar
12)     spring-jdbc.jar
Once you have this in classpath - your scenario will execute
Hope this helps.

I am trying to extract metadata from essbase into a flat file using ODI.

I have 2 questions in this regard :
Some of the account members storage property is missing in the extract.the reason which i suspect is due to the parent child sorting that did not happen while extracting.How do i do this.I do not see this option when i select IKM hyperion Essbase Metadata to SQL....
I have many account members that have more than one UDA's upto 5 UDA's.But in my extrcat only one UDA appears.How do i incorporate all the UDA's in a single column,sperated by a comma,the extract file as such is semicolon seperated,mainly because of this reason and some alias descriptions have comma's in the source system
ODi is extracting metadata in a descending order.How do i change it to sort records in parent child order
Thanks,
Lingaraj
Edited by: user649227 on 2009/06/10 6:50 AM

Hi,
There was an issue with early versions of the KM around the storage property, this has since been resolved. I recommend upgrading to the latest release of ODI or have a look through the patches.
Cheers
John
http://john-goodwin.blogspot.com/

Sort Order issue when exporting from DRM

The sort order hierarchy (Parent/Child) in DRM is correct, and appears in the right order. When the hierarchy gets exported, some of the nodes are out of order in HFM.
There are shared nodes in the hierarchy. There is a Custom Sort order that is set correctly for the hierarchy in DRM.There is also a Query that was created to export nodes that does not contain the word Shared.
Ex
DRM
Parent 1
Child 2700
Child 2701
Appears in HFM
Parent 1
Child 2701
Child 2700
The sort order is not correct in Smartview. Why would the nodes show correctly in DRM, but export out of order, and not show correctly in HFM?
Any suggestions or comments would be greatly appreciated.

Can you evaluate the DRM export results with the Hiearchy structure, also make sure the Default Hierarchy Sort on the Hierarchy has a value assigned to it, whether it is core or custom based on node ID, DRM should export nodes as they appear in DRM.

Essbase 11.1.2 dimension build slow

Hi All,
I wonder if anyone has had similar problems or ideas of how to solve the problem I have.
We've recently migrated to Essbase 11.1.2 running on some big SPARC 64 bit servers and everything is going well.
We have a problem with dimension builds though. They work, just very slowly taking sometimes over a minute to build a dimension with just 10-20 members in it. With 22 dimensions to build it is taking over 20 minutes to build our dimensions - much more time then loading the gigabytes of data after and this is making the overnight process slower.
The model was migrated from 11.1.1.2 and we converted the outline. The dimension builds on the old server were 4 minutes. The old rules files are still used but as a test I tried creating a new rules file in the same application to load the meta data from a text file instead of an Oracle SQL server but the same problem exists.
We use deferred restructure on an ASO model but the restructure is fine - just the 'BuildDimFile' session runs for over a minute and then starts again for over a minute for the next dim build. Number of members seems to make no difference be it 10 or so to 60,000.
Has anyone got any ideas why or seen similar? Or should I really move out of the dark ages and learn Essbase Studio!
Thanks for your help,
Dan

It seems to be related to the number of dimensions.
I tried creating a basic outline, two dimensions and loaded with a basic rules file. Took 8 seconds in total, no problem.
I then tried copying in one of the existing rules files that builds a dimension with four members. Still no problem.
I then went to the existing outline and deleted all but two dimensions and tried rebuilding with the rules file - it is still quick. I then added the dimensions back, by typing them, all as stored with no members underneath and it suddenly jumps to 40 seconds (of which 30 sec for the dimension build time, 10 sec for the restructure) using the same rules file and data. I'd expect the restructure time to go up, but not the build time.
Possibly unrelated - EAS often produces an error message when loading an outline stating that I have -1536 MB memory free and the outline is 0 MB do I still wish to load?
Dan

"Get photos from camera" advanced dialog sort order

Hello All,
I'm having a problem with the order of the photos in the advanced dialog when there are photos from more than one date. The import dialog orders the photos by decreasing date and increasing time. For example, a series of photos with the date/times (in order of being taken):
10/20/11 11:30 PM
10/20/11 11:31 PM
10/20/11 11:34 PM
10/21/11 01:03 AM
10/21/11 01:04 AM
will display as:
10/21/11 01:03 AM
10/21/11 01:04 AM
10/20/11 11:30 PM
10/20/11 11:31 PM
10/20/11 11:34 PM
Now imagine say one or two thousand photos taken over three or four days and wanting to rename them. Right now I have to load the group associated with each day, and then keep adjusting the index number so that the naming scheme will make any sense. This was asked in the previous post: http://forums.adobe.com/message/2981895#2981895 and has not been answered. The photo order really makes no sense to me. Surely there is some way of fixing this?
Many thanks in advance,
Chris Jones

OK, here is the situation as I see it.
Took another round of pictures on day two. Used the same method as outlined in post # 7. The day 2 photos show up first and then day 1 photos. This is in the same order as the pictures are shown on the card, with the newest pictures at the front. So if using advanced rename it starts the rename at the first picture on the card and works down, in this case newest to oldest.
Now I took the same card and pictures and used the method I always use. Short date + custom name. In this case since you are not renaming the pictures, it uses the camera name and therefore the pictures are labeled from oldest to newest. This is because the camera labels in an advancing sequence starting at the first picture.
So the easy way to avoid the problems you are addressing is to download the pictures to Bridge using the camera name, use the correct sort order, or manual sort to order pictures, and then do a batch rename. As the batch rename starts at the first pictures and works its way to the last picture in sequence.
If you feel this is awkward for your workflow I would suggest you submit a feature request to have a sort order on the photo downloader for some future update. If enought people submit the same request it may get done.
Let me know if this answers the question satisfactorily.

Err:Two-pass & Expence reporting properties from dimension build rules file

Hi All,
i'm trying to build account dimension from rules file along with properties.
My source file for dimension building is like below:
Parent,Member Name,Alias,Consolidation,Storage,Time Balance,TB Skip,Variance Reporting,Two Pass,Formula,UDA1:Account
Account,Acc1,,+,Dynamic Calc,None,None,Non-Expense,Two-Pass Calc,,Revenue
Acc1,Acc2,,+,Dynamic Calc,None,None,Non-Expense,Not Two-Pass,,Revenue
Acc1,Acc3,,+,Dynamic Calc,None,None,Non-Expense,Not Two-Pass,,Revenue
after building dimension 'non two-pass' values are showing as 'two-pass' and 'non-expense' are showing as 'Expense'.
if any one knows please let me know.
Thanks in advance.
Kiran

Try using member property codes :- http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/frameset.htm?dotrules.htm#dotrules_2
Cheers
John
http://john-goodwin.blogspot.com/

Cannot Access Dimension Library from Workspace - Hyp 9.3.1

Dear All,
I've got error message when trying to access dimension library from workspace with information :
(0)null
(org.apache.axis.AxisFault)
below is the more detail :
Trace: com.hyperion.awb.web.common.BaseService.openSession(BaseService.java:112)
com.hyperion.awb.web.common.BaseAction.checkWebSession(BaseAction.java:64)
com.hyperion.bpm.web.common.BaseAction.execute(BaseAction.java:65)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
Exception org.apache.axis.AxisFault rethrown
Anybody can give me a clue?...
Many thanks in advance
Lucky

Has this ever worked? If so, restart your EPMA web service and the EPMA process manager service.
If this has never worked, can you goto http://EPMAMACHINE:19091/awb
where EPMAMACHINE is the ip address or name and see if you get the login prompt. If the login prompt here is working and you can login properly then I suggest you re-deploy workspace and the web server configuration from the config tool.
Regards,
-John

Dimension build in ASO system 9.3

Hi,
I've 10 dimensions with 1000 members in an ASO cube in system 9.3. Now I need to update the outline on daily basis without clearing the data out. I've 10 millions of data in that cube. I got 2 options here and
Option 1: I can load only the inserted/updated members from source using the rule file with option "Merge"
Option 2: I can load all the members from source using the rule file with option "Remove Unspecified".
I'm wondering whether option 2 will impact the outline build time or not. Pls advice.

I don't think it will affect it much if at all. When merging, Essbase has to figure out if the member exists, when doing a remove unspecified, I think Essbase clears all the members and readds them from your file. Since this is ASO the thing I would worry about is the outline growing. This has been a known problem. At some point it corrupts from getting so large. My suggestion would be to start with a "model" outline that you copy over your real outline then build from there. It gives you a same starting point on every build. If you are rebuilding the dimension every time, its not a big deal

Multiple Dimension Builds using MAXL

We currently use ESSCMND to perform multiple dimension builds and data loads. We have been using the "INCBUILDDIM" in Escmnd to update the outline with multiple files without restructuring until the last file. Is there an equivalent command for MAXL ??

Yes, you can mimic the BEGININCBUILDDIM command from ESSCMD in version 6.5. I've appended a sample script below to show that functionality. Until you upgrade to V6.5 you could shell to Esscmd and do your dim builds there. login 'xxx' 'PASSWORD' on 'LOCALHOST'; spool on to 'd:\ESSBASE\CLIENT\OUTPUT.LOG'; alter system load application 'SAMPTEST'; alter application 'SAMPTEST' load database 'BASIC'; import database 'SAMPTEST'.'BASIC' dimensions from server text data_file 'ACCTBLD1.TXT' using server rules_file 'ACTBLD.RUL', from server text data_file 'ACCTBLD2.TXT' using server rules_file 'ACTBLD.RUL' preserve all data on error append to 'ERR.OUT'; spool off; logout; exit;

Essbase Studio Deployment Dimension Build Errors

I have a ASO cube used to handle Subsidiary financial reporting to parent. Rather than alternate hierarchies, we use attribute dimensions for yearly differentiation. The ASO cube typically holds information for Current year + 3 prior years. This is the first year that we will achieve this as this cube was created near the beginning of 2010. Therefore, with the cube already having attribute dimension for 2010 & 2011, with the beginning of 2013 it is necessary to create the 2012 attribute dimensions. The cube has 13 anchor dimensions. Typically only 4 of these dimensions have attribute dimensions derived from them. Nonetheless, the following is the build list of the dimensions in the essbase model:
1: Financials Standard, Dynamic, Sparse
2: GL Date Time, Stored, Sparse
3: Incident Date Standard, Stored, Sparse
4: View Standard, Dynamic, Dense
5: Company Standard, Multiple-hierarchy, Sparce
6: Well location Standard, Stored, Sparse
7: Depletion Code Standard, Stored, Sparse
8: Vendor Standard, Stored, Sparse
9: Entity Standard, Stored, Sparse
10: Profit Center Standard, Stored, Sparse
11: Curr Yr Cost Obj Standard, Stored, Sparse
12: Past Yr Cost Obj Standard, Stored, Sparse
13: Measures Accounts, Dynamic, Existing
Attribute dimensions are mainly created in 4 of the Defined Hierarchies with in the cube; 1:FINANCIALS, 5:COMPANY, 6:WELL Location, & 10:PROFIT CENTER.
According to the Essbase Server log, upon deployment, the FINANCIALS Hierarchy generates 19 Dimension Build rule files with the associated SQL to pull members from our SQL Dimension Build tables obviously based on the way the Hierarchy is built as well as the joins created in the MiniSchema in the referenced Data Source. The COMPANY Hierarchy generates 5 Dimension Build rule files, WELL LOCATION generates only 1 Dimension Build rule file (this is mainly due to the fact that all the attributes generated from WELL LOCATION are built from the same table), and PROFIT CENTER Generates 3 Dimension build rule files. At this point for comparison purposes I want to include excerpts from the Server Deployment Log file depicting the dimension build rule files generated from the PROFIT CENTER Hierarchy:
Rule 1 Labeled XXXX_PRO.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON (cp_319.[profit_center_code]=cp_328.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul
FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_276.[profit_center_code]=cp_328.[profit_center_code_2011]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
These Dimension Build rule files are recreated nightly on 4 different production servers, each one successfully redeploying nightly with zero errors.
So now I need to add the new 2012 tables to the Data Source/MiniSchema, create the joins in the MiniSchema mimicking the joins for the 2010 & 2011 Attribute Dimensions. It would be difficult to demonstrate the joins in the MiniSchema but trust me they are there and this is proven by the additional Dimension Build rule files from the appropriate Hierarchies.
So on our test server, which is configured exactly like all 4 of our production servers, I have begun the creation of the 2012 attribute dimensions. I begin with the FINANCIALS Hierarchy adding 7 new attribute dimensions, 6 that are cross table and one that is inter-table.
At this point no changes have been made to any of the other 3 Hierarchies that contain Attribute dimensions; COMPANY, WELL LOCATION, or PROFIT CENTER. They still look exactly as they did in the current state discussed above. Upon deployment, the FINANCIALS Hierarchy generates , as expected 25 Dimension Build rule files, 6 additional because only 6 were cross table attributes, the 7th was within the anchor table and therefore would be included in the first dimension build rule file. COMPANY still generates 5 Dimension Build rule files, again as expected. WELL LOCATION still generates only the 1 Dimension rule file also as expected. Lastly, PROFIT CENTER also again only generates the 3 Dimension Rule files, however, one has materially changed as noted below:
Rule 1 Labeled XXXX_PRO.rul
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON ((cp_319.[profit_center_code]=cp_328.[profit_center_code]) AND (cp_328.[profit_center_code]=cp_319.[profit_center_code])) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_328.[profit_center_code_2011]=cp_276.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
The change in Rule 1 above appears to now require something different from the previous deployment and when we run the deployment now it runs forever and ultimately fails, yet no changes have been made to the Hierarchy, no changes have been made to the MiniSchema involving joins to the tables used in the building of the Hierarchy, and no new tables have been added to the data source that would affect this Hierarchy.
Additionally, I have also run each of these incrementally, and the PROFIT CENTER even incrementally still makes the change to the SQL statement shown above.
So finally, to my question, Why and What caused this Dimension Build Rule file to change and ultimately led to deployment failure? Has anyone ever encountered this in Essbase Studio Deployments?

Gurus, anybody anything on this one??
I haave done a small adjustment in the dimension order by which I have eliminated the following error:
Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
Record #40 - No time dimension defined
But, I have the following new error/warning (cube build successfull in this case) when I made this adjustment:
Record #427 - Error adding Attribute to member PATB4_ADJ-PDA (3320)
The adjustment I made is... I moved TIME dimension up and ACCOUNT dimension below that...so the order I have now is TIME,ACCOUNT,SCENATRIO,XXX,XXXX instead of ACCOUNT,TIME,SCENARIO,XXX,XXXXX ..*would this create any performance issues?*

Sorting by Member's Alias name during dimension build

I dynamically build/update an Employee dimension each month. I want to sort the members by their alias name, which in this case is the employee name. Has anyone done this before? The data file which I'm using to build the outline is already sort by employee name. The problem I have is each month when I do an update build, all the new members drop to the bottom. The option in the load rule definition to sort members is no good because that sorts the member by their ID and not by their Alias.Thanks for helping!!Peter

The best method is to clear all the members of the dimension and rebuild the entire dimension from scratch.This can be done manually through the Outline editor from the Essbase Applicaiton Manager or using an Incremental Build Dim from Esscmd or Maxl.Using Esscmd you it would be easiest to have a dummy build file with a single member and process that file first then process the real file. Use the remove unspecified option and set sorting to none. Regardless of method do NOT restructure the data between deleting all the old members and processing the updated file.If you restructure between these steps you will need to reload all data.Joseph HoganSenior Essbase Lead ConsultantHyperion Solutions203.703.3300 x6364

EPMA 11.1.2.1 dimension build from FlatFile to EPMA to EssbaseASO using ODI, member sorting order issues

Similar Messages

Maybe you are looking for