IV13219: BMXAA0031E: OBJECT SR IS READ-ONLY. CHECK BUSINESS RULES OF MBO OR MBOSET OBJECT.

APAR status

• Closed as program error.

Error description

• Maximo 7.5.0.0
  
  Steps to Replicate:
  
  Go TO WORKORDERS> Work Order Tracking> Service Request (oil)
  
  Create new SR
  Fill in all fields, they have a added field which is linked to a
  DOMAIN
  they created
  Save
  Create WO from Action Menu
  Go to WO and Change status to COMP
  SR is in RESOLVED Status at this point
  Change status of WO to CLOSE
  this is where the Error comes up
  
  Error message - Portuguese:
  ---------------------------
  BMXAA0031E - O objeto SR ﾂ somente leitura.  Verifique as regras
  de
  negﾢcios do objeto MBO ou MBOSET.
  
  Error message - English:
  ------------------------
  BMXAA0031E: Object SR is read-only. Check business rules of MBO
  or
  MBOSET object.
  
  This problem appears to be Oil & Gas related.
  
  The following appears to be the problem...
  
  Reviewing the SystemOut.log file that was attached in the PMR
  you will
  notice the stacktrace error that gets created.  The word doc
  attached to
  the PMR shows that they are closing the WORK ORDER, not
  COMPLETING the
  work
  order.  Once the work order is closed the SR gets closed,  thus
  becoming
  readonly.
  
  STEPS & EXPLANATION
  1. Save Occurs as soon as the work order status is changed to
  CLOSED.
  2. When the Work Order status is changed to CLOSED it then
  changes the
  SR to RESOLVED a.k.a CLOSED as well,  which makes it readonly.
  3. Then you will see that within the
  PlusGFldTicketPlusGNonConAccept
  (oil and gas related) file they are attempting to set a value to
  null in
  the setAcceptByField method.  When the OIL and GAS file attempts
  to set
  the value to null on a READ ONLY SR object,  the error is
  thrown.
  
  
  STACKTRACE from SystemOut.log
  psdi.util.MXAccessException: BMXAA0031E - O objeto SR ￇﾸ somente
  leitura. Verifique as regras de negￇcios do objeto MBO ou
  MBOSET.
     at psdi.mbo.Mbo.checkFieldAccess(Mbo.java:5455)
     at psdi.mbo.MboValue.checkFieldAccess(MboValue.java:2225)
     at psdi.mbo.MboValue.setValueNull(MboValue.java:478)
     at psdi.mbo.MboValue.setValueNull(MboValue.java:486)
     at
  psdi.plusg.app.ticket.PlusGFldTicketPlusGNonConAccept.setAcceptB
  yField(P
  lusGFldTicketPlusGNonConAccept.java:73)
     at
  psdi.plusg.app.ticket.PlusGFldTicketPlusGNonConAccept.initValue(
  PlusGFld
  TicketPlusGNonConAccept.java:46)
     at psdi.mbo.MboValue.initValue(MboValue.java:401)
     at psdi.mbo.MboValue.isNull(MboValue.java:504)
     at psdi.mbo.Mbo.validate(Mbo.java:4116)
     at psdi.mbo.MboSet.validate(MboSet.java:4855)
     at psdi.mbo.MboSet.validateTransaction(MboSet.java:7225)
     at
  psdi.txn.MXTransactionImpl.validateTransaction(MXTransactionImpl
  .java:37
  5)
     at
  psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.jav
  a:207)
     at
  psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
     at psdi.mbo.MboSet.save(MboSet.java:6912)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All oil and gas users                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: An error happens when a Work Order      *
  *                      created from a Service Request is       *
  *                      changed to closed status.               *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  An error happens when a Work Order created from a Service
  Request is changed to closed status.
  

Problem conclusion

• One of the field classes was setting some values in the read
  only object without checking the record status. This field
  class was changed to set the value regardless the read only
  status of the records.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | HABSHAN
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO OIL & GA

• Fixed component ID

  5724R5400

Applicable component levels

• R750 PSY

     UP