SAP BPC 10.1 US elimination rule, purpose of additional accounts

[former_member429819]

Hi experts,

from the example below for US elimination rule, what is the purpose of the script bookings to USELIMDIFF accounts (red rectangles).

Basically both accounts 11301100 and 21171000 are being eliminated with booking the opposite figure to entity E_CG2 to the same accounts, so the only purpose of bookings the same opposite figures to USELIMDIFF account from my pov is just the check if entity E_CG2 are 0 on USELIMDIFF account?

(purpose the middle column in the second table of the picture)

Thanks,

Tomas.

[former_member186338 · Accepted solution]

From the beginning of the same document:

"The following ACCOUNT property is used within the US Elimination program to provide customized logic control: ELIMACC The ELIMACC property identifies the account id that is used to generate the elimination records . By entering a value for this property, the system identif ies the associated account as an intercompany account and is therefore subject to elimination. The property value entered in this field is the “elimination” account against which the associated account id

will be eliminated. If this property is left blank, the system will ignore the account and not perform any elimination calculations on any records associated with that account id"

And yes, you can check it for zero to ensure that, for example, sales are equal to purchases for some group!

P.S. In the real life it will be not zero)) For example due to different booking period....

[former_member186338]

In general:

US Elimination Rule logic

1. Find records with AUDITTRAIL defined in the rule as source and with ACCOUNT having not empty property ELIMACC (with valid ACCOUNT ID in this property).
2. For each record use ENTITY property of INTCO dimension member to find the partner company. If not found - do nothing.
3. Find the first common parent between the record ENTITY member and the ENTITY member from ENTITY property of INTCO dimension member.
4. Find the elimination entity as a direct children of first common parent with ENTITY member property ELIM = Y. If not found - go to the parent of the first common parent and test it's children etc...
5. If elimination entity is not found - do nothing.
6. Create the record with ENTITY member as elimination entity, INTCO member from original record, ACCOUNT from original record, AUDITTRAIL from the rule destination and negative recourd amount.
7. After all records are processed aggregate on ENTITY (will be elimination entity), INTCO (from original record) and ACCOUNT.ELIMACC for created records (to remove different ACCOUNT ID's).
8. For each aggregated record write it with negative amount to ACCOUNT=ACCOUNT.ELIMACC (all other dimensions from aggregate).

[former_member429819]

Thanks Vadim, you pointed it out as always.

Tomas.

[former_member186338]

P.S. for different elimination account groups it's better to use different elimination accounts...

For example:

ELIM_Sales_Purch

ELIM_AR_AP

ELIM_Loan

[former_member429819]

Yes, thats exactly the direction where our discussion with business leads us, it will dissolve the user's confusion from offsetting accounts and remove moving elimination values among IC groups.

[former_member429819]

Hi Vadim, thanks for your answer.

That point is clear if the ELIMACC property is empty the account is not being eliminated so for US Elim script it is a must have to run.

My question was more like, why is that script written like that? What is the added value of booking the opposite value to real account and then to "dummy" account USELIMDIFF.

I am trying to explain it to person that was doing IC elim in MS Excel and that step is somthing extra for him and is not accepting the answer (script is written like that), I know what are the prerequisities of running the US elim script but what is the real purpose of that step?

Many thanks,

Tomas.

[former_member186338]

It by design 🙂

Actually, elimination transaction is generated in the elimination entity and like any transaction has to involve debit and credit of 2 accounts:

1. accounts to be eliminated (for example AR or AP accounts - multiple accounts of each type)

2. special elimination account (USELIMDIFF in this sample)

As a result elimination entity is balanced.