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

Similar Messages

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

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

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?

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

How to implement parent entity for core data

Hi there.
I am starting a document-based Core Data application (Cocoa) and developed the following data model;
The 'invoice' entity is a parent entity of 'items', because ideally I would want there to be many items for each invoice. I guess my first point here is - is what I am trying to do going to be achieved using this method?
If so, I have been trying several ways in Interface Builder to sort out how to implement this structure with cocoa bindings. I have made a Core Data app before, just with one entity. So this time, I have two separate instances of NSArrayController's connected to tables with relevant columns. I can add new 'invoice' entities fine, but I can't get corresponding 'items' to add.
I tried setting the Managed Object Context of the 'item' NSArrayController to this;
I thought this would resolve the issue, but I still have found no resolution to the problem.
If anyone done something similar to this, I'd appreciate any help
Thanks in advance,
Ricky.

Second, when you create a Core Data Document Based application, XCode generates the MyDocument class, derivating from NSPersistentDocument. This class is dedicated to maintain the Managed Object Model and the Managed Object Context of each document of your application.
There is only one Context and generally one Model for each Document.
In Interface Builder, the Managed Object Context must be bound to the managedObjectContext of the MyDocument instance: it's the File's owner of the myDocument.xib Nib file.
It's not the case in your Nib File where the Managed Object Context is bound to the invoiceID of the Invoice Controller.
It's difficult to help you without an overall knowledge of your application, perhaps could you create an InvoiceItem Controller and bind its Content Set to the relationship of your invoice.

Changing the name and currency of a parent entity.

Hello Experts,
Just looking to confirm the impacts of changing a parent entity name as well as the default currency. I am assuming since it is not a base entity I will just need to reconsolidate all historical years across all scenarios and unpost and update any PCA journals as well as any report, dataform, grid changes and if the entity is mentioned in the rules. Updating metadata child parent association. Are there any other items I am not considering such as Process Management, etc...?

Hi,
changing the reporting currency has realy quite an impact. So the biggest recommendation would always be to use a test-system first :-)
I think, that you mentioned most of the items.
- yes, reconsolidate, because all [Parent], [Proportion], [Elim], [Contrib] items will be los
- all journals on other elements than <Entity Curr Adjs> --> thats important! Even if you change back the currency to the original one will not enable the journals again!
- P-Mgmt --> if you change the reporting currency of an entity, you cannot change the P-Management if it is different than "not started". So you should reject all periods, where the P-Management of that entity was started. (there, if you miss one, you can load MD with the old currency and it will work again).
- please also consider if you have somewhere historic rates which you might need to adjust as well.
good luck!

Input data at Parent Entity

Hi,
We are thinking of creating a "Input" rule for parent entities for a scenario for an account and have couple of questions
1. My assumption is, when we write the rule, it by default enables input for all parent entities and no need to put any condition for POV. Correct?
2. Account should NOT be tagged as "IsCalculated" and should be "ISConsolidated". Correct?
Thanks in advance.

Hi,
First question: I don't think it uses parent entities by default, or any POV by default for that matter. We specify each POV we want to run the INPUT sub on, whether it be entities, accounts, custom dimensions, periods, year, etc. Just be aware that once you run an INPUT rule on a parent entity, it never uses the numbers loaded or entered in the base entities. It's a case where the sum of [Contribution Total] of the children Do NOT EQUAL the <Entity Currency> of the parent.
Second question: If the account is tagged IsConsolidated, it should work only starting with the parent entity since it ignores all date in children entities. Also, we do have accounts that have INPUT rules on them but that aren't tagged as IsCalculated, and it works fine.
Dany

Unable to view ECA and PCA value dimension for Parent Entity

Hi,
Situation: There is a parent Enity in (INR) with about 5 children Entity ( also in INR). Application default currency is USD .
Parent has ' allowadjfromchildren' selected and Children have 'allowAdjs' selected .
When I pull up a data grid with Parent and children for a particular POV , I can see data in < Entity currency > , < Entitty curr Adj> , <parent curr> , <Parent Currency Adj> for all children , However I dont see the <Entity curr Adj > or < parent curr Adj> at the Parent Level .
I can only see <entity currency> <entity curr total> and <parent curr>, <parent curr total> for the Parent .
qs. 1 . is this standard functionality ? Since Adjustment was not made at parent level , those intersection of ECA and PCA for parent will remain empty ?
qs 2 : Is there a way to roll up the sum of all children values in ECA into ECA at parent level ? rule change may be ?
eg . If child 1 has 10 , child 2 has 20 and child 3 has 30 in ECA , then their Parent to have 60 in ECA.
Currenty in our Appsettings we DO NOT have the Consolidationrules parameter selected .
Not sure if i was clear , Will appreciate some thoughts and direction on this .
Vik.

Hi,
Seeing that the currency is the same for the parent and children in your example, you will not see a difference between the children's <Entity Curr Adjs> and <Parent Curr Adjs>. In other words, if you post $10 to Child1 <Entity Curr Adjs>, you will also see that same amount in the <Parent Curr Adjs> - that is normal behavior and the child will only contribute the $10 to the parent. Because you have selected AllowAdjFromChildren HFM will allow you to post to [Parent Adjs] and [Contribution Adjs].
Q1: Yes, the adjustments are made to the child and will form part of the <Entity Currency> amounts in the parent. The parent's adjustment value members will store journals to the parent.
Q2: The sum of all the [Contribution Total] value members of the children will make up the <Entity currency> of the parent.
Q3: No, you will see the 60 in <Entity Currency> of the parent -- the way it works in more detail below:
EC + ECA = ECT;
Trans to Parent currency and seperate journals to PCA;
Security defines access to the [] nodes and if the parent has AllowAdjsFromChildren then [Parent Adjs] will be available;
Rules apply to [Proportion] and [Elimination] giving [Contribution];
Final adjustments allowed to [Contribution Adjs] to get to [Contribution Total]
Parent <Entity Currency> is the sum of children [Contribution Total];
Process starts again for the parent.
Regards,

Selected Parent is not defined in CONSGROUP dimension ( SAP BPC 7.5 SP08)

Helllo
While updating the Dynamic Hierachy getting the below error.
Selected Parent is not defined in CONSGROUP dimension
Any Clues.
my Consgroup dimension is below
ID EVDESCRIPTION PARENT_GROUP CURRENCY_TYPE ENTITY GROUP_CURRENCY STORE_ENTITY STORE_GROUP_CURR
Thanking you in advance

Hi,
I think you have resolved this issue
I am able to mapped all entity except 1 in DHE.
I even updated ORG_INTCO as I_NONE.
Still I am unable to mapped this entity with group entity as I am getting subject error.
Mine is sub-parent scenario, ie. the parent in question has 2 child which are properly mapped but linkage of this sub-parent to parent is not showing due to subject error.
Any thoughts.
Regards,
Paresh

HFM Entity detail report - aggregated journal information for parent entity

Hi,
Anyone know if it's possible to view all the journal details that contribute to a parent entity? The entity detail report shows only journal details for the selected entity and I would like to see all journal ID's that contribute to a selected parent entity. Tried also with journal reports, but it's not possible to utilize the entity hierarchies in this way.
Thanks!

In addition to my confusing baffle above would the below solution work?
If I setup an entity group total "G"- 100% ownership
Under this total I have the main trading company "A" - 51% owned by our group
then also under this "G" total another group "I" which will consolidate the 3 investment companies 100% owned by the main trading company "A" but give this group an ownership of 51% so that when I take the consolidated values of group "G" I only have my 51% iroll up into our group accounts.
So it will look like this in the entity hierarchy:
Consol group accounts
--G group
----A entity - 51% owned by Consol group
----I group
--------B entity - 100% owned by A
--------C entity - 100% owned by A
--------D entity - 100% owned by A
At the consol level I only want 51% of this new group. Can someone please confirm that if I allocate ownership to "A" entity and "I" Group 51% ownership then I will get the correct results.
Also, if we do not have management control of "A" entity do I also tag this as Associate as well as "I" group?
Many thanks
LG
Edited by: jamdom on Aug 6, 2012 9:26 PM
Edited by: jamdom on Aug 6, 2012 9:28 PM
Edited by: jamdom on Aug 6, 2012 9:29 PM

Pension not calculated when EE is hired mid-month

Hi All
Please suggest for the following....
When an Employee is hired in the middle of the month, the system doesn't calculate Pension Contribution.
Like if an EE is hired on 10th April. The system will calculate all payments & deductions, but it is not calculating the Pension Contributions.
I am maintaining IT 169, 171 for Pension Contribution.
The problem I found behind this is.....(WIth the help of an ABAPer)
-: System checks the Payroll Period Start Date with the Org. Assignment start date. When it doesnu2019t match, the system does not calculate the Pension Contribution.
For the time being I solved this through the following action -: In debugging, I canceled this condition (skipped this check). Then it calculated the Pension Contribution.
But, this is not the right solution for achieving that as we are changing standard SAP coding.
Please suggest any solution for the same.
Thanks & Regards

If your schema has p0169 with BEG that will happen, try put below Param1 which fits your requirement.
BEG
Infotype records are evaluated on the payroll period begin date.
No changes within the current payroll period are taken into
consideration.
No proration of contributions takes place, even if the record ends
within the current payroll period.
END
Infotype records are evaluated on the payroll period end date.
No changes within the current payroll period are taken into
consideration.
No proration of contributions takes place, even if the record begins
within the current payroll period.
CHK
Infotype records are evaluated on the payroll check date (the pay date),
regardless of whether the check date falls into the payroll period
itself.
A record whose validity starts after the end date of the current payroll
period is still evaluated if the check date (which lies in the future)
falls within the validity period of the infotype.
FRST
Infotype records are evaluated if there is any intersection of plan
infotype and payroll period. The first intersection is taken to
determine the full period deduction amount which is stored without
proration.
LAST
Infotype records are evaluated if there is any intersection of plan
infotype and payroll period. The last intersection is taken to determine
the full period deduction amount which is stored without proration.

Due date not calculated in F-28

Hello,
Can anyone tell me if in standard SAP, in F-28 (incoming payment) why the due date (or payment date) is not calculated ?
I fulfilled posting date and document date (both 01/09/2009) and payment terms also (Z100 - 90 days end of month), but after saving the document and when i check it in FB03, i found that payment date (or due date) still 01/09/2009 and not 30/11/2009.
Can someone explain why and in which cases SAP dosn't calculate the due date ?
In advance, thank you for help

Hi,
The transaction F-28 - Incoming payment, in general it is used for receiving payments. Then what is your requirement to calculate due data from posting date of this document. Are you referring to value date in the bank item? The due date will be calculated from baseline date in invoice, in this case you need to check the baseline date in the invoice (open item), right?
Correct me, if my understanding on your requirement is wrong.
thanks,
Kumar

Overheads not calculated in CK11N cost estimation

Hi all,
I have two issues
1. When i am executing CK11N,i am not able to get the overhead calculation in itemization,but its showing some ridiculess firgure in cost component structure.I am using dependency D020.
2 . when i am using dependency D050 the system not calculating overheads.
We have single plant with two process Repetative and Process order.I want to calculate the overhead on the Order type basis but the system is not calculating the overhead.
So i changed the dependency to D050,now its showing the overhead figure in cost component structure but whic is not matching with the overhead rate i have given..
as my go live is 20 of this month .....its bit emergency
Revert
Regards
Pran

Hi all,
Thnx for your reply.
But i have maintained all the entries in the respective area,even though i am geeting the issue.
It was working fine for my previous repetative manufacturing ...i am using the single cost sheet for both repetative and process order.
And one more thing is that i have a Semi finished goods which is the output of REIM order and is included in process order of the finished good.
The system is calculating the overheads for the semi finished good too once again.
Eg,
Raw Material A and B produces Semi finish material C overheads and the utilities are calculated correctly in Repetative manufacturing.
The semi finished material C is used in producing the finished material D ....in which the system is not caculating the utilities.The big problem is that the figure(value) of itemzation and the Cost component structure is showing two different values.
I am not sure and able to know how and why the system calculates and from where it gets these values ...... totally confussed and under pressure (may not be able to to explain properly).
Revert
Pran

Depreciation not calculated and posted

Dear All
I have a problem. Actually we had a legacy data transfer last year in the month of March.
All the assets were posted to new company code fronm the old company code by using an initial clearing account.
the entries were done through f-02.
My problem lies in the fact that 4 assets which were posted at that time are not functioning well.
The balances got transfered as opening balances in Aw01n but there is no planned depreciation for them for the year 09-10.The amounts are coming as " zero" in the planned depreciation tab.
As a result of which my asset acquisition reports are not coming correct.
I have figured out the diiferences..
The differences are regarding these 4 assets only.
Could any of you please help me in finding the reason why the depreciation is not calculated on these assets since April 2009 and how they are appearing "ZERO" in the acquistion report when there is a actual balance in the asset
Thanking you
regards
Ruby

Hi
I have checked the asset in the previous company code also.. All the parameters are same..plus in that company code the sysytem has shown the planneed depreciation too for all the assets.
now I think the problem lies in the depreciation key or in some linking between depreciation key and the asset..
have you any clue about the areas that needs to be checked for this sort of linkage?
Plus there is no over charging of depreciation.... The system didnot calculate anything in the present company code.........
Regards
Ruby jamwal

Parent entity not calculating.

Similar Messages

Maybe you are looking for