D365 F&O version 10.0.37 - Generate Sales Order Pick list batch job not completing

(1) Share

Report

Posted on by Daniel DiLoreto

We just updated to version 10.0.37 and having significant issues generating Sales Order Pick List. Normally the batch job runs in under 10 minutes. It's been very consistent over the last six months; runs 5x/per day. Now on 10.0.37 either the job won't finish or takes over two hours.

Has anyone experienced issues with this batch job?

NOTE: we use inventory management and not Advanced warehousing.

Replication:

Navigation: Sales and marketing ->Sales orders -> Order shipping ->Generate picking list

Standard selection criteria:

I have the same question (0)

All responses (10)

Answers (1)

André Arnaud de Cal... 300,803 Super User 2025 Season 2 on at

Like (0)

Report

Hi Daniel,

Can you reproduce this issue in a UAT or development environment? If so, a developer can use the trace parser to check what is causing the delays. Do you have customizations or partner add-ons installed on this environment?

Was this reply helpful? Yes No
Daniel DiLoreto 43 on at

Like (0)

Report

Hi André,

Yes, it is being replicated in our Sandbox and other CHE on version 10.0.37. Interesting is that we have a CHE on version 10.0.35 and it's working as expected; under 10 minute run time. We'll look into the trace parser.

There is a customization on printing, but ruled that out because it only runs if the 'print picking' list is used which is currently disabled.

Was this reply helpful? Yes No
GT-06050602-0 28 on at

Like (0)

Report

Hi

Do you really have order lines with a ship date up to 730 days ago which are still Open? I don't know if it'll help, but if you don't perhaps you could reduce that number.

Was this reply helpful? Yes No
Mariano Melo 332 Moderator on at

Like (0)

Report

Hi!

First, you can try to clean up the batch job history.

Clean up the batch job history

You can try to set-up a high priority to the batch job using this functionality:

Priority-based batch scheduling

but, Same as Guy said, I recommend to reduce the 730 days if not strictly necessary.

Was this reply helpful? Yes No
Daniel DiLoreto 43 on at

Like (0)

Report

Thanks Mariano and Guy for your responses.

1. Batch job history is a weekly routine that keeps last six months. I'm not inclined to shorten that because of situations as these that we lose execution history and documentation with Microsoft cases.

2. We implemented priority based scheduling several months ago. It's setup with appropriate priority. We have plenty of batch server and resources available. Plus we have never seen run times this high. It happened immediately on version 10.0.37. I have a CHE without much resources on version 10.0.35 that completes the job in under ten minutes.

3.The negative 730 is appropriate for our business. Furthermore, I've setup manual jobs only looking at the current day and the batch still took over two hours. I even had to cancel the jobs.

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

Like (0)

Report

Hi Daniel,

A CHE and the production tiers can't be compared as a CHE has a local SQL server with the database and production environments are using Azure SQL. If you have the same data in your CHE where it is much faster, then create a support ticket for Microsoft. They can check if the database is in the same geo as the app service. You can also try to restart all production services and check if that solves the performance issue.

Was this reply helpful? Yes No
Daniel DiLoreto 43 on at

Like (0)

Report

Thanks Andre for the reply.

Yes we have created a MS support case and waiting for response. The same data existing on the CHE that has significantly fewer resources. In addition we have two comparable CHE's. One on 10.0.37 and other on 10.0.35. 10.0.35 CHE completes more data in less than 10 minutes. That's why we are down the path of a version issue.

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

Like (0)

Report

Thanks for your reply, Daniel. Please update this thread once you get more information from Microsoft.

Was this reply helpful? Yes No
Community member 4 on at

Like (1)

Report

Has anyone gotten a response from MS on this issue yet? Our group just went to 10.0.36 and we are having a very similar if not the same issue. Previously Gen Pick list batch jobs taking < 5 min now over 4 hrs.

Was this reply helpful? Yes No
Verified answer

Daniel DiLoreto 43 on at

Like (0)

Report

We had this resolved by manually disabling the following inflight:

CredManSOSplitSiteEnabledForPickingPackingInvFlight

Code view:

This was causing incorrect calculation loops. Once this was disabled the Sales Order pick list batch immediately returned to function as expected; less than ten minutes.

Microsoft also created this issue in LCS: 871478

https://fix.lcs.dynamics.com/Issue/Details?bugId=871478&dbType=3&qc=da34619ffe810fd96ec46c9290b7fc5610d3eb506cc02015c95278c8a0cada50

Microsoft never officially stated when the CredManSOSplitSiteEnabledForPickingPackingInvFlight was activated in D365. We saw it when once we were in version 10.0.37. Previously we were on 10.0.35.

Also, We did see an improvement with this update, but the issue still persisted until the inflight was disabled.

LCS Issue: 854868

https://fix.lcs.dynamics.com/Issue/Details?kb=0&bugId=854868&dbType=3

Lastly, our immediate solution was to disable credit check at Pick List generation. This was not desirable, but it worked for the short term.

Was this reply helpful? Yes No