Rules - Parent entity not rolling up from base calcs

What's the problem: Parent Entity member is calculating with a number for a certain account, even though I've specifically excluded this from happening in my rule. I don't want the parent entity to calculate
What should happen: Parent Entity member should just add up the result of its children for that account
Hi guys,
I have a calculation that is designed to specifically run at base entity level only. So I'm expecting that the parent result for a certain account should just be the addition of the results in its child entity members for that account
You can see from the code snippet below that I'm running the statements only when they're enclosed by the vIsBaseEntity conditional statement.
I want to get the required number, a simple A-B calc which looks at the change from prior year (but flips the sign if it's an equity account) into the SBS_MOVE custom 1 member.
If vIsBaseEntity then
     For Each vBSMoveAcct in HS.Account.List("","CalcBSMovementAccounts")
          If HS.Account.UD2(vBSMoveAcct) = "Equity" Then
     HS.Exp "A#" & vBSMoveAcct & ".C1#SBS_MOVE." & All_NONES_XC1C2C4 & " = A#" & vBSMoveAcct & "." & ALL_TOPS_XC2C4 & " - A#" & vBSMoveAcct & ".Y#Prior.P#Last." & ALL_TOPS_XC2C4
          Else
          'Standard Calculation
          'C1#SBS_MOVE = Prior Year End Amount - Current Period Balance Sheet Amount
          HS.Exp "A#" & vBSMoveAcct & ".C1#SBS_MOVE." & All_NONES_XC1C2C4 & " = A#" & vBSMoveAcct & ".Y#Prior.P#Last." & ALL_TOPS_XC2C4 & " - A#" & vBSMoveAcct &"." & ALL_TOPS_XC2C4
          End If
     Next
end if     
However what actually happens is that whilst the base entities do calc, as specified in the rule, the parent entity does as well for a few accounts, even though that's not specified anywhere in my rule (or in my rules file anywhere else)
The parent entity for a certain account (Pl reserves), instead of giving me the result of (Current Year YTD minus Prior Year YTD), just gives me the result of Current Yr YTD, or just the A part of the A-B.
The above code is the only place where SBS_MOVE calculates.
I've tried to use a HS.Clear to clear that parent intersection first but to no avail.
So the intersection doesn't have any erroneous data left in it, it actively calculates a result for that parent member when I've specifically told it not to! Why???
Please help!
Thanks,
Sal

To expand a little on this for newbies who may look for this problem:
The aggregation operator never aggregate means that nowhere in your application will any intersection containing this member aggregate so if this is your problem the symptoms will be:
1. Dynamic Calc doesn't work.
2. Any aggregation scripts that are aggregating on intersections with that member will not work
eg. for example you have a member "no project" and you set it to never aggregate, then any parents in any dimension where they intersect with "no project" will fail to show data, whether they be dynamic calc or you are running a script.
If you have months or quarters the easiest way to see this is that suddenly the automated sums on the forms where you are using your "no project" member stop working so that your period data doesn't roll up into quarter or year.
Agnete
Edited by: Agnete on Oct 8, 2012 7:58 PM

Similar Messages

  • Help Please - Parent Entity not clearing

    We had a parent entity with 2 base children. We removed those 2 children and made the parent childless. How do we clear that parent entity ?

    First of all, avoid making a parent into a child, and alson don't turn parents into children -- in any dimension.
    On the entity you have turned into a base: if you are seeing data in the parent which you cannot determine its source, then load a blank rules file temporarily. It should be a rules file containing only:
    Sub Calculate()
    End Sub
    Load this and reconsolidate. You should no longer see numbers in the parent entity (confirm this). Then re-load the original rules file. If you then see data after the original rules file has been loaded, it is most likely from the rules and not from having been a parent previously.
    One way you can clear data from a parent is to load a single record data file, where instead of a numeric data value you can load "NoData" for al 12 periods and then load this in replace mode. This approach will clear the data values from the entity.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Parent entity not calculating.

    Hi,
    Earlier today, we posted a few JEs to the children of an entity 'ABC'. When we run the overall consolidation, the process aborts at this entity. When we choose to calculate just this parent entity 'ABC', it calculates all its children but it fails at this parent entity 'ABC'. This parent entity was calculating fine before.

    An aborted consolidation is a rules error, not a data error. If you look in the system messages you should see the actual error. Paste the error messages here and maybe we can help. Be sure to look through the details of each red error message.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • WSUS patch status information not rolling up from Downstream to Upstream

    We have a Windows 2008 R2 WSUS server running WSUS 3.2.7600.274
    We have a Downstream replica also Windows 2008 R2 WSUS server running WSUS 3.2.7600.274
    At some stage the Patch Needed status stopped rolling up from the downstream to the upstream server. ie the needed/installed/error counts can all be seen on the downstream replica however on the upstream they all show as 0 and the updates with no status
    is the total number of patches available.
    After days of troubleshooting. We re-installed WSUS on both the upstream and downstream and let the agents report in again and the issue was resolved.
    Less that 30 days later the issue has started occurring again. Needed counts are correct on the downstream replica however this is not replicating up to the upstream. New agents that report in show "no status" for all patches, and all agents
    show 'no Status" for any new patches. 
    The downstream server has now been deleted from the upstreams "Downstream Servers" section, forcing all machines to be removed from the Upstream console and then re-sync the downstream again. Now all machines show no status for all patches.
    The WSUS instances are at the same version.
    The time is within 1 minute of each other on downstream and upstream.
    the rollup reporting is enabled on the upstream.
    Currently we have the support teams using the downstream for reporting and approving patches on the upstream. Not ideal.

    Thanks for the reply Michael,
    The SoftwareDistribution.log file on the downstream replica has the below quite regularly:
    2015-04-08 21:37:30.215 UTC Warning w3wp.5 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=0c03abf0-abb8-4ca3-ad3b-d61960b7922e, ErrorCode=ConfigChanged, Message=, Client=d2acf1c9-c820-428c-8634-44c2e69272e6
    2015-04-08 21:37:48.575 UTC Warning w3wp.6 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=e4110e63-2358-447c-b003-4596b60abee1, ErrorCode=ConfigChanged, Message=, Client=47e558c1-e57e-4948-829c-98eb99727321
    2015-04-08 21:37:50.700 UTC Warning w3wp.6 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=434cd484-86dc-468a-a57a-e69cd9e869c2, ErrorCode=ConfigChanged, Message=, Client=6d4c52c5-0252-4260-b07c-15674cee68f3
    2015-04-08 21:38:02.934 UTC Warning w3wp.7 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=423780bf-8957-4278-8af1-4520d241c683, ErrorCode=ConfigChanged, Message=, Client=6c3a8800-9261-487b-b79a-421f8d26cead

  • CProjects Program - Dates do not roll up from projects

    Hi Experts,
    We are on cProjects 4.0, Support Pack 11.
    We created a project (Project I) having three phases - each phase having a task. We then assigned this project to a program (Program I). We also assigned the phases of the project to those of the program.
    Following this, we increased the duration of the task in phase II of the project (Project I) becasuse of which the dates rolled down to subsequent project elements (we have Top-down scheduling).
    However, this roll down is not to be seen in the porgram (Program I).
    Any suggestion???
    Thanks and Regards,
    Bittu.

        We certainly are concerned, VeryUnsatisfiedCostumer!
    If you do not want the phones on the account to be under the Edge program you would have 14 days from the date of the upgrade to return back to the place of purchase to be placed on a 2 year contract.
    While the account is on Edge, we are not able to change the liablity of the account to someone else. This is a policy that is not able to be altered. If it was something that could changed we would do it in a heartbeat. We truly apologize for any frustration this may have caused.
    TamaraH_VZW
    Follow us on Twitter @VZWSupport

  • Entity data in alternate rollup not rolling up to parent.

    We have a number of different entity hierarchies in our application.  In our main entity hierarchy we have system rules setup to pull specific account data down to STAT accounts for particular entities and then that same STAT account data is pulled over to another entity multiplied by -1 as an offset so when the two entities rollup to a common parent the result is 0.  This offset entity exists in other hierarchies.  In the other hierarchies this offset entity STA account data does not rollup to the parent.  The data only shows up to Parent Currency Total in the value dimension.  Anything above that is empty, but viewing the parent.child combo in the main hierarchy and we can see data populated all the way up to Contribution Total, therefore roling up to the parent.  Below is the rules we have setup.
    Here in simplier terms is what we see.
    Hierarchy 1
    Entity A = $10
    Entity B = -$10
    Parent Entity C = $0
    Hierarchy 2
    Entity B = -$10 (Entity A does not exist in this hierarchy)
    Parent Entity D = $0 (should be -$10)
    Has anyone see an issue like this before?
    Rule
    If HS.Scenario.Member <> "ProForma" Then
       If HS.Value.Member <> "[Elimination]" Then
      If HS.Entity.Member() = "E261" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285 = A#AC76740"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286 = A#AC70160"
      End If
      If HS.Entity.Member() = "E271" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285 = A#AC76740"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286 = A#AC70160"
      End If
    'E103 - Corporate offset
    If YearPOV > "2013" Then
      If EntityPOV = "E103" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285.I#[ICP None] = (E#E300.A#AC90285.I#[ICP Top] + E#E104.A#AC90285.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286.I#[ICP None] = (E#E300.A#AC90286.I#[ICP Top] + E#E104.A#AC90286.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90287"
       HS.Exp "A#AC90287.I#[ICP None] = (E#E300.A#AC90287.I#[ICP Top] + E#E104.A#AC90287.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90288"
       HS.Exp "A#AC90288.I#[ICP None] = (E#E300.A#AC90288.I#[ICP Top] + E#E104.A#AC90288.I#[ICP Top]) * (-1)"
      End If
      End If

    There are trigger account rules, but not for this scenario.  This also occurred before we added those rules.  If you see below in our main hierarchy E100 we have a corporate offset for -2,695,080 which goes against the data rolling up in E104 and E300.  In the secondary hierarchy only E103 exists with one other entity E428 and for some reason that offset data does not roll up to the parent E060.

  • Data at base level not consolidating to the parent entity

    HI All
    I have an issue with data which exisits at the base level but do not consolidate to its parent entity.
    For example,
    2000
    2001
    2002
    2003
    Here only 2002 has data, but that is not appearing at 2000. I have checked the accounts and there we have set the IsConsolidated property.
    The consolidation happens for other entities like 1000 & 3000. The problem is only with 2000.
    Has anyone come accross this before and what is the best way to fix this?
    Thanks,
    Appu

    Is it possible that you have not activated consolidation of the entities for the period you want to consolidate? Check out the Ownership Management screens for the entity 2000. Are all child entities set to Active? Is the proper Method set? Is the PCON = 100?
    Also have you tried to select one of the child entities (e.g. 2001) and run the Force Calculate Contribution? What does this entity return at the +[Contribution]+ level?

  • Data not rolling up to Parent Level

    Working on BPC 7.5 Level 10
    Member set of report are on base level.
    Data Present on 2014.AUG but not rolling up to parent.

    Naveen,
    I am storing Data with Periodic  Measures.
    Jan          Feb          Mar          Q1
    100          50                              0          --- Q1 will be 0 as your ACCTYPE is AST/LEQ
    Now when i change the Measures in REPORT to YTD or Keep Periodic(By default AST and LEQ account type will refer to YTD).
    Jan          Feb          Mar          Q1
    100          50                             0
    As per the logic explained by you
    --> Data present for JAN,FEB on Periodic 100,50  - Yes . But when you say Feb Data is 50 it means your value has reduced from 100 in Jan to 50 in Feb which means the periodic value of Feb is -50. Dont get confused. For AST/LEQ value of 50 in Feb means the total balance till Feb is 50. You are getting 0 in Q1 as your March value has become 0 which means your total balance at the end of March is 0 and hence your Q1 ending March shows value 0. If you post something in March then your Q1 will show the same value. 
    For AST/LEQ the Q1 value is same as the March value and Year.TOTAL value is same as Dec Value.
    -->Data should be when YTD JAN,FEB 100,150. For AST/LEQ ACCTYPES Measure YTD and Periodic show same values as AST and LEQ are YTD in nature by default.
    Nikhil

  • Deployment Rule Sets do not properly launch the latest available version from the JRE6 family when the jpi-version is specified by the RIA

    Issue Summary
    In Java 1.7 Update 71, Java 1.7 Update 72 and Java 1.8 Update 25 Deployment Rule Sets do not properly launch the latest available version from the JRE6 family when the jpi-version is specified by the RIA.  We've noticed this with Oracle Forms and Reports 11g where we have forms that specify Java 1.6 Update 20.  We used to be able to specify Java 1.6 Update 26 in our Ruleset, but now the only version a that works in our ruleset is Java 1.6 Update 20 which is the same version requested by the JPI-Version attribute of the jar.  The long term solution would be to upgrade Oracle Forms and Reports, however this isn't currently in the cards.
    RuleSet.xml Test
    Ruleset.xml

    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    &lt;ruleset version=&quot;1.0+&quot;&gt;  
    &lt;rule&gt;
       &lt;id location=&quot;*.javatester.org&quot; /&gt;
       &lt;action permission=&quot;run&quot; version=&quot;1.6*&quot; /&gt;
    &lt;/rule&gt;
    &lt;ruleset version=&quot;1.0+&quot;&gt;
    &lt;rule&gt;
       &lt;id location=&quot;*.internaldomain.name&quot; /&gt;
       &lt;action permission=&quot;run&quot; version=&quot;1.6*&quot; /&gt;
    &lt;/rule&gt;
    &lt;/ruleset&gt;
    Test 1 (Control)
    Installed Java Versions:
    – 1.7 Update 51 b13 (both x86 and x64 however x86 is invoked)
    – 1.6 Update 26 b03 (both x86 and x64 however x86 is invoked)
    Deployment Ruleset works as expected for both URLs
    Test 2
    Installed Java Versions:
    – 1.7 Update 72 (both x86 and x64 however x86 is invoked)
    – 1.6 Update 26 b03 (both x86 and x64 however x86 is invoked)
    The RuleSet works for JavaTester.org however on internaldomain.name we get the following error:
    With the trace logging turned on, I suspected the version attribute supplied by the RIA. I was able to trick Java by adding the following to my system deployment.properties file:
    deployment.javaws.jre.0.product=1.6.0_20
    deployment.javaws.jre.0.path=C\:\\Program Files (x86)\\Java\\jre6\\bin\\javaw.exe
    deployment.javaws.jre.0.enabled=true
    Because the RIA requests 1.6.0_20 it matches 1.6* from the deployment ruleset sooner than 1.6.0_26. However, if 1.6.0_20 is not available 1.6.0_26 should match according to the Deployment Rule Set documentation:
    http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/security/deployment_rules.html
    The version of the JRE that is used is determined by the following order of precedence:
    1. The current version of the JRE is used if it is available and matches both the version attribute and the version requested by the RIA.
    2. The latest available version of the JRE is used if it matches both the version attribute and the version requested by the RIA.
    3. The current version of the JRE is used if it is available and matches the version attribute.
    4. The latest available version of the JRE is used if it matches the version attribute.
    If no version is available that meets the criteria, then the RIA is blocked, and a message is shown to the user. To provide a custom message, include the message element.
    As a result:
    If Java 1.6.0_20 is listed in the version requested by the RIA and 1.6.0_20 is listed in the deployment.properties file, #1 matches.
    If Java 1.6.0_20 is listed in the version requested by the RIA, but 1.6.0_20 is NOT listed in the deployment.properties file the #1 SHOULD match, but doesn’t. It used to match up-to and including JRE 1.7 Update 51 however the ruleset appears to no longer match in subsequent versions.
    #2 should never match with our current Deployment Ruleset. It would match if we specified 1.7* as a version in the Ruleset.xml.
    #3 used to be broken as well after JRE 1.7 Update 51 however this bug has been marked as fixed. See: http://bugs.java.com/view_bug.do?bug_id=8032781
    I have reproduced this issue with Java 1.7 Update 71, Java 1.7 Update 72, and Java 1.8 Update 25 when one of these versions are installed with Java 1.6 Update 26.

    I can't seem to edit this post anymore, for some odd reason.
    So here goes;
    I found this post in NVIDIA's knowledge base;
    When installing an after-market graphics card into a certified Windows 8 PC with UEFI enabled, the s...
    The interesting parts in this post are as follows;
    When an after-market graphics card is installed into a motherboard with UEFI enabled in the system BIOS, or if the system is a certified Windows 8 PC with Secure Boot enabled, the system may not boot.
    UEFI is a new system BIOS feature that is provided on most new motherboards. A UEFI system BIOS is required in order for the Windows 8 Secure Boot feature to work. Secure boot is enabled by default on certified Windows 8 PCs.
    In order to get the PC to boot with a graphics card that does not contain UEFI firmware, the end-user must first disable the secure boot feature in the system's SBIOS before installing the graphics card.
    Note: Some system SBIOS's incorporate a feature called compatibility boot. These systems will detect a non-UEFI-enabled firmware VBIOS and allow the user to disable secure boot and then proceed with a compatibility boot. If the system contains a system SBIOS the supports compatibility boot, the user will need to disable secure boot when asked during boot process
    This leads me to believe that the BIOS update that wrecked my setup was 9SKT58A/9SJT58A, which only contains one change;
    "Adds support for updating BIOS from a WIN7 BIOS to a WIN8 BIOS".
    I've just ordered a cheap UEFI-compatible GT640 from Gainward, so I hope I'll be able to try that out this weekend.

  • Deleting parent entity of oneToMany does not delete children first,

    I have two entities related with a bi-rdirectional OneToMany relationship. When I delete the parent, I want eclipseLink to automatically delete the child entities first before deleting the parent entity. I have implemented what I understand all the documents are telling me I should implement, but I can not get it working.
    When I try and delete the parent I get an SQLException as the foreign key constraint has been violated as there are child records for the parent I am trying to delete. It was my understanding, that if you have all the annotations correct on my Entities, then all i have to do is delete the parent and eclipseLink will delete the children first and therefore i should never get the SQL exception.
    Here is some snippets of my code.
    Entities
    @Entity(name = "PARENTS")
    public class ParentEntity {
         @Id
         @Column(name = "PARENT_ID", nullable = false)
         private String parentID;
         @Column(name = "DISPLAY_NAME", nullable = false)
         private String displayName;
         @OneToMany(mappedBy="parent", orphanRemoval=true, cascade=CascadeType.ALL)
         private Collection<ChildEntity> childEntities;     
    @Entity(name = "CHILDREN")
    @IdClass(ChildIdentifier.class)
    public class ChildEntity {
         @Id
         @Column(name="ITEM_ID", nullable=false)
         private String itemID;
         @Id
         @ManyToOne()
         @JoinColumn(name="PARENT_ID", nullable=false)
         private ParentEntity parent;
    public class ChildIdentifier implements Serializable {
         private String itemID;
    private String parent;
    Tables created from these entities
    PARENTS
    Name Null? Type
    PARENT_ID NOT NULL VARCHAR2(36)
    DISPLAY_NAME NOT NULL VARCHAR2(255)
    PrimaryKey = PARENT_ID
    CHILDREN
    Name Null? Type
    ITEM_ID NOT NULL VARCHAR2(36)
    PARENT_ID NOT NULL VARCHAR2(255)
    PrimaryKey = ITEM_ID,PARENT_ID
    ForeignKey = PARENTID = PARENTS.PARENT_ID
    Code to delete a parent
         public void deleteParent(String id)
              ParentEntity e= em.find(ParentEntity .class, id);
              if (e!= null)
                   em.remove(e);
    Exception seen
    javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120119-r10715): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-02292: integrity constraint (MYSCHEMA.CHILDREN_FK_P_PARENTS) violated - child record found
    Error Code: 2292
    Call: DELETE FROM PARENTS WHERE (PARENT_ID = ?)
    I have added eclipse logging entries in my persistence.xml to try and see what is going on
    <property name="eclipselink.logging.level" value="FINE"/>
    <property name="eclipselink.logging.parameters" value="true"/>
    And in my jdev console when running my test, i do not see any queries of CHILDREN before it tries to delete from PARENTS.
    Am I missing something really obvious?
    Thanks in advance.
    Edited by: smaslin on Feb 20, 2012 9:20 AM
    Edited by: smaslin on Feb 21, 2012 5:26 AM

    "optional=false" only affects DDL generation, not runtime JPA behavior. PrivateOwned is similar to orphanRemoval in that it should cause the removal of child entities when they are dereferenced from the parent (ie remove them from the parent's collection). Cascade remove or cascade all should be all you need, but PrivateOwned+orphanRemoval should still cause the collection to be removed, as long as there are entities within the Parent's list of children to remove.
    The only case where I can see this not occuring is if you have not been maintaining the bidirectional relationship. That is, if you have added Child entities and set a parent, but not updated the Parent's collection of children to reflect that change. A simple test is to refresh the parent before removal - call em.refresh(e); right before the em.remove(e);. If this works, then you will need to change your application so that when you add parents to a child you also add the child to the parent's list of children - JPA does not maintain relationships for you and not doing so will keep the cache inconsistent with what is in the database.
    Best Regards,
    Chris

  • HT201302 How do I delete a photo from my camera roll and not delete it from a folder

    When I delete photos from my camera roll, it also deletes them from the folder I've saved them in. How do I delete from the camera roll and not lose them from the folder?

    "When I delete photos from my camera roll, it also deletes them from the folder I've saved them in. "
    Correct.  There is only one photo and it is in the camera roll.  The folders you create are just a way to organize the pics.  it does not create a duplicate pic.
    Just as a song is in your library and a playlist, a pic is in the camera roll and the folder.
    If you delete a song from the library, then it is gone.  The same is true of pics.

  • Upgrading from 11.5.9.2 to 12.0.4, Legal entity not migrated

    Hi,
    Upgrading from 11.5.9.2 to 12.0.4, Legal entity not migrated, due to this issue unable to process any accounting transaction, In the GMA_MIGRATION_LOG contain the below message.
    TABLE_NAME     LINE_NO     RUN_ID     MESSAGE_TOKEN     M_TYPE     PARAM1     PARAM2
    GL_SUBR_STA     144,378.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Legal Entities
    GL_SUBR_STA     144,379.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Cost Types
    GL_SUBR_STA     144,380.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Previous Cost Types
    GL_SUBR_STA     144,381.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Current Cost Types
    GL_SUBR_STA     144,382.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Previous Periods
    GL_SUBR_STA     144,383.00     1,393.00     GMA_MIGRATION_ERROR_ABSTRACT     E     GL_SUBR_STA     Current Periods
    GL_SUBR_STA     144,355.00     1,392.00     GMA_MIGRATION_TABLE_STARTED     P     GL_SUBR_STA     NULL
    GL_SUBR_STA     144,356.00     1,392.00     GMA_TABLE_MIGRATION_TABLE_FAIL     P     NULL     NULL

    Hi,
    Please refer to your other thread.
    GRE/Legal Entity not migrated in R12
    Re: GRE/Legal Entity not migrated in R12
    Regards,
    Hussein

  • Data not rolling up of a dynamic calc member for a particular entity

    Hi,
    In my planning application data is not rolling up of a dynamic calc member for a particular entity whereas it is working fine for other entity.
    Please find below the sample Smartview Retrieve
    ----------------Member_ALL---Member_None---Member Top---Member_ALL---Member_None---Member Top
    ----------------Entity 1----------Entity 1------------Entity 1----------Entity 2----------Entity 2------------Entity 2
    Acc1------------100----------------#--------------------#---------------122---------------#-------------------122
    NOTE: # denotes missing
    Member_ALL and Member_None are children of Member_Top. Both Member_ALL and Member_Top are Dynamic Calc whereas Member_None is Store.
    As shown above data is rolling upto Member Top for entity 2 while it is not getting rolled up for Entity 1.
    Request you to please help in finding the error.
    Thanks in Advance'
    Joseph

    Hi Joseph,
    Is Acct 1 Dynamic Calc? In that case will it NOT calculate the combination MemberTop->Entity1 as Member_ALL->Entity1 + Member_None->Entity1.
    I beleive it'll calculate the Acct1 member again for Member Top based on the dynamic formula (whatever the logic). If you make it Acct1 Stored, then the aggregation will be correct by first calculating and storing the Acct1 member and then AGG the Member dimension.
    Cheers,
    Abhishek

  • Error at the time of MIGO- not reading the excise base from invoice

    hi gurus
    when we do inward the material during sto using migo, the following error occurs Error at the time of MIGO- not reading the excise base from invoice
    kindly suggest right answers to overcome this?
    with regards
    baalakrushnan.da

    hi,
    Go to logistics general and see whether for the excise group migo settings are maintained.
    See for the material in depot chapter id and excise indicators are maintained ie J1ID.
    since depot also considered as plant so the chapter id and plant combination has to be maintained.
    Regards
    Saju

  • Profit Center not getting copied from WBS master data to settlement rule

    Hello,
    I am facing issues during settlement to G/L. From FI side we have set up some validations that the  FI postings shld always carry a Profit Ctr. Now when I am doing settlement to B/S account, the profit ctr from WBS master data gets copied to settlement details and hence on FI posting (Credit line).
    However when I am trying to settle to Expenxse/P&L account this is not happening. The profit Ctr is not getting copied from WBS master data to Settlement details and hence the settlement is not going thru. The profit derived is a dummy profit ctr and not the one on WBS master data.
    I have posted this query on FI forum too but no satisfactory answers.
    Pls let me know, what is the system behaviour....will the prof ctr on WBS master data gets copied on settlement rule details automatically ?
    Sarang

    Which exit do I use in OPSN? any thts or some exit in FI?
    I am on ECC-6.0...
    One thing to mention, the prof ctr is getting copied to settlement rules for Balance sheet account but not for P&L.This is more confusing...
    Sarang

Maybe you are looking for