web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

on-hand entries cleanup job in AX2012 R3

(0) ShareShare
ReportReport
Posted on by 346

Hi All ,

AX 2012 R3 CU10

The mentioned batch job - Warehouse on-hand entries cleanup job frequently down and taking more time to end than expected, which is causing an impact on Mobile device operations or scanning latency issues.  The batch job runs on dedicated batch server only .

Could I know the reason for batch down and why takes more time than expected?

Any pointers from your end to identify the root cause of such issues ?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    guk1964 Profile Picture
    10,888 on at

    Did you run this our of hours?

    When there are users transacting in the system record locks are the likely explanation. 

    When the hotfix was released it came with a warning that it will run very slowly if you have negative inventory, which is another likely cause.

     The first version only deleted until location level it was  updated to delete all dimensions in a later version so if you are still on CU10 look for an updated hotfix. 

    You might also consider these other, related, clean up tasks:

    Containerization history purge

     to delete containerization history from WHSContainerizationHistory table based on number of days to keep the history provided on dialog

    Wave batch cleanup

     to clean up batch job history records related to Wave processing batch group

    Cycle count plan cleanup

    to clean up batch job history records related to Cycle count plan configurations

    Mobile device activity log cleanup

    to delete mobile device activity log records from WHSMobileDeviceActivityLog table based on number of days to keep the history provided on dialog

    Work user session log cleanup

     to delete work user session records from WHSWorkUserSessionLog table based on number of hours to keep provided on dialog

    There are several more in inventory management.

  • sri17 Profile Picture
    346 on at

    Thanks for your reply , Magic !!

    [quote user="magic1949"]

    Did you run this our of hours?

    [/quote]

    The client production process runs 24*7 ,but the transactions load would be less at midnight , hence the job runs at every midnight.

    Could you give some more light on why batch job runs more than expected time and how to identify root cause from AX point of view ?

    [quote user="magic1949"]

    When there are users transacting in the system record locks are the likely explanation. 

    [/quote]

    The main issue is that if these warehouse clean-up batch job runs more than the expected time , it is critical impact on the warehouse mobile device operations ,example - TO , Product receipt , Production picking list , Sales shipment , operations takes more then expected time .

    [quote user="magic1949"]

    When there are users transacting in the system record locks are the likely explanation. 

    [/quote]

     The first version only deleted until location level it was  updated to delete all dimensions in a later version so if you are still on CU10 look for an updated hotfix. 

    As said that AX version is AX 2012 R3 CU 10 only.

    [quote user="magic1949"]

    There are several more in inventory management.

    [/quote]

    Please explain what more we have in inventory management to improve performance.

  • Suggested answer
    guk1964 Profile Picture
    10,888 on at

    Inventory and warehouse management> Periodic> Clean up> Inventory journals cleanup

    Inventory and warehouse management> Periodic> Clean up> Inventory settlements cleanup

    Inventory and warehouse management> Periodic> Clean up> Inventory dimensions cleanup

    Inventory and warehouse management> Periodic> Clean up> Dimension inconsistency cleanup

    Try in a test system first. Take care if you have  customisations that might affect these tasks.

    Run a dedicated a batch server AOS

    Probably also a good idea to also check your transaction log is empty to start- and maybe whether it  temporary expansion, and or more frequent back up if there is a lot ot data to purge,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans