Order calculating attribute dimension

Hi all,I have an outine with 4 dimensions measure ( dimension tagged as accounts and desnse )Scenario (dimension tagged as dense)Year (dimension tagged as sparse) (Y02,Y03, Y04)store (dimension tagged as sparse)society (attribute dimension) ( soc1,soc2,soc3)The base dimension of the attribute is store.The dimension are displayed in the outline as described above.The dimension measure has a the following members price pieces number""medium price"= price/"pieces number" (tagged as dynamic and Two-pass calculations )the dimension Scenario has 2 members Actual , "Previous year" (tagged as dynamic and Two-pass calculations) with the following formula:if (@ismbr(Y03) ) Actual->Y02;elseif (@ismbr(Y04) ) Actual->Y03;endif;when I display from excel the memberssoc1 "medium price" Y03 "Previous year" Essabase produces incorrect results ( "medium price" is not price/"pieces number") why?Thanks, lucia

1) Is year tagged as 'Time'?2) Why is the year formula two-pass?Rich SullivanBeacon Analytics

Similar Messages

  • Calculation issue on attribute dimension

    The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
    "Two-pass calc skipped on member [X] in attribute calc"
    Please advise on how to resolve this.
    Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
    It also says that Two-pass calculation member property is unavailable for attribute dimensions.
    So does it mean that every two pass calc member is skipped?
    I'm a bit confused.. how does it work?
    Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
    Thanks.
    null
    .

    Hello,
    I will give it a try:
    << I assume you have the two-pass calc member on the accounts dimension and the associated dimension of the attribute dimension is not the accounts dimension either. >>
    Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
    So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
    The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
    You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
    Hope this helps a bit.
    Regards,
    Philip Hulsebosch
    www.trexco.nl

  • Outline Ordering of Dense Dimensions

    To optimize your cube I understand that you first have your dense dimensions at the top of the outline then your sparse with few members, then sparse with most members and last your attribute dimension. But didn't find any provision of which order a dense dimension should be? Should the dense dimension with few members be at the top or dense dimension with most members?TIA

    The recommended configuration is the "hourglass" shape - largest dense to smallest, smallest sparse to largest. Personally, I can understand the sparse dimension ordering - it has an impact on the efficiency of the calculator cache, but I have not seen any documentation or experienced significant performance gains by changing the order of dense dimensions.That being said, changing the order of dense dimensions WILL have an impact on the calculation order, which may be important if you have certain types of formulas or dependencies in your dense dimensions.The thing to keep in mind about optimization is that the order of the dimensions in your outline is probably lower on the list of priorities, behind the sparse/dense settings, optimizing scripts, using dynamic calcs, intelligent calc, etc.Regards,Jade---------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • Problems with multiple Attribute Dimensions

    Hello Guys,
    when i try to get data from an Essbase database using the Grid API with more then one Attribute Dimension,
    the server needs a very long time to response or doesn't response at all.
    I encounter the same behaviour when i perform a query using the Excel Query Designer.
    Here is a sample query log output:
    <subquery>
    <cluster size="1">
    <dim size="1"><member>MEASURE</member></dim>
    <dim size="1"><member>PERIOD</member></dim>
    <dim size="1"><member>YEAR</member></dim>
    <dim size="1"><member>CATEGORY</member></dim>
    <dim size="1"><member>CURRENCY</member></dim>
    <dim size="1"><member>CUSTOMER</member></dim>
    <dim size="1"><member>PRODUCT</member></dim>
    <dim size="1"><member>Business</member></dim>
    <dim size="1"><member>black</member></dim>
    <dim size="1"><member>Attribute Calculations</member></dim>
    </cluster>
    </subquery>
    <elapsedtime>94.217 seconds
    Any help would be appreciated.
    Regards,
    Martin Brandl

    Thanks for the swift response. Always ideas are useful.
    As of now , Middleware cannot split the file.
    Thing is SAP is creating two Idocs with different message types. Problem is First IDoc contains ORDERS message type but also DELIVERY segments as well. Second IDoc with DELIVERY message tyoe but ORDERS segments as well... This is the problem... I think we are missing some field activation in file for EDIDC record.
    As far as I know file port supports the number of IDocs in one file.. Hope TRFC port also supports that

  • Re-Order the Sparse Dimensions

    Hi,
    We have a typical scenario where in we need to change the order of sparse dimensions in the outline.The cube is already in use,however,as we got rid of few members in one of the sparse dimension and we want to change the order of sparse dimensions in the outline to enhance the performance.
    My question here is,
    1.How to change the order of the sparse dimensions in the outline?
    2.What would be the impact?
    Any quick response on this is highly appreciated !!
    Thanks,
    RNG

    1) We can improve calculation performance by changing the order of standard (not attribute) sparse dimensions in the database outline. We can Order standard sparse dimensions by the number of members they contain, placing the dimension that contains the fewest members first.
    This arrangement provides a number of possible improvements, depending on the site:
    ●The calculator cache functions more effectively, providing approximately a 10% performance improvement if you have a database outline with a very large dimension (for example, a dimension containing 1000 members).
    ●Parallel calculation, if enabled, is more likely to be used if the standard sparse dimension with the most members is the last standard sparse dimension in the outline.
    2) I think there would not be an any impact...
    JSA

  • Hierarchical attribute dimension with Essbase Studio

    Hi everybody,
    I need to load product dimension which is organized in a relational parent-child table like this:
    (parent_code, member_code, member_alias, brand, consolidation, formula)
    Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has its own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
    (brand_parent, brand_child, brand_alias).
    I need to do this load with Essbase Studio but I do not known how to create the Product hierarchy in cube schema in order to load the hierarchical parent-child attributes. Documentation and tutorials only show examples for flat attributes. I thought of these two ways but not sure if will work:
    case 1) Product hierarchy like this:
    Parent_code
    Member_code
    Brand_parent
    Brand_child
    Member_code
    case 2) Product hierarchy like this:
    Parent_code
    Member_code
    Brand_parent
    Brand
    Member_code
    Has anyone had to this? How did you do it?
    Any help will be very appreciate.
    Thank you,
    Daniela

    I've not tried it, but you should be able to build the attribute hierarchy within the product hierarchy. sort of like
    Parent Code
    ---member Code
    Brand Parent
    ---Brand Code
    -----Member Code.
    A couple of things
    1. Remember to create the self join between Parent_code and Member code
    2. IF this does not work, I suggest creating either a user defined table or a view that just gives you distinct brand parent and Brand Code. Join the Brand Code to the product table on brand_code = brand code and use that table to build that hierarchy.

  • Attribute Dimension or Alternate Hierarchy

    Hello,
    We have a sparse dimension that has probably around 1500 members. We need to report on these members in different views then the current hierarchy holds. Is it best to create an alternate hierarchy with these 1500 members or to tag these members with various attributes and then use the attribute in the different reports. I did some research and found that attribute dimensions often have slow FR performance since they are dynamic, however, I feel like 1500 shared members is a lot. Any tips, tricks, advice would be greatly appreciated.

    Hi,
    I don't think 1500 shared members is a concern in and of itself (unless you are putting them all under one dynamic parent!). You are correct there could be some response time impact with attribute dimension retrievals, but then shared members under dynamic sparse parents may present similar concerns.
    I would encourage you to think about the structure and navigability desired. You should keep in mind that shared member rollups can only be used in reports consistent with the dimension they are in. One advantage of attribute dimensions over shared rollups is that, only with attribute dimensions, can you cross-tab report against the base dimension. If your users care about being able to see certain alternate groupings across the main dimension, then I would suggest going with attribute dimensions.
    There are other considerations. For instance, adding a large number of shared rollups in your BSO anchor dimension (the physically last dimension with hierarchy), you put more demand on Essbase calculator cache.
    Out of time for now. Just sharing some initial thoughts I hope you will find helpful.
    Darrell Barr

  • Sorting Attribute dimension members

    Other then reloading attribute dimension members in a different order. Is there a possbility with ODI or the SortMember.cmd utility to perform such a task?
    I ask since I know presently while reloading the attribute dimension with ODI it drops the latest member to the bottom. This is not the order I need it in. I tried to mess with the load in ODI and still no fix. I tried to use the SortMember and it only appears to work on all dimension but currency, period, and years as it reads in the planning admin guide. This is for 11.1.2.1.
    Does anybody have any input? If so please reply.
    Thanks,
    DjSmeadly

    It is one area that has never been addressed so sorting attribute members is not so easy, as far as I aware the sortmember utility does not work on attribute dimensions.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Problem adding attribute dimension

    Version: 9.2
    Cube: ASO
    I feel like I am dropping the ball. I am trying to add an attribute to my ASO cube at the bottom of my outline. Everything I try to edit the member properties I get an "Attribute Calculations dimension can not be created". I don't have any calculations/consolidations.
    When I click the database properties-->Attribute settings-->Calucation dimension names-->(try entering a name) all I get is "NULL value for member name string".
    When I use ASOsamp(or any app) I can create/tag an attribute dimension though.

    Hi There,
    I guess you might've added a Gen1, member, i.e. a dimension, at the end of the outline & intended it to be an Attribute dimension. Correct?
    If yes, after adding the member at the end,
    - Before opening the dialog for member properties, tag the dimension as "Attribute" by clicking on the appropriate icon, right on the outline page.
    - Associate this attr. dim to one of your sparse dims.
    - Add a member to the Attribute dim. & associate it with one of the members of sparse dim.
    - Now, it should let you save the outline.
    Good luck!
    - Natesh

  • Deploying Essbase Text-Attribute Dimensions

    Hello,
    we have an Essbase-cube with a text-attribute dimension. All associations are fine, also the validation. The deployment fails with the error:
    "Level zero members defined as dynamic calc must have a formula assigned to them"
    As it is an attribute dimension, there is something wrong.
    Any help apreciated!
    Michael

    Are you sure you don't have an Account or some other dimension's member that has been tagged as dynamic calc and yet does not have a formula?
    That's the message you'll get when that happens.
    The Planning refresh should (hopefully) show you which member is that way. Failing that you can go into Essbase and try doing outline validations -- I suspect the error will not have gone across but it may be worth a try. If the latter is the case, you are going to have to compare the two -- Planning and Essbase to find that dynamically calculated member without a formula.
    Regards,
    Cameron Lackpour
    P.S. The message sort of makes sense, sort of -- attribute dimensions are dynamic, but I've never personally seen this error.

  • Outline will not restructure after adding another attribute dimension

    I have a large ASO outline - 9 dimensions with 30 attribute dimensions. When I add another attribute dimension - top level - and then add a single child, the outline will no longer save and restructure itself. If I clear all the data in the cube and load the new attribute, it will save and restructure. I can then add all of the data back in and actually add or remove attribute members and the cube will save and restructure itself. I have tried to up the memory setting on the application - in various increments - up to 1.5GB with no difference in performance. While I can (may have to) live with the fact that I can load the attributes in during the nightly rebuild cycle by placing them in the correct build order in the MaXL scripts, I can no longer run an update for that attribute in EAS console on demand. Has anyone else had this problem with a large number of attribute dimensions in their ASO cube and if so, how have you gotten around it. As a side note, I cannot compress the outline even after clearing the data and aggregations. The "Compact Outline" routine hangs and I have to kill EAS to stop the process. Thanks,

    Have you taken the new RAM stick out yet?
    Powerbooks can pretty picky when it comes to RAM.
    Joe

  • Linking 2 attribute dimensions

    Dear all,I have an application that contains, among others, an "Entity" dimension and a "Territory" dimension, both of them are sparse.I have created an attribute dimension on each.The problem starts now: each entity has a natural territory where selling directly to customers is allowed (the French entity or subsidiary is allowed to sell in France); however, sales to other territories other than its own must be done through the corresponding entity or subsidiary.I have started tagging the entities with the attributes: "France"... but Essbase does not allow me to tag the territories with exactly the same attributes: I cannot use "France" for a territory.1) what is my best option for the outline2) how can I easily check in a script (in a FIX) that for the Entities in their natural territories some calculations must be done; and different calculations for the rest of the territoriesThank you very much for your help

    Yes, you can. You just cannot assign 2 attributes from the same attribute dimension to the same member.

  • Setting Evaluation order and Reordering dimension

    hi i was going through the hp admin pdf and i have a few doubts
    what do you mean by setting the evaluation option in planning means and why is it reccomended to select only one dimension(setting evaluation order)
    in "About Reordering Dimensions" topic it was mentioned about the ordering of aggregating sparse dimensions before non aggregatin ones , what are these two types and also it was said to arrange the sparse dimensions in the order of more sparse members to less sparse members but isnt it the opposite way around i mean as per the hour glass model the order should be from least sparse to most sparse dimension and attribute dimension in the end
    what exactly is the diffrence in Setting Evaluation Order and Reordering dimensions ?

    Reording the dimensions sets the order of the dimensions in essbase, reordering the dimensions can be part of optimizing the database.
    Setting the evaluation order is more to do with how the dimensions are evaluated in forms, so if account is set to be first then the properties of the account members data type will be used first, for instance if the account member is set to Percentage then member will be displayed as a percentage.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error While Building Attribute Dimension in ASO Cube

    Hi all,
    Cuurently I'm trying to bulit an ASO application in Oracle EPM 11.1.1.3
    When I'm building an attribute dimension "QSize" in ASO cube ,I'm Getting some Warnings
    I'm using Flat file as my source AND MY RULE FILE IS
    GEN2,QSIZE, ALIAS2,QSIZE
    1, ">100"
    2, "100-249"
    3, "250-499"
    4, "500-1000"
    5, "<1000"
    I VALIDATED THE RULE FILES,
    when i try to load the data into the essbase,Its giving me a warning stating that
    Record #1 - Incorrect Syntax For Member <100 (3305)
    *1 "<100"*
    and i don't see the alias name for member 1
    I came know that Essbase doesn't allow ">" character at the beginning of Dimension Or Member Name
    Please let me know if there is Any other way,where I can Assign the alias "<100"
    Thx in Advance
    Regards,
    RSG
    Edited by: SG on Jan 22, 2011 3:03 PM
    Edited by: SG on Jan 22, 2011 3:04 PM
    Edited by: SG on Jan 22, 2011 3:06 PM

    Could you get away with an underscore? I think that works. You will have _<100 which is not ideal but might be worth a try.
    Failing that, go with GT and LT. <--This is incredibly lame, but sometimes users go for the "computer is too stupid" answer. Which in this case, is sort of true.
    Regards,
    Cameron Lackpour

  • Problem with calculated attribute

    I have created a calculated attribute on an Entity that derives its value from two persistent attributes.
    I am only interested in displaying the calculated attribute and not the attributes it is derived from.
    If I put the calculated attribute in a View object without the other attributes I will get an error ( (oracle.jbo.DMLException) JBO-26080: Error while selecting entity for AccountPosting) when displaying data from the View object.
    This error does not occur if I add the other attributes to the View object and it all works OK.
    Why is this? Surely the calculated attribute is only calculated at the Entity object layer, so what does the View object have to do with this?

    The Java datatype for the two Number attributes is Number
    When I switch to Integer or Long, I get an error but the stack is different.
    oracle.jbo.DMLException: JBO-26080: Error while selecting entity for SLEO
         at oracle.jbo.server.BaseSQLBuilderImpl.doEntitySelect(BaseSQLBuilderImpl.java:658)
         at oracle.jbo.server.EntityImpl.doSelect(EntityImpl.java:5025)
         at oracle.jbo.server.EntityImpl.lock(EntityImpl.java:3386)
         at oracle.jbo.server.EntityImpl.setAttributeValueInternal(EntityImpl.java:2148)
         at oracle.jbo.server.EntityImpl.setAttributeValue(EntityImpl.java:2079)
         at oracle.jbo.server.AttributeDefImpl.set(AttributeDefImpl.java:1774)
         at oracle.jbo.server.EntityImpl.setAttributeInternal(EntityImpl.java:1032)
         at mypackage2.SLEOImpl.setDETAIL(SLEOImpl.java:113)
         at mypackage2.SLEOImpl.setAttrInvokeAccessor(SLEOImpl.java:144)
         at oracle.jbo.server.EntityImpl.setAttribute(EntityImpl.java:945)
         at oracle.jbo.server.ViewRowStorage.setAttributeValue(ViewRowStorage.java:1241)
         at oracle.jbo.server.ViewRowStorage.setAttributeInternal(ViewRowStorage.java:1150)
         at oracle.jbo.server.ViewRowImpl.setAttributeInternal(ViewRowImpl.java:1111)
         at oracle.jbo.server.ViewRowImpl.setAttrInvokeAccessor(ViewRowImpl.java:1086)
         at oracle.jbo.server.ViewRowImpl.setAttribute(ViewRowImpl.java:833)
         at oracle.jbo.jbotester.JboTesterUtil.setData(JboTesterUtil.java:173)
         at oracle.jbo.jbotester.JBOFieldHelper.setDataValue(JBOFieldHelper.java:114)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEdit(JBOFieldHelper.java:175)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEditAndValidate(JBOFieldHelper.java:205)
         at oracle.jbo.jbotester.JBOFieldHelper$DefaultJBOFocusListener.focusLost(JBOFieldHelper.java:239)
         at java.awt.AWTEventMulticaster.focusLost(AWTEventMulticaster.java:172)
         at java.awt.Component.processFocusEvent(Component.java:5006)
         at java.awt.Component.processEvent(Component.java:4888)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:777)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:497)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    ## Detail 0 ##
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]FOR UPDATE cannot be specified on a READ ONLY cursor.
         at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown Source)
         at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
         at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
         at oracle.jbo.server.BaseSQLBuilderImpl.doEntitySelect(BaseSQLBuilderImpl.java:533)
         at oracle.jbo.server.EntityImpl.doSelect(EntityImpl.java:5025)
         at oracle.jbo.server.EntityImpl.lock(EntityImpl.java:3386)
         at oracle.jbo.server.EntityImpl.setAttributeValueInternal(EntityImpl.java:2148)
         at oracle.jbo.server.EntityImpl.setAttributeValue(EntityImpl.java:2079)
         at oracle.jbo.server.AttributeDefImpl.set(AttributeDefImpl.java:1774)
         at oracle.jbo.server.EntityImpl.setAttributeInternal(EntityImpl.java:1032)
         at mypackage2.SLEOImpl.setDETAIL(SLEOImpl.java:113)
         at mypackage2.SLEOImpl.setAttrInvokeAccessor(SLEOImpl.java:144)
         at oracle.jbo.server.EntityImpl.setAttribute(EntityImpl.java:945)
         at oracle.jbo.server.ViewRowStorage.setAttributeValue(ViewRowStorage.java:1241)
         at oracle.jbo.server.ViewRowStorage.setAttributeInternal(ViewRowStorage.java:1150)
         at oracle.jbo.server.ViewRowImpl.setAttributeInternal(ViewRowImpl.java:1111)
         at oracle.jbo.server.ViewRowImpl.setAttrInvokeAccessor(ViewRowImpl.java:1086)
         at oracle.jbo.server.ViewRowImpl.setAttribute(ViewRowImpl.java:833)
         at oracle.jbo.jbotester.JboTesterUtil.setData(JboTesterUtil.java:173)
         at oracle.jbo.jbotester.JBOFieldHelper.setDataValue(JBOFieldHelper.java:114)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEdit(JBOFieldHelper.java:175)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEditAndValidate(JBOFieldHelper.java:205)
         at oracle.jbo.jbotester.JBOFieldHelper$DefaultJBOFocusListener.focusLost(JBOFieldHelper.java:239)
         at java.awt.AWTEventMulticaster.focusLost(AWTEventMulticaster.java:172)
         at java.awt.Component.processFocusEvent(Component.java:5006)
         at java.awt.Component.processEvent(Component.java:4888)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:777)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:497)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
    ----- LEVEL 1: DETAIL 0 -----
    java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]FOR UPDATE cannot be specified on a READ ONLY cursor.
         at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
         at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown Source)
         at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
         at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
         at oracle.jbo.server.BaseSQLBuilderImpl.doEntitySelect(BaseSQLBuilderImpl.java:533)
         at oracle.jbo.server.EntityImpl.doSelect(EntityImpl.java:5025)
         at oracle.jbo.server.EntityImpl.lock(EntityImpl.java:3386)
         at oracle.jbo.server.EntityImpl.setAttributeValueInternal(EntityImpl.java:2148)
         at oracle.jbo.server.EntityImpl.setAttributeValue(EntityImpl.java:2079)
         at oracle.jbo.server.AttributeDefImpl.set(AttributeDefImpl.java:1774)
         at oracle.jbo.server.EntityImpl.setAttributeInternal(EntityImpl.java:1032)
         at mypackage2.SLEOImpl.setDETAIL(SLEOImpl.java:113)
         at mypackage2.SLEOImpl.setAttrInvokeAccessor(SLEOImpl.java:144)
         at oracle.jbo.server.EntityImpl.setAttribute(EntityImpl.java:945)
         at oracle.jbo.server.ViewRowStorage.setAttributeValue(ViewRowStorage.java:1241)
         at oracle.jbo.server.ViewRowStorage.setAttributeInternal(ViewRowStorage.java:1150)
         at oracle.jbo.server.ViewRowImpl.setAttributeInternal(ViewRowImpl.java:1111)
         at oracle.jbo.server.ViewRowImpl.setAttrInvokeAccessor(ViewRowImpl.java:1086)
         at oracle.jbo.server.ViewRowImpl.setAttribute(ViewRowImpl.java:833)
         at oracle.jbo.jbotester.JboTesterUtil.setData(JboTesterUtil.java:173)
         at oracle.jbo.jbotester.JBOFieldHelper.setDataValue(JBOFieldHelper.java:114)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEdit(JBOFieldHelper.java:175)
         at oracle.jbo.jbotester.JBOFieldHelper.applyEditAndValidate(JBOFieldHelper.java:205)
         at oracle.jbo.jbotester.JBOFieldHelper$DefaultJBOFocusListener.focusLost(JBOFieldHelper.java:239)
         at java.awt.AWTEventMulticaster.focusLost(AWTEventMulticaster.java:172)
         at java.awt.Component.processFocusEvent(Component.java:5006)
         at java.awt.Component.processEvent(Component.java:4888)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
         at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:777)
         at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:497)
         at java.awt.Component.dispatchEventImpl(Component.java:3506)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Maybe you are looking for