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 have a user request to add an escalation to apply a date/time stamp to a new user defined field when a PO's receipt status is set to 'COMPLETE'. So every 15 min an escalation runs to find any PO that has the receipt status equal to 'COMPLETE' and the user defined field is null. That part works fine. But if someone does a return and the receipt status goes back to 'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
I've tried setting the value to ~NULL~ and <blank value>, but neither has worked with the escalation. Does anyone know the correct method to have an action set a NULL value to a field?
As an alternative, you could use the e-audit capability instead.?
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Jason Verly
Sent: March-22-12 1:02 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Setting value to NULL via Action Set Value
I have a user request to add an escalation to apply a date/time stamp to a
new user defined field when a PO's receipt status is set to 'COMPLETE'. So
every 15 min an escalation runs to find any PO that has the receipt status
equal to 'COMPLETE' and the user defined field is null. That part works
fine. But if someone does a return and the receipt status goes back to
'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
I've tried setting the value to ~NULL~ and <blank value>, but neither has
worked with the escalation. Does anyone know the correct method to have an
action set a NULL value to a field?
Not that I can see right now. Subsequent to the date/time stamp will be another escalation that checks the PO is APPR status, the Receipts are COMPLETE, and the user defined date/time stamp is over 45d. Once those conditions are met, we will automatically change the status to COMP and then 5d later automatically close the PO.
--- In MAXIMO@yahoogroups.com, "Shannon Rotz" <shannonrotz@...> wrote:
>
>
>
> As an alternative, you could use the e-audit capability instead.?
>
>
>
>
>
>
>
> Shannon
>
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Jason Verly
> Sent: March-22-12 1:02 PM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Setting value to NULL via Action Set Value
>
>
>
>
>
> I have a user request to add an escalation to apply a date/time stamp to a
> new user defined field when a PO's receipt status is set to 'COMPLETE'. So
> every 15 min an escalation runs to find any PO that has the receipt status
> equal to 'COMPLETE' and the user defined field is null. That part works
> fine. But if someone does a return and the receipt status goes back to
> 'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
>
> I've tried setting the value to ~NULL~ and <blank value>, but neither has
> worked with the escalation. Does anyone know the correct method to have an
> action set a NULL value to a field?
>
>
>
>
>
>
>
Are you checking to make sure that all receipts have been invoiced? In my
experience, that's the hardest part .
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Jason Verly
Sent: March-22-12 2:12 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Setting value to NULL via Action Set Value
Not that I can see right now. Subsequent to the date/time stamp will be
another escalation that checks the PO is APPR status, the Receipts are
COMPLETE, and the user defined date/time stamp is over 45d. Once those
conditions are met, we will automatically change the status to COMP and then
5d later automatically close the PO.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Shannon
Rotz" <shannonrotz@...> wrote:
>
>
>
> As an alternative, you could use the e-audit capability instead.?
>
>
>
>
>
>
>
> Shannon
>
>
>
> From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
[mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf
Of
> Jason Verly
> Sent: March-22-12 1:02 PM
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] Setting value to NULL via Action Set Value
>
>
>
>
>
> I have a user request to add an escalation to apply a date/time stamp to a
> new user defined field when a PO's receipt status is set to 'COMPLETE'. So
> every 15 min an escalation runs to find any PO that has the receipt status
> equal to 'COMPLETE' and the user defined field is null. That part works
> fine. But if someone does a return and the receipt status goes back to
> 'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
>
> I've tried setting the value to ~NULL~ and <blank value>, but neither has
> worked with the escalation. Does anyone know the correct method to have an
> action set a NULL value to a field?
>
>
>
>
>
>
>
I just ran a test for you doing something similar on my production system. I got it to work. The proper way to do it is to have the following:
Action: <whatever you want to name it> I'll call it SETFIELDXTONULL
Object: PO (I assume that's where your custom field is)
Type: SETVALUE
Value: (just leave this completely blank)
Parameter/Attribute: FIELDX <whatever your custom field is>
I believe you have said you tried that. If that is not working, I would suggest maybe something is wrong with the SQL used in the escalation. Some troubleshooting suggestions:
--First and most importantly -- in your Escalation WHERE clause(s), do not start with the word WHERE. Maximo already has this built-in. If you put it, your SQL essentially becomes SELECT * FROM po WHERE WHERE blah blah blah. Double WHERE there will cause it to fail. (I made that mistake on my first test; I removed my WHERE word and then my escalation worked).
--Find a PO that has a value in your custom field. Reconfigure the escalation to fire on PO = <that PO number>. Does it work?
--Did you set your escalation point to repeat? It needs to repeat.
--Just to make sure you have the proper setup -- you should have one Escalation record running every 15 minutes. It should have two Escalation Points. The first finds PO's where RECEIPTSTATUS = 'COMPLETE' and FIELDX is null (and for efficiency sake, you might also want to have it exclude POs of CLOSEd status). That should have the action to put in the timestamp. The second Esc. Point should find POs where RECEIPTSTATUS in ('NONE', 'PARTIAL') and STATUS != 'CLOSE' and FIELDX is null. The action should be to set FIELDX to null. Again, both these Esc. Points need to repeat.
--Does your Escalation SQL work from the back-end?
Travis Herron
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> I have a user request to add an escalation to apply a date/time stamp to a new user defined field when a PO's receipt status is set to 'COMPLETE'. So every 15 min an escalation runs to find any PO that has the receipt status equal to 'COMPLETE' and the user defined field is null. That part works fine. But if someone does a return and the receipt status goes back to 'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
>
> I've tried setting the value to ~NULL~ and <blank value>, but neither has worked with the escalation. Does anyone know the correct method to have an action set a NULL value to a field?
>
There must have been something in my escalation that wasn't catching because I retested it and now it works as expected.
Thanks for looking at this!
--- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@...> wrote:
>
> I just ran a test for you doing something similar on my production system. I got it to work. The proper way to do it is to have the following:
>
> Action: <whatever you want to name it> I'll call it SETFIELDXTONULL
> Object: PO (I assume that's where your custom field is)
> Type: SETVALUE
> Value: (just leave this completely blank)
> Parameter/Attribute: FIELDX <whatever your custom field is>
>
>
> I believe you have said you tried that. If that is not working, I would suggest maybe something is wrong with the SQL used in the escalation. Some troubleshooting suggestions:
>
> --First and most importantly -- in your Escalation WHERE clause(s), do not start with the word WHERE. Maximo already has this built-in. If you put it, your SQL essentially becomes SELECT * FROM po WHERE WHERE blah blah blah. Double WHERE there will cause it to fail. (I made that mistake on my first test; I removed my WHERE word and then my escalation worked).
>
> --Find a PO that has a value in your custom field. Reconfigure the escalation to fire on PO = <that PO number>. Does it work?
>
> --Did you set your escalation point to repeat? It needs to repeat.
>
> --Just to make sure you have the proper setup -- you should have one Escalation record running every 15 minutes. It should have two Escalation Points. The first finds PO's where RECEIPTSTATUS = 'COMPLETE' and FIELDX is null (and for efficiency sake, you might also want to have it exclude POs of CLOSEd status). That should have the action to put in the timestamp. The second Esc. Point should find POs where RECEIPTSTATUS in ('NONE', 'PARTIAL') and STATUS != 'CLOSE' and FIELDX is null. The action should be to set FIELDX to null. Again, both these Esc. Points need to repeat.
>
> --Does your Escalation SQL work from the back-end?
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > I have a user request to add an escalation to apply a date/time stamp to a new user defined field when a PO's receipt status is set to 'COMPLETE'. So every 15 min an escalation runs to find any PO that has the receipt status equal to 'COMPLETE' and the user defined field is null. That part works fine. But if someone does a return and the receipt status goes back to 'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
> >
> > I've tried setting the value to ~NULL~ and <blank value>, but neither has worked with the escalation. Does anyone know the correct method to have an action set a NULL value to a field?
> >
>
Hey Travis: I have to say, for some reason I never thought of just leaving
the field blank! I'll file that away in my head for when it's needed :)
Shannon
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
Travis Herron
Sent: March-23-12 6:50 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Setting value to NULL via Action Set Value
I just ran a test for you doing something similar on my production system. I
got it to work. The proper way to do it is to have the following:
Action: <whatever you want to name it> I'll call it SETFIELDXTONULL
Object: PO (I assume that's where your custom field is)
Type: SETVALUE
Value: (just leave this completely blank)
Parameter/Attribute: FIELDX <whatever your custom field is>
I believe you have said you tried that. If that is not working, I would
suggest maybe something is wrong with the SQL used in the escalation. Some
troubleshooting suggestions:
--First and most importantly -- in your Escalation WHERE clause(s), do not
start with the word WHERE. Maximo already has this built-in. If you put it,
your SQL essentially becomes SELECT * FROM po WHERE WHERE blah blah blah.
Double WHERE there will cause it to fail. (I made that mistake on my first
test; I removed my WHERE word and then my escalation worked).
--Find a PO that has a value in your custom field. Reconfigure the
escalation to fire on PO = <that PO number>. Does it work?
--Did you set your escalation point to repeat? It needs to repeat.
--Just to make sure you have the proper setup -- you should have one
Escalation record running every 15 minutes. It should have two Escalation
Points. The first finds PO's where RECEIPTSTATUS = 'COMPLETE' and FIELDX is
null (and for efficiency sake, you might also want to have it exclude POs of
CLOSEd status). That should have the action to put in the timestamp. The
second Esc. Point should find POs where RECEIPTSTATUS in ('NONE', 'PARTIAL')
and STATUS != 'CLOSE' and FIELDX is null. The action should be to set FIELDX
to null. Again, both these Esc. Points need to repeat.
--Does your Escalation SQL work from the back-end?
Travis Herron
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Jason
Verly" <jason.verly@...> wrote:
>
> I have a user request to add an escalation to apply a date/time stamp to a
new user defined field when a PO's receipt status is set to 'COMPLETE'. So
every 15 min an escalation runs to find any PO that has the receipt status
equal to 'COMPLETE' and the user defined field is null. That part works
fine. But if someone does a return and the receipt status goes back to
'NONE' or 'PARTIAL', I want the user defined field to be empty/null.
>
> I've tried setting the value to ~NULL~ and <blank value>, but neither has
worked with the escalation. Does anyone know the correct method to have an
action set a NULL value to a field?
>