Dimensions of building using rule files

Similar Questions

• Dimension to build using the SQL table and process to populate the SQL table

  I have a dimension in a cube that is manually* built by one of our power users. Now, I have to get all the information of members of this dimension in a SQL table (example: with columns... Level0, level0property, level1, level1property etc...) to use this table in the STUDIO for the responsibility of the Member.
  
  Is there any easy process to do this? Currently I am building each line manually in the SQL table and there are 1100 + members in that manually built dimension. Please advice.

  Look at the outline of applied olap Extractor is a free utility

• Table of Build using Pseudo-file of waiting

  I'm moving to use a queue by simply creating a table.  I writing to a write DAQmx values in a loop at 50 ms, but I won't update the chart every 50 ms (for obvious reasons).  I use a global functional for transmitting data from a slower loop to 500 ms.

  Problem is that I get that each point of the tenth.  Y at - it an easy way to build an array and pass (without overwrite or skip data) to the slower without having to queue loop?

  Thanks for the help.

  Why not use a queue?  It is by far the most effective way to do what you want.

  What you have run in with the FGV is a race condition.  They you used it, it might as well be a local variable or a global variable.  FGVs do NOT prevent the race conditions in the way that you use it.  Here's a good article about the race conditions in the field of LabVIEW log:http://labviewjournal.com/2011/08/race-conditions-and-functional-global-variables-in-labview/

• Very Urgent... Update withsingle properties accounts dimension rules file

  I want to build a rules file that updates the properties of accounts like dimension (data storage, Consolidation, UDA, Calc to spend two, comments, balance of time, time balance Skip, VarReporting, CurrConv, CurrConvCategory) in the rule file.

  Well, you want to use a rule of charge of dimension to change/add properties.

  Is your question, "is it possible?"

  The answer is Yes.

  Make sure that in the generation of Dimension parameters you check ' allow property changes "If you plan on loading and changing member properties.

  Otherwise, it is difficult to know what you're trying to do.

  Kind regards

  Cameron Lackpour

• Creation of multiple dimensions with the rule files

  Hello
  Is it posible to create multiple dimensions using rules file. I managed to create 1 Dimension using the rules file, but I need to create two dimension using rules (customer and Distribution_Channel) file.
  Help, please.
  
  -Amit

  Hello

  You need the files in separate rules for the construction of separate dimensions.
  You can use the same metadata file well.

  So, you must create 3 files of rules for the 3 dimensions.

  See you soon
  RS

• Ask about the load of metadata in Essbase using the rules file

  Hello

  In our application, we load the metadata using the Essbase rules file and here, we are faced with a problem. Suppose we have load a member of level 0, called "xxxx" under two different parent, assume parents are Parent_AAAA and Parent_BBBB. But our demand is the operator of consolidation for the first occurrence (i.e. under the Parent_AAAA) is '+' and for the Member shared under Parent_BBBB is ' - '. But, when we are load using rule file the operator of consolidation for the Member always shared loading as ' + '. Y at - it a trick to change the operator of consolidation for other than manually changing outline shared member?

  Pls help... Thanks in advance.

  I don't think that there is a way to change the default setting.

  However, what you can do is to have a different charge and rule file different text with only the metadata that you want to have an exception for shared members. In this way, you can get that you don't have to change existing rules file.

  Concerning

  ORACLE | Essbase

• DATAEXPORT and rule files

  I have a requirement where I export data demand A projections and it powers the B application. Both applications are different so I do all my mapping using rule files. In my calculation script, I'm specifying months to be exported to & CurrMonth:Dec in my statement of FIX and lets say that the year is FY11.
  
  When I export data using DATAEXPORT it gives me period in colums... i.e. initially that I export all the 12 months of data he gave me data for the 12 months in the columns so I traced each column with a month in my rules file. It was working fine and imported in the right place.
  
  But now since I only need the current month data to reduce the number of exported months according to the current month will be different every time. So, how I prepare the rules file so that it is satisfactory data for some months come in and recognizes what months are imported? It will be a pain if we will need to prepare the rule files each month and set up the mapping for the months to come in.
  
  Please let me know if there is a way to make it easier and more effective. Any ideas are appreciated.
  
  Kind regards
  ~ Hervé

  I think that you can just create a file of false data with a single record load but every 12 months. You can read that in your data load rule and retrieve columns to appear and then match.

  Throw the folder and now to apply the amended rule file to your sometimes a month, then two, then three, etc. etc, load the file.

  I will note that ETL in a file of data load is a bit dangerous to venture somewhere: I've been bitten by that firmly and painfully. A better (although Yes, more complicated and more expensive) way to achieve this is to export to SQL and make your transformations with a view, or, breathless, in one product as a ODI ETL. If I were in your position, I would write emails explain to everyone that if I do ETL in a State of charge, it is only because someone who held a gun to my head. Yes, I don't really like to do ETL in a State of charge.

  Kind regards

  Cameron Lackpour

  PS I know there are others on this forum who think I courses focus on it - all that I can say is just wait. Here are a few threads on this topic:
  http://www.Network54.com/Forum/58296/thread/1180721593/load+rule
  http://www.Network54.com/Forum/58296/thread/1311019508/data+load+optimization+-headervs + column

  Published by: CL November 3, 2011 15:54

  Published by: CL November 3, 2011 15:54
  Ed. - I tried, once again, to use the word that describes the leather thingies that we put on our feet when walking on the place of the word "post". You know, this word that begins with the letter "s". I continue to be mystified why this is an illegal word in OTN, but it is. I still think that someone does not like the shoe industry. :)

• ODI vs rule file load

  Hi all
  
  I would like to know the difference between the loading data to essbase directly using files of rules from a flat file or an RDBMS and load using ODI.
  And using rule files in interface ODI to load the data, what kind of performance and efficiency can be achieved with it.
  
  Thank you

  The choice is really yours, I'm not sure you how many performance advantage you would see ODI not use with a rule of load, sometimes it is just better to test and see.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Build dimension using the rules file

  I use Oracle Hyperion worm 9.3.1. So that the dimensions of formatting built using the rule file, I came across the 'JOIN' and 'Create Join using' options. Can someone help me to know the difference between these two options?
  
  Published by: 873675 on July 20, 2011 12:25 AM

  The documentation explains the difference with examples, now I was going to post the link, but I might as well post the info from the link.

  Join the fields

  You can join several fields into one. The new field is given the name of the first field in the join. For example, if a data source has separate fields for the number of product (100) and the family of products (-10), you must join the fields (100-10) before loading in the Sample.Basic database.

  Create a field by joining fields

  You can reach the fields by placing fields joined in a new field. This procedure leaves intact original fields. Creating a field is useful if you need concatenate the fields of the data source to create a member.

  For example, if a data source has separate fields for the number of product (100) and the family of products (-10), you must join the fields (100-10) before loading in the Sample.Basic database. If, however, you want to keep the two existing fields in the data source, you can create a field (100-10) using a join. The data source includes now all three fields (100, - 10 and 100-10).

  To read other rule options - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/ddlfield.html

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Type of Dimension set using the Rules file

  Hello
  
  I tried to build a dimension (ASO) of accounts using the build parent-child and wanted to know if we can specify the dimension type "Account" to in the rules file?
  Also all the codes of the property can be given in a single column or placing them in separate columns a good practice? I need to make this hierarchy of dimension as 'dynamic '.
  
  I use the definition of dimension of the rules file option name.
  
  Thanks for your contributions!

  Yes you can do it in a rules file. In the setting dimension dialog box, go to the third tab. You can see the list of dimensions and the possibility of adding dimensions. Right-click on the desired size and then select Edit properties. Then, you can set the dimension type and dimension member properties.
  With regard to the properties. I always keep in separate columns of my source.

• ATTRPARENT dimension of the text attribute to several levels of construction with a rules file

  Hello

  My first post here.

  I'm trying to create the dimension generation rule to create a dimension of the multilevel text attribute and then combine with the basic dimension.

  So far, it is difficult.

  With regard to my experience:

  -J' have a relatively basic understanding of the rules of charge both with regard to the data loads and define the updates - I find this quite confusing area and the documentation does not help that much

  -J' only started using dimensions attribute, so for me it's a new concept, but we are already quite useful in certain applications

  -J' I try to automate the process of construction of dimension attribute, and then associating attributes with the basic dimension

  I use the following documentation as a guide:

  Building size attribute and associate attributes

  http://docs.Oracle.com/CD/E12825_01/EPM.111/esb_dbag/frameset.htm?dotdimb.htm

  and / or

  Work with the attribute multi-level Dimensions

  http://docs.Oracle.com/CD/E26232_01/doc.11122/esb_dbag/frameset.htm?ch21s06s05.html

  (essentially the same source in both cases)

  The ultimate goal is to replicate one of our existing recently created attribute dimensions of a cube to another.

  I built a few versions of the required flat file and the corresponding rules file, but none worked.

  I tend to get the following validation error message:

  This field is defined as an ATTRPARENT. The following column must be a field of association attribute type.

  As I got stuck so I gave to the current actual attributes and moved on to experimenting with the sample / base cube.

  I built a flat file that is supposed to create a new dimension of text attribute named ABC with two attributes level structure:

  ABC

  A

  AA

  AB

  B

  BA

  BB

  and associate it with the dimension of the product in the following way

  200-10 AA

  200-20 AB

  200-30 BA

  200-40 BB

  The flat file looks like this:

  "AA"      "A"         "200-10"               "A"         "AA"      "200"

  "AB"      "A"         "200-20"               "A"         "AB"      "200"

  "AB"      "B"         "200-30"               "B"         "AB"      "200"

  "BB"       "B"         "200-40"               "B"         "BB"       "200"

  and the rule file has 6 matching columns with titles as follows:

  Level0, LEVEL1 ABC, ABC Level0, product ATTRPARENT0, ABC ABC0, LEVEL1 product, product

  all agree with what the documentation says.

  The first 2 columns are intended to define and create the dimension of the attribute, while the 4 next make association...

  I couldn't the above rules file to validate.

  The same validation error message appeared as previously:

  This field is defined as an ATTRPARENT. The following column must be a field of association attribute type.

  However when I tried to actually update the outline of the mistakes of dimbuild.err file has been created which gives some additional clues:

  \\ATTRPARENT column 4 must precede a numeric or datetime column attribute association

  Now... Finally the interesting part...

  Back to the documentation...
  

  I don't mind if the size of the attribute is generated and then those associated with step or in two separate steps.

  I try to do both tasks in one step only because that's what the documentation seems to suggest attributes at several levels.

  First of all I read:

  Note:

  If you work with a multilevel dimension attribute or with a dimension of the attribute of the digital type, Boolean, or date, the rules file requires an additional field. See working with Dimensions of the multilevel attribute.

  Yes, I work with a dimension of the multilevel attribute so the above statement applies (I guess) and so I'm going to see what works with several levels attribute Dimensions has to say.

  Then, I read:

  When an attribute is part of a digital multi-level, Boolean, or dimension attribute date, the source data must include columns for all generations or the size of the attribute levels.

  Fair enough... so I do what they say... my attribute dimension is at several levels, so I can assume that the statement above applies...

  So, I build my rule in accordance with the guidelines above.

  And then, as we have already mentioned, I get the error message about ATTRPARENT and when I read, it turns out that ATTRBPAREN cannot be used for numeric or date attribute dimensions !

  I'm totally confused at this point.

  What about the attribute text multi-level dimensions ?

  They are several levels but they are NOT numeric or date those!

  The documentation does not seem to tell what to do in this case...

  Anyone build something like that?

  What is the thing that I'm missing?

  What about

  I'm glad that you got to work. I tested and that is to create the dimension attribute and associate it with the rule of the load.

  You could ignore the construction size manually. Remove the attribute dimension. The rule1 go for the Dimension settings under the definition of Dimension tab. Then right-click on the product and change the properties. On the attribute tab, add 'Test' or whatever you want to call the attribute, and assign the text type. He adds the attribute and associate it with the basic dimension when it create the hierarchy. Note that the rules could actually be reversed where you create members of level 0 and then more later to create the hierarchy.  Of course you must pass the size of the attribute association to the other rule

• Essbase error when you try to change the dimension through the rule files

  Hi Knowledgebank.
  
  I'm new to Essbase. I'm trying to change my dimension through the rule files and Iam getting error (Dimension build setings).
  
  Example:
  
  My current dimensiion is:
  
  MARKET TOTAL
  ASIA
  Singapore
  CHINA
  HONG KONG
  NORTH AMERICA
  SOUTH AMERICA
  
  
  I am trying to add a few new countries of SOUTH AMERICA and I can't. Is there a step by step guide to achieve this?
  I'm following the documentationi but still errors.
  
  Help on this is going to help me go further.
  
  Note:-I am able to load the data successfully.

  'TOTAL MARKET' 'COUNTRY'--> header I have jump while loading
  'SOUTH AMERICA' 'BRAZIL '.
  'SOUTH AMERICA' 'ARGENTINA '.

  As above, your first file is correct if you use generation referance.
  Your mapping in the rules file should be like this.
  Gen2, Gen3 TOTAL MARKET, MARKET TOTAL
  'SOUTH AMERICA' 'BRAZIL '.
  'SOUTH AMERICA' 'ARGENTINA '.

  For generation Referance always starts on Gen2.
  Gen1 sets the level of the dimension. If the dimension is not there, you must set in the definition of dimension not in Field1.

• Issue while loading data using the file Rules Essbase

  Hi all

  I am facing problem while loading data using the Rules file. In the rules file, I rejected several members in two areas (two dimensions). Now if I load the data using the rules file I'm getting errors for all members in the dataload.err file. If I reject mutiple members of a single field, the data load without settling errors in the dataload.err file.

  I want to know how rmany members of several fields of ejection for loading data using the file Rules Essbase? Is it possible?

  Okay, okay... I think that you must assign Global Select / reject Boolean in the parameters of loading data as 'Or':

  

• import of dimension and member via maxl, how to create the data file and rules files

  Hello
  
  I have a task of importing Essbase, dimension and Member for project requirement, I have to use the text file or spreadsheet.
  I wonder what format can be imported into Essbase?
  I tried to create, failed.
  
  You have samples to help me? file size and rules files...
  
  I'm looking for a lot in http://gerardnico.com/wiki/epm/essbase/dimension_build#about, but there is no samples.
  
  Thanks in advance...
  
  Best regards
  Samantha

  Have you been through this?

  http://download.Oracle.com/technology/products/bi/Essbase/demos/Essbase_11.1.1_Overview/Lesson4.htm

  Kind regards

  Cameron Lackpour

• Construction of dimension with a rules file for Hyperion Planning

  Hello Experts!
  
  I'm on version 11.1.1.3. I created a classic with 3 Hyperion Planning application plan types, and in EA I have successfully downloaded the same members of dimension entity with the same rules file in each of the 3 contours under my application from HP. Then I've also updated database in the Planning, but I don't see any new dimension member in HP. - could someone help me with what is wrong? Hyperion Planning of work with files of rules for dimension is not build? Thanks in advance!

  No planning does not work with the rule files, you must load dimensions information directly in the planning, and then push it to essbase.

  See you soon

  John
  http://John-Goodwin.blogspot.com/