Hello Hasan,

In your Consolidation video you show us how to use the Segment Rules mapping when it comes to mapping COA1 to COA2...

For each entry in the COA1 (Company, Account, Dept ) you map the values to COA2.. 1:1 just about..

What if you have 10 Companies and 1000 Natural Accounts in your Subsidiary COA.
There's a LOT of entry involved and a lot maintenance.

Is this the BEST way of mapping.

Seems like it would be a part-time job for someone to maintain the mapping prior to monthend Consol runs.

Charlie :)

I am sensing a mix up here. In Segment Rules mapping you map each segment (not each combination) of the parent COA to the either a constant value or to some segment of subsidiary ledger. If parent COA has three segment then all you need is three rules in your segment rule mapping.
Segment Rules mapping is the best way to go.
You also have the option of using Account Rules mapping where you can map each combination of the parent is mapped to the subsidiary. This is to handle special scenarios. Usually Account Rules mapping is used in combination with Segment Rules mapping. Account Rules mapping takes precedence over segment rules. I remember explaining all that in the videos.

Hello Hasan,

I think I might not have explained myself properly
Let's say I use Segement Rules mapping. I have a 3 segment coa in both my subidiary coa and parent coa.

My natural account segment in my subsidary coa is 4 chars.
My natural account segment in my parent coa has 6 chars.

I also have approx 1000 natural accounts in my subsidiary natural account value-set.

This looks like I will have to map these 1000 values in my subsidiary natural account segment to my parent natural account segment..

That seems like one heck of a job... and maintenance is a pain every month... assuming, if there are changes to some of these natural accounts.

That was my main point.. :)

Yes you will have to maintain the mapping manually.
It is one time effort to load 1000 accounts in the rollup mapping rule.
If 1000 segment values could be loaded in a value set then they could also be loaded in the rollup mapping rule.
You can use data loaders. In fact you should use data loader in this case.
This is a pretty normal scenario and I dont see this as a big issue.
Mapping has to be maintained if you add new account values but that will be less frequent.