Orphaned Inventory(stock) Transactions

(0) Share

Report

Posted on by Dave W

380

We have an issue where we are seeing orphaned Stock Transactions where the Issue Status is Reserved Physical or On Order. There is an identical record where the stock has been sold, it looks to be that the original record is not getting updated and then being left in the DB. Have been unable to replicate in test.

Wondering if anyone else has come across this?

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dave,

Please provide more details. What is the source of those transactions? Have you looked at the source document to see if there are remaining items?

Was this reply helpful? Yes No
Dave W 380 on at

Like (0)

Report

Hi André,

The source of these transactions is retail transactions(sales), they would appear to be added when an open statement for the store is 'Calculated'. We thought that maybe there was an issue around then using 'Clear Statement' but any tests appear to clear transactions ok leaving no records behind.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,069 Super User 2025 Season 2 on at

Like (0)

Report

Hi Dave,

You might have a look at Issue search on Lifecycle services to see if there is a known issue and probably also a hotfix: https://fix.lcs.dynamics.com

Tip: use keyword AND and OR with capitals to refine your search. e.g. "inventory AND retail"

Was this reply helpful? Yes No
Ahmed Hesham 2,227 on at

Like (0)

Report

if you working with AX for Retail ?

check the statement status it is posted or calculated

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Dave W,

We are seeing exactly the same issue, but have not been able to identify the exact cause. Possibly it might be a user session crashing when calculating or posting the statement as we saw a large decrease in the affected records when we moved the majority of statement calculation and posting to be run via a batch job.

Did you manage to identify the root cause for it?

Omar

Was this reply helpful? Yes No
Dave W 380 on at

Like (0)

Report

Hi Omar,

No we never got to the exact root cause, it's been with Microsoft pretty much since i posted this originally, they've had a look but not made much progress with the cause. We were of the same thinking as you regarding the session crashing whilst calculating the statement, we tried to replicate that by Stopping the service etc but couldn't replicate it. We've given our customer a job to clean things up but clearly it is a frustrating issue and they would prefer it not to happen at all.

Regards
Dave

Was this reply helpful? Yes No
BaidarBakhat on at

Like (0)

Report

Hello Dave,

Which version of AX are you using? This happens some times when you clear the Retail statement after calculating, clear process didn't clear all the transactions. This issue is fixed in AX2012 Cu9.

Are you using calculate and post Inventory in retail?

Was this reply helpful? Yes No
Dave W 380 on at

Like (0)

Report

Hi Baidar,

Yes we are using it in Retail. Do you know what the hotfix is for this rather than going fully CU9?

Thanks
Dave

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I was able to replicate at least some of this issue in our test environment the other day. For us, these orphaned records seem to be created when a Retail statement is calculated, cleared and then subsequently deleted on a user session at the same time as the "post stock" job runs as a batch process. When I did this, transactions were reserved on InventTrans against the deleted statement ID in addition to the new statement ID.

Does this sound similar to what might be happening with you? I'd be really interested to hear either way.

Was this reply helpful? Yes No
Dave W 380 on at

Like (0)

Report

Hi Omar, yes that sounds identical to what we looked at only we never managed to replicate. This is what we originally got from MS.

'the problem is with the P jobs and stock posting at the same time. This problem has been identified but can't be re created by MS.'

Maybe they sorted it as of CU9 per Baider's post.

Was this reply helpful? Yes No