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 cloned locations for a meter-reading application. I want a default query that has an order by clause in it. The problem is that the locations applications append "type not in ('STOREROOM')" to queries and for some order by clauses, it puts it after the order by clause which causes the query to return an oracle error.
Does anyone know how to suppress this from being appended to queries in locations applications?
Kevin Wertz
Grifols Therapeutics
Clayton NC
If you show all controls, select the presentation and look at the properties is it there in the where clause?
On Aug 23, 2013, at 10:11 AM, "kevwertz" <wertzee@gmail.com> wrote:
> I have cloned locations for a meter-reading application. I want a default query that has an order by clause in it. The problem is that the locations applications append "type not in ('STOREROOM')" to queries and for some order by clauses, it puts it after the order by clause which causes the query to return an oracle error.
>
> Does anyone know how to suppress this from being appended to queries in locations applications?
>
> Kevin Wertz
> Grifols Therapeutics
> Clayton NC
>
>
Let me try this, and maybe someone can tell me if there is a "stupid Maximo
trick" to get this to work.
I am setting up meter reading routes in routes. Using the sequence field in
the route stops to set the order in which they want to do the route.
However they don't want to do the routes on work orders, so I created a
button in routes, tied to a simple workflow that sets the route id on the
user's user record, then sends the user to the "Location Meter Reading"
application (clone of locations app, obviously).
The location meter reading application has a default query in the
presentation object that pulls the locations from the route's stops.
However the order by in the query is failing, due to the issue I specified
in the first email. Since I sent the first email, I figured out that the
order by doesn't fail if there are not any single quotes in the query.
Weird huh?
Problem is, to reference the route being performed to be able to reach the
sequence column, I have to use the :user variable, which of course resolves
to 'WERTZK'. Yeah, single quotes, so it fails with the oracle right
parenthesis missing error.
Any ideas on any tricks to accomplish what I'm trying to do?
Kevin Wertz
Grifols, Inc
Clayton NC
On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
> **
>
>
> I have cloned locations for a meter-reading application. I want a default
> query that has an order by clause in it. The problem is that the locations
> applications append "type not in ('STOREROOM')" to queries and for some
> order by clauses, it puts it after the order by clause which causes the
> query to return an oracle error.
>
> Does anyone know how to suppress this from being appended to queries in
> locations applications?
>
> Kevin Wertz
> Grifols Therapeutics
> Clayton NC
>
>
>
You could try this I've not tried it myself but its worth a bash use a relationship from locations to person that's assuming that personid = :user will work and then person to route then you could
order the list screen table set the order by to :-
By relationship1.relationjship2.sequence
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Kevin Wertz
Sent: 27 August 2013 16:28
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from location queries?
Let me try this, and maybe someone can tell me if there is a "stupid Maximo trick" to get this to work.
I am setting up meter reading routes in routes. Using the sequence field in the route stops to set the order in which they want to do the route.
However they don't want to do the routes on work orders, so I created a button in routes, tied to a simple workflow that sets the route id on the user's user record, then sends the user to the "Location Meter Reading"
application (clone of locations app, obviously).
The location meter reading application has a default query in the presentation object that pulls the locations from the route's stops.
However the order by in the query is failing, due to the issue I specified in the first email. Since I sent the first email, I figured out that the order by doesn't fail if there are not any single quotes in the query.
Weird huh?
Problem is, to reference the route being performed to be able to reach the sequence column, I have to use the :user variable, which of course resolves to 'WERTZK'. Yeah, single quotes, so it fails with the oracle right parenthesis missing error.
Any ideas on any tricks to accomplish what I'm trying to do?
Kevin Wertz
Grifols, Inc
Clayton NC
On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
> **
>
>
> I have cloned locations for a meter-reading application. I want a
> default query that has an order by clause in it. The problem is that
> the locations applications append "type not in ('STOREROOM')" to
> queries and for some order by clauses, it puts it after the order by
> clause which causes the query to return an oracle error.
>
> Does anyone know how to suppress this from being appended to queries
> in locations applications?
>
> Kevin Wertz
> Grifols Therapeutics
> Clayton NC
>
>
>
------------------------------------
Email addresses you might need:
Posting: MAXIMO@yahoogroups.com
Join : MAXIMO-subscribe@yahoogroups.com
Leave : MAXIMO-unsubscribe@yahoogroups.com
Cry : MAXIMO-owner@yahoogroups.com
Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
Come and visit us at Offshore Europe 2013
Find out more on our website
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
You can use the :user variable in a relationship. But unfortunately I've
tried a relationship similar to that in the order by of the list table
object. I get an ora-904 error shown below.
BMXAA4210E - Database error number 904 has occurred.ORA-00904:
"ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier
Wasn't sure if I needed the colon in front, but when I tried that, I got
this.BMXAA4210E - Database error number 1008 has occurred.
ORA-01008: not all variables bound
I guess you can't reference relationships in the order by on table objects.
I was kind of surprised to find this out. I thought for sure this would
work.
KW
On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> You could try this I've not tried it myself but its worth a bash use a
> relationship from locations to person that's assuming that personid = :user
> will work and then person to route then you could
> order the list screen table set the order by to :-
>
> By relationship1.relationjship2.sequence
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Kevin Wertz
> Sent: 27 August 2013 16:28
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> Let me try this, and maybe someone can tell me if there is a "stupid
> Maximo trick" to get this to work.
>
> I am setting up meter reading routes in routes. Using the sequence field
> in the route stops to set the order in which they want to do the route.
>
> However they don't want to do the routes on work orders, so I created a
> button in routes, tied to a simple workflow that sets the route id on the
> user's user record, then sends the user to the "Location Meter Reading"
> application (clone of locations app, obviously).
>
> The location meter reading application has a default query in the
> presentation object that pulls the locations from the route's stops.
> However the order by in the query is failing, due to the issue I specified
> in the first email. Since I sent the first email, I figured out that the
> order by doesn't fail if there are not any single quotes in the query.
> Weird huh?
>
> Problem is, to reference the route being performed to be able to reach the
> sequence column, I have to use the :user variable, which of course resolves
> to 'WERTZK'. Yeah, single quotes, so it fails with the oracle right
> parenthesis missing error.
>
> Any ideas on any tricks to accomplish what I'm trying to do?
>
> Kevin Wertz
> Grifols, Inc
> Clayton NC
>
> On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
>
> > **
>
> >
> >
> > I have cloned locations for a meter-reading application. I want a
> > default query that has an order by clause in it. The problem is that
> > the locations applications append "type not in ('STOREROOM')" to
> > queries and for some order by clauses, it puts it after the order by
> > clause which causes the query to return an oracle error.
> >
> > Does anyone know how to suppress this from being appended to queries
> > in locations applications?
> >
> > Kevin Wertz
> > Grifols Therapeutics
> > Clayton NC
> >
> >
> >
>
>
>
> ------------------------------------
>
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
> Come and visit us at Offshore Europe 2013
> Find out more on our website
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and
> Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N
> 2PB.
>
>
> **************************************************************************************************************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
>
> **************************************************************************************************************
>
>
>
Well I think the issue is with the application and the fact that the main object is the location table at the point of initiation
After it has found the records the relationship works i.e. I painted a list tab column with the field relationship.stopsequence and it displayed correctly, however you still can't sort
location = :location and siteid = :siteid and route = ( select 'EL001' from person where personid = :user) -- I used this relationship just to check
but I think you will have big problems getting this to work
Question why don't they want to use work orders I have just changed the work order actuals tab so at each task you can enter a meter readings and it works great 7.5
They don't actually need PM's they can just go to the work order select action apply route and if the route is task based they get one work order with all the tasks i.e. stops in sequence
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Kevin Wertz
Sent: 27 August 2013 17:47
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from location queries?
You can use the :user variable in a relationship. But unfortunately I've tried a relationship similar to that in the order by of the list table object. I get an ora-904 error shown below.
BMXAA4210E - Database error number 904 has occurred.ORA-00904:
"ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier Wasn't sure if I needed the colon in front, but when I tried that, I got this.BMXAA4210E - Database error number 1008 has occurred.
ORA-01008: not all variables bound
I guess you can't reference relationships in the order by on table objects.
I was kind of surprised to find this out. I thought for sure this would work.
KW
On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> You could try this I've not tried it myself but its worth a bash use a
> relationship from locations to person that's assuming that personid =
> :user will work and then person to route then you could order the list
> screen table set the order by to :-
>
> By relationship1.relationjship2.sequence
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> Of Kevin Wertz
> Sent: 27 August 2013 16:28
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> Let me try this, and maybe someone can tell me if there is a "stupid
> Maximo trick" to get this to work.
>
> I am setting up meter reading routes in routes. Using the sequence
> field in the route stops to set the order in which they want to do the route.
>
> However they don't want to do the routes on work orders, so I created
> a button in routes, tied to a simple workflow that sets the route id
> on the user's user record, then sends the user to the "Location Meter Reading"
> application (clone of locations app, obviously).
>
> The location meter reading application has a default query in the
> presentation object that pulls the locations from the route's stops.
> However the order by in the query is failing, due to the issue I
> specified in the first email. Since I sent the first email, I figured
> out that the order by doesn't fail if there are not any single quotes in the query.
> Weird huh?
>
> Problem is, to reference the route being performed to be able to reach
> the sequence column, I have to use the :user variable, which of course
> resolves to 'WERTZK'. Yeah, single quotes, so it fails with the oracle
> right parenthesis missing error.
>
> Any ideas on any tricks to accomplish what I'm trying to do?
>
> Kevin Wertz
> Grifols, Inc
> Clayton NC
>
> On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
>
> > **
>
> >
> >
> > I have cloned locations for a meter-reading application. I want a
> > default query that has an order by clause in it. The problem is that
> > the locations applications append "type not in ('STOREROOM')" to
> > queries and for some order by clauses, it puts it after the order by
> > clause which causes the query to return an oracle error.
> >
> > Does anyone know how to suppress this from being appended to queries
> > in locations applications?
> >
> > Kevin Wertz
> > Grifols Therapeutics
> > Clayton NC
> >
> >
> >
>
>
>
> ------------------------------------
>
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com Leave :
> MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
> Come and visit us at Offshore Europe 2013 Find out more on our website
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> and Wales with a registered office address at: 40 Holborn Viaduct,
> London, EC1N 2PB.
>
>
> **********************************************************************
> ****************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
>
> **********************************************************************
> ****************************************
>
>
>
------------------------------------
Email addresses you might need:
Posting: MAXIMO@yahoogroups.com
Join : MAXIMO-subscribe@yahoogroups.com
Leave : MAXIMO-unsubscribe@yahoogroups.com
Cry : MAXIMO-owner@yahoogroups.com
Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
Lots of issues with using work orders, you add all the overhead of creating
the work orders then applying the route, then someone has to follow through
on completing and reviewing the work orders and filling in all the required
fields that we require to move to COMP. We are trying to replace an easy to
use home-grown system so we have to make this as simple as possible for the
users to accept the move to Maximo.
The other issue is that they do many rounds daily and adding that volume to
the workorder table and other related tables just didn't seem prudent to me.
Any experience with java? The appending of the storeroom type thing
ultimately comes from the LocationAppBean and indeed I have found the code
where this gets appended. Wondered if any one maybe had any guidance or
documentation on how to create a clone of the LocationAppBean and remove
the appending of the storeroom restriction.
KW
On Wed, Aug 28, 2013 at 11:21 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> Well I think the issue is with the application and the fact that the main
> object is the location table at the point of initiation
> After it has found the records the relationship works i.e. I painted a
> list tab column with the field relationship.stopsequence and it displayed
> correctly, however you still can't sort
>
> location = :location and siteid = :siteid and route = ( select 'EL001'
> from person where personid = :user) -- I used this relationship just to
> check
>
> but I think you will have big problems getting this to work
>
> Question why don't they want to use work orders I have just changed the
> work order actuals tab so at each task you can enter a meter readings and
> it works great 7.5
> They don't actually need PM's they can just go to the work order select
> action apply route and if the route is task based they get one work order
> with all the tasks i.e. stops in sequence
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Kevin Wertz
> Sent: 27 August 2013 17:47
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> You can use the :user variable in a relationship. But unfortunately I've
> tried a relationship similar to that in the order by of the list table
> object. I get an ora-904 error shown below.
>
> BMXAA4210E - Database error number 904 has occurred.ORA-00904:
> "ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier Wasn't sure if
> I needed the colon in front, but when I tried that, I got this.BMXAA4210E -
> Database error number 1008 has occurred.
>
> ORA-01008: not all variables bound
>
> I guess you can't reference relationships in the order by on table objects.
> I was kind of surprised to find this out. I thought for sure this would
> work.
> KW
>
> On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright <ian.wright@gdfsuezep.co.uk
> >wrote:
>
> > **
>
> >
> >
> > You could try this I've not tried it myself but its worth a bash use a
> > relationship from locations to person that's assuming that personid =
> > :user will work and then person to route then you could order the list
> > screen table set the order by to :-
> >
> > By relationship1.relationjship2.sequence
> >
> >
> > -----Original Message-----
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> > Of Kevin Wertz
> > Sent: 27 August 2013 16:28
> > To: MAXIMO@yahoogroups.com
> > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > location queries?
> >
> > Let me try this, and maybe someone can tell me if there is a "stupid
> > Maximo trick" to get this to work.
> >
> > I am setting up meter reading routes in routes. Using the sequence
> > field in the route stops to set the order in which they want to do the
> route.
> >
> > However they don't want to do the routes on work orders, so I created
> > a button in routes, tied to a simple workflow that sets the route id
> > on the user's user record, then sends the user to the "Location Meter
> Reading"
> > application (clone of locations app, obviously).
> >
> > The location meter reading application has a default query in the
> > presentation object that pulls the locations from the route's stops.
> > However the order by in the query is failing, due to the issue I
> > specified in the first email. Since I sent the first email, I figured
> > out that the order by doesn't fail if there are not any single quotes in
> the query.
> > Weird huh?
> >
> > Problem is, to reference the route being performed to be able to reach
> > the sequence column, I have to use the :user variable, which of course
> > resolves to 'WERTZK'. Yeah, single quotes, so it fails with the oracle
> > right parenthesis missing error.
> >
> > Any ideas on any tricks to accomplish what I'm trying to do?
> >
> > Kevin Wertz
> > Grifols, Inc
> > Clayton NC
> >
> > On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
> >
> > > **
> >
> > >
> > >
> > > I have cloned locations for a meter-reading application. I want a
> > > default query that has an order by clause in it. The problem is that
> > > the locations applications append "type not in ('STOREROOM')" to
> > > queries and for some order by clauses, it puts it after the order by
> > > clause which causes the query to return an oracle error.
> > >
> > > Does anyone know how to suppress this from being appended to queries
> > > in locations applications?
> > >
> > > Kevin Wertz
> > > Grifols Therapeutics
> > > Clayton NC
> > >
> > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> > Come and visit us at Offshore Europe 2013 Find out more on our website
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> > and Wales with a registered office address at: 40 Holborn Viaduct,
> > London, EC1N 2PB.
> >
> >
> > **********************************************************************
> > ****************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> >
> > **********************************************************************
> > ****************************************
> >
> >
> >
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>
It doesn't seem to be the appending the storeroom that causes the problem I played around with where clause on the locations app its something to do with the order by I think
You can replace the bean just as you would any other class but it then becomes a pain i.e. regression testing blah blah
I would actually say it's a bug in the way it parses the string
I entered this in the where clause of the application (sql server) as I had already tested it in sql studio and it gave me the results I wanted
exists (select null from route_stop where route = 'EL001' and location = locations.location)
order by (select stopsequence from route_stop where route = 'EL001' and location = locations.location)
click find bang it dies
then I tried this
exists (select null from route_stop where route = 'EL001' and location = locations.location)
order by (select stopsequence from route_stop where ROUTESTOPID = 5 and location = locations.location)
AND IT WORKS doesn't give me the result I want i.e. it doesn't order correctly but doesn't complain about a database error - after parsing the where clause Maximo gives you :-
(exists (select null from route_stop where route = 'EL001' and location = locations.location)) and (type in ( 'COURIER' , 'HOLDING' , 'LABOR' , 'OPERATING' , 'REPAIR' , 'SALVAGE' , 'VENDOR' )) order by (select stopsequence from route_stop where routestopid = 5 and location = locations.location)
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Kevin Wertz
Sent: 28 August 2013 16:43
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from location queries?
Lots of issues with using work orders, you add all the overhead of creating the work orders then applying the route, then someone has to follow through on completing and reviewing the work orders and filling in all the required fields that we require to move to COMP. We are trying to replace an easy to use home-grown system so we have to make this as simple as possible for the users to accept the move to Maximo.
The other issue is that they do many rounds daily and adding that volume to the workorder table and other related tables just didn't seem prudent to me.
Any experience with java? The appending of the storeroom type thing ultimately comes from the LocationAppBean and indeed I have found the code where this gets appended. Wondered if any one maybe had any guidance or documentation on how to create a clone of the LocationAppBean and remove the appending of the storeroom restriction.
KW
On Wed, Aug 28, 2013 at 11:21 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> Well I think the issue is with the application and the fact that the
> main object is the location table at the point of initiation After it
> has found the records the relationship works i.e. I painted a list tab
> column with the field relationship.stopsequence and it displayed
> correctly, however you still can't sort
>
> location = :location and siteid = :siteid and route = ( select 'EL001'
> from person where personid = :user) -- I used this relationship just
> to check
>
> but I think you will have big problems getting this to work
>
> Question why don't they want to use work orders I have just changed
> the work order actuals tab so at each task you can enter a meter
> readings and it works great 7.5 They don't actually need PM's they can
> just go to the work order select action apply route and if the route
> is task based they get one work order with all the tasks i.e. stops in
> sequence
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> Of Kevin Wertz
> Sent: 27 August 2013 17:47
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> You can use the :user variable in a relationship. But unfortunately
> I've tried a relationship similar to that in the order by of the list
> table object. I get an ora-904 error shown below.
>
> BMXAA4210E - Database error number 904 has occurred.ORA-00904:
> "ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier Wasn't
> sure if I needed the colon in front, but when I tried that, I got
> this.BMXAA4210E - Database error number 1008 has occurred.
>
> ORA-01008: not all variables bound
>
> I guess you can't reference relationships in the order by on table objects.
> I was kind of surprised to find this out. I thought for sure this
> would work.
> KW
>
> On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright
> <ian.wright@gdfsuezep.co.uk
> >wrote:
>
> > **
>
> >
> >
> > You could try this I've not tried it myself but its worth a bash use
> > a relationship from locations to person that's assuming that
> > personid = :user will work and then person to route then you could
> > order the list screen table set the order by to :-
> >
> > By relationship1.relationjship2.sequence
> >
> >
> > -----Original Message-----
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On
> > Behalf Of Kevin Wertz
> > Sent: 27 August 2013 16:28
> > To: MAXIMO@yahoogroups.com
> > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > location queries?
> >
> > Let me try this, and maybe someone can tell me if there is a "stupid
> > Maximo trick" to get this to work.
> >
> > I am setting up meter reading routes in routes. Using the sequence
> > field in the route stops to set the order in which they want to do
> > the
> route.
> >
> > However they don't want to do the routes on work orders, so I
> > created a button in routes, tied to a simple workflow that sets the
> > route id on the user's user record, then sends the user to the
> > "Location Meter
> Reading"
> > application (clone of locations app, obviously).
> >
> > The location meter reading application has a default query in the
> > presentation object that pulls the locations from the route's stops.
> > However the order by in the query is failing, due to the issue I
> > specified in the first email. Since I sent the first email, I
> > figured out that the order by doesn't fail if there are not any
> > single quotes in
> the query.
> > Weird huh?
> >
> > Problem is, to reference the route being performed to be able to
> > reach the sequence column, I have to use the :user variable, which
> > of course resolves to 'WERTZK'. Yeah, single quotes, so it fails
> > with the oracle right parenthesis missing error.
> >
> > Any ideas on any tricks to accomplish what I'm trying to do?
> >
> > Kevin Wertz
> > Grifols, Inc
> > Clayton NC
> >
> > On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
> >
> > > **
> >
> > >
> > >
> > > I have cloned locations for a meter-reading application. I want a
> > > default query that has an order by clause in it. The problem is
> > > that the locations applications append "type not in ('STOREROOM')"
> > > to queries and for some order by clauses, it puts it after the
> > > order by clause which causes the query to return an oracle error.
> > >
> > > Does anyone know how to suppress this from being appended to
> > > queries in locations applications?
> > >
> > > Kevin Wertz
> > > Grifols Therapeutics
> > > Clayton NC
> > >
> > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> > Come and visit us at Offshore Europe 2013 Find out more on our
> > website
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> > and Wales with a registered office address at: 40 Holborn Viaduct,
> > London, EC1N 2PB.
> >
> >
> > ********************************************************************
> > **
> > ****************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> >
> > ********************************************************************
> > **
> > ****************************************
> >
> >
> >
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com Leave :
> MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>
------------------------------------
Email addresses you might need:
Posting: MAXIMO@yahoogroups.com
Join : MAXIMO-subscribe@yahoogroups.com
Leave : MAXIMO-unsubscribe@yahoogroups.com
Cry : MAXIMO-owner@yahoogroups.com
Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
Yep, you discovered what I mentioned in my second email in this string. It
works when there are not single quotes in the order by. But the only way I
could think of to tell Maximo which route we are executing is by putting it
on the user record and then referencing it by using the :user variable. But
the user variable resolves to 'WERTZK', so that screws it up. I'm open to
any other ideas on how to log which route we're working on without using
the user record. I really wish Maximo provided a way to easily set
variables.
KW
On Wed, Aug 28, 2013 at 12:23 PM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> It doesn't seem to be the appending the storeroom that causes the problem
> I played around with where clause on the locations app its something to do
> with the order by I think
> You can replace the bean just as you would any other class but it then
> becomes a pain i.e. regression testing blah blah
>
> I would actually say it's a bug in the way it parses the string
>
> I entered this in the where clause of the application (sql server) as I
> had already tested it in sql studio and it gave me the results I wanted
>
> exists (select null from route_stop where route = 'EL001' and location =
> locations.location)
> order by (select stopsequence from route_stop where route = 'EL001' and
> location = locations.location)
>
> click find bang it dies
> then I tried this
>
> exists (select null from route_stop where route = 'EL001' and location =
> locations.location)
> order by (select stopsequence from route_stop where ROUTESTOPID = 5 and
> location = locations.location)
>
> AND IT WORKS doesn't give me the result I want i.e. it doesn't order
> correctly but doesn't complain about a database error - after parsing the
> where clause Maximo gives you :-
>
> (exists (select null from route_stop where route = 'EL001' and location =
> locations.location)) and (type in ( 'COURIER' , 'HOLDING' , 'LABOR' ,
> 'OPERATING' , 'REPAIR' , 'SALVAGE' , 'VENDOR' )) order by (select
> stopsequence from route_stop where routestopid = 5 and location =
> locations.location)
>
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Kevin Wertz
> Sent: 28 August 2013 16:43
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> Lots of issues with using work orders, you add all the overhead of
> creating the work orders then applying the route, then someone has to
> follow through on completing and reviewing the work orders and filling in
> all the required fields that we require to move to COMP. We are trying to
> replace an easy to use home-grown system so we have to make this as simple
> as possible for the users to accept the move to Maximo.
>
> The other issue is that they do many rounds daily and adding that volume
> to the workorder table and other related tables just didn't seem prudent to
> me.
>
> Any experience with java? The appending of the storeroom type thing
> ultimately comes from the LocationAppBean and indeed I have found the code
> where this gets appended. Wondered if any one maybe had any guidance or
> documentation on how to create a clone of the LocationAppBean and remove
> the appending of the storeroom restriction.
>
> KW
>
> On Wed, Aug 28, 2013 at 11:21 AM, Ian Wright <ian.wright@gdfsuezep.co.uk
> >wrote:
>
> > **
>
> >
> >
> > Well I think the issue is with the application and the fact that the
> > main object is the location table at the point of initiation After it
> > has found the records the relationship works i.e. I painted a list tab
> > column with the field relationship.stopsequence and it displayed
> > correctly, however you still can't sort
> >
> > location = :location and siteid = :siteid and route = ( select 'EL001'
> > from person where personid = :user) -- I used this relationship just
> > to check
> >
> > but I think you will have big problems getting this to work
> >
> > Question why don't they want to use work orders I have just changed
> > the work order actuals tab so at each task you can enter a meter
> > readings and it works great 7.5 They don't actually need PM's they can
> > just go to the work order select action apply route and if the route
> > is task based they get one work order with all the tasks i.e. stops in
> > sequence
> >
> > -----Original Message-----
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> > Of Kevin Wertz
> > Sent: 27 August 2013 17:47
> > To: MAXIMO@yahoogroups.com
> > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > location queries?
> >
> > You can use the :user variable in a relationship. But unfortunately
> > I've tried a relationship similar to that in the order by of the list
> > table object. I get an ora-904 error shown below.
> >
> > BMXAA4210E - Database error number 904 has occurred.ORA-00904:
> > "ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier Wasn't
> > sure if I needed the colon in front, but when I tried that, I got
> > this.BMXAA4210E - Database error number 1008 has occurred.
> >
> > ORA-01008: not all variables bound
> >
> > I guess you can't reference relationships in the order by on table
> objects.
> > I was kind of surprised to find this out. I thought for sure this
> > would work.
> > KW
> >
> > On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright
> > <ian.wright@gdfsuezep.co.uk
> > >wrote:
> >
> > > **
> >
> > >
> > >
> > > You could try this I've not tried it myself but its worth a bash use
> > > a relationship from locations to person that's assuming that
> > > personid = :user will work and then person to route then you could
> > > order the list screen table set the order by to :-
> > >
> > > By relationship1.relationjship2.sequence
> > >
> > >
> > > -----Original Message-----
> > > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On
> > > Behalf Of Kevin Wertz
> > > Sent: 27 August 2013 16:28
> > > To: MAXIMO@yahoogroups.com
> > > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > > location queries?
> > >
> > > Let me try this, and maybe someone can tell me if there is a "stupid
> > > Maximo trick" to get this to work.
> > >
> > > I am setting up meter reading routes in routes. Using the sequence
> > > field in the route stops to set the order in which they want to do
> > > the
> > route.
> > >
> > > However they don't want to do the routes on work orders, so I
> > > created a button in routes, tied to a simple workflow that sets the
> > > route id on the user's user record, then sends the user to the
> > > "Location Meter
> > Reading"
> > > application (clone of locations app, obviously).
> > >
> > > The location meter reading application has a default query in the
> > > presentation object that pulls the locations from the route's stops.
> > > However the order by in the query is failing, due to the issue I
> > > specified in the first email. Since I sent the first email, I
> > > figured out that the order by doesn't fail if there are not any
> > > single quotes in
> > the query.
> > > Weird huh?
> > >
> > > Problem is, to reference the route being performed to be able to
> > > reach the sequence column, I have to use the :user variable, which
> > > of course resolves to 'WERTZK'. Yeah, single quotes, so it fails
> > > with the oracle right parenthesis missing error.
> > >
> > > Any ideas on any tricks to accomplish what I'm trying to do?
> > >
> > > Kevin Wertz
> > > Grifols, Inc
> > > Clayton NC
> > >
> > > On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@gmail.com> wrote:
> > >
> > > > **
> > >
> > > >
> > > >
> > > > I have cloned locations for a meter-reading application. I want a
> > > > default query that has an order by clause in it. The problem is
> > > > that the locations applications append "type not in ('STOREROOM')"
> > > > to queries and for some order by clauses, it puts it after the
> > > > order by clause which causes the query to return an oracle error.
> > > >
> > > > Does anyone know how to suppress this from being appended to
> > > > queries in locations applications?
> > > >
> > > > Kevin Wertz
> > > > Grifols Therapeutics
> > > > Clayton NC
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > >
> > > Email addresses you might need:
> > > Posting: MAXIMO@yahoogroups.com
> > > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > > MAXIMO-unsubscribe@yahoogroups.com
> > > Cry : MAXIMO-owner@yahoogroups.com
> > > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> > >
> > > Come and visit us at Offshore Europe 2013 Find out more on our
> > > website
> > >
> > > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> > > and Wales with a registered office address at: 40 Holborn Viaduct,
> > > London, EC1N 2PB.
> > >
> > >
> > > ********************************************************************
> > > **
> > > ****************************************
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity to whom they
> > > are
> > addressed.
> > > If you have received this email in error please notify the system
> > manager.
> > >
> > > ********************************************************************
> > > **
> > > ****************************************
> > >
> > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> >
> >
>
>
>
> ------------------------------------
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>
Not sure if it helps but we are using System Properties to define routes that we are using for a specific process.
--- In MAXIMO@yahoogroups.com, Kevin Wertz <wertzee@...> wrote:
>
> Yep, you discovered what I mentioned in my second email in this string. It
> works when there are not single quotes in the order by. But the only way I
> could think of to tell Maximo which route we are executing is by putting it
> on the user record and then referencing it by using the :user variable. But
> the user variable resolves to 'WERTZK', so that screws it up. I'm open to
> any other ideas on how to log which route we're working on without using
> the user record. I really wish Maximo provided a way to easily set
> variables.
>
> KW
>
>
> On Wed, Aug 28, 2013 at 12:23 PM, Ian Wright <ian.wright@...>wrote:
>
> > **
> >
> >
> > It doesn't seem to be the appending the storeroom that causes the problem
> > I played around with where clause on the locations app its something to do
> > with the order by I think
> > You can replace the bean just as you would any other class but it then
> > becomes a pain i.e. regression testing blah blah
> >
> > I would actually say it's a bug in the way it parses the string
> >
> > I entered this in the where clause of the application (sql server) as I
> > had already tested it in sql studio and it gave me the results I wanted
> >
> > exists (select null from route_stop where route = 'EL001' and location =
> > locations.location)
> > order by (select stopsequence from route_stop where route = 'EL001' and
> > location = locations.location)
> >
> > click find bang it dies
> > then I tried this
> >
> > exists (select null from route_stop where route = 'EL001' and location =
> > locations.location)
> > order by (select stopsequence from route_stop where ROUTESTOPID = 5 and
> > location = locations.location)
> >
> > AND IT WORKS doesn't give me the result I want i.e. it doesn't order
> > correctly but doesn't complain about a database error - after parsing the
> > where clause Maximo gives you :-
> >
> > (exists (select null from route_stop where route = 'EL001' and location =
> > locations.location)) and (type in ( 'COURIER' , 'HOLDING' , 'LABOR' ,
> > 'OPERATING' , 'REPAIR' , 'SALVAGE' , 'VENDOR' )) order by (select
> > stopsequence from route_stop where routestopid = 5 and location =
> > locations.location)
> >
> >
> > -----Original Message-----
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> > Kevin Wertz
> > Sent: 28 August 2013 16:43
> > To: MAXIMO@yahoogroups.com
> > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > location queries?
> >
> > Lots of issues with using work orders, you add all the overhead of
> > creating the work orders then applying the route, then someone has to
> > follow through on completing and reviewing the work orders and filling in
> > all the required fields that we require to move to COMP. We are trying to
> > replace an easy to use home-grown system so we have to make this as simple
> > as possible for the users to accept the move to Maximo.
> >
> > The other issue is that they do many rounds daily and adding that volume
> > to the workorder table and other related tables just didn't seem prudent to
> > me.
> >
> > Any experience with java? The appending of the storeroom type thing
> > ultimately comes from the LocationAppBean and indeed I have found the code
> > where this gets appended. Wondered if any one maybe had any guidance or
> > documentation on how to create a clone of the LocationAppBean and remove
> > the appending of the storeroom restriction.
> >
> > KW
> >
> > On Wed, Aug 28, 2013 at 11:21 AM, Ian Wright <ian.wright@...
> > >wrote:
> >
> > > **
> >
> > >
> > >
> > > Well I think the issue is with the application and the fact that the
> > > main object is the location table at the point of initiation After it
> > > has found the records the relationship works i.e. I painted a list tab
> > > column with the field relationship.stopsequence and it displayed
> > > correctly, however you still can't sort
> > >
> > > location = :location and siteid = :siteid and route = ( select 'EL001'
> > > from person where personid = :user) -- I used this relationship just
> > > to check
> > >
> > > but I think you will have big problems getting this to work
> > >
> > > Question why don't they want to use work orders I have just changed
> > > the work order actuals tab so at each task you can enter a meter
> > > readings and it works great 7.5 They don't actually need PM's they can
> > > just go to the work order select action apply route and if the route
> > > is task based they get one work order with all the tasks i.e. stops in
> > > sequence
> > >
> > > -----Original Message-----
> > > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> > > Of Kevin Wertz
> > > Sent: 27 August 2013 17:47
> > > To: MAXIMO@yahoogroups.com
> > > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > > location queries?
> > >
> > > You can use the :user variable in a relationship. But unfortunately
> > > I've tried a relationship similar to that in the order by of the list
> > > table object. I get an ora-904 error shown below.
> > >
> > > BMXAA4210E - Database error number 904 has occurred.ORA-00904:
> > > "ROUTESTOP_CURRENTROUTE"."STOPSEQUENCE": invalid identifier Wasn't
> > > sure if I needed the colon in front, but when I tried that, I got
> > > this.BMXAA4210E - Database error number 1008 has occurred.
> > >
> > > ORA-01008: not all variables bound
> > >
> > > I guess you can't reference relationships in the order by on table
> > objects.
> > > I was kind of surprised to find this out. I thought for sure this
> > > would work.
> > > KW
> > >
> > > On Tue, Aug 27, 2013 at 12:23 PM, Ian Wright
> > > <ian.wright@...
> > > >wrote:
> > >
> > > > **
> > >
> > > >
> > > >
> > > > You could try this I've not tried it myself but its worth a bash use
> > > > a relationship from locations to person that's assuming that
> > > > personid = :user will work and then person to route then you could
> > > > order the list screen table set the order by to :-
> > > >
> > > > By relationship1.relationjship2.sequence
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On
> > > > Behalf Of Kevin Wertz
> > > > Sent: 27 August 2013 16:28
> > > > To: MAXIMO@yahoogroups.com
> > > > Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > > > location queries?
> > > >
> > > > Let me try this, and maybe someone can tell me if there is a "stupid
> > > > Maximo trick" to get this to work.
> > > >
> > > > I am setting up meter reading routes in routes. Using the sequence
> > > > field in the route stops to set the order in which they want to do
> > > > the
> > > route.
> > > >
> > > > However they don't want to do the routes on work orders, so I
> > > > created a button in routes, tied to a simple workflow that sets the
> > > > route id on the user's user record, then sends the user to the
> > > > "Location Meter
> > > Reading"
> > > > application (clone of locations app, obviously).
> > > >
> > > > The location meter reading application has a default query in the
> > > > presentation object that pulls the locations from the route's stops.
> > > > However the order by in the query is failing, due to the issue I
> > > > specified in the first email. Since I sent the first email, I
> > > > figured out that the order by doesn't fail if there are not any
> > > > single quotes in
> > > the query.
> > > > Weird huh?
> > > >
> > > > Problem is, to reference the route being performed to be able to
> > > > reach the sequence column, I have to use the :user variable, which
> > > > of course resolves to 'WERTZK'. Yeah, single quotes, so it fails
> > > > with the oracle right parenthesis missing error.
> > > >
> > > > Any ideas on any tricks to accomplish what I'm trying to do?
> > > >
> > > > Kevin Wertz
> > > > Grifols, Inc
> > > > Clayton NC
> > > >
> > > > On Fri, Aug 23, 2013 at 10:11 AM, kevwertz <wertzee@...> wrote:
> > > >
> > > > > **
> > > >
> > > > >
> > > > >
> > > > > I have cloned locations for a meter-reading application. I want a
> > > > > default query that has an order by clause in it. The problem is
> > > > > that the locations applications append "type not in ('STOREROOM')"
> > > > > to queries and for some order by clauses, it puts it after the
> > > > > order by clause which causes the query to return an oracle error.
> > > > >
> > > > > Does anyone know how to suppress this from being appended to
> > > > > queries in locations applications?
> > > > >
> > > > > Kevin Wertz
> > > > > Grifols Therapeutics
> > > > > Clayton NC
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > >
> > > > Email addresses you might need:
> > > > Posting: MAXIMO@yahoogroups.com
> > > > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > > > MAXIMO-unsubscribe@yahoogroups.com
> > > > Cry : MAXIMO-owner@yahoogroups.com
> > > > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> > > >
> > > > Come and visit us at Offshore Europe 2013 Find out more on our
> > > > website
> > > >
> > > > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> > > > and Wales with a registered office address at: 40 Holborn Viaduct,
> > > > London, EC1N 2PB.
> > > >
> > > >
> > > > ********************************************************************
> > > > **
> > > > ****************************************
> > > > This email and any files transmitted with it are confidential and
> > > > intended solely for the use of the individual or entity to whom they
> > > > are
> > > addressed.
> > > > If you have received this email in error please notify the system
> > > manager.
> > > >
> > > > ********************************************************************
> > > > **
> > > > ****************************************
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Email addresses you might need:
> > > Posting: MAXIMO@yahoogroups.com
> > > Join : MAXIMO-subscribe@yahoogroups.com Leave :
> > > MAXIMO-unsubscribe@yahoogroups.com
> > > Cry : MAXIMO-owner@yahoogroups.com
> > > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> > >
> > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> > Email addresses you might need:
> > Posting: MAXIMO@yahoogroups.com
> > Join : MAXIMO-subscribe@yahoogroups.com
> > Leave : MAXIMO-unsubscribe@yahoogroups.com
> > Cry : MAXIMO-owner@yahoogroups.com
> > Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
> >
> >
> >
>
>
>
>
Ok here is my answer to your problem - no cloned apps no work flow just add your meter readings in for each stop on the route :-)
In db config create a relationship against the route_stop table
called
ACTIVELOCATIONMETER
The child is
LOCATIONMETER
The relationship is
Location = :location and siteid = :siteid and active = 1
In your routes application find the following sectioncol
<sectioncol id="main_routestop_table_1_grid4_sec1_row1_col1">
Locate its end tag
</sectioncol>
Paste the following in immediately after
<sectioncol id="main_routestop_table_1_grid4_sec1_row1_col99">
<table id="locmeterread_grid_outer_1_1_meter_read" label="Location Meter Readings" relationship="ACTIVELOCATIONMETER">
<tablebody displayrowsperpage="20" filterable="true" id="locmeterread_grid_outer_1_1_meter_read_tablebody">
<tablecol filterable="false" id="locmeterread_grid_outer_1_1_meter_read_tablebody_1" mxevent="toggledetailstate" mxevent_desc="Show Detail" sortable="false" type="event"/>
<tablecol dataattribute="metername" id="locmeterread_grid_outer_1_1_meter_read_tablebody_2" sortable="true"/>
<tablecol dataattribute="meter.metertype" id="locmeterread_grid_outer_1_1_meter_read_tablebody_3" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_3" sortable="false"/>
<tablecol dataattribute="lastreading" id="locmeterread_grid_outer_1_1_meter_read_tablebody_4" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_4" sortable="false"/>
<tablecol dataattribute="lastreadingdate" id="locmeterread_grid_outer_1_1_meter_read_tablebody_5" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_5" sortable="false"/>
<tablecol dataattribute="newreading" id="locmeterread_grid_outer_1_1_meter_read_tablebody_6" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" sortable="false"/>
<tablecol dataattribute="newreadingdate" id="locmeterread_grid_outer_1_1_meter_read_tablebody_7" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" sortable="false"/>
<tablecol dataattribute="dorollover" id="locmeterread_grid_outer_1_1_meter_read_tablebody_9" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_17" sortable="false"/>
<tablecol dataattribute="inspector" id="locmeterread_grid_outer_1_1_meter_read_tablebody_8" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" sortable="false"/>
</tablebody>
<tabledetails id="locmeterread_grid_outer_1_1_meter_read_1">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid4" label="Details">
<sectionrow id="locmeterread_grid_outer_1_1_meter_read_1_grid41">
<sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_1">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_11">
<multiparttextbox dataattribute="location" descdataattribute="location.description" descinputmode="readonly" id="locmeterread_grid1_2" inputmode="readonly"/>
<multiparttextbox dataattribute="metername" descdataattribute="meter.description" descinputmode="readonly" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_1"/>
<textbox dataattribute="meter.metertype" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_3" inputmode="readonly"/>
<textbox dataattribute="lastreadingdate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_5" lookup="datelookup"/>
<textbox dataattribute="newreading" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" inputmode="required" lookup="valuelist"/>
<textbox dataattribute="newreadingdate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" inputmode="required" lookup="datelookup"/>
<checkbox dataattribute="dorollover" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"/>
<textbox applink="person" dataattribute="inspector" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" inputmode="required" lookup="person" menutype="normal"/>
</section>
</sectioncol>
<sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_2">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_21">
<checkbox dataattribute="isdelta" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_9"/>
<textbox dataattribute="sincelastoverhaul" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_10"/>
<textbox dataattribute="sincelastinspect" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_11"/>
<textbox dataattribute="sincelastrepair" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_12"/>
<textbox dataattribute="sinceinstall" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_13"/>
<textbox dataattribute="lifetodate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_14"/>
<textbox dataattribute="Average" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_15" inputmode="readonly"/>
<textbox dataattribute="remarks" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_16"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
</table>
</sectioncol>
Come and visit us at Offshore Europe 2013
Find out more on our website
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
If you decide to use it you can buy me a pint
Rgds Ian
BPD Zenith Ltd
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Ian Wright
Sent: 29 August 2013 08:54
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] remove "type not in ('STOREROOM')" from location queries?
Ok here is my answer to your problem - no cloned apps no work flow just add your meter readings in for each stop on the route :-)
In db config create a relationship against the route_stop table
called
ACTIVELOCATIONMETER
The child is
LOCATIONMETER
The relationship is
Location = :location and siteid = :siteid and active = 1
In your routes application find the following sectioncol
<sectioncol id="main_routestop_table_1_grid4_sec1_row1_col1">
Locate its end tag
</sectioncol>
Paste the following in immediately after
<sectioncol id="main_routestop_table_1_grid4_sec1_row1_col99">
<table id="locmeterread_grid_outer_1_1_meter_read" label="Location Meter Readings" relationship="ACTIVELOCATIONMETER">
<tablebody displayrowsperpage="20" filterable="true" id="locmeterread_grid_outer_1_1_meter_read_tablebody">
<tablecol filterable="false" id="locmeterread_grid_outer_1_1_meter_read_tablebody_1" mxevent="toggledetailstate" mxevent_desc="Show Detail" sortable="false" type="event"/>
<tablecol dataattribute="metername" id="locmeterread_grid_outer_1_1_meter_read_tablebody_2" sortable="true"/>
<tablecol dataattribute="meter.metertype" id="locmeterread_grid_outer_1_1_meter_read_tablebody_3" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_3" sortable="false"/>
<tablecol dataattribute="lastreading" id="locmeterread_grid_outer_1_1_meter_read_tablebody_4" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_4" sortable="false"/>
<tablecol dataattribute="lastreadingdate" id="locmeterread_grid_outer_1_1_meter_read_tablebody_5" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_5" sortable="false"/>
<tablecol dataattribute="newreading" id="locmeterread_grid_outer_1_1_meter_read_tablebody_6" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" sortable="false"/>
<tablecol dataattribute="newreadingdate" id="locmeterread_grid_outer_1_1_meter_read_tablebody_7" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" sortable="false"/>
<tablecol dataattribute="dorollover" id="locmeterread_grid_outer_1_1_meter_read_tablebody_9" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_17" sortable="false"/>
<tablecol dataattribute="inspector" id="locmeterread_grid_outer_1_1_meter_read_tablebody_8" linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" sortable="false"/>
</tablebody>
<tabledetails id="locmeterread_grid_outer_1_1_meter_read_1">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid4" label="Details">
<sectionrow id="locmeterread_grid_outer_1_1_meter_read_1_grid41">
<sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_1">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_11">
<multiparttextbox dataattribute="location" descdataattribute="location.description" descinputmode="readonly" id="locmeterread_grid1_2" inputmode="readonly"/>
<multiparttextbox dataattribute="metername" descdataattribute="meter.description" descinputmode="readonly" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_1"/>
<textbox dataattribute="meter.metertype" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_3" inputmode="readonly"/>
<textbox dataattribute="lastreadingdate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_5" lookup="datelookup"/>
<textbox dataattribute="newreading" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" inputmode="required" lookup="valuelist"/>
<textbox dataattribute="newreadingdate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" inputmode="required" lookup="datelookup"/>
<checkbox dataattribute="dorollover" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"/>
<textbox applink="person" dataattribute="inspector" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" inputmode="required" lookup="person" menutype="normal"/>
</section>
</sectioncol>
<sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_2">
<section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_21">
<checkbox dataattribute="isdelta" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_9"/>
<textbox dataattribute="sincelastoverhaul" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_10"/>
<textbox dataattribute="sincelastinspect" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_11"/>
<textbox dataattribute="sincelastrepair" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_12"/>
<textbox dataattribute="sinceinstall" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_13"/>
<textbox dataattribute="lifetodate" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_14"/>
<textbox dataattribute="Average" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_15" inputmode="readonly"/>
<textbox dataattribute="remarks" id="locmeterread_grid_outer_1_1_meter_read_1_grid4_16"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
</table>
</sectioncol>
Come and visit us at Offshore Europe 2013
Find out more on our website
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************
So, just reviewing this now...you have figured out how to do the meter
readings from routes? I had this idea but I figured I would have to do the
readings from a location-based app due to the meter reading beans being
included there.
KW
On Thu, Aug 29, 2013 at 4:17 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> If you decide to use it you can buy me a pint
>
> Rgds Ian
> BPD Zenith Ltd
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Ian Wright
> Sent: 29 August 2013 08:54
> To: MAXIMO@yahoogroups.com
> Subject: RE: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
>
> Ok here is my answer to your problem - no cloned apps no work flow just
> add your meter readings in for each stop on the route :-)
>
> In db config create a relationship against the route_stop table
> called
> ACTIVELOCATIONMETER
> The child is
> LOCATIONMETER
> The relationship is
>
> Location = :location and siteid = :siteid and active = 1
>
> In your routes application find the following sectioncol
>
> <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col1">
>
> Locate its end tag
>
> </sectioncol>
>
> Paste the following in immediately after
>
> <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col99">
> <table id="locmeterread_grid_outer_1_1_meter_read" label="Location Meter
> Readings" relationship="ACTIVELOCATIONMETER">
> <tablebody displayrowsperpage="20" filterable="true"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody">
> <tablecol filterable="false"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_1"
> mxevent="toggledetailstate" mxevent_desc="Show Detail" sortable="false"
> type="event"/>
> <tablecol dataattribute="metername"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_2" sortable="true"/>
> <tablecol dataattribute="meter.metertype"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_3"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_3"
> sortable="false"/>
> <tablecol dataattribute="lastreading"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_4"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_4"
> sortable="false"/>
> <tablecol dataattribute="lastreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_5"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_5"
> sortable="false"/>
> <tablecol dataattribute="newreading"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_6"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_6"
> sortable="false"/>
> <tablecol dataattribute="newreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_7"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_7"
> sortable="false"/>
> <tablecol dataattribute="dorollover"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_9"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"
> sortable="false"/>
> <tablecol dataattribute="inspector"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_8"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_8"
> sortable="false"/>
> </tablebody>
> <tabledetails id="locmeterread_grid_outer_1_1_meter_read_1">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid4"
> label="Details">
> <sectionrow id="locmeterread_grid_outer_1_1_meter_read_1_grid41">
> <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_1">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_11">
> <multiparttextbox dataattribute="location"
> descdataattribute="location.description" descinputmode="readonly"
> id="locmeterread_grid1_2" inputmode="readonly"/>
> <multiparttextbox dataattribute="metername"
> descdataattribute="meter.description" descinputmode="readonly"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_1"/>
> <textbox dataattribute="meter.metertype"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_3" inputmode="readonly"/>
> <textbox dataattribute="lastreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_5" lookup="datelookup"/>
> <textbox dataattribute="newreading"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" inputmode="required"
> lookup="valuelist"/>
> <textbox dataattribute="newreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" inputmode="required"
> lookup="datelookup"/>
> <checkbox dataattribute="dorollover"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"/>
> <textbox applink="person" dataattribute="inspector"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" inputmode="required"
> lookup="person" menutype="normal"/>
> </section>
> </sectioncol>
> <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_2">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_21">
> <checkbox dataattribute="isdelta"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_9"/>
> <textbox dataattribute="sincelastoverhaul"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_10"/>
> <textbox dataattribute="sincelastinspect"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_11"/>
> <textbox dataattribute="sincelastrepair"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_12"/>
> <textbox dataattribute="sinceinstall"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_13"/>
> <textbox dataattribute="lifetodate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_14"/>
> <textbox dataattribute="Average"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_15"
> inputmode="readonly"/>
> <textbox dataattribute="remarks"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_16"/>
> </section>
> </sectioncol>
> </sectionrow>
> </section>
> </tabledetails>
> </table>
>
> </sectioncol>
>
> Come and visit us at Offshore Europe 2013
> Find out more on our website
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and
> Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N
> 2PB.
>
>
> **************************************************************************************************************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
>
> **************************************************************************************************************
>
>
>
>
>
>
>
Yes I did it recently on a clone of the work order where we do completions i.e. we just enter actuals and I put this on the main screen and tasks
I realised at the time you just need the relationship so I tried it on the routes application and it seems to work fine
Rgds Ian
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Kevin Wertz
Sent: 29 August 2013 16:26
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from location queries?
So, just reviewing this now...you have figured out how to do the meter readings from routes? I had this idea but I figured I would have to do the readings from a location-based app due to the meter reading beans being included there.
KW
On Thu, Aug 29, 2013 at 4:17 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> If you decide to use it you can buy me a pint
>
> Rgds Ian
> BPD Zenith Ltd
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> Of Ian Wright
> Sent: 29 August 2013 08:54
> To: MAXIMO@yahoogroups.com
> Subject: RE: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
>
> Ok here is my answer to your problem - no cloned apps no work flow
> just add your meter readings in for each stop on the route :-)
>
> In db config create a relationship against the route_stop table called
> ACTIVELOCATIONMETER The child is LOCATIONMETER The relationship is
>
> Location = :location and siteid = :siteid and active = 1
>
> In your routes application find the following sectioncol
>
> <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col1">
>
> Locate its end tag
>
> </sectioncol>
>
> Paste the following in immediately after
>
> <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col99">
> <table id="locmeterread_grid_outer_1_1_meter_read" label="Location
> Meter Readings" relationship="ACTIVELOCATIONMETER">
> <tablebody displayrowsperpage="20" filterable="true"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody">
> <tablecol filterable="false"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_1"
> mxevent="toggledetailstate" mxevent_desc="Show Detail" sortable="false"
> type="event"/>
> <tablecol dataattribute="metername"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_2"
> sortable="true"/> <tablecol dataattribute="meter.metertype"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_3"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_3"
> sortable="false"/>
> <tablecol dataattribute="lastreading"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_4"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_4"
> sortable="false"/>
> <tablecol dataattribute="lastreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_5"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_5"
> sortable="false"/>
> <tablecol dataattribute="newreading"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_6"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_6"
> sortable="false"/>
> <tablecol dataattribute="newreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_7"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_7"
> sortable="false"/>
> <tablecol dataattribute="dorollover"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_9"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"
> sortable="false"/>
> <tablecol dataattribute="inspector"
> id="locmeterread_grid_outer_1_1_meter_read_tablebody_8"
> linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_8"
> sortable="false"/>
> </tablebody>
> <tabledetails id="locmeterread_grid_outer_1_1_meter_read_1">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid4"
> label="Details">
> <sectionrow id="locmeterread_grid_outer_1_1_meter_read_1_grid41">
> <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_1">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_11">
> <multiparttextbox dataattribute="location"
> descdataattribute="location.description" descinputmode="readonly"
> id="locmeterread_grid1_2" inputmode="readonly"/> <multiparttextbox
> dataattribute="metername"
> descdataattribute="meter.description" descinputmode="readonly"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_1"/>
> <textbox dataattribute="meter.metertype"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_3"
> inputmode="readonly"/> <textbox dataattribute="lastreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_5"
> lookup="datelookup"/> <textbox dataattribute="newreading"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_6" inputmode="required"
> lookup="valuelist"/>
> <textbox dataattribute="newreadingdate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_7" inputmode="required"
> lookup="datelookup"/>
> <checkbox dataattribute="dorollover"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"/>
> <textbox applink="person" dataattribute="inspector"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_8" inputmode="required"
> lookup="person" menutype="normal"/>
> </section>
> </sectioncol>
> <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_2">
> <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_21">
> <checkbox dataattribute="isdelta"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_9"/>
> <textbox dataattribute="sincelastoverhaul"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_10"/>
> <textbox dataattribute="sincelastinspect"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_11"/>
> <textbox dataattribute="sincelastrepair"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_12"/>
> <textbox dataattribute="sinceinstall"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_13"/>
> <textbox dataattribute="lifetodate"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_14"/>
> <textbox dataattribute="Average"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_15"
> inputmode="readonly"/>
> <textbox dataattribute="remarks"
> id="locmeterread_grid_outer_1_1_meter_read_1_grid4_16"/>
> </section>
> </sectioncol>
> </sectionrow>
> </section>
> </tabledetails>
> </table>
>
> </sectioncol>
>
> Come and visit us at Offshore Europe 2013 Find out more on our website
>
> GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> and Wales with a registered office address at: 40 Holborn Viaduct,
> London, EC1N 2PB.
>
>
> **********************************************************************
> ****************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
>
> **********************************************************************
> ****************************************
>
>
>
>
>
>
>
------------------------------------
Email addresses you might need:
Posting: MAXIMO@yahoogroups.com
Join : MAXIMO-subscribe@yahoogroups.com
Leave : MAXIMO-unsubscribe@yahoogroups.com
Cry : MAXIMO-owner@yahoogroups.com
Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
Awesome Ian, thanks so much for your time. I will proof-of-concept this and
present it as an option. One big problem with it though, there will be
several hundred readings on some of these routes and they will really need
to save periodically. When they do, the list will pop back to the first
page.
KW
On Thu, Aug 29, 2013 at 11:58 AM, Ian Wright <ian.wright@gdfsuezep.co.uk>wrote:
> **
>
>
> Yes I did it recently on a clone of the work order where we do completions
> i.e. we just enter actuals and I put this on the main screen and tasks
> I realised at the time you just need the relationship so I tried it on the
> routes application and it seems to work fine
>
> Rgds Ian
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of
> Kevin Wertz
> Sent: 29 August 2013 16:26
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] remove "type not in ('STOREROOM')" from
> location queries?
>
> So, just reviewing this now...you have figured out how to do the meter
> readings from routes? I had this idea but I figured I would have to do the
> readings from a location-based app due to the meter reading beans being
> included there.
>
> KW
>
> On Thu, Aug 29, 2013 at 4:17 AM, Ian Wright <ian.wright@gdfsuezep.co.uk
> >wrote:
>
> > **
>
> >
> >
> > If you decide to use it you can buy me a pint
> >
> > Rgds Ian
> > BPD Zenith Ltd
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf
> > Of Ian Wright
> > Sent: 29 August 2013 08:54
> > To: MAXIMO@yahoogroups.com
> > Subject: RE: [MAXIMO List] remove "type not in ('STOREROOM')" from
> > location queries?
> >
> >
> > Ok here is my answer to your problem - no cloned apps no work flow
> > just add your meter readings in for each stop on the route :-)
> >
> > In db config create a relationship against the route_stop table called
> > ACTIVELOCATIONMETER The child is LOCATIONMETER The relationship is
> >
> > Location = :location and siteid = :siteid and active = 1
> >
> > In your routes application find the following sectioncol
> >
> > <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col1">
> >
> > Locate its end tag
> >
> > </sectioncol>
> >
> > Paste the following in immediately after
> >
> > <sectioncol id="main_routestop_table_1_grid4_sec1_row1_col99">
> > <table id="locmeterread_grid_outer_1_1_meter_read" label="Location
> > Meter Readings" relationship="ACTIVELOCATIONMETER">
> > <tablebody displayrowsperpage="20" filterable="true"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody">
> > <tablecol filterable="false"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_1"
> > mxevent="toggledetailstate" mxevent_desc="Show Detail" sortable="false"
> > type="event"/>
> > <tablecol dataattribute="metername"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_2"
> > sortable="true"/> <tablecol dataattribute="meter.metertype"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_3"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_3"
> > sortable="false"/>
> > <tablecol dataattribute="lastreading"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_4"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_4"
> > sortable="false"/>
> > <tablecol dataattribute="lastreadingdate"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_5"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_5"
> > sortable="false"/>
> > <tablecol dataattribute="newreading"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_6"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_6"
> > sortable="false"/>
> > <tablecol dataattribute="newreadingdate"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_7"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_7"
> > sortable="false"/>
> > <tablecol dataattribute="dorollover"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_9"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"
> > sortable="false"/>
> > <tablecol dataattribute="inspector"
> > id="locmeterread_grid_outer_1_1_meter_read_tablebody_8"
> > linkedcontrolid="locmeterread_grid_outer_1_1_meter_read_1_grid4_8"
> > sortable="false"/>
> > </tablebody>
> > <tabledetails id="locmeterread_grid_outer_1_1_meter_read_1">
> > <section id="locmeterread_grid_outer_1_1_meter_read_1_grid4"
> > label="Details">
> > <sectionrow id="locmeterread_grid_outer_1_1_meter_read_1_grid41">
> > <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_1">
> > <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_11">
> > <multiparttextbox dataattribute="location"
> > descdataattribute="location.description" descinputmode="readonly"
> > id="locmeterread_grid1_2" inputmode="readonly"/> <multiparttextbox
> > dataattribute="metername"
> > descdataattribute="meter.description" descinputmode="readonly"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_1"/>
> > <textbox dataattribute="meter.metertype"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_3"
> > inputmode="readonly"/> <textbox dataattribute="lastreadingdate"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_5"
> > lookup="datelookup"/> <textbox dataattribute="newreading"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_6"
> inputmode="required"
> > lookup="valuelist"/>
> > <textbox dataattribute="newreadingdate"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_7"
> inputmode="required"
> > lookup="datelookup"/>
> > <checkbox dataattribute="dorollover"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_17"/>
> > <textbox applink="person" dataattribute="inspector"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_8"
> inputmode="required"
> > lookup="person" menutype="normal"/>
> > </section>
> > </sectioncol>
> > <sectioncol id="locmeterread_grid_outer_1_1_meter_read_1_grid41_2">
> > <section id="locmeterread_grid_outer_1_1_meter_read_1_grid41_21">
> > <checkbox dataattribute="isdelta"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_9"/>
> > <textbox dataattribute="sincelastoverhaul"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_10"/>
> > <textbox dataattribute="sincelastinspect"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_11"/>
> > <textbox dataattribute="sincelastrepair"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_12"/>
> > <textbox dataattribute="sinceinstall"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_13"/>
> > <textbox dataattribute="lifetodate"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_14"/>
> > <textbox dataattribute="Average"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_15"
> > inputmode="readonly"/>
> > <textbox dataattribute="remarks"
> > id="locmeterread_grid_outer_1_1_meter_read_1_grid4_16"/>
> > </section>
> > </sectioncol>
> > </sectionrow>
> > </section>
> > </tabledetails>
> > </table>
> >
> > </sectioncol>
> >
> > Come and visit us at Offshore Europe 2013 Find out more on our website
> >
> > GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England
> > and Wales with a registered office address at: 40 Holborn Viaduct,
> > London, EC1N 2PB.
> >
> >
> > **********************************************************************
> > ****************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they are
> addressed.
> > If you have received this email in error please notify the system
> manager.
> >
> > **********************************************************************
> > ****************************************
> >
> >
> >
> >
> >
> >
> >
>
>
>
> ------------------------------------
>
>
> Email addresses you might need:
> Posting: MAXIMO@yahoogroups.com
> Join : MAXIMO-subscribe@yahoogroups.com
> Leave : MAXIMO-unsubscribe@yahoogroups.com
> Cry : MAXIMO-owner@yahoogroups.com
> Group : http://groups.yahoo.com/group/MAXIMOYahoo! Groups Links
>
>
>