IV82632: MAXIMO TELEMATICS(TR)CREATES DUPLIATE WORKORDERS EVEN WITH "PREVENT DUPLICATE WORK ORDERS" OPTION SELECTED

APAR status

• Closed as program error.

Error description

• Maximo Transportation Telematics(tr)creates dupliate
  workorder(s) even with "Prevent Duplicate Work Orders" option
  selected
  
  In The Telematrics Import Setup > a listing of Workorders in the
  "Work Order Statuses That Can Prevent Work Order Duplication"
  are set and the codes(tr) action is set "Prevent Duplicate
  Wororders" yet duplicate workorders are still getting created
  
  
  Action Taken:
  Tested importing and processing of the Telematics data and was
  able to reproduce the problem the client has reported that the
  even though  in the Organziations(tr) >Transportation options >
  Telematics Setup >Workorder Status that can prevent workorder
  duplication > values are set  along with Data Import(tr) >Codes
  (tr)  Telematics code > Action for Telematics Code >
  select"Prevent Duplicate Work Orders" does not appear to be
  reading the Workorder status setup  in the " Temematics
  Import Setup "Work Order STatus that can prevent Workorder
  Duplication"
  
  
  Reproduced in Maximo 7507 TR 751 , Maximo 7509 TR 751
  
  Steps to Reproduce
  1)create xml and xsd files  > load to directory on server
  machine example  created file called import.xml , and import.xsd
   file loaded to  c:\temp directory
  use Asset # 13143, 13144, 12510 - make sure all active
  in your xml file you will 3 assets to test will and the 4
  required
  fields.
  example:
  <RECORD>
              <ASSETNUM>13144</ASSETNUM>
              <CODEDATA>1700</CODEDATA>
              <TELECODE>CODE1</TELECODE>
              <READINGDATE>2016-02-12T09:30:40</READINGDATE>
  2)Organization (tr)> select EagleNA > select action >
  Transporation options >Telematics Import Setup
  3)Templates section >click new row
  4)Template = Test Template > Active > check Acitve > Default
  Site> Bedford  > XSD file location > c:\temp\import.xsd  >XML
  file location >
  c:\temp\impor.xml >Action on Import Complete = MOVE
  File location on completion  > c:\temp\complete
  5)Mappings for Template Test Template section > click new row
  6)Transaction Table Field > select Assestnum  > XML Eelement =
  select Assetnum
  7)click new row > Transaction Table Field > Select Codedata >
  XML Element = Codedata
  8)click new row > Transaction Table Fieldd > Select Telecode >
  XML  Element  = Telecode
  9)click new row > Transaction Table Field > Readingdate  >XML
  Element = Readingdate
  10) Workorder Statuses that can Prevent Work Order Duplication >
  click new row > Work Order Status = APPR
  11) click ok.
  12) Data Import (tr) > Telematics Code(tr) > click new row
  13)Telematics code = Code1 > description Code  telematics code 1
  14)Action for Telematics code1 > click new row
  15)Description =  Code 1 telematics  Test Template > Template
  field > Select Value > select Test Template (created in step #4)
   > Action > select  CREATEWO >  Type = FAULT > Type = CM >
  Prevent Duplicate Workorder > check
  16) Save record
  17)Data Import(tr) > Telematics Data Import (tr)
  18)select action > import telematics data > Template name = Test
  Template (created in step 4)> click ok
  19) Message received > BMXAL04151-Data has ben imported > click
  ok
  20)select action > Process telematics data > do not select run
  in background mode > click ok
  21) Message received > BMXAL04161- The transaction table has
  been processed
  22)Workorder Tracking (tr) > search for assets loaded example
  asset 13144
  23) select Workorder generated > change status to APPR, repeate
  for all the assets you have loaded.  in test file loaded 3
  assets 13143,13144, and 12510 - changed all 3 workorders
  generated to APPR (note this is the status that is setup to
  prevent duplicate workorders)
  25)Data Import > Telematics Code(tr) > Code1> expand Action
  section
  26)Action section> uncheck "Prevent Dupliate Wokorder"
  27)Save record.
  28)Now update xml spread sheet to imported again.
  29)from the c:\temp\complete directory move completed import.xml
  file  back to  c:\temp directory.
  30) rename file back to import , now edit import.xml file  and
  change the readingdate  and codedata  > and Save file
  example:
  <RECORD>
              <ASSETNUM>13144</ASSETNUM>
              <CODEDATA>1800</CODEDATA>
              <TELECODE>CODE1</TELECODE>
              <READINGDATE>2016-02-13T09:30:40</READINGDATE>
  31)Data Import(tr) > Telematics Data Import (tr)
  32)select action > import telematics data > Template name = Test
  Template (created in step 4)> click ok
  33) Message received > BMXAL04151-Data has ben imported > click
  ok
  30)select action > Process telematics data > do not select run
  in
  background mode > click ok
  34) Message received > BMXAL04161- The transaction table has
  been
  processed
  35)Workorder Tracking (tr) > search for assets loaded example
  asset
  13144 > note you will now see 1st workorder in APPR status and
  new
  (2nd) workorder in WAPPR status - this is expected because the
  Codes(tr) action
  "Prevent Duplicate Workorder" was unchecked.
  36)Data Import > Telematics Code(tr) > Code1> expand Action
  section
  37)Action section> check "Prevent Dupliate Wokorder"
  38)Save record.
  39)Workorder Tacking >select last Workorders generated > change
  status to Closed, repeat for all
  the assets you have loaded.  in test file loaded 3 assets
  13143,
  13144, and 12510 - change all 3 last workorders generated to
  Closed.
  You will still have the 1st workorders generated from Step#22
  in APPR status.
  40)Now update xml spread sheet to imported again.
  41)from the c:\temp\complete directory move completed import.xml
  file
  back to  c:\temp directory.
  42)rename file back to import , now edit import.xml file  and
  change
  the readingdate  and codedata  > and Save file
  example:
  <RECORD>
              <ASSETNUM>13144</ASSETNUM>
              <CODEDATA>1800</CODEDATA>
              <TELECODE>CODE1</TELECODE>
              <READINGDATE>2016-02-13T09:30:40</READINGDATE>
  43)Data Import(tr) > Telematics Data Import (tr)
  44)select action > import telematics data > Template name = Test
  Template (created in step 4)> click ok
  45) Message received > BMXAL04151-Data has ben imported > click
  ok
  46)select action > Process telematics data > do not select run
  in background mode > click ok
  47) Message received > BMXAL04161- The transaction table has
  been processed
  48)Workorder Tracking (tr) > search for assets loaded example
  asset 13144
  49)You will now see the orig Workers created from step#22 in
  APPR status and now you have new workorder(s)  created in WAPPR
  status which should not have been  created since the "Prevent
  Duplicate Wokroder" option has been "re-checked"  on the
  Codes(tr) action.
  
  This is incorrect - Maximo should be reading the Codes(tr)
  Action "Prevent Duplicate Workorder" option that has been
  rechecked  however what appears to  happen if at any point in
  the Telematices import/process function the "Prevent Duplicate
  Workorder" option is unchecked and import/process is run without
  it checked creating duplicate workorders when the the option is
  rechecked Maximo ignores that "prevent dupliate workorder" flag.
  
  
  If the "Prevent Duplicate Workorder" option is set from the
  start of the process and never unchecked
  then it works as it should, but it the process runs and the flag
  is unchecked at the start or after 2 or 3 runs
  of the process then Maximo does not see/read the "prevent
  duplicate workorder" option anymore
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * none                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * MAXIMO TELEMATICS(TR)CREATES DUPLIATE WORKORDERSEVEN WITH    *
  * "PREVENT DUPLICATE WORK ORDERS" OPTION SELECTED              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * none                                                         *
  ****************************************************************
  

Problem conclusion

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:

Fix information

• Fixed component name

  MX TRANSPORTATI

• Fixed component ID

  5724R5500

Applicable component levels

• R751 PSY

     UP