Delete Attribute Dimension Using MAXL

Hi everyone,
Is there any option to delete attribute dimension using MAXL? Our requirement demands to delete and reload every night. Please suggest if anybody has did this before.
Thanks!

A post of the same sort of topic area :- HOW can i delete the members in dim using MAXL
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Creating dimensions using MaxL commands

Is there anyway to create one or more dimensions using MaxL commands?
Also setting their parameters like "Accounts/Time", "Label Only" and "Dense/Sparse"?

Here's a sample from the documentation:
import database sample.basic dimensions
from data_file '/data/calcdat.txt'
using rules_file '/data/rulesfile.rul'
on error append to '/logs/dimbuild.log';
Check: import dimensions in the MaxL part of the technical reference you will find more examples.

Creating a hierarchy in an attribute dimension using EIS

we use EIS for our data/member loads.
I have a couple of cubes with attribute dims and I had no problems using EIS to create those attribute dims as they did not have a hierarchy
I have a new requirement to create an attribute dim with a hierarchy.
I am not sure how can I do this in EIS. Please advice.
I went through the chm file but could not really figure out anything about it.
Thank you.

Actually you can have hierarchies in your attribute dims in EIS, including text attributes. I have a number of models where we do this.
It works the same as with regular dimensions. Assume you have a table with product codes and then a column for lev 0 attribute and lev 1 attribute.
So code is XYZ
Lev 0 attribute is Red
Lev 1 attribute is Primary
When you set up your attribute dim in EIS, set both attribute columns as attribute, then in the metaoutline model, drag lev1 attibute onto the outline, then drag lev0 attribute under it. You will get a warning that you can only associate the lev0 attribute with the base dimension, which is fine. Associate the lev0 attribute with the base dim as you normally would and build your outline.
Your end result will be an attribute dim that looks like this
Product Color
--Primary
----Red

How to create an attribute dimension in Essbase Studio?

I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?

so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info

Attribute dimension build method

Hi All,
Please do let me know the process to build the attribute dimension using rules file. I tried it following the same way as any other normal dimension but donot get the property associated to the attribute dim. We want this process to be automated as we rebuilt the ourline each time during the load. Pleaes help.
Thanks,
Praveen

Have a read of the section :- Building Attribute Dimensions and Associating Attributes
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1060796
Cheers
John
http://john-goodwin.blogspot.com/

Attribute dimension

Hi,
can we create groups in attribute dimension using rules file.
we can do it by manually , but i wanna do using rules files.please throw some light .
thanks
kishore

Yes you can, but you can't do in in the same rule that you assign the attributes to base dimensions in. You have to have a seperate rule to build the hierarchy

How to load data to attribute dimension

hi gurus,
I have two questions:
1. could I enter data into attribute dimension using SmartView?
2. how could i load data into attribute dimension using load rules?
Regards,
Daniel

Hi,
1.
You can't send data back into Essbase if your POV has an attribute specified. The attribute will calculate (by default it does a sum) your POV dynamically and only bring back data which has that attribute assigned to it.
If you want to send data back into Essbase then the easiest way would be to keep the same POV and just remove the reference to the attribute. Smartview will then let you send data back into the Essbase cube.
2.
Same answer as point 1. Attributes are ways of adding more detail to members that already exist. You dont' load data into the attribute, you load data into the member that the attribute is assigned to.
Hope this helps,
Gee

How to delete the members in one dimension use the maxl script

i have question that i want to delete the members in one dimension useing the maxl script, but i do not know how to do it. can the maxl delete the members in one dimension? if can, please provide an sample script, thank you so mcuh.

MaxL does not have commands to alter an outline directly, except the reset command which can delete all dimensions but not members selectively. The best you could do would be to run a rules file (import dimensions) using a file that contains the members you want to keepload rule for the dimension. As typical the warning is to test this first before you do it on a production database

HOW can i delete the members in dim using MAXL

Hi All,
I want to delete the all the memebers for dimensions before reloading so how ca n i write the maxl script for this to delete the members in the dimensions
plz can any one help on this its very urjent ,
It would be appriciated ...
Thanks

There is no way to alter an outline with MaxL, MaxL is an admin language for processing. The only option, as Glenn mentioned is to issue the reset all command to blow away everything. But you probably don't want to do that, so instead you use Maxl to run a series of load rules to achieve your goal.
Load rules do not have functionality to delete outline members, it does have a feature however that allows you to remove unspecified members from a dimension build, so when loading in your members, if existing members are not in the import, they are removed. So Glenn's point was to create a source file with a single dummy member. When you load using "Remove Unspecified" it will delete all the members and just keep the one dummy member. Then when you go back a second time and actually load the real members, the dummy member will be removed and you will have a clean dim with only your new members. This is a work around solution, but it's what a lot of people do.
Now if you have 15 dimensions you need to do this with, you might want to take a slightly different approach. I'm assuming 15 dimensions is probably an ASO cube and this method will be preferable to avoid outline fragmentation.
Create a copy of your outline with all the base dimensions that do not change intact. For the ones that do change, just have your dim root member. Consider this your starting outline template and save a copy of it. When you want to rebuild your cube have a server process that takes the copy of your template outline and copies it over your existing outline file in the directory structure. Then run your load rules to import your new members.

Maxl Command to delete a dimension from a outline

Hi All,
What is the maxl command to delete a dimension from a outline.
Thanks,
Ram..

Read :- HOW can i delete the members in dim using MAXL
It has your answer.
Cheers
John
http://john-goodwin.blogspot.com/

Error: 1030001 while Dimension Building using MaxL

Hi, I am bulding dimesions using MaxL import statement. My script builds the diemsions properly. But in Logfile, It shows this error without generating any error files. ...... ..... OK/INFO - 1021000 - Connection With SQL Database Server is Established. OK/INFO - 1021002 - SQL Connection is Freed. OK/INFO - 1007132 - Building Dimensions Elapsed Time : [0.781] seconds. ERROR - 1241101 - Unexpected Essbase error 1030001. OK/INFO - 1019017 - Reading Parameters For Database [Drxxxxxx]. OK/INFO - 1019012 - Reading Outline For Database [Drxxxxxx]. ...... ... Can anybody can help me out with it? I know that Error: 1030001 is geneated due to API or path problems, I checked all paths, all is good. Thanks in advance, Marma

We are getting this error too. I believe that the error occurs because Essbase tries to evaluate outline before you finish building all of your dimensions. To me, it should be a Warning, not an Error. But my experience with Essbase is that anything that has to do with GUI or presentation of information to its developers (non-scrollable text boxes, log info, etc.) is lousy, so this is not a surprise. I had to build a logic in my batch programs to ignore this error when parsing log file for errors in execution. Hope you can do the same.

Reporting on Attribute Dimension in HFR using Planning Connection

Hi,
We are using Planning/HFR version 11.1.2. We have one issue with Hyperion Financial Reports. For connecting to HFR we have used the Planning Database connection. Apart from Standard dimensions we have also got attribute dimensions in our application. When I go and develop a report in the FR Studio - in the Dimension Layout the Attribute dimensions are not displayed only the standard dimensions are available for report selection. We also want to report on the attribute dimension. Is there a way we can achieve that?
...We are aware that if we connect to FR using an Essbase connection the attribute dimensions show up on the Dimension layout but we have some text data to report at which essbase cannot handle.......
Any response on this would be highly appreciated
Alex

Hi Alex
That sounds like a bug, I have used attribute dimensions in reporting lots of times in earlier versions and I'm sure that some of those used planning rather than essbase connections. I've not read the documentation around the subject so can't be sure but it sounds pretty fundamental so I'd be surprised if not a bug.
Worth doing a bit of digging on Oracle support or in the readme files or even raising an SR if you have that option.
Regards
Stuart

Exporting Essbase Dimensions using ODI (specifically attribute)

I am working on creating a flat file using ODI connected to an Essbase database. I have set up my topology correctly and have been able to export the dimension into a .txt file succesfully. My issue I am having is when I try to include an attribute dimension associated with the main dimension (in this case, organization). I get the following failure:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 89, in ?
com.hyperion.odi.essbase.ODIEssbaseException: The source column [ServiceByAUTypeAttribute] is not valid for dimension [Organization]
I went to the specific line, but see nothing out of the ordinary. The column is a valid attribute dimension for Organization.

It means you have not set a staging area for your on columns on the target datastore, as you are using essbase in your interface you will need a staging area, essbase as a technology has no SQL capabilities.
Cheers
John
http://john-goodwin.blogspot.com/

Tutorial required for performing Dimension Build using Maxl

Hi all,
Can you please suggest me a Tutorial for performing Dimension Build using Maxl?
Best Regards

From the tech ref Samples
Exampleimport database sample.basic dimensions
from data_file '/data/calcdat.txt'
using rules_file '/data/rulesfile.rul'
on error append to '/logs/dimbuild.log';
Deferred-Restructure Examples
For Data File Sources:
import database sample.basic dimensions
from server text data_file 'genref' using server rules_file 'genref' suppress verification,
from server text data_file 'level' using server rules_file 'level' suppress verification,
from server text data_file 'time' using server rules_file 'time'
preserve input data on error append to 'C:\Hyperion\products\eas\client\dataload.err';
For SQL Sources:
import database sample.basic dimensions
connect as 'usrname1' identified by 'password1' using server rules_file 'genref',
connect as 'usrname2' identified by 'password2' using server rules_file 'level',
connect as 'usrname3' identified by 'password3' using server rules_file 'time'
on error append to 'C:\Hyperion\products\eas\client\dataload.err';
For Data and SQL Sources:
import database sample.basic dimensions
from server text data_file 'genref' using server rules_file 'genref',
from server text data_file 'level' using server rules_file 'level',
connect as 'usrname1' identified by 'password1' using server rules_file 'genref',
connect as 'usrname2' identified by 'password2' using server rules_file 'genref'
on error append to 'C:\Hyperion\products\eas\client\dataload.errr';>
Try it and post back if you have errors
Regards
Celvin
http://www.orahyplabs.com

How to create Base Dimensions with MaxL and Text File?

Hi,
Doing a scratch rebuild of a cube every month. Don't want to have a 'dummy' outline with base dimensions to copy over every build. Instead want to build from text file somehow. Thus my plan is to: 1) Delete the existing app/db 2) Create a new blank app/db 3) Create the base dimensions in the outline via text file and 4) Build entire outline via a text file. I'm stuck on #3 how to get the 'base dimensions' built via text file. I need:
ACCOUNTS
PERIOD
VALUE
VIEWS
SCENARIO
CUSTOM4
YEAR
CUSTOM3
CUSTOM2
ENTITY
CUSTOM1
I see this MaxL, but it uses a 'rules file' and I never have built a rules file to create base dims so I'm confused if it's possible or not...
import database sample.basic dimensions
from data_file '/data/calcdat.txt'
using rules_file '/data/rulesfile.rul'
on error append to '/logs/dimbuild.log';

We rebuild our Departments and Organization from an enterprise hierarchy master each week.
The way we implemented (what you call #3) was to not do #1 and #2, but to have a "destructive" load rule for each of these dimensions using a text file. (in the "Dimension Build Settings" for the load rule, select "Remove Unspecified" to make it destructive)
The text file just has the dimension name (parent) and any children we needed defined in a parent/child relationship. For instance
"Sales Departments" "0100-All Departments"
This essentially works the same as deleting the app because the destructive load rules will drop all the blocks of data that were unspecified.
Then we run our SQL load rule to build the rest of the dimensions from the Location Master.
We perform a level-0 export prior to this process, then reload the level-0 data and execute all the consolidation scripts to get the data back (now in a current enterprise defined hierarchy)

Delete Attribute Dimension Using MAXL

Similar Messages

Maybe you are looking for