hey any one know about dimension build rules in hyperion and how to load dimensions using these build rules,please respond..

Hyperion Dimension consists set of members. To build these members, Rules need to be developed where one can provide the input fields, any transformation logic, accepting or rejecting the input information, etc. In Dimension Build settings one need to specify what needs to be done if the member is already existing in the specified dimension, what build method is to be used like generation or level or parent/child reference, etc.
Having build the rule file and validation, run this script using ESSCMD or MaxL script to build the Dimension by using Builddim or Import database command OR Update the Outline by providing the input file and the rule file in the Outline editor.

An essbase database contains dimensions, members, and data values. ● loading data is the process of adding data values to an essbase database from a data source, such as a spreadsheet or sql database. If the data source is not perfectly formatted, you need a rules file to load the data values. ● building dimensions is the process of loading dimensions and members to an essbase database outline by using a data source and a rules file. You can also use outline editor to add dimensions and members manually. Process for data loading and dimension building to load data values or dimensions and members into an essbase database, follow these steps: 1. Set up the data source. If you are not using a rules file, you must set up the data source outside essbase. 2. If necessary, set up the rules file. 3. Perform the data load or dimension build. Creating rules files a rules files tells essbase what changes to make to the data source and outline during a data load or dimension build. This chapter describes how to create a rules file for data loading or dimension building. Understanding the process for creating data load rules files to create a data load rules file, follow these steps: 1. Determine whether to use the same rules file for data loads and dimension builds. 2. Create a rules file. 3. Set the file delimiters for the data source. 4. Map each rules file field to the data source and define field properties. 5. If necessary, set record, field, and data operations to change the data in the data source during loading. 6. Validate and save the rules file. Understanding the process for creating dimension build rules files to create a dimension build rules file, follow these steps: 1. Determine whether to use the same rules file for data loads and dimension builds. 2. Create a rules file. 3. Set the file delimiters for the data source. 4. If you are creating a dimension, name the dimension. 5. Select the build method. 6. If necessary, change or set the properties of members and dimensions you are building. 7. If necessary, set record and field operations to change the members in the data source during loading. 8. Set field type information, including field type, field number, and dimension. 9. Validate and save the rules file. Combining data load and dimension build rules files before you start building a rules file, you need to decide whether the rules file will be used for data loads and dimension builds, or whether the rules file will be used for only for data loads or only for dimension builds. Once you create a rules file, you cannot separate it into two rules files. Similarly, you cannot merge two rules files into one file. Use the same rules file for both data load and dimension build if you plan to load the data source and build new dimensions at the same time. Use separate rules files for data load and dimension build under any of the following circumstances: ● to build an outline from scratch ● to perform different field operations during the data load and dimension build ● to re-use the data load or dimension build rules file separately ● to use data sources that contain no data values, only dimensions creating rules files to create a rules file: 1. If you are creating the rules file on the essbase server, connect to the server. Connecting to the server is not necessary if you are creating the rules file on the client. 2. Open data prep editor. You can open data prep editor with a new or existing rules file. After you open data prep editor, put the editor in the correct mode 3. Open the data source. In data prep editor, you can open data sources such as text files, spreadsheet files, and sql data sources. Data prep editor displays the data source, enabling you to see what needs to be changed. ● to open text files and spreadsheet files, ● to open sql data sources, to open an sql data source, use essbase sql interface. The essbase sql interface guide provides information on supported environments, installation, and connection to supported data sources. Contact your essbase administrator for more information. You can define a substitution variable for the data source name (dsn). When you open a sql data source, you can select the substitution variable for the value you want to use combining data load and dimension build rules files as the dsn. For example, you can create a substitution variable named payroll_detail and create a rules file that specifies payroll_detail as the substitution variable for the data source name. Before performing the data load or dimension build, you must set the value for payroll_detail to the data source name you want to use; for example, an oracle or ibm db2 database. When a data load or dimension build is performed, the substitution variable value that essbase server finds at that time is used understanding build methods the build method that you select determines the algorithm that essbase uses to add, change, or remove dimensions, members, and aliases in the outline. The kind of build method that you select depends on the type of data in the data source. Using generation references top-down data sources are organized left to right from the highest level to the lowest level. Each record begins with the most general information and progresses to the most specific information. The name of the new member is at the end of the record. When using a top-down data source, use the generation references build method. In the rules file, specify the generation number and the field type of each field of the data source. Essbase numbers members within a dimension according to the hierarchical position of the member within the dimension. The numbers are called generation references. A dimension is always generation 1. All members at the same branch in a dimension are called a generation. Generations are numbered top-down using level references in a bottom-up data source, each record defines a single member of a dimension. The definition begins with the most specific information about the member and provides progressively more general information. A typical record specifies the name of the new member, then the name of its parent, then its parent’s parent, and so forth. Levels are defined from a bottom-up hierarchical structure. Using parent-child references use the parent-child references build method when every record of the data source specifies the name of a new member and the name of the parent to which you want to add the new member. Members in a database exist in a parent-child relationship to one another.