IJ28637: ADDING NEW LOTNUM VIA MIF REFOBJECT AND REFOBJECTID ARE NULL IN INVLIFOFIFOCOST TABLE

APAR status

• Closed as program error.

Error description

• If you try to do CURBALADJ via MIF it causes the "refobject"
  and "refobjectid" fields to be populated as NULL valuess in the
  INVLIFOFIFOCOST table where
  
  This error is invisible, however
  from this point, future transactions can have the wrong FIFO
  cost sent via integrations.
  
  We found that existing APAR
  IJ09158 addressed adjustment on existing invbalances records.
  This new APAR is intended to address adjustment in the new
  InvBalances sent in via MIF.
  
  STEPS TO REPRODUCE:
  
  1. Create a
  new Item in Item Master application:
  
  Itemtest
  Item Set:
  SET1
  Lot Type: LOT
  
  2. From ?More Actions? menu, select option
  ?Add Items to Storeroom? and enter following:
  
  Site:
  BEDFORD
  Storeroom: CENTRAL
  
  3. Click OK
  
  4. In Storeroom
  Information screen enter following:
  
  Item: Itemtest
  Issue Cost
  Type: FIFO
  Unit Cost: 10.00
  Default Bin: 10
  Current Balance:
  60
  Lot: ABC
  Issue Unit: EACH
  
  5. Click OK
  
  Dialog at top of
  screen appears briefly:
  
  BMXAA1938E - Items have been add to
  the storeroom.
  
  6. From ?More Actions? menu, select ?Change
  Status? and Set to ACTIVE
  
  7. Roll New Status to Organizations
  and Inventory? (ticked)
  
  8. Now Launch Postman API tool
  
  9.
  Enter the following as the POST call method:
  
  http://<maximo
  hostname>/meaweb/es/EXTSYS1/MXINVBALInterface
  
  10. Enter the
  XML in the Body where the CURBAL value has been changed from 60
  to 80 and LOTNUM has been changed from ABC to DEF:
  
  <?xml
  version=?1.0" encoding=?UTF-8??>
  <SyncMXINVBAL xmlns=?http://www
  .ibm.com/maximo>
  <MXINVBALSet>
  <INVBALANCES>
  <BINNUM>10</BINNUM>
  
  <CURBAL>80</CURBAL>
  <COSTDATE>2020-09-21T11:33:24+01:00</COSTDA
  TE>
  <ITEMNUM>ITEMTEST</ITEMNUM>
  <ITEMSETID>SET1</ITEMSETID>
  <LOC
  ATION>CENTRAL</LOCATION>
  <LOTNUM>DEF</LOTNUM>
  <ORGID>EAGLENA</OR
  GID>
  <RECONCILED>1</RECONCILED>
  <SITEID>BEDFORD</SITEID>
  <UNITCO
  ST>100</UNITCOST>
  </INVBALANCES>
  </MXINVBALSet>
  </SyncMXINVBAL>
  
  
  The POST response is successful resulting in following
  confirmation:
  
  <?xml version=?1.0?
  encoding=?UTF-8"?><SyncMXINVBALResponse
  xmlns=?http://www.ibm.com/maximo
  xmlns:xsi=?http://www.w3.org/2001/XMLSchema-instance
  creationDateTime=?2020-09-08T11:20:35+01:00? transLanguage=?EN?
  baseLanguage=?EN?
  messageID=?900115995604353296193"></SyncMXINVBALResponse>
  
  11.
  Run the following SQL queries:
  
  SELECT * FROM INVLIFOFIFOCOST
  WHERE ITEMNUM= ?ITEMTEST? AND location= ?CENTRAL?;
  
  Result:
  REFOBJECT AND REFOBJECTID ARE both returned with ?NULL?
  value
  
  SELECT * FROM INVTRANS WHERE ITEMNUM =
  ?ITEMTEST?
  
  Result:
  
  ITEMNUM: ITEMTEST
  LOTNUM: DEF
  INVTRANSID:
  1976056831
  
  LOTNUM was updated in MIF everytime it was changed
  it to a different value. This creates a new invbalances
  record.
  
  UNEXPECTED RESULTS:
  The REFOBJECT AND REFOBJECTID are
  NULL only when new LOTNUMs are added but existing LOTNUMs are
  successful in that both fields are populated with
  values.
  
  EXPECTED RESULTS:
  The REFOBJECT AND REFOBJECTID should
  be updated with values
  
  i.e.
  
  REFOBJECT: INVTRANS
  REFOBJECTID:
  1976056806
  
  Environment: Maximo 7.6.1.1
  

Local fix

• Dev to provide fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users who use MIF to send in new Invbalances records  *
  * for LIFO/FIFO cost type                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The REFOBJECT and REFOBJECTID are blank when users send in   *
  * new Invbalances records using MIF to perform balance         *
  * adjustment for LIFO/FIFO items.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

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