Maximo Open Forum

Hello Everyone,

The ReorderCronTask is not generating any PR from last few days in our environment. The last success run was on 20th July, since then the ReorderCronTask is executing everyday but not generating any PR.
I have checked the ReorderCronTask setup and everything seems to be fine. Also, I have verified that the task is running everyday and it is not showing any errors in the cron task run history but still no PR's are getting generated.
I have checked the REORDERMUTEX table and there are no locks. Also, the REORDERPAD table shows the item selected for reorder but there are no PR in the system.
I have checked the SystemOut.log file and did not find anything specific which can point out the error. But, there is an entry mentioning "BMXAA3463E - An error has occurred and must be corrected by a system administrator. Review the REORDER application log from the <HOME> directory to determine the cause of the error from the logged error messages." error. 

Attached are the log files - 

1. esorder.txt -> This file is configured in the cron setup. I am attaching the log since 20th July. The last successful run was on 20th July, since then the reorder process is not working.
2. SystemErr_log.txt -> I see there is a "[8/15/23 6:04:21:189 CDT] 000001ca SystemErr     R java.lang.NullPointerException"  on line number 198. I am not sure if this  is causing the reorder process to terminate in between. I am hoping that even if there is some error for the items, the reorder process will log the error and will continue on the next item.

We are not able to figure out the error which is causing the reorder to process to fail. Has anyone faced similar problem? Any help with this is highly appreciated.

Attachment(s)

SystemErr_Log.txt   29 KB 1 version

esorder.txt   15 KB 1 version

I think your issue is pulling a company record based on the lines involved. I would set SQL logging to INFO before it runs to confirm and see if you can identify what company is being queried. Or if that's not possible, try to do something like:

select * from invvendor where vendor is not null and not exists(select 1 from companies where invvendor.vendor=companies.company and invvendor.orgid=companies.orgid);

That should show you invalid INVVENDOR records that could be impacting your reorder. 

Thank You, Steven. That worked.

As you pointed out correctly, it was company issue which I was able to figure out after turning on the SQL logging. A new company type was added in the system but reorder process was looking for default company type (V, M, or C). There was a missing configuration in the company type domain to internally convert the new company type to one of the default types -> V, M, or C. The reorder process worked after fixing the configuration.

Thank You!!