This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I've been trying to disable a user in Maximo 6.2 (Oracle, Weblogic) for a few days now, on and off. The user is disabled, but the person and laborcode records are still 'ACTIVE' because I cannot find this person's references in the system.
So, I try to inactivate in Labor, and I get "A person may not be changed to inactive iif the person is assigned on a labor that is referenced on an open assignment or work plan"
Cool. I go to assignments table, find he's referenced on two workorders. The maintenance supervisor closes them. Rows now have 'Completed' status. Still can't disable.
Okay, maybe he's on a job plan? Nope, not there either. An existing non-assignment workorder? Nope, none that I can see.
Here's the wrinkle: I inherited the installation and they did not set SQL logging on in production. Don't ask me why, they weren't rotating logs either. So, I have to use inductive reasoning here, or, maybe, someone knows which class(es) I need to decompile to locate the check.
-C
Look at wplabor...that's the work plan
> On Oct 13, 2015, at 9:00 AM, maximal@wanko.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
> I've been trying to disable a user in Maximo 6.2 (Oracle, Weblogic) for a few days now, on and off. The user is disabled, but the person and laborcode records are still 'ACTIVE' because I cannot find this person's references in the system.
>
>
> So, I try to inactivate in Labor, and I get "A person may not be changed to inactive iif the person is assigned on a labor that is referenced on an open assignment or work plan"
>
>
> Cool. I go to assignments table, find he's referenced on two workorders. The maintenance supervisor closes them. Rows now have 'Completed' status. Still can't disable.
>
>
> Okay, maybe he's on a job plan? Nope, not there either. An existing non-assignment workorder? Nope, none that I can see.
>
>
> Here's the wrinkle: I inherited the installation and they did not set SQL logging on in production. Don't ask me why, they weren't rotating logs either. So, I have to use inductive reasoning here, or, maybe, someone knows which class(es) I need to decompile to locate the check.
>
>
> -C
>
>
>
>
---In MAXIMO@yahoogroups.com, <sarahlockestewart@gmail.com> wrote :
>>Look at wplabor...that's the work plan
I did, but now I'm thinking to join it with workorder on anything not COMP,CAN, CLOSE. I thought I did this already.
-C
You're on 6.2? Did you read this -
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ24481 ?
Chris.
On Tue, Oct 13, 2015 at 9:20 AM, Sarah Stewart sarahlockestewart@gmail.com
[MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
>
> Look at wplabor...that's the work plan
>
> > On Oct 13, 2015, at 9:00 AM, maximal@wanko.com [MAXIMO] <
> MAXIMO@yahoogroups.com> wrote:
> >
> > I've been trying to disable a user in Maximo 6.2 (Oracle, Weblogic) for
> a few days now, on and off. The user is disabled, but the person and
> laborcode records are still 'ACTIVE' because I cannot find this person's
> references in the system.
> >
> >
> > So, I try to inactivate in Labor, and I get "A person may not be changed
> to inactive iif the person is assigned on a labor that is referenced on an
> open assignment or work plan"
> >
> >
> > Cool. I go to assignments table, find he's referenced on two workorders.
> The maintenance supervisor closes them. Rows now have 'Completed' status.
> Still can't disable.
> >
> >
> > Okay, maybe he's on a job plan? Nope, not there either. An existing
> non-assignment workorder? Nope, none that I can see.
> >
> >
> > Here's the wrinkle: I inherited the installation and they did not set
> SQL logging on in production. Don't ask me why, they weren't rotating logs
> either. So, I have to use inductive reasoning here, or, maybe, someone
> knows which class(es) I need to decompile to locate the check.
> >
> >
> > -C
> >
> >
> >
> >
>
>
>
>
>
---In MAXIMO@yahoogroups.com, <lawlessc@gmail.com> wrote :
>>You're on 6.2? Did you read this - >>http://www-01.ibm.com/support/docview.wss?uid=swg1IZ24481 http://www-01.ibm.com/support/docview.wss?uid=swg1IZ24481 ?
No, but I just did, and that explains it.
All right, there's no stomach here to upgrade within MXES6 if we're planning to move to 7.6, so I'm forced to perform an end run I guess. Thanks Mr. Lawless!
-C
Select * from wplabor where wplabor.wonum in (select wonum from workorder where history flag=0) and wplabor.laborcode='THELABORCODE':
That should find the work orders the system still thinks reference your precious employee.
> On Oct 13, 2015, at 9:25 AM, maximal@wanko.com [MAXIMO] <MAXIMO@yahoogroups.com> wrote:
>
> ---In MAXIMO@yahoogroups.com, <sarahlockestewart@gmail.com> wrote :
> >>Look at wplabor...that's the work plan
>
>
> I did, but now I'm thinking to join it with workorder on anything not COMP,CAN, CLOSE. I thought I did this already.
>
>
> -C
>
>
>
>
>
>
>
>
>
>
>
---In MAXIMO@yahoogroups.com, <sarahlockestewart@gmail.com> wrote :
Select * from wplabor where wplabor.wonum in (select wonum from workorder where history flag=0) and wplabor.laborcode='THELABORCODE':
That should find the work orders the system still thinks reference your precious employee.
*****************
Nope, he wasn't there. Lawless found the APAR, it's a class bug. I had to manually insert a laborstatus row, delete a laborcraftrate row, update labor, then I was able to set the person INACTIVE. Sucked.
-C