cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

US Eliminations not working properly for alternate hierarchies

Former Member
0 Kudos
510

My model's Entity Dimension contains 4 hierarchies.  When I run the USElimination business rule for all entities, everything eliminates perfectly in H1.  However, for H2, H3 and H4 one trading partner does not eliminate at all.  In all cases, the eliminating entry is to occur at an ELIM entity that is under the top member for those three hierarchies.   All other transactions in H2, H3 and H4 work perfectly, and that particular trading partner eliminates properly in H1.  Have checked all properties in Entity and INTCO, and they are correct.  Has anyone run into this issue?  It's as if the business rule/package cannot see the top member for H2, H3 and H4.

Any help would be greatly appreciated.  Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

former_member186338
Active Contributor
0 Kudos

Hi Jack,

But why do you think that US Elimination will work with multiple hierarchies? Per definition "US Eliminations uses the concept known as “posting at first common parent"" There is simple ELIM property to support single hierarchy and nothing else!

Vadim

Former Member
0 Kudos

Vadim:

Thank you for the quick response.

In 7.5MS (and also NW I think), the script logic allowed you to pick individual hierarchies...in 10.x

The alternate hierarchies have their own sets of eliminating entities, and all entities appear in all hierarchies....e.g. H1

TOT_LEGAL

     CORP

          entity A

     PLANTS

          entity B

     ELIM_TOT

H2:

TOT_REGION

     USA

       entity A

     EUR

          entity B

     ELIM_REGION

I would expect transactions between entities A and B (I'm leaving out INTCO dimension for simplicity). to eliminate at ELIM_TOT and ELIM_REGION for H1 and H2 respectively.

As I mentioned, the eliminations are running perfectly for all four hierarchies EXCEPT for one particular INTCO dimension member for H2, H3 and H4.  Note that in my simple example above ELIM_TOT and ELIM_REGION only have parents in H1 and H2, respectively.

I don't recall ever seeing anything from SAP where US Eliminations for multiple hierarchies are not supported.

former_member186338
Active Contributor
0 Kudos

To my mind it was only related to MS not NW...

Please read this document:

Vadim

former_member186338
Active Contributor
0 Kudos

Ups, just read help for US Elimination rule for BPC NW 10:

"The default elimination logic does its searches in the first organizational structure (hierarchy) of the entity dimension. This can be modified to have the elimination performed in all hierarchies existing in the entity dimension. If no common parent is found, no elimination occurs. If no elimination entity is found below the first common parent, the next common parent is searched."

"This can be modified" - how? No idea!

Vadim

Former Member
0 Kudos

Thank you for finding that....and it was good for a laugh too!

We will contact support and get their input.  Maybe we need to modify a Process Chain and create a package link.

former_member186338
Active Contributor
0 Kudos

"Maybe we need to modify a Process Chain and create a package link." - nothing to modify in the process chain - it's a standard chain to run script...

Former Member
0 Kudos

Mystery solved....several of the Intercompany entities had a value for the INTCO property, designating them as having a trading partner, which is incorrect....we removed those properties and everything looked good.

BTW, evidently you can control which hierarchy is getting investigated by putting this line in the script logic:

HIERARCHY=H1

just like we could in the MS version.  We tested it by clearing out all elim data, choosing H3 and runniing the package.  Only H3 elim entities were populated.

Answers (0)