bcs cross investment data

[dsantos]

Hello,

We ara trying to make a cross participation between 2 entities without success.

Scenario:
A has the 80% of B
B has the 5% of A.

In the investment data, first we create the participation of A over B as "first consolidation"
Then when we go to create the second investment data of B over A as well as "firs consolidation" the system get us a error.

The error message:

Diagnosis:
An activity First Consolidation with activity number 1000000012 already exists for investee unit A.

System Response
The system terminates processing.

Procedure
Create the activity for a different investee unit or add activity number 1000000012 to the activity.

Somebody can help us??

[Hot Asien Teen]

Try the activity Increase In Capitalization. This produces goodwill and acts similar to a first consolidation, though with out the master data entries.

[dsantos]

I tried that you said and we get the next system error:

There is no parent unit in consolidation group combination [ G11000 (Cons Group) ]
Message no. UCF6687

But we have put the flag "parent unit" above entity A in the Accounting Techniques.

[dsantos]

We have solved last error, putting away other company that belongs to the group.

Last scenario
Gruop(A,B,C)

Actual scenario(A,B)
A first consolidation 80% of B
B increase capitalization above A 5%

The error desapeard but when we consolidate the gruop the system only recognize the first investment operation of A into B.

[Hot Asien Teen]

where are you storing your equity and investments? AFD, RFD?

Have you made sure that your journals for RFD equal your AFD?

[Hot Asien Teen]

You will have a few more issues:

5% ownership doesnt consolidate with purchase menthod, it should use equity method. Have you mainainted a different accounting technique for this sub unit? If not there would have to be a journal to show the associate ownership.
Second, you will only have one parent unit per group, so how will you show the minority interest in B?
Unless this is par for the course, I would suggest manually journalling these entries in, or re-classing based on a logic which you can re-use...