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.
We did not have any Java customizaton around PO, PO Revision or Contract. It ended up being a bug within Maximo when there were attachments associated with the PO. We got a fix from IBM and now don't have the issue.
--- In MAXIMO@yahoogroups.com, "areddy214" wrote:
>
> Have you done any Java customization around PO, PO Revision and Contract. I had not seen in the OOB systems.
>
> Thanks
> AR
>
> --- In MAXIMO@yahoogroups.com, "Molly" wrote:
> >
> > We are in the process of upgrading to Maximo 7.5.0.1 and have found an interesting issue. When we try and revise a PO associated with a Contract, it revises the contract as well. Interesting thing is this only occurs on upgraded POs\Contracts. If I create a new PO\Contract in 7.5.0.1, i don't see this issue. Funny thing is, we can no longer find the contract in the Purchasing Contracts application because that application uses a view that joins the CONTRACTS and CONTRACTPURCH tables and the contract only gets revised in the CONTRACTS table thus the join does not work.
> >
> > Do you use contracts and have you seen this?
> >
> > --- In MAXIMO@yahoogroups.com, Brian Swanson wrote:
> > >
> > > This is new functionality in version 7. It does not exist in your current version.
> > >
> > >
> > >
> > > Brian Swanson
> > > Systems Analyst-Maximo
> > > Information Technology
> > >
> > >
> > >
> > > HermanMiller
> > >
> > >
> > >
> > > From: zeroxpectations@
> > > To: "MAXIMO@yahoogroups.com" ,
> > > Date: 09/18/2012 08:47 AM
> > > Subject: Re: [MAXIMO List] Maximo and Revision enhancement
> > > Sent by: MAXIMO@yahoogroups.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Greetings. I am running v6.2.6 and just for my own personal understanding, and please forgive my ignorance, could you please define "Revised PO"? I am understanding this to mean the same thing as a
> > > "Change order", but when you say "exists on a revised PO" do you mean one with completed receipts? If so, then I understand your frustration.
> > >
> > > Thanks
> > >
> > > On Sep 17, 2012, at 1:19 PM, Brian Swanson wrote:
> > >
> > > >
> > > > HI All,
> > > > It's been a while since I posted here, but I see there has been some discussion on the new processes around Revisions.
> > > >
> > > > We are using Maximo 7.5.0.1. I'm looking to go to 7.5.0.3. In both versions, I'm working on 3 PMR's that have been identified as bugs dealing with Revisions. I have come to the conclusion, that who
> > > > ever came up with this new process, did a very poor job of development.
> > > >
> > > > Detail listed below. Please contact me directly if you would like more detail.
> > > >
> > > > 1. You can NOT move an asset to another site if the Asset exists on a Revised PO.
> > > >
> > > > 2. You can NOT change any Item to Obsolete that exists on a revised PO
> > > >
> > > > 3. Auto Reorder looks at items on a Revised PO as being on order. (We fixed this for now by creating an escalation that updates the POLINES.RECEIPTSCOMPLETE = 0 and PO.RECEIPTS = 'COMPLETE' where
> > > > status = 'REVISD')
> > > >
> > > > 4. New for Maximo 7.5.0.3, can't change the Order Unit on PO's. Receiving will fail.
> > > >
> > > > I hope to have hot fixes for these soon.
> > > >
> > > > Thanks
> > > >
> > > > Brian Swanson
> > > > Systems Analyst-Maximo
> > > > Information Technology
> > > >
> > > > HermanMiller
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>