Functional area derivation issues

[Former Member]

We recently migrated to the new GL.

We are using functional area substitution and have found that in some cases the functional area is not derived correctly and have been searching for reasons. The rules have been in place for many years and always worked previously.

The instances where they do not work are for postings where the postings are to secondary cost elements rather than primary GL accounts.

We have located a configuration transaction FAREA_MODE. We have found that this seems to help in getting the rule to work. However, we do not know what this configuration was designed to do and what other impacts it could have. It can only be access using the tcode and it not in the IMG.

Has anyone used this configuration area (FAREA_MODE) with P&L accounts or does anyone know its intended purpose?

Thanks

[Former Member · Accepted solution]

You can check this Enhancement of Determination of Functional Area

Financial Accounting Global Settings (New)->Tools->Customer Enhancements->Enhance Determination of Functional Area

I guess all your previous version substitution callup points will be 0005(Cost of sales accounting) and as you have migrated to New GL it checks for callup point 0006(Cost of Sales Accounting (New)).If the Determine Functional Area on Entry Screen is set ON then make it OFF by which it will automatically derive the logic of older version.

Hope this solves your query.

Regards

Andrew

[Former Member · Accepted solution]

I did that in order to get it to work at all but still in cases where the posting is a secondary cost element it does not set the functional area correctly. Most the time it works okay but sometimes not.

[Former Member · Accepted solution]

I apologize for not mentioning we had already done that and do appreciate your time and input to assist us. Thanks.

[Former Member · Accepted solution]

Hi Donna,

Nice that your query has been solved.

In that case kindly close this thread as Solved.

Regards

Andrew

[Former Member · Accepted solution]

Unfortunately this does not solve the problem I did that configuration before we went live but we still encountered this problem