Technical Blog Post
Abstract
EAM Corner: A user is unable to Cancel a Contract Revision with PNDREV status if a Open PO exists with APPR?.
Body
Welcome to the EAM Corner!!!!
My name is Ghazala and I work in level 2 support for IBM on the EAM product. This blog series will all be helpful tips, tricks and how-to's on Maximo EAM .
Be sure to follow me on DeveloperWorks ---------> Click here to follow me on DeveloperWorks!
Recently I've been working with a customer, who encountered an issue with a User not being able to cancel a Contract Revision which is on PNDREV
Status and not been approved yet. If any Revision of the Contract are linked with an open Purchase Order PO(s) with APPR status.
Following steps have been used to reproduce the issue:
1.Go to > Purchasing > Purchase Requisitions
Create New PR 1031
Priority 1
Currency USD
Click on the PR Lines Tab
Click New Row
Line Type Service - Line Cost 10000 (leave all other fields empty)
Save - Approve
Create Contract Test 1
PR is now in Closed Status
2.Go to > Contracts > Purchase Contracts - test1
Vendor: EMI - Emergency Maintenance Inc.
Click Properties Tab - Checkbox the Create Release Option
Select Action - Authorize Sites - Bedford
Change Status - Approved
Select Action - Create Release PO "Zara"
3.Go to > Purchasing > Purchase Orders - "Zara"
Change Status - Approved
4.Go to > Contracts > Purchase Contracts - 1031
Select Action - Revise Contract
The System displays error BMXAA6146W.
This contract revision is currently referenced on one or more open purchasing documents. Documents PO "zara" currently reference
this contract revision. Do you want to proceed? Try to change status BMXAA4042E - The status cannot be changed for the selected records.
Resolving the problem:
Cancelling a Contract does indeed check for any PO references (POs in status APPR or INPRG) against any and all revisions of that Contract; if any are found, the Contract may not be cancelled. This is intended, as Maximo has no way of determining the validity of POs referencing previous Contract revisions. Some open POs referencing previous
Contract revisions may have been unaffected by the revision, and may still be valid.
In the client's case, it is suggested that the referenced PO be either closed or cancelled so that the Contract may be cancelled.
Currently, when a Contract is revised, the previous revision will remain in APPR until the current revision is moved from PNDREV. The current business logic does not consider that the user may want to discard the pending revision; as a Contract in PNDREV cannot be referenced on a PO, this should be allowed.
An APAR IV84104 has been raised to address this issue!
Thanks for reading, be sure to look out for my next installment.
UID
ibm11131177