ICAUDIT causing troubles in MSCM

We use MSCM for RAD and Par/Cycle counting. The ICAUDIT scheduler is 'breaking' MSCM - aparently the ICAUDIT scheduler is taking forever to run (6,613 seconds) causing hung threads causing our delivery tickets to not print. Eventually it get's so bad they re-boot MSCM. Our IT department is telling us we cannot upload more than 2000 changes to our item master/item locations at a crack, and that we have to wait 2 hours in between uploads.

2000 changes is not a lot as we have 4 locations we need to add each item to.

Is anyone else having troubles like this?? I cannot imagine that MSCM requires a limit to the adds/changes made within the item master. . . but weirder things have happened.

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Comments

Legacy Contributor

What version are you running?

pcesarz

We just upgraded to MSCM v10.1.5.1 a few weeks ago. But we had this same problem once before. We have v9.0.1.9 apps.

Legacy Contributor

Does Support say anything about MSCM server settings? Have you logged an Incident?

pcesarz

IT did log an incident. Assed for the typical logs, rebooted the system multiple times and then decided it was ICAUDIT again and closed the ticket. We have not (to my knowledge) asked to review the settings. Which is where I think the problem lies.

I am getting the hint that using MSCM should not be changing/restricting daily processing of the item master. . . true?

Legacy Contributor

Was your incident worked by an MSCM resource? I would reopen the incident, ask for an MSCM resource and request escalation if necessary.

pcesarz

Just wanted to supply a little bit of closure to this one. It appears that the changes we made to our configuration file way back when were not included when we did the upgrade. So all of the 'tweaks' we did are not there. We are working on getting them back. Thanks all!

Copyright © 2025 Infor. All rights reserved.