Dimension Build Load Rule Reject Record

Hi,
I'm trying to create a load rule that build the accounts dimsenion with a flat file. I would like to exclude any accounts that starts with "S" from being added to the account dimension. I have a parent/child build method for this load rule. i'm using the Reject Record to set the condition that any string contain S will be rejected but for some reason when I load it doesn't do anything. it makes EAS freeze up. so, my flat file looks like this.
New Accounts,S50000,Accounts - S50000
New Accounts,60000,Accounts - 60000
New Accounts,S45000,Accounts - S45000

Hi,
Your posting does not tell me what you entered in the reject record setting to try to achieve the desired result. If you entered "S" and used the "Contains" setting it should have worked providing you know your data and don't have occurrences of this character possible other than in the first ordinal position. If you tried to use a wildcard asterisk callout, Essbase load rule select/reject logic does not take wildcard inputs (like "S*").
Instead, a tried and true trick of Essbase load rules is to make a copy of the field in question, split it up and take background select/reject action on just the first character of a reference copy of the original field. This is done by using the field "create on join" method and simply joining the field to itself (an unintuitive but effective way to make a copy of a field for use in the load rule settings). Having done this, now split the copy of the field after one character. The remaining field section can be set to ignore for dim builds (or data loads as you might have to do later to match your dim build results in data loads). Now you have a single character field for which you can set the reject setting of contains or equal to "S" and then... please get this part... ignore the field for dim builds in field properties. Essbase will not try to use this partial field to build anything since it is ignored, but the assigned reject logic on occurrences of the isolated single character field will still be interpreted.
This is old school Essbase but it still works. I am not here to say it is intuitive or that it represents the ultimate functionality in an ETL interface. Many with SQL skills would take care of this pre-load-rule in SQL string management. But this method is not that hard to apply and is effective if all you want to do is use load rule settings. Let me know if it helps.
Darrell

Similar Messages

  • Essbase Build Dimension using load rules - Jagged Recursive hierarchy

    Hi,
    I am building a dimension from data that has the following parent/child relationship
    PARENT CHILD
    A B
    C D
    C E
    C F
    A C
    Load dimension results in the following hierarchy:-
    A
    |__B
    |__C
    |_F
    C
    |_D
    |_E
    I would like the hierachy to be:-
    A
    |__B
    |__C
    |_F
    |_D
    |_E
    Is there a way to achieve this? Is is to do with the order of rows in the data file?
    Thanks
    Dinesh

    Hi,
    I agree with the advice already posted about allowing moves in your dim build settings on the dimension in question. I just want to help clarify the other comment about how your file is sorted. As long as you are building a main rollup only (i.e., no shared member, alternate hierarchies in the same input file), the Essbase parent/child build method doesn't require any particular record order (as long as the pairings are correct in and of themselves). Essbase p/c method is powerful for ragged hierarchy creation and also able to "figure out" the intended hierarchy.
    Now if you are including shared member relationships in the file, just be sure to have those records AFTER all records for the main rollup (logically as if you were simply using a second input file for the same rule). They don't have to be sorted within the rollup either.
    BTW, the other strength of the p/c method is the ability to handle upper level shares (i.e., when your shared members are referencing members that are above level 0 in their stored (main hierarchy) positions.
    Darrell

  • Dimension Build using Rule File

    I am using Oracle Hyperion Ver 9.3.1. While formatting the dimensions built using the rule file i came across the options "JOIN" and "Create Using Join". Can anyone help me in knowing the difference between these two options?
    Edited by: 873675 on Jul 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.
    Joining Fields
    You can join multiple fields into one field. The new field is given the name of the first field in the join. For example, if a data source has separate fields for product number (100) and product family (-10), you must join the fields (100-10) before loading them into the Sample.Basic database.
    Creating a Field by Joining Fields
    You can join fields by placing the joined fields into a new field. This procedure leaves the original fields intact. Creating a field is useful if you need to concatenate fields of the data source to create a member.
    For example, if a data source has separate fields for product number (100) and product family (-10), you must join the fields (100-10) before you load them into the Sample.Basic database. If, however, you want to preserve the two existing fields in the data source, you can create a field (100-10) using a join. The data source now includes all three fields (100, -10, and 100-10).
    For other rule options read - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/ddlfield.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Load rules generate by Essbase Studio

    I'm using Essbase Studio to create dimension build load rules in Essbase. When the dimension load rules are created in Essbase, does it use the ODBC connection in the Essbase server or in Essbase Studio?

    It depends on if you are using streaming or non-streaming mode. If streaming mode then it has to be on the Essbase server if non-streaming mode then it goes through the Studio server

  • Shared Members in Load Rules

    Hello,I am trying to build a dimension build load rule.How do you create shared members within a dimension? Does it have to be through a parent-child load rule? What if you have a subset of a dimension, (eg duplicate hierarchy) with more then two levels, ie parent child? How do you create shared memebers then?Any help would be greatly appreciated.Thanks.

    I'm a newbie in dim build using load rule too. I'd a bunch of products that had to be in 2 roll-up structures, apparently as shared members in one of them. It took little effort to build the first roll-up using a generation build method. Just when I thought it was gonna be a slam dunk, I couldn't create the second roll-up. I kept trying different load options but it just wouldn't work. I noticed the "Do Not Share" check box was always disabled. So I clicked on the different build method buttons. I noticed that the box become enable when I selected the parent/child method. I tried and it turned out to work fine. So, for the little knowledge I have, it seems you must use the parent/child rule to create shared members.

  • Alternate hierarchy dimension build with load rules

    Hi,
    I am trying to build a alternate hierarchy dimension using load rules (I feel using EIS is easier to build ASO and multiple hierarchies but we r trying to get rid of EIS member loads). Looking at different posts my understanding is it has to be done using two different rules file first to build the stored hierarchies then use parent-child reference to build the shared hierarchy. Below is the link for the picture how I am trying to build the dimension. I've tried different possibilities but no luck, I am having a tough time to come up with a way to do this using rules file.
    http://s24.postimg.org/u5hl4eyqt/basis.jpg

    If your file is in a parent/child order, then you can build easily in one rule. make sure the primary (stored Hierarchy) gets built first followed by the alternate hierarchies. I suggest adding a SortID column to the source so you can sort the file to get it into the right order. You can also build the alternate hierarchies using level or generation builds in one load rule, but especially if you have a lot of alternate hierarchies or members, then the parent/child method is easiest.
    Read in the DBAG about parent/child files and it will give you more info

  • Dynamic dimension building

    Hi
    In our project we are using Essbase11.1.4 version.We have a 8 Dimensions.For one dimension we are loading new members ( some account numbers ) every month through informatica-Essbase connector ( Dynamic dimension building ) with rules.The new members are adding below the existing members.But for smartview reporting purpose client wants one member ( Accounts Total ) to be retained always at last.Can we do this ?Please help.
    Version - Essbase 11.1.4
    Thanks
    Edited by: Palem on Dec 10, 2012 10:29 PM

    Can some one help please ?

  • Load Rule (Dimension Build) using "Add as Child of"

    I have a dimension file that contains Level0 Members, Aliases and Agg Signs. When I use the Build Method of "Add as Child Of", I appears that I cannot add the Alias in the same Load rule. On the first field, I select the Dimension with no Field Type or Number. On the next field, I select Alias and the Dimension, however, when I put a level number of 0, the load rule does not verify and if I try to leave the Number blank then I I get an error the error message of "You must specify a valid number for this field type".How do you add aliases, properties, etc when using the Dimension build with the build method of "Add as child of" in the same load rule? I cannot find anything in the DBAG.Thanks.....

    As your post seems to indicate, there is no way to do it in one pass. There are a few things that you can't do the way you should be able to - like, say updating two alias tables at once... Regards,Jade------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • Null transformation in Studio generated rules fails to build / load

    I have a dimension field with nulls in my table.
    Luckily there is a handy <Null> search and replace rule in Studio.
    Not-so-luckily it fails to do what you'd think, ie. transform nulls.
    The dimension is built without the desired member.
    The dataload fails due to "data item found before member" because the column with the nulls is skipped, not transformed.
    Looking at the data load rule, it looks like it should work. Ie. the transformation displays properly. But it doesn't work when you deploy the cube.
    And of course you can't look at the Studio-deployed dimenstion build rule. Our innocent eyes apparently can not handle such things. But I'd expect you'd sees something that appears to work on display but doesn't build what it shows.
    Anyone seen this or have any ideas, besides modifying the source data which is the road I'm going to have to take. Call me silly, but I think the tool should be able to do this, not just pretend to.
    Thanks.
    Todd Binenstock

    Glenn,
    Thanks. It's been a trip. Yes, ultimately I gave up and got an NVL() put into the view I was given.
    I looked at the load rule and it appears to do the null substitution when you manually retrieve/view the records within the rule, but it clearly fails to work when it actually builds/loads.
    You can do a custom SQL to do the build, but there won't be a member on the dimension to load to unless you get the null transform in the build rule. And of course you can't edit that SQL (except some minimal hacks you can do in the binding using CPL)
    I tried adding a manual member and got a "duplicate field in query" error and did not see anything wrong. Opened an SR and got a call 3 weeks later after going another direction. Theoretically that should work, I just haven't gotten back to it.
    I was trying to use the tool for transformations instead of SQL, mostly to see what it can do. So far, not so happy on the nulls. I think its more of a load rule issue than a Studio issue. Just wish someone would make it work like you'd expect. I am getting good at workarounds, but a little tired of things almost working as advertised.
    Todd Binenstock

  • Rejected Records when building my cube

    the sql statement of the allocation works fine and gives the right result
    SELECT /*+ bypass_recursive_check cursor_sharing_exact no_expand no_rewrite */
    T1_PUR_DATEORDERED ALIAS_1,
    T1_PUR_CTRORIGIN_UID ALIAS_2,
    SUM(T1_PUR_AMTFREIGHTBC) ALIAS_3
    FROM
    SELECT /*+ no_rewrite */
    T1."PUR_DATEORDERED" T1_PUR_DATEORDERED,
    T1."PUR_CTRORIGIN_UID" T1_PUR_CTRORIGIN_UID,
    T1."PUR_AMTFREIGHTBC" T1_PUR_AMTFREIGHTBC
    FROM
    CHDDL."ITS$QSI$BIVIEWPURCHASE" T1 )
    T1
    GROUP BY
    (T1_PUR_CTRORIGIN_UID, T1_PUR_DATEORDERED)
    ORDER BY
    T1_PUR_CTRORIGIN_UID ASC NULLS LAST ,
    T1_PUR_DATEORDERED ASC NULLS LAST
    However when I build it I always get 35570 invalid member of the target dimension
    in AWM 11.2 I get very strange characters listed. this is not the case with slqplus. when I select out of rejected records I get as well strange characters.
    desc of my cube shows varchar2(19), varchar2(16) and number
    the direct query under sqlplus shows
    ALIAS_1 ALIAS_2 ALIAS_3
    2008-12-03 00:00:00 zzz0000000000n4 0
    2009-05-09 00:00:00 zzz0000000000n4 0
    2009-05-11 00:00:00 zzz0000000000n4 0
    2009-05-12 00:00:00 zzz0000000000n4 0
    2011-05-25 00:00:00 zzz0000000000n4 0
    2011-09-05 00:00:00 zzz0000000000n4 0
    6 Zeilen ausgewõhlt.
    in rejected recordes it shows
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    1
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    2
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    3
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    4
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    5
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    46736 9584 35570
    (XSRWLD06) Ein Spaltenwert ist kein g³ltiges Member seiner Zieldimension.
    6
    ┐┐┐┐┐ë┐┐┐┐┐┐┐┐┐┐┐┐┐
    Dimension building works fine,
    Any Help would be appreciated
    Christof
    Edited by: 883727 on Oct 3, 2011 9:14 PM

    Hi there,
    The only situation where records get rejected is when the relevant dimension values are not present and the fact record cannot be joined on one (or more) of it's foreign key records.
    Have you maintained all of your dimensions first?
    Thanks,
    Stuart Bunby
    OLAP Blog: http://oracleOLAP.blogspot.com
    OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
    OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
    DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

  • Dimension Build Rule converting characters to ascii

    Hi
    I have a dimension build rule which has been in place over a year. However every few weeks it converts some of the dimension members to ascii characters but loads with the correct alias. The next time the load runs, it tries to enter the real member and it falls over as the alias is not assigned to the member with the ascii characters.
    Has anyone seen this before or have any suggestions as to what could be causing it.
    Thanks

    Have you tried recreating the load rule to see if it's some form of weird corruption?
    That doesn't seem very likely (it's either corrupt or it's not <--This is why I Like Computers) -- how about can you confirm that your source is exactly the same both times? I'll bet it's not and you just see the result manifested in the dimension build.
    Regards,
    Cameron Lackpour

  • Dimension build rule file (Sort member)

    I am loading sorted data for one of the dimension. But its is not coming in sorted fashion in outline. New member which i am adding is always coming in The end.Even though that member is in sorted format in the file.
    I am using generation method . I am putting member for only generation 2 and its alias.I tried using ascending option but it is giving me error
    Can any body help me with this

    As Glenn said, the build only builds new members. In order to have FULL control over the order of a resultant dimension's order, you need to blank out the dimension first and then build via the load rule. As Glenn mentioned, you can do "incremental dimension building". You can do this directly in EAS in an interactive manner by using outline/update outline in pull downs. Just do not save the outline until all your changes are done. You can also accomplish incremental builds via Esscmd or via MaxL, but I'll assume for right now you are still testing. The advantages of the incremental changes is that you can do a number of changes before Essbase commits to doing a restructure, which is time consuming, not to mention confusing if you are "deleting" (however temporary) the entire dimension's hierarchy.
    Regarding setting ascending order
    1) in the load rule's Dimension Build Settings prompt
    2) Select Dimension Build Settings tab
    3) highlight the dimension you are changing
    4) select Ascending for sort order
    This should work...I've never had it error out. However, I will say that it sorts the entire dimension...not just the siblings of a new member. Your upper level members will move as well. Because of this, the ascending sort in a load rule is undesirable. Give it a try. If you don't like the results, just don't save the outline.
    Kevin

  • MAXL - using multiple Dimension build rules in single script...

    I seem to be having problems running multiple Dimension build rules in a single MAXL script, is this a known problem or just an issue that I'm having? The build rules independently work as designed but when joined into a single script the script hangs...
    So, this is a 2 part question...
    1) Does MAXL not play nice when using multiple Dimension load rules in a single script?
    2) Do I need to run the build rules independent of each other?
    Also, is there some type of refresh/update on the cube that you can use in the script and would it be necessary...?
    Thanks for any light you can shed on the issue.
    Adam,

    I've written multiple dimension build statements as a part of 1 long MaxL statement. I'm executing this MaxL via a shell script (that replaces the variables such as username, password, servername, file path etc.) I've not seen any issues doing so.
    However, I've noted that, number of imports statements in 1 single MaxL command does not bode well for more than *60* import statements at once. So, if you're using more than 60 source files to build your dimensions, please consider breaking up your MaxL into multiple statements.
    Note: All but last of the import statements have 'deferred' re-structure specified. It speeds up the build process.

  • Load rule failure in ASO cube building

    Hi
    I have an ASO cube and I'm trying to use a load rule to build my entire Measures dimension. Everything seemed to be working fine before, I had about 7,000 measures tagged with a particular UDA, however, now when I do the build, only about 2,200 of the members are getting tagged with the UDA, although there is no error file. There doesn't seem to be any rhyme or reason as to why some members are successfully getting the UDA assigned to them and some aren't. I even tried creating a new load rule and using a text file with the particular accounts, and again, it says everything was fine, but when I go back and look at the outline it's hit and miss. Any thoughts?

    Hi,
    I dont see any reason ,why it add UDA's for few and does not for few.
    I request you to do the following
    1. Check the data file
    2. Check the rule file
    3. and as per the definitions of the rule file ( i.e build properties, data source options ..etc.
    see ,whether the data file is in harmony.
    Sandeep Reddy Enti
    HCC

  • Choosing Dimension Members / Creating Data Load Rule Files

    Hi
    Let me explain this problem using an example. Let's say I have a dimension table called "Product" and its has ProductId, ProductCode & ProductName fields, and a Fact table with ProductId and Value columns. As you can see ProductId has beed used to link to Fact table. I want to display ProductCode as dimension members (ProductName as Alias). I have no problem creating this scenario using EIS. But when I am not sure whether I could do this with EAS. I tried but I cannot get it working. Does anybody know to do this in EAS please? Also, how to create the data load rule for this problem using ProductId?
    Regards
    Chandra

    You can do this using a SQL load rule.
    One rule to build your dimension, simply select statement on the one Dimension table.
    Second rule to load data is going to require a Select statement with a join to pull the product name from the dimension table and the data from the fact table linked on the Product id.

Maybe you are looking for