cancel
Showing results for 
Search instead for 
Did you mean: 

Consolidation in Multiple group currencies with only one GC coming from ECC

Former Member
0 Kudos

Dear Experts,

We have a requirement of consolidation in multiple group currencies in our SEM-BCS (BW based) system.

Our main group currency is USD which has been defined as group currency in ECC for all companies.

And we have been doing consolidation in USD for some years now.

Now there is addtional requirement of doing the consolidation (IU eliminations etc) for our Australian group (a subgroup of our main hierarchy) companies in AUD. All of the Australian companies currently have AUD as Local Currency and USD as their group currency (Which is needed to do the overall consolidation in USD).

What is the best way to consolidate the Australian piece in AUD?

Since we have the AUD values already stored in Local currency, can we some way use those to do the consolidation in AUD? May be something like copying those LC values to a new Group Currency (AUD) with no translation or translation at 1:1 ratio.

Please give you suggestions ASAP.

Thanks

Ramesh

Accepted Solutions (0)

Answers (1)

Answers (1)

dan_sullivan
Active Contributor
0 Kudos

The steps I suggest are:

1. Possibly create a separate version for the AUD GC consolidation

2. If separate version, create special version for different task hierarchy for AUD version

3. Create copy method to copy source values from GC USD to target values to GC AUD

4. Create copy task and assign copy method from above step

5. If separate versions, create AUD task hierarchy to include copy task as well as all consolidation eliminations and COI tasks

6. If no separate version, add copy task to existing task hierarchy (it will only be relevant for GC AUD)

7. The AUD consolidation must only be executed for the AUD node of the hierarchy so if a separate version is implemented for this it may be best to create a separate hierarchy for this with that same node (to avoid duplicate maintenance).

There are likely a few details Iu2019ve forgotten about, but this is a brief roadmap for what you need.

Former Member
0 Kudos

Dan,

Thanks so much for your quick response. Please see my questions marked below each of your points.

The steps I suggest are:

1. Create a true translation method/task with a true rounding method. This will translate AUD to USD for the USD GC/version.

We are already getting values in USD GC for all companies including Australian companies from ECC as we have USD as GC in ECC. Do we still need this step?

2. Add translation task to task hierarchy

3. Create the AUD GC and possibly a separate AUD version

Will do

4. If separate version, create special version for different task hierarchy for AUD version

Will do

5. Create copy method to copy source values from GC USD to target values to GC AUD

If I understand correctly to get the values in AUD GC we are saying to translating the USD GC values to AUD GC values. In this approach, as the translation in ECC is happening at spot rate, it is not practical to take the USD GC values and translate those back to AUD GC which would match with the LC AUD values.

As the AUD values are already available in LC, they would expect the GC AUD values are not different from LC AUD values.

 Is there a way to copy the values in Local Currency (AUD) to the new GC (AUD) directly instead of doing any translation from AUD to USD and from USD back to AUD ?

 or can we just translate the LC (AUD) values from ECC to GC (AUD) at 1:1 ratio in BCS instead of translating from USD GC to AUD GC

6. Create copy task and assign copy method from above step

7. If separate versions, create AUD task hierarchy to include copy task as well as all consolidation eliminations and COI tasks

 Will do

8. If no separate version, add copy task to existing task hierarchy (it will only be relevant for GC AUD)

9. The AUD consolidation must only be executed for the AUD node of the hierarchy so if a separate version is implemented for this it may be best to create a separate hierarchy for this with that same node (to avoid duplicate maintenance).

You mean only to create the Australian portion of the hierarchy in the new version or create entire hierarchy and execute consolidation only for Australian group ?

Please clarify.

Thanks

Ramesh

dan_sullivan
Active Contributor
0 Kudos

1. The final consolidation occurs in GC and is (or should be) reported in GC. If the ECC USD values are acceptable then this is not needed. However my recollection is that the EC re-measurement at Peabody was quite time consuming and this may be a good opportunity to re-assess whether or not it would be acceptable to perform this in BCS.

5. In my experience, when LC and GC are the same the copy may populate both LC and GC with the same values. If that is the case for Peabody (you have to test this), then no further translation is needed. Otherwise a new method with a 1:1 approach, as you mentioned, should do the trick. This would be included in the copy method.

9. All that is needed is to create a new hierarchy and then make the top node the same node that exists currently for the Australian cons group. This way when the cons group is changed it is automatically changed for both hierarchies. The AUD consolidation tasks would then be executed for this hierarchy node with the parameters set to GC=AUD.