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.
Hey Gang,
We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
Just curious if anyone has gotten this to work and if there is a clean way of doing it.
thanks,
John B
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com, John Ballnik <jballnik@...> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
If currently always use revision 0
<ns0:PO action="AddChange">
<ns0:REVISIONNUM>0</ns0:REVISIONNUM>
<ns0:STATUS>APPR</ns0:STATUS>
Etc ......
If it changes in sap they unapproved to make the change
<ns0:PO action="AddChange">
<ns0:REVISIONNUM>0</ns0:REVISIONNUM>
<ns0:STATUS>WAPPR</ns0:STATUS>
Then when they approve again
<ns0:PO action="AddChange">
<ns0:REVISIONNUM>0</ns0:REVISIONNUM>
<ns0:STATUS>APPR</ns0:STATUS>
I never get any issues about PENDREV the only issue I do get is that I have to use a sequential queue as they can flip the status so quick the messages get confused and it would end up as WAPPR when it should have been APPR
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
Sent: 29 July 2013 23:19
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Incoming MIF PO Revision object
Hey Gang,
We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
Just curious if anyone has gotten this to work and if there is a clean way of doing it.
thanks,
John B
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.
**************************************************************************************************************
Sweet...I'll give that a try
________________________________
From: maximomaniac <nishantnageshwar@gmail.com>
To: MAXIMO@yahoogroups.com
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com, John Ballnik <jballnik@...> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
It didn't work for me
-> I tried leaving it blank, Error message = Revisionnum must have a number
-> I tried entering null, Error Message = Revision number cannot be null, must be an integer
-> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
Do I have to set any inbound restrictions?
________________________________
From: maximomaniac <nishantnageshwar@gmail.com>
To: MAXIMO@yahoogroups.com
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com, John Ballnik <jballnik@...> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
If you pass it and want Maximo to assign it automatically you will probably have to exclude the field on the inbound transaction.
R/
Will
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
Sent: Tuesday, July 30, 2013 2:03 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
It didn't work for me
-> I tried leaving it blank, Error message = Revisionnum must have a number
-> I tried entering null, Error Message = Revision number cannot be null, must be an integer
-> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
Do I have to set any inbound restrictions?
________________________________
From: maximomaniac <nishantnageshwar@gmail.com<mailto:nishantnageshwar%40gmail.com>>
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@...<mailto:jballnik@...>> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
But if I exclude it, how would Maxim know to create a new revision?
________________________________
From: Will Hampton <will.hampton@exxtremeconsulting.com>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Sent: Tuesday, July 30, 2013 12:46 PM
Subject: RE: [MAXIMO List] Re: Incoming MIF PO Revision object
If you pass it and want Maximo to assign it automatically you will probably have to exclude the field on the inbound transaction.
R/
Will
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
Sent: Tuesday, July 30, 2013 2:03 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
It didn't work for me
-> I tried leaving it blank, Error message = Revisionnum must have a number
-> I tried entering null, Error Message = Revision number cannot be null, must be an integer
-> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
Do I have to set any inbound restrictions?
________________________________
From: maximomaniac <nishantnageshwar@gmail.com<mailto:nishantnageshwar%40gmail.com>>
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@...<mailto:jballnik@...>> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
Here is my inbound message format for creating and updating PO:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:max="http://www.ibm.com/maximo">
<soap:Header/>
<soap:Body>
<max:SyncMEM_PO creationDateTime="?" baseLanguage="EN" transLanguage="EN" messageID="?" maximoVersion="?" xmlns:max="http://www.ibm.com/maximo">
<max:MEM_POSet>
<max:PO action="AddChange" relationship="?" deleteForInsert="?" transLanguage="EN">
<max:MAXINTERRORMSG>SAMPLE TEXT</max:MAXINTERRORMSG>
<max:CURRENCYCODE changed="?">KRW</max:CURRENCYCODE>
<max:DESCRIPTION changed="?">PO FROM SAP</max:DESCRIPTION>
<max:EXCHANGERATE changed="?">1.00000</max:EXCHANGERATE>
<max:LANGCODE changed="?">EN</max:LANGCODE>
<max:PONUM changed="?">12324</max:PONUM>
<max:POTYPE changed="?">STD</max:POTYPE>
<max:REVCOMMENTS changed="?">Updates from SAP</max:REVCOMMENTS>
<max:SITEID changed="?">0375</max:SITEID>
<max:STATUS maxvalue="?" changed="?">APPR</max:STATUS>
<max:VENDOR changed="?">123082</max:VENDOR>
<max:POLINE action="AddChange" relationship="?" deleteForInsert="?">
<max:DESCRIPTION changed="?">BELT TIMING R95-0003-7 210L100</max:DESCRIPTION>
<max:ENTERBY changed="?">MXINTADM</max:ENTERBY>
<max:CONVERSION changed="?">1</max:CONVERSION>
<max:UNITCOST changed="?">1</max:UNITCOST>
<max:ITEMNUM changed="?">000000000012000367</max:ITEMNUM>
<max:LINETYPE changed="?">ITEM</max:LINETYPE>
<max:ORDERQTY changed="?">20.000</max:ORDERQTY>
<max:ORDERUNIT changed="?">EA</max:ORDERUNIT>
<max:POLINENUM changed="?">1</max:POLINENUM>
<max:REFWO changed="?"/>
<max:VENDELIVERYDATE changed="?">2013-07-20</max:VENDELIVERYDATE>
<max:STORELOC changed="?">1000</max:STORELOC>
</max:POLINE>
</max:PO>
</max:MEM_POSet>
</max:SyncMEM_PO>
</soap:Body>
</soap:Envelope>
Maximo knows it by action AddChange where PONUM is the key. if PONUM exist, it will try to change the PO and in 7.5 will create new revision.
--- In MAXIMO@yahoogroups.com, John Ballnik <jballnik@...> wrote:
>
> But if I exclude it, how would Maxim know to create a new revision?
>
>
>
>
> ________________________________
> From: Will Hampton <will.hampton@...>
> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> Sent: Tuesday, July 30, 2013 12:46 PM
> Subject: RE: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> Â
> If you pass it and want Maximo to assign it automatically you will probably have to exclude the field on the inbound transaction.
>
> R/
> Will
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
> Sent: Tuesday, July 30, 2013 2:03 PM
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> It didn't work for me
>
> -> I tried leaving it blank, Error message = Revisionnum must have a number
>
> -> I tried entering null, Error Message = Revision number cannot be null, must be an integer
>
> -> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
>
> Do I have to set any inbound restrictions?
>
> ________________________________
> From: maximomaniac <nishantnageshwar@...<mailto:nishantnageshwar%40gmail.com>>
> To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> Sent: Monday, July 29, 2013 6:40 PM
> Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> I recently worked on this and here is the solution:
> -Include Rev number as a attribute in MIF PO object structure.
> -Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
> -Maximo will automatically change the status of previuos version to REVISD.
>
> --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@<mailto:jballnik@>> wrote:
> >
> > Hey Gang,
> >
> > We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
> >
> > 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> > 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
> >
> > Just curious if anyone has gotten this to work and if there is a clean way of doing it.
> >
> > thanks,
> > John B
> >
> >
> >
>
>
>
>
>
>
>
>
>
>
>
Is your inbound processing class psdi.iface.app.po.MaxPOProcess ?
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
Sent: 30 July 2013 20:03
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
It didn't work for me
-> I tried leaving it blank, Error message = Revisionnum must have a number
-> I tried entering null, Error Message = Revision number cannot be null, must be an integer
-> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
Do I have to set any inbound restrictions?
________________________________
From: maximomaniac <nishantnageshwar@gmail.com<mailto:nishantnageshwar%40gmail.com>>
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@...<mailto:jballnik@...>> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
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.
**************************************************************************************************************
Got it working...thanks!
Just make sure to include the REVCOMMENTS field and it works.
________________________________
From: Ian Wright <ian.wright@gdfsuezep.co.uk>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Sent: Wednesday, July 31, 2013 12:07 AM
Subject: RE: [MAXIMO List] Re: Incoming MIF PO Revision object
Is your inbound processing class psdi.iface.app.po.MaxPOProcess ?
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
Sent: 30 July 2013 20:03
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
It didn't work for me
-> I tried leaving it blank, Error message = Revisionnum must have a number
-> I tried entering null, Error Message = Revision number cannot be null, must be an integer
-> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
Do I have to set any inbound restrictions?
________________________________
From: maximomaniac <nishantnageshwar@gmail.com<mailto:nishantnageshwar%40gmail.com>>
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Sent: Monday, July 29, 2013 6:40 PM
Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
I recently worked on this and here is the solution:
-Include Rev number as a attribute in MIF PO object structure.
-Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
-Maximo will automatically change the status of previuos version to REVISD.
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@...<mailto:jballnik@...>> wrote:
>
> Hey Gang,
>
> We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
>
> 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
>
> Just curious if anyone has gotten this to work and if there is a clean way of doing it.
>
> thanks,
> John B
>
>
>
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.
**************************************************************************************************************
Good to hear that.
Let me know if you face any issue in Receiving/Invoices which is next step to PO.
-Nishant N
--- In MAXIMO@yahoogroups.com, John Ballnik <jballnik@...> wrote:
>
> Got it working...thanks!
>
> Just make sure to include the REVCOMMENTS field and it works.
>
>
>
>
> ________________________________
> From: Ian Wright <ian.wright@...>
> To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
> Sent: Wednesday, July 31, 2013 12:07 AM
> Subject: RE: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> Â
> Is your inbound processing class psdi.iface.app.po.MaxPOProcess ?
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of John Ballnik
> Sent: 30 July 2013 20:03
> To: MAXIMO@yahoogroups.com
> Subject: Re: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> It didn't work for me
>
> -> I tried leaving it blank, Error message = Revisionnum must have a number
>
> -> I tried entering null, Error Message = Revision number cannot be null, must be an integer
>
> -> I tried entering the current REV number and new status, Error Message = PO cannot be change to <status>
>
> Do I have to set any inbound restrictions?
>
> ________________________________
> From: maximomaniac <nishantnageshwar@...<mailto:nishantnageshwar%40gmail.com>>
> To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> Sent: Monday, July 29, 2013 6:40 PM
> Subject: [MAXIMO List] Re: Incoming MIF PO Revision object
>
>
>
> I recently worked on this and here is the solution:
> -Include Rev number as a attribute in MIF PO object structure.
> -Pass the value as null, maximo will automatically assign the next rev number to every new incoming transaction.
> -Maximo will automatically change the status of previuos version to REVISD.
>
> --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, John Ballnik <jballnik@<mailto:jballnik@>> wrote:
> >
> > Hey Gang,
> >
> > We are incorporating the new features of 7.5 into our PO interface. It looks like the incoming message has to include the revision number if I want a new revision created, correct? But a couple of questions/observations
> >
> > 1) What if I don't know the revision number? Is there a way to tell the MIF just to create a new revision?
> > 2) During the testing and including the revision number in the incoming message, a revision (1) was created but revision (0) stayed at a status of APPR. When I tried to revise that PO, I got an error saying it is in a status of PNDREV. So it would appear that the revision took but the status does not reflect that.
> >
> > Just curious if anyone has gotten this to work and if there is a clean way of doing it.
> >
> > thanks,
> > John B
> >
> >
> >
>
>
>
>
> 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.
> **************************************************************************************************************
>
>
>
>
>
>
>
>
>