IV82863: Record is not getting saved for the robbery request

APAR status

• Closed as program error.

Error description

• PROBLEM: Record is not getting saved for the robbery request
  PERFORMANCE ISSUE: N/A
  STEPS TO REPRODUCE:
  replicated in maxdemo
  1.) Create a new workorder against an asset.
  2.) Go to Plan Tab, create a task
  add material against that task.
  3.) Check the robbery checkbox against the material
  robbery details section appears automatically
  Click New row to create a new record of robbery
  4.) Save the record.
  5.) After saving the record the record is not getting saved ,the
  details in the robbery section get's vanished.
  6.) Create and save the record again,The record get's saved for
  the next time.
  Note : Record is not getting saved only for the robbery request
  raised against the material mapped against task.
  CURRENT ERRONEOUS RESULT: robbery record should get saved the
  first time
  EXPECTED RESULT: 1.) Record is not getting saved against the
  robbery request for
  the first time, robbery section is getting vanished.
  2.) Record is even not getting saved in the database, row is not
  getting created in the database.
  ADDITIONAL INFO:
  ENVIRONMENT (SYSTEM INFO):  TPAE 7.5.0.7 IFIX 018
  Transportation 7.5.1
  ACM 7.5.1.1
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo with ACM enabled.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Robbery section was not save when ACM Robbery is checked on  *
  * the Material table window in the work order app.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * none                                                         *
  ****************************************************************
  

Problem conclusion

• This is fixed in code.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Interim Fix for Release 7.5.0.11 Product
  

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

  MX ASSET CONFIG

• Fixed component ID

  5724R4500

Applicable component levels

• R750 PSY

     UP