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.
Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
Hi
I don't think so. That has been the functionality since Iknow since 411.
If you need to modify a PO line or PO you have to put it back into WAPPR or Waiting Approval.
thanks
Ray DeFelice
PWD
--- In MAXIMO@yahoogroups.com, "John" <jwood@...> wrote:
>
> Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
>
Hi,
You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
I used this condition
((:historyflag=0) and (:status in
(select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
Dave Bone
Ocean Spray Cranberries
--- In MAXIMO@yahoogroups.com, "John" <jwood@...> wrote:
>
> Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
>
Thanks,
We decided just to add another field for the users to use.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
>
> I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
>
> I used this condition
>
> ((:historyflag=0) and (:status in
> (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
>
> But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
>
> This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
>
> Dave Bone
> Ocean Spray Cranberries
>
>
>
>
> --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> >
> > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> >
>
Gday John,
What would be an example text input the users would enter (on this Approved/Sent) PO?
Sent on the Sprint� Now Network from my BlackBerry�
-----Original Message-----
From: "John" <jwood@ch2mhillacademyservices.com>
Sender: MAXIMO@yahoogroups.com
Date: Wed, 10 Aug 2011 15:18:05
To: <MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Maximo 7.1.1.5 PO and POLine Long Descriptions
Thanks,
We decided just to add another field for the users to use.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
>
> I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
>
> I used this condition
>
> ((:historyflag=0) and (:status in
> (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
>
> But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
>
> This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
>
> Dave Bone
> Ocean Spray Cranberries
>
>
>
>
> --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> >
> > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> >
>
Hi,
Here are some actual comments. They really like this since they can make changes without changing the status.
Contractor came in twice. First time to make temp repairs and then 2nd time to replace parts see wo long discription.
Repair order 41771 & 41931 based on pm shipping dock repairs with multi work orders.
spoke with Larry. quoted World Wide motor with heavy cast enclosure (not comletely water proof) $830.82 plus C-face $62.88. will check quotes from other venders for stainless options.
DALE RESOLVED ISSUE WITHOUT THESE MATERIALS. PO CANCELLED. RP
VENDOR ACKNOWLEDGEMENT SHOWS INCORRECT BILL AND SHIP TO REFERENCE TO SULPHUR SPRINGS. SS CALLED TO LET ME KNOW THEY RECEIVED OUR PKG. VENDOR REQUESTED SS FORWARD PKG TO US USING VENDOR'S FED EX ACCOUNT NUMBER. BRENDA SMITH WILL TAKE CARE OF SHIPMENT. RP 11/29/10
Emailed PO to Ronnie Dressler 8/9/10 8/10/10 email from Ron Dressler XY-12 should be there today or tomorrow and CoolingCare probably Friday
Just about anything they need to keep track of during the purchase.
Dave Bone
Ocean Spray Cranberries
--- In MAXIMO@yahoogroups.com, planschd@... wrote:
>
> Gday John,
>
> What would be an example text input the users would enter (on this Approved/Sent) PO?
>
> Sent on the Sprint® Now Network from my BlackBerry®
>
> -----Original Message-----
> From: "John" <jwood@...>
> Sender: MAXIMO@yahoogroups.com
> Date: Wed, 10 Aug 2011 15:18:05
> To: <MAXIMO@yahoogroups.com>
> Reply-To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Re: Maximo 7.1.1.5 PO and POLine Long Descriptions
>
>
> Thanks,
>
> We decided just to add another field for the users to use.
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
> >
> > I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
> >
> > I used this condition
> >
> > ((:historyflag=0) and (:status in
> > (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
> >
> > But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
> >
> > This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
> >
> > Dave Bone
> > Ocean Spray Cranberries
> >
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> > >
> > > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> > >
> >
>
>
>
>
>
>
>
Dave, you have made me a hero with our Purchasing group by giving them an editable field after the PO is APPR/INPRG status.
Thanks again for the help you put into this group!
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> Here are some actual comments. They really like this since they can make changes without changing the status.
>
> Contractor came in twice. First time to make temp repairs and then 2nd time to replace parts see wo long discription.
>
> Repair order 41771 & 41931 based on pm shipping dock repairs with multi work orders.
>
> spoke with Larry. quoted World Wide motor with heavy cast enclosure (not comletely water proof) $830.82 plus C-face $62.88. will check quotes from other venders for stainless options.
>
> DALE RESOLVED ISSUE WITHOUT THESE MATERIALS. PO CANCELLED. RP
>
> VENDOR ACKNOWLEDGEMENT SHOWS INCORRECT BILL AND SHIP TO REFERENCE TO SULPHUR SPRINGS. SS CALLED TO LET ME KNOW THEY RECEIVED OUR PKG. VENDOR REQUESTED SS FORWARD PKG TO US USING VENDOR'S FED EX ACCOUNT NUMBER. BRENDA SMITH WILL TAKE CARE OF SHIPMENT. RP 11/29/10
>
> Emailed PO to Ronnie Dressler 8/9/10 8/10/10 email from Ron Dressler XY-12 should be there today or tomorrow and CoolingCare probably Friday
>
> Just about anything they need to keep track of during the purchase.
>
> Dave Bone
> Ocean Spray Cranberries
>
> --- In MAXIMO@yahoogroups.com, planschd@ wrote:
> >
> > Gday John,
> >
> > What would be an example text input the users would enter (on this Approved/Sent) PO?
> >
> > Sent on the Sprint® Now Network from my BlackBerry®
> >
> > -----Original Message-----
> > From: "John" <jwood@>
> > Sender: MAXIMO@yahoogroups.com
> > Date: Wed, 10 Aug 2011 15:18:05
> > To: <MAXIMO@yahoogroups.com>
> > Reply-To: MAXIMO@yahoogroups.com
> > Subject: [MAXIMO List] Re: Maximo 7.1.1.5 PO and POLine Long Descriptions
> >
> >
> > Thanks,
> >
> > We decided just to add another field for the users to use.
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > Hi,
> > >
> > > You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
> > >
> > > I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
> > >
> > > I used this condition
> > >
> > > ((:historyflag=0) and (:status in
> > > (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
> > >
> > > But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
> > >
> > > This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
> > >
> > > Dave Bone
> > > Ocean Spray Cranberries
> > >
> > >
> > >
> > >
> > > --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> > > >
> > > > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> > > >
> > >
> >
> >
> >
> >
> >
> >
> >
>
Hi,
Glad to help.
Speaking of heroes does this mean I get to be an argonaut?
http://en.wikipedia.org/wiki/Jason
That golden fleece is worth about $1,700 an once right now!
Dave Bone
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> Dave, you have made me a hero with our Purchasing group by giving them an editable field after the PO is APPR/INPRG status.
>
> Thanks again for the help you put into this group!
>
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > Here are some actual comments. They really like this since they can make changes without changing the status.
> >
> > Contractor came in twice. First time to make temp repairs and then 2nd time to replace parts see wo long discription.
> >
> > Repair order 41771 & 41931 based on pm shipping dock repairs with multi work orders.
> >
> > spoke with Larry. quoted World Wide motor with heavy cast enclosure (not comletely water proof) $830.82 plus C-face $62.88. will check quotes from other venders for stainless options.
> >
> > DALE RESOLVED ISSUE WITHOUT THESE MATERIALS. PO CANCELLED. RP
> >
> > VENDOR ACKNOWLEDGEMENT SHOWS INCORRECT BILL AND SHIP TO REFERENCE TO SULPHUR SPRINGS. SS CALLED TO LET ME KNOW THEY RECEIVED OUR PKG. VENDOR REQUESTED SS FORWARD PKG TO US USING VENDOR'S FED EX ACCOUNT NUMBER. BRENDA SMITH WILL TAKE CARE OF SHIPMENT. RP 11/29/10
> >
> > Emailed PO to Ronnie Dressler 8/9/10 8/10/10 email from Ron Dressler XY-12 should be there today or tomorrow and CoolingCare probably Friday
> >
> > Just about anything they need to keep track of during the purchase.
> >
> > Dave Bone
> > Ocean Spray Cranberries
> >
> > --- In MAXIMO@yahoogroups.com, planschd@ wrote:
> > >
> > > Gday John,
> > >
> > > What would be an example text input the users would enter (on this Approved/Sent) PO?
> > >
> > > Sent on the Sprint® Now Network from my BlackBerry®
> > >
> > > -----Original Message-----
> > > From: "John" <jwood@>
> > > Sender: MAXIMO@yahoogroups.com
> > > Date: Wed, 10 Aug 2011 15:18:05
> > > To: <MAXIMO@yahoogroups.com>
> > > Reply-To: MAXIMO@yahoogroups.com
> > > Subject: [MAXIMO List] Re: Maximo 7.1.1.5 PO and POLine Long Descriptions
> > >
> > >
> > > Thanks,
> > >
> > > We decided just to add another field for the users to use.
> > >
> > > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > > >
> > > > Hi,
> > > >
> > > > You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
> > > >
> > > > I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
> > > >
> > > > I used this condition
> > > >
> > > > ((:historyflag=0) and (:status in
> > > > (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
> > > >
> > > > But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
> > > >
> > > > This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
> > > >
> > > > Dave Bone
> > > > Ocean Spray Cranberries
> > > >
> > > >
> > > >
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> > > > >
> > > > > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
I can grant you status of 'Honorary' Argonaut, but the fleece was sold years ago when I thought $1200/oz was the max.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> Glad to help.
>
> Speaking of heroes does this mean I get to be an argonaut?
>
> http://en.wikipedia.org/wiki/Jason
>
> That golden fleece is worth about $1,700 an once right now!
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > Dave, you have made me a hero with our Purchasing group by giving them an editable field after the PO is APPR/INPRG status.
> >
> > Thanks again for the help you put into this group!
> >
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > Hi,
> > >
> > > Here are some actual comments. They really like this since they can make changes without changing the status.
> > >
> > > Contractor came in twice. First time to make temp repairs and then 2nd time to replace parts see wo long discription.
> > >
> > > Repair order 41771 & 41931 based on pm shipping dock repairs with multi work orders.
> > >
> > > spoke with Larry. quoted World Wide motor with heavy cast enclosure (not comletely water proof) $830.82 plus C-face $62.88. will check quotes from other venders for stainless options.
> > >
> > > DALE RESOLVED ISSUE WITHOUT THESE MATERIALS. PO CANCELLED. RP
> > >
> > > VENDOR ACKNOWLEDGEMENT SHOWS INCORRECT BILL AND SHIP TO REFERENCE TO SULPHUR SPRINGS. SS CALLED TO LET ME KNOW THEY RECEIVED OUR PKG. VENDOR REQUESTED SS FORWARD PKG TO US USING VENDOR'S FED EX ACCOUNT NUMBER. BRENDA SMITH WILL TAKE CARE OF SHIPMENT. RP 11/29/10
> > >
> > > Emailed PO to Ronnie Dressler 8/9/10 8/10/10 email from Ron Dressler XY-12 should be there today or tomorrow and CoolingCare probably Friday
> > >
> > > Just about anything they need to keep track of during the purchase.
> > >
> > > Dave Bone
> > > Ocean Spray Cranberries
> > >
> > > --- In MAXIMO@yahoogroups.com, planschd@ wrote:
> > > >
> > > > Gday John,
> > > >
> > > > What would be an example text input the users would enter (on this Approved/Sent) PO?
> > > >
> > > > Sent on the Sprint® Now Network from my BlackBerry®
> > > >
> > > > -----Original Message-----
> > > > From: "John" <jwood@>
> > > > Sender: MAXIMO@yahoogroups.com
> > > > Date: Wed, 10 Aug 2011 15:18:05
> > > > To: <MAXIMO@yahoogroups.com>
> > > > Reply-To: MAXIMO@yahoogroups.com
> > > > Subject: [MAXIMO List] Re: Maximo 7.1.1.5 PO and POLine Long Descriptions
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > We decided just to add another field for the users to use.
> > > >
> > > > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > You could probably override the read only for certain fields by creating a condition and then using that in the application designer with a signature option to make the filed input mode query.
> > > > >
> > > > > I put two fields on our main PO form for comments and a check box indicating the PO was sent to the vendor. These fields are not sent on the PO to the vendor and the users can always change them until the PO is closed. That way they can keep track of what needs to be done or any issues right on the PO.
> > > > >
> > > > > I used this condition
> > > > >
> > > > > ((:historyflag=0) and (:status in
> > > > > (select value from synonymdomain where domainid = 'POSTATUS' and (maxvalue = 'WAPPR' or maxvalue = 'APPR' or maxvalue = 'INPRG'))))
> > > > >
> > > > > But changing anything on the PO after it is approved that is transmitted to the vendor can be a very big issue. You don't want someone change the PO lines after the PO has been transmitted to the vendor unless it is absolutely required. If they change a PO line we still require they unapprove the PO and make the change.
> > > > >
> > > > > This brings up another point about purchasing. In Maximo you can set up audit tables. You should audit all of the purchasing related tables and most of the fields in those tables. The tables PO, POLINE, INVOICE, INVOICELINE, MATRECTRANS, SERVRECTRANS etc.. should all be audited. That way if for any reason a question arises of what was changed, when it was changed and who made the change you have the data.
> > > > >
> > > > > Dave Bone
> > > > > Ocean Spray Cranberries
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --- In MAXIMO@yahoogroups.com, "John" <jwood@> wrote:
> > > > > >
> > > > > > Is there a setting somewhere in Maximo 7.1.1.5 that enables modifying the PO and POLine Long Descriptions without taking the PO out of APPR status.
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>