Hi all,
Here is a fun, but annoying fact. The ORGID on the JP needs to be defined. Once defined, you don't need to do the same on the JOBLABOR as all labor is then assumed to be from that same ORGID. Meaning, using this tool, you cannot just set the ORGID on the JOBLABOR without also having it on the JOBPLAN.
I just don't know why, when you can do the same from the UI, just not via the data load tool.
The side effect is that this then makes the JOBPLAN specific to that ORGID. This is a problem where you have a JOBPLAN that can and should be used across multiple organizations. My only solution is then to go and execute some SQL to null out the JOBPLAN.ORGID afterwards.
------------------------------
Craig Kokay
Principal Consultant
COSOL
email:
craig.kokay@cosol.global#IBMChampion
------------------------------
Original Message:
Sent: 12-15-2025 08:29
From: Noah van P
Subject: Error when loading crafts on Job Plans
I am trying to populate the Craft field on my Job Plans, but I keep getting the following error:
However, when I try to associate this exact data manually directly in Maximo, it works. Has anyone experienced this before or any tips to fix this?
Thanks in advance!
#Administration
#Integrations
#MaximoApplicationSuite
#MaximoForAviation
#MaximoUserGroups
------------------------------
Noah van P
Brussels Airport Company
------------------------------