I'm looking at automation for our project management process which would include creating PO revisions for users. I see that on a PNDREV PO there are several fields in the PO line user interface that can't be changed, such as work order number and gl debit account. What are the business rules behind these restrictions? In other words, what data integrity problems would I encounter if I chose to alter one of those fields from an automation script on a PO revision? Thanks.

Bob

------------------------------
Robert Goff
------------------------------



#Maximo
#AssetandFacilitiesManagement
#MaximoEAM

Hi Robert,

How was the PO generated?  For example, if you planned direct issue items on a work order and a PR was generated to order those items for the work order and those PR lines were copied to the PO, you could be breaking that logic.  

Were there receipts against the PO?  There are limited revision options once a receipt is processed. 

I just tested a very simple PO revision where I generated the PO manually and entered a line item with charge to information of a work order.  I approved the PO.   I didn't process any receipts.  I then revised the PO and I was able to update the work order and GL Debit.  Likely there is logic based on the scenario to make those fields read-only as there would be downstream affects on transactions.

I attached a document that overviewed the PO Revision functionality when it was added in Maximo 7.5.

------------------------------
Lacey Radabaugh
Client Technical Professional
IBM
------------------------------

Original Message:
Sent: Tue May 26, 2020 12:13 PM
From: Robert Goff
Subject: PO Revision Business Rules

I'm looking at automation for our project management process which would include creating PO revisions for users. I see that on a PNDREV PO there are several fields in the PO line user interface that can't be changed, such as work order number and gl debit account. What are the business rules behind these restrictions? In other words, what data integrity problems would I encounter if I chose to alter one of those fields from an automation script on a PO revision? Thanks.

Bob

------------------------------
Robert Goff
------------------------------



#MaximoEAM
#Maximo
#AssetandFacilitiesManagement

Thank you, Lacey; that got me thinking in the right direction. I can see now that if there are returns or corrections to be made on receiving lines or invoices, having a different GL on the PO line than on the receipt will cause pain. Your response was helpful.

Bob

------------------------------
Robert Goff
------------------------------

Original Message:
Sent: Wed May 27, 2020 08:43 AM
From: Lacey Radabaugh
Subject: PO Revision Business Rules

Hi Robert,

How was the PO generated?  For example, if you planned direct issue items on a work order and a PR was generated to order those items for the work order and those PR lines were copied to the PO, you could be breaking that logic.  

Were there receipts against the PO?  There are limited revision options once a receipt is processed. 

I just tested a very simple PO revision where I generated the PO manually and entered a line item with charge to information of a work order.  I approved the PO.   I didn't process any receipts.  I then revised the PO and I was able to update the work order and GL Debit.  Likely there is logic based on the scenario to make those fields read-only as there would be downstream affects on transactions.

I attached a document that overviewed the PO Revision functionality when it was added in Maximo 7.5.

------------------------------
Lacey Radabaugh
Client Technical Professional
IBM

Original Message:
Sent: Tue May 26, 2020 12:13 PM
From: Robert Goff
Subject: PO Revision Business Rules

I'm looking at automation for our project management process which would include creating PO revisions for users. I see that on a PNDREV PO there are several fields in the PO line user interface that can't be changed, such as work order number and gl debit account. What are the business rules behind these restrictions? In other words, what data integrity problems would I encounter if I chose to alter one of those fields from an automation script on a PO revision? Thanks.

Bob

------------------------------
Robert Goff
------------------------------



#AssetandFacilitiesManagement
#MaximoEAM
#Maximo