Maximo List Archive

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.



Re: [MAXIMO List] Re: PM Generation Maximo 7.5

From: Shannon Sutton (2012-03-07 07:24)

Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu> wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com, "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: Martin J. Wunder (2012-03-07 10:10)

Hi Shannon,

Check the Maxsequence table and make sure that your seeds are correct. Sometimes when you add a Long descriptions to a Job plan task or a safety plan, hazards, precaution, etc. the seeds get out of sync and when Maximo generates the PM that is using that Job Plan or Safety Plan then it will not create the WO. Also, you need to check for referential integrity on all the fields that pass data from tables or domains.

Here is a link that shows you how to fix the broken maxsequence http://www.maximokb.com/kb/index.php?View=entry&EntryID=5

Hope this help!


From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Shannon Sutton
Sent: Wednesday, March 07, 2012 9:25 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: PM Generation Maximo 7.5


Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu <mailto:therron%40pcci.edu> > wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: Shannon Rotz (2012-03-07 10:05)

You might need to up the logging levels in order to get information out of it … did you check the stderr.log, or just the stdout.log? Sometimes I find errors in the stderr.log that aren’t available in the stdout.log.



Shannon

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Shannon Sutton
Sent: March-07-12 6:24 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: PM Generation Maximo 7.5


Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu <mailto:therron%40pcci.edu> > wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: in2data (2012-03-08 23:10)

Hi,
Open the PM then generate the work order for the PM and do not use the frequency so it should generate. Note the work order number.
If you cannot find that in the work order table then it was not generated.
Check to see if it's part of a PM hierarchy or route.
You can start removing data like the owner, work group, lead and supervisor to see if that clears up the issue.
Once you find what is causing the issue then you'll probably find something wrong with that record.
I think if a user is the lead or supervisor and they do not have a craft assigned to their labor record that may cause an issue.
Dave Bone
--- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
>
> Yeah i took all that into consideration as well..
>
>
>
> Shannon Sutton
> CMMS Specialist
> EMCOR Government Services
> On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@...> wrote:
>
> > I can't say exactly what the case will be here, but I'd bet it's something like this:
> >
> > Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
> >
> > It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
> >
> > Best of luck,
> >
> > Travis Herron
> >
> > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > >
> > > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> > >
> > > --- In MAXIMO@yahoogroups.com, "Mary" <mdurward@> wrote:
> > > >
> > > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > > >
> > > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > > >
> > > > Just a suggestion based on a similar issue we had. Good luck!
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > > > >
> > > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > > >
> > > >
> > >
> >
> >
>
> This message is for the named person's use only. It may contain confidential,
> proprietary or legally privileged information. No confidentiality or privilege
> is waived or lost by any mistransmission. If you receive this message in error,
> please immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. You must not, directly or indirectly,
> use, disclose, distribute, print, or copy any part of this message if you are
> not the intended recipient.
>
>
>
>
>


From: Shannon Sutton (2012-03-09 13:15)

I have figured out my PM generation issue.. This was on our development
server.. When admin mode is turned ON and you create a PM it will not
generate a workorder even when Admin Mode is switched to OFF.. If PM is
created with Admin Mode OFF then there are no issues.. So not sure if
anyone else has ran into this particular issue, but we will take it to IBM
and see what they suggest..



Shannon Sutton
CMMS Specialist
EMCOR Government Services
Office: 571-403-8940
Cell: 571-970-7965

(Embedded image moved to file: pic25721.gif)



From: "in2data" <in2data@yahoo.com>
To: MAXIMO@yahoogroups.com
Date: 03/08/2012 06:10 PM
Subject: [MAXIMO List] Re: PM Generation Maximo 7.5
Sent by: MAXIMO@yahoogroups.com






Hi,

Open the PM then generate the work order for the PM and do not use the
frequency so it should generate. Note the work order number.

If you cannot find that in the work order table then it was not generated.

Check to see if it's part of a PM hierarchy or route.

You can start removing data like the owner, work group, lead and supervisor
to see if that clears up the issue.

Once you find what is causing the issue then you'll probably find something
wrong with that record.

I think if a user is the lead or supervisor and they do not have a craft
assigned to their labor record that may cause an issue.

Dave Bone

--- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@...> wrote:
>
> Yeah i took all that into consideration as well..
>
>
>
> Shannon Sutton
> CMMS Specialist
> EMCOR Government Services
> On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@...> wrote:
>
> > I can't say exactly what the case will be here, but I'd bet it's
something like this:
> >
> > Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose
your PM.DESCRIPTION field is 200 characters. When it generates, the 200
characters won't fit. The PM generation task completed successfully, but it
ended up failing for some other thing that it doesn't consider. Basically a
run-time error.
> >
> > It's probably something like that. The PM has some piece of information
that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD
(or whatever that field is called) that has been deleted or is inactive;
maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a
PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe
some invalid piece of data on the Job Plan or Safety Plan. Something like
that -- unless it's happening to you on EVERY PM.
> >
> > Best of luck,
> >
> > Travis Herron
> >
> > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > >
> > > Its generating as a PM worktype... the PM generation says it is
creating a workorder but the workorder is a ghost.. i could understand if i
was doing an incorrect search via the front-end but not being able to find
the workorder via sql server management studio also.. To me that is odd and
it is only on newly created PMs within the last few weeks.. I guess my only
option is to retore the db back a few weeks ago and see if something has
occured within the last few weeks that could be causing the issue..
> > >
> > > --- In MAXIMO@yahoogroups.com, "Mary" <mdurward@> wrote:
> > > >
> > > > What work order type is your PM generating? There are a number of
new work order types built into Maximo 7.5. If you happen to use one of the
newer ones, it may not be selected by the standard query in the work order
application.
> > > >
> > > > For example, if you find that your PM is creating a work order type
that you are not expecting, go to the work order application and use the
advanced search option to select that work order type.
> > > >
> > > > Just a suggestion based on a similar issue we had. Good luck!
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@>
wrote:
> > > > >
> > > > > Just noticed today in my developement environment that when i
create a new PM and generate a workorder, it tells me PM xxxxx has created
workorder xxxxx.. I am not able to locate the workorder via Maximo
interface or SQL, the asset or location has no reference to the workorder
and the logs are not showing any errors.. Has anyone ran into this issue
before? I am out of ideas to troubleshoot..
> > > > >
> > > >
> > >
> >
> >
>
> This message is for the named person's use only. It may contain
confidential,
> proprietary or legally privileged information. No confidentiality or
privilege
> is waived or lost by any mistransmission. If you receive this message in
error,
> please immediately delete it and all copies of it from your system,
destroy any
> hard copies of it and notify the sender. You must not, directly or
indirectly,
> use, disclose, distribute, print, or copy any part of this message if you
are
> not the intended recipient.
>
>
>
>
>




This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.



From: phanish bharadwaj (2012-03-13 22:03)

Does the Next Date/Due Date field on the PM show up a futuristic date based on your frequency. That for me is the only indicator suggesting if a Work Order has really got created. If not, then it is something to do with the data on the PM or any new customization you may have on the PM or on the Work Order app. Another thing worth taking a look at is to ensure if the location on the PM is an operating location.
 
Cheers.
--- On Wed, 3/7/12, Shannon Rotz <shannonrotz@yahoo.ca> wrote:
From: Shannon Rotz <shannonrotz@yahoo.ca>
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5
To: MAXIMO@yahoogroups.com
Date: Wednesday, March 7, 2012, 12:05 PM
 
You might need to up the logging levels in order to get information out of it … did you check the stderr.log, or just the stdout.log? Sometimes I find errors in the stderr.log that aren’t available in the stdout.log.
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Shannon Sutton
Sent: March-07-12 6:24 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: PM Generation Maximo 7.5
Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu <mailto:therron%40pcci.edu> > wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: Shannon Rotz (2012-03-13 22:40)

That reminds me … I have had problems with work order generation in cases where something is required on the work order (i.e. set to required in DBConfig, not just at the App Designer level), but the PM/Job Plan doesn’t have the data needed to fill in that required field.

Just a thought …


Shannon

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of phanish bharadwaj
Sent: March-13-12 10:03 PM
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5


Does the Next Date/Due Date field on the PM show up a futuristic date based on your frequency. That for me is the only indicator suggesting if a Work Order has really got created. If not, then it is something to do with the data on the PM or any new customization you may have on the PM or on the Work Order app. Another thing worth taking a look at is to ensure if the location on the PM is an operating location.

Cheers.
--- On Wed, 3/7/12, Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> > wrote:
From: Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> >
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Date: Wednesday, March 7, 2012, 12:05 PM

You might need to up the logging levels in order to get information out of it … did you check the stderr.log, or just the stdout.log? Sometimes I find errors in the stderr.log that aren’t available in the stdout.log.
Shannon
From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of Shannon Sutton
Sent: March-07-12 6:24 AM
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Subject: Re: [MAXIMO List] Re: PM Generation Maximo 7.5
Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu <mailto:therron%40pcci.edu> <mailto:therron%40pcci.edu> > wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.


From: Jagan Rajan (2012-03-14 08:37)

Please help me on this.
 
Past two times when I ran the PM’s manually to create work orders I got duplicate work orders for all the PM’s.
In Pm module I went to advance search and pulled up all the Pm’s with Extended date for the month and ran them by going to select action and generate work orders. It doubled the number of work orders created and had 1 set of duplicate for  work orders.
 
I did the same with the Estimated Next Due date in advance search and ran the pm’s and did not get any duplicates.
 
Appreciate your help.
 
Thanks
Lens
Maximo Version 7.1.1.0


From: Shannon Rotz (2012-03-14 09:50)

The first thing that I would do is check the log file on the server, just after you run the PMs manually. Are there any errors?


Shannon

From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Jagan Rajan
Sent: March-14-12 8:38 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Pm Generating duplicate wo's


Please help me on this.

Past two times when I ran the PM’s manually to create work orders I got duplicate work orders for all the PM’s.
In Pm module I went to advance search and pulled up all the Pm’s with Extended date for the month and ran them by going to select action and generate work orders. It doubled the number of work orders created and had 1 set of duplicate for work orders.

I did the same with the Estimated Next Due date in advance search and ran the pm’s and did not get any duplicates.

Appreciate your help.

Thanks
Lens
Maximo Version 7.1.1.0


From: Gideon Olivar (2012-03-14 15:12)

Agree with Shannon. We had similar issue before wherein a required field in the work order is not field up during WO generation thus it didn't create a record. Might be worth checking. And also if you know of the previous COUNT, and it did not increase, then no WO has been generated. Just my thought also.
________________________________
From: Shannon Rotz <shannonrotz@yahoo.ca>
To: MAXIMO@yahoogroups.com
Sent: Wednesday, 14 March 2012 4:40 PM
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5

 
That reminds me … I have had problems with work order generation in cases where something is required on the work order (i.e. set to required in DBConfig, not just at the App Designer level), but the PM/Job Plan doesn’t have the data needed to fill in that required field.
Just a thought …
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of phanish bharadwaj
Sent: March-13-12 10:03 PM
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5
Does the Next Date/Due Date field on the PM show up a futuristic date based on your frequency. That for me is the only indicator suggesting if a Work Order has really got created. If not, then it is something to do with the data on the PM or any new customization you may have on the PM or on the Work Order app. Another thing worth taking a look at is to ensure if the location on the PM is an operating location.
Cheers.
--- On Wed, 3/7/12, Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> > wrote:
From: Shannon Rotz <shannonrotz@yahoo.ca <mailto:shannonrotz%40yahoo.ca> >
Subject: RE: [MAXIMO List] Re: PM Generation Maximo 7.5
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Date: Wednesday, March 7, 2012, 12:05 PM
You might need to up the logging levels in order to get information out of it … did you check the stderr.log, or just the stdout.log? Sometimes I find errors in the stderr.log that aren’t available in the stdout.log.
Shannon
From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of Shannon Sutton
Sent: March-07-12 6:24 AM
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Subject: Re: [MAXIMO List] Re: PM Generation Maximo 7.5
Yeah i took all that into consideration as well..
Shannon Sutton
CMMS Specialist
EMCOR Government Services
On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@pcci.edu <mailto:therron%40pcci.edu> <mailto:therron%40pcci.edu> > wrote:
> I can't say exactly what the case will be here, but I'd bet it's something like this:
>
> Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
>
> It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
>
> Best of luck,
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@...> wrote:
> >
> > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> >
> > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "Mary" <mdurward@> wrote:
> > >
> > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > >
> > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > >
> > > Just a suggestion based on a similar issue we had. Good luck!
> > >
> > > --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> , "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > >
> > >
> >
>
>
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are
not the intended recipient.



From: hanscomm2000 (2012-04-17 13:37)

Remembered your post when we just had a similar problem in 7.5. I have an answer that we found, check to make sure you are not in Admin mode in DB configuration. Even if the PM is created when in Admin Mode, it indicates that the work order is created, but nothing happens. We had to delete the PM and re-create the PM when the system was not in Admin Mode to correct the problem.
Hope this helps, like the Admin Mode feature, but it sure can get you.....
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> Open the PM then generate the work order for the PM and do not use the frequency so it should generate. Note the work order number.
>
> If you cannot find that in the work order table then it was not generated.
>
> Check to see if it's part of a PM hierarchy or route.
>
> You can start removing data like the owner, work group, lead and supervisor to see if that clears up the issue.
>
> Once you find what is causing the issue then you'll probably find something wrong with that record.
>
> I think if a user is the lead or supervisor and they do not have a craft assigned to their labor record that may cause an issue.
>
> Dave Bone
>
>
>
>
>
> --- In MAXIMO@yahoogroups.com, Shannon Sutton <ssutton@> wrote:
> >
> > Yeah i took all that into consideration as well..
> >
> >
> >
> > Shannon Sutton
> > CMMS Specialist
> > EMCOR Government Services
> > On Mar 7, 2012, at 9:18 AM, "Travis Herron" <therron@> wrote:
> >
> > > I can't say exactly what the case will be here, but I'd bet it's something like this:
> > >
> > > Suppose your WORKORDER.DESCRIPTION field is 100 characters. Suppose your PM.DESCRIPTION field is 200 characters. When it generates, the 200 characters won't fit. The PM generation task completed successfully, but it ended up failing for some other thing that it doesn't consider. Basically a run-time error.
> > >
> > > It's probably something like that. The PM has some piece of information that "doesn't fit" in the work order. . .maybe a PM.SUPERVISOR or PM.LEAD (or whatever that field is called) that has been deleted or is inactive; maybe a PM.WORKTYPE that's been removed from the WORKTYPE domain; maybe a PM.LOCATION or PM.ASSETNUM that has been deleted or decommissioned; maybe some invalid piece of data on the Job Plan or Safety Plan. Something like that -- unless it's happening to you on EVERY PM.
> > >
> > > Best of luck,
> > >
> > > Travis Herron
> > >
> > > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > > >
> > > > Its generating as a PM worktype... the PM generation says it is creating a workorder but the workorder is a ghost.. i could understand if i was doing an incorrect search via the front-end but not being able to find the workorder via sql server management studio also.. To me that is odd and it is only on newly created PMs within the last few weeks.. I guess my only option is to retore the db back a few weeks ago and see if something has occured within the last few weeks that could be causing the issue..
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "Mary" <mdurward@> wrote:
> > > > >
> > > > > What work order type is your PM generating? There are a number of new work order types built into Maximo 7.5. If you happen to use one of the newer ones, it may not be selected by the standard query in the work order application.
> > > > >
> > > > > For example, if you find that your PM is creating a work order type that you are not expecting, go to the work order application and use the advanced search option to select that work order type.
> > > > >
> > > > > Just a suggestion based on a similar issue we had. Good luck!
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "shannon" <shannonsuttondale@> wrote:
> > > > > >
> > > > > > Just noticed today in my developement environment that when i create a new PM and generate a workorder, it tells me PM xxxxx has created workorder xxxxx.. I am not able to locate the workorder via Maximo interface or SQL, the asset or location has no reference to the workorder and the logs are not showing any errors.. Has anyone ran into this issue before? I am out of ideas to troubleshoot..
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> > This message is for the named person's use only. It may contain confidential,
> > proprietary or legally privileged information. No confidentiality or privilege
> > is waived or lost by any mistransmission. If you receive this message in error,
> > please immediately delete it and all copies of it from your system, destroy any
> > hard copies of it and notify the sender. You must not, directly or indirectly,
> > use, disclose, distribute, print, or copy any part of this message if you are
> > not the intended recipient.
> >
> >
> >
> >
> >
>