Thanks for the response, Andrew.
Yes, the CONTROLACCOUNT on LABORCRAFTRATE table was null initially.
I associated the labor with a work location (with internal labor control account specified), and that brought a value across to the CONTROLACCOUNT.
Then I removed that work location.
I now tried associating the labor with the craft-vendor combination, and this time it brought across the external labor control account correctly to the CONTROLACCOUNT.
So, it would appear that something is broken in the code. I shall raise it with IBM.
Version is MAS 9.0.0
------------------------------
Tom M
------------------------------
Original Message:
Sent: Mon March 16, 2026 04:53 AM
From: Andrew Jeffery
Subject: External Labor Control Account
Hi Tom,
Are you setting the Labor Control Account for the Vendor before you associate the labor to the craft?
The Labor Control Account for the Vendor is a default for the LABORCRAFTRATE record. What I would do is unhide the CONTROLACCOUNT on the Crafts - Associated Labor table window details, I suspect it is null. Trying creating a new record for the same vendor and see whether the Labor Control Account gets copied to the Control Account, if it does, then you can copy the value and update the original labor who belongs to the same vendor. If it is not being defaulted then you should create a case with IBM Support.
You can see this all working in an article that I wrote a few years ago - https://maximosecrets.com/2020/05/11/financial-processes-on-work-orders-1-of-3/
But, code can break, although you'd think why would something that works be changed.
A general principle here - it is easier to think about the debit side and get that working, credit side accounts can be an after thought. That means that often the data for Items, Labor, etc is already created and the control accounts on those records will have null values. You may need to unhide those fields, to help you understand whether it is null or not and then to modify the value if it is null or wrong.
In Chart of Accounts, there is an Update Database action that allows you to - Overwrite Blank Accounts Only. It is doing this across many tables and many records for an organization. I think it needs to be thoroughly tested with a copy of your own data with SQL logging turned on, so that you can see what tables/records are updated so that you can evaluate whether this should be used (or not). Take great care with this action.
Regards - Andrew
------------------------------
Andrew Jeffery
Maximo SME
Naviam
Barnstaple, Devon, UK
+44 (0)777 1847873
------------------------------