Account & Company codes mapping

[srikanth_godavarthi]

Hi Experts,

Can you please clarify me on the below account and company codes mapping.

Say for example we have 100 company codes, and we have assigned the company codes to the belonged account codes like  one to many.

for example:

we have maintained 100 properties for each company code and filled with member 'Y' if that belongs to that account code. see below.

And we have maintained a company code property for costcentre dimension as well. and in input template we have derived the accounts based on the costcentre and company code.

like Costcentre :109112

      companycode:10

Based on the company codes we do override the accounts.

My question is Is this the mapping done in correct way or is there any other way to implement the same.here for Account dimension we have maintained 100 + properties for all company codes and need to maintain the members manually like 'Y' for their belonged accounts. I just want to know is there any alternative for this?

Appriciate your thoughts on the same.

Thanks in advance.

Srikant.

[former_member186338]

Hi Srikant,

But what is the business logic behind this? What are you trying to achieve?

Vadim

[srikanth_godavarthi]

Hi Vadim,

Sorry for the late reply.

we maintained 100 properties with a member 'Y' (if the account belongs to that company code) for the account dimension like below.

co_10,co_11,co_12.......

Using these properties and members, we override the accounts in all  input templates to input the numbers.

I just want to know is there any other way to maintain company codes for accounts, other than maintaining 100+ properties in account dimension.

Thanks in advance.

Best regards,

srikant.

[former_member186338]

Hi Srikant,

If you want to have 100 individual charts of accounts (for each company) then 100 properties is OK.

But in other cases finance people are simply using common single chart of accounts for all companies!

Vadim

P.S. Another option is to use some special matrix (company, account and all other dimensions - dummy members). Fill matrix with 1 for valid combinations. Then create report supressing empty rows... Then create second real report sharing row axis with the first.