IV99595: USING MIF NEW CLASSIFICATION AND ATTRIBUTES MUST BE IMPORTED TWICE WHEN CLASSIFICATION IS UPDATED AND ATTRIBUTES ARE SAME,

APAR status

• Closed as program error.

Error description

• Using MIF, new classification and attributes must be sent
  twice if existing classification is changed
  On the first import the classification changes, but the
  attributes are
  cleared out
  On the second import the attributes are inserted
  
  Steps to reproduce:
  1. goto Integration > Object structures
  2. duplicate MXOPERLOC and name it KLOPERLOC
  3, add it to enterprise services and external systems
  4. create two classifications
  DPOLE  Distribution Pole - attributes MATERIAL and HEIGHT
  TPOLE  Transmission Pole - attributes MATERIAL and HEIGHT
  5. create operating location, K1 with classification TPOLE
  6. import the following xml
  <?xml version="1.0" encoding="UTF-8"?>
  <SyncKLOPERLOC xmlns="http://www.ibm.com/maximo"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <KLOPERLOCSet>
     <LOCATIONS >
       <LOCATION>K1</LOCATION>
       <SITEID>BEDFORD</SITEID>
       <HIERARCHYPATH>DPOLE</HIERARCHYPATH>
       <LOCATIONSPEC>
         <ALNVALUE>BRASS</ALNVALUE>
         <ASSETATTRID>MATERIAL</ASSETATTRID>
       </LOCATIONSPEC>
       <LOCATIONSPEC>
         <NUMVALUE>50</NUMVALUE>
         <ASSETATTRID>HEIGHT</ASSETATTRID>
       </LOCATIONSPEC>
     </LOCATIONS>
  </KLOPERLOCSet>
  </SyncKLOPERLOC>
  
  7. Note that classification changes and description changes, but
  attributes are now missing
  8. Import the same xml again, and attributes are now added
  

Local fix

• Import twice.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo MIF users who import Locations with location          *
  * specification attributes that contain common attributes.     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Locations specifications are not created when user use MIF   *
  * import of location with locationspec records. This does not  *
  * happen using the Locations UI.  It happens in MIF when the   *
  * two classifications contain common attributes.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Import the second time.                                      *
  ****************************************************************
  

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.6.0.9 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

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels

• R760 PSY

     UP