Amending GL Account Determination - Asset Class (Depreciation Postings)

[Former Member]

Hi Gurus -

I did have a quick check on the forums, so apologise if this has been asked before.

The business wants us to amend the to GL account determination for depreciation postings for asset class 9022 to point to 430xxx rather than 450xxx.

I know this bit of config is done via AO90. However what would be the implications of doing this change if any. My concern is this asset class was configured back in Mid 2009, so there will be postings against it.

> Is the change above possible.

> Else is there another process I need to do to amend the GL Acct Det for asset class 9022. If so please kindly provide, the steps and details

Thanks again

Regards

Jay

Edited by: Jays77 on Feb 8, 2011 4:43 PM

[Former Member · Accepted solution]

Hi,

if the change is related to depreciation account (which is a P&L account) it should be no issue, after the change the next depreciation run will use the new account assignment.

It would be different if the affected account is a balance sheet account (eg APC value) as the balances remain on the old account number if nothing is reposted.

Nevertheless, try in testclient first (including a reversal (if possible) of a posting with the OLD account assignment (if the OLD account is only posted using AFAB depr. run, there is no reversal possible)).

best regards, Christian

Edited by: Christian Ortner on Feb 8, 2011 4:50 PM

[Former Member · Accepted solution]

Hi -

Thanks very much for you feedback. Yes its only the depreciation accounts, therefore PandL Accounts only.

Would you be able to confim all I need to do for this bit of config is, change the depreciation PandL accounts in AO90? Else is there anything further I need to do in Config or somewhere else?

Thanks

Jay

[Former Member · Accepted solution]

Hi,

apart from changing the account in AO90 check your Accounting/Controlling reports if the new account/cost element ia assigned to every report.

Maybe Financial statement version, some account groups and/or cost element groups and/or reports need to be adjusted.

Again, try in testclient first, make a depreciation run, post the depreciation, check the results in your reporting environment.

Best regards, Christian

[Former Member · Accepted solution]

Thanks for your help - Issue solved.

[Former Member · Accepted solution]

HI Again -

Further details of the error message when running depreciation via AFAB is shown below, I am failrly sure both errors are Master Data related errors -

The first error appears to be master data. I have checked the cost centre etc, but cannot see anything obvious. The second error the issues states configuration, but I still thinks its linked to the first error, so some form or Master Data Issue.

You further help and feedback would be appreciated?

Thanks

Jay

ERROR 1

Account 430510 requires an assignment to a CO object

Message no. KI235

Diagnosis

You have not defined a CO account assignment for an account that is relevant to cost accounting.

System Response

Account 430510 is defined as a cost element.

This means that you must always specify a CO account assignment.

Procedure

Enter one of the following CO account assignments

Order

Cost center / cost center/ activity type

Sales order item (for a project or cost relevant)

Project / WBS element

Cost object (Process manufacturing)

Network/ Network activities

Business process

Profitability segment

Real estate object

The posting row affected is 0000000001, account 430510.

ERROR 2

Field Order is a required field for G/L account GBJN 430510

Message no. F5808

Diagnosis

The value for field "Order" in the interface to Financial Accounting is an initial value but you are required to make an entry in the field selection for G/L account "430510" in company code "GBJN" linked to the field selection for posting key "40".

System Response

Error

Procedure

It might be an error in the configuration of the G/L account field selection. The initial application, used to call up the interface must otherwise define a value for field "Order". If this is the case, contact the consultant responsible for the application used to call up the interface or get in contact with SAP directly.

[Former Member · Accepted solution]

Hi again,

the first message KI235 explains that the posting created for the new acount number (which is also a cost element) happens without a CO-object (this should be assigned in asset master data).

the second message F5808 is raised because the posting screen that appears during AFAB requires a mandatory entry for the field CO-order.

So (as you already said), it looks like your asset master record is not assigned to an internal order (CO-order).

Best regards, Christian

[Former Member · Accepted solution]

Hi Christian -

Thanks very much for the swift response.

I'll give this ago and hopefully this will post.

Thanks

Jay

[Former Member]

Hi -

Unfortunately issue is not resolved. I ran AFAB to test depreciation, and I got the following errors =

A = Account 430510 requires an assignment to a CO object

B = Field Order is a required field for G/L account 20JN 430510

I will provide more error details shortly.

Thanks

Jay