IJ42077: MAXIMO MOBILE BAD QUERY FOR MXAPIINVBAL OBJECT STRUCTURE

APAR status

• Closed as program error.

Error description

• Steps to recreate in a demo system:
  1) Update your user record to have a mismatch between your
  default insert site and your storeroom site (IE BEDFORD for
  default insert site and NASHUA for storeroom site)
  2) In the Technician web application (it's easiest to show here
  but would also be replicated on a mobile device if first run),
  try to issue the item 11406. This exists in the CENTRAL
  storeroom in bin A-5-6. The storeroom will fill in but you'll
  see the bin is null when you have a mismatch between storeroom
  site and default insert site
  3) If you try to issue the item, it will throw an error because
  it doesn't exist in a null bin.
  
  Maximo Mobile utilizes the object structure query
  ACTIVEITEMSITE on MXAPIINVBAL for displaying bins when issuing
  items. The query out of box is as follows:
  
  siteid = (select storeroomsite from maxuser where userid =
  :USER) and itemnum in (select itemnum from item where status in
  (select value from synonymdomain where domainid='ITEMSTATUS' and
  maxvalue='ACTIVE'))
  
  There are multiple issues with this query. The first is we're
  utilizing the storeroomsite on maxuser instead of defsite. Every
  other query (work orders, inventory, assets, locations, etc.)
  utilize the default insert site. This could cause the
  application to download all the data for BEDFORD but then for
  INVBALANCES it could download the data for NASHUA site for
  example which wouldn't be usable.
  
  The second is we're looking at the item record to see if that
  status is ACTIVE. But items can be made obsolete at an inventory
  level while remaining active at an ITEM level. If it's obsolete
  at the inventory level we shouldn't download them. Even if ITEM
  was the desired object, this query was written with the
  assumption that an itemnum is unique but it is not. An item can
  exist in multiple sets spread across organizations.
  
  
  Third is we're only looking for ACTIVE items but we can issue
  items in a PENDOBS status. Our inventory query (SHOWINVENTORY on
  MXAPIINVENTORY) will display PENDOBS items so it's possible for
  us to have selected a storeroom that does not allow us to select
  a bin.
  
  I believe our query should be this instead:
  
  siteid = (select defsite from maxuser where userid = :USER) and
  exists (select 1 from inventory where
  inventory.itemnum=invbalances.itemnum and
  inventory.location=invbalances.location and
  inventory.siteid=invbalances.siteid and
  inventory.itemsetid=invbalances.itemsetid and status in
  (:&synonymlist&_itemstatus[ACTIVE,PENDOBS]))
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Mobile                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * MAXIMO MOBILE BAD QUERY FOR MXAPIINVBAL OBJECT STRUCTURE     *
  ****************************************************************
  

Problem conclusion

• The fix has been made.
  

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels