Disposal Error "Account for transaction type depreciation (prior years) does not exist"

(0) Share

Report

Posted on by Community Member

All -

We are trying to submit a disposal - scrap journal and keep getting the following error message:

"Account for transaction type Depreciation (prior years), value model, does not exist for..."

I have checked the posting profile accounts, the value models for each asset, etc and everything seems to be setup correctly. Can anyone tell me how to correct this error or what causes it?

Thank you.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Sort by

André Arnaud de Cal... 306,118 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Coquet,

Please check if the main accounts setup for this Depreciation (prev years) disposal parameter are actually included in an active account structure.

If this is the case, can you then provide some more information like if you have copied setting from one environment or legal entity to another? Did you setup the disposal parameters per individual asset group? You can also try to delete the disposal parameter line and re-enter it.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

The main accounts are set up in the active account structure. The settings for Fixed Assets are shared across all 12 legal entities we have set up in AX. This issue is only occurring in one of the entities.

We set up disposal parameters per individual asset group and I have verified that the parameters are correct. In November 2015, we were able to dispose of assets in the same asset group for the same entity.

I don't believe we have copied settings between legal entities since they are shared. However, I can verify that.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

We have not copied settings and we have tried deleting the disposal parameter line but the error still showing up.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Update: We have found a bug on the Microsoft codes. Hoping to get fixed soon.

Was this reply helpful? Yes No
André Arnaud de Cal... 306,118 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Coquet,

Interesting. Can you share the details what is wrong?

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

It seems our IT dept may have done a patch to the SQL servers and somehow the codes were broken. They are still researching.

Was this reply helpful? Yes No
CU14050944-0 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Coquet

as i have the same issue .. could you share your solution?

Thanks

Pirmin

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Our issue stemmed from a system patch our IT department uploaded and it broke the codes within AX. They had to work with Microsoft to fix the issue. It was not anything I could fix on my own.

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Coquet,

Do you know which MS fix solved this problem?

Thanks,

Best,

Pal

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Coquet, sorry I was not pay attention to your comment. Your IT dept was fixed the code not obtain any fix, right?

Thanks,

Pal

Was this reply helpful? Yes No