APAR status
Closed as program error.
Error description
PROBLEM DESCRIPTION Customer recently applied 7612 Ifix 10 and while testing we found a scenario where the changes made in OOB is making Custom Automation Script fail. Automation Script is using getOwner method to identify who owns/will the WPMaterial record that is being add. Before Ifix, if taskid was changed on WPMaterial, then the getOwner method would return that as the owner. Now after Ifix, even after changing taskid, the Header is always the owner. This will cause Significant issue as we have lot of custom logic around this. Why isn't the MBO ownership changing with taskid ? STEPS TO REPRODUCE STEPS TO REPRODUCE: 1) Create a new Object Launch Point script for WPMATERIAL using Python language, at Save (), add and update actions: from psdi.util.logging import MXLoggerFactory logger = MXLoggerFactory.getLogger("maximo.script") x = "WPMATERIAL.DUPLICATE" owner = mbo.getOwner() wonum = owner.getString("WONUM") if owner is not None: logger.debug(x + ' **There is an owner for ' + mbo.getName() + ' and the owner is ' + mbo.getOwner().getName()) errorgroup = "mygroup" errorkey = x + " **There is an owner for " + mbo.getName() + " and the owner is " + mbo.getOwner().getName() + " and WONUM is " + wonum else: logger.debug(x + ' **There is NO OWNER ') errorgroup = "mygroup" errorkey = x + " **There is NO OWNER " 2) GO to WorkOrder Tracking and create a new WO = HEADWO. Add a new TASK ( TASK may be 10 ) In the plans tab, Add a new Material Record with no TASK, Save The warning will show up and WONUM is HEADWO, printed in the warning. mygroup#WPMATERIAL.DUPLICATE **There is an owner for WPMATERIAL and the owner is WORKORDER and WONUM is HEADWO This is working as expected 3) Still in the same HEADWO, In the plans tab, add a new Material line Set TASK = 10 Hit Save The warning will show up and WONUM is still HEADWO, printed in the warning. mygroup#WPMATERIAL.DUPLICATE **There is an owner for WPMATERIAL and the owner is WORKORDER and WONUM is HEADWO This is wrong since now the WPMATERIAL belongs to the TASK workorder. RESULTS Not working EXPECTED RESULTS Works PRODUCT VERSION Tivoli's process automation engine 7.6.1.2-IFIX20210625-1908
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * MAXIMO, ACM * **************************************************************** * PROBLEM DESCRIPTION: * * WPMATERIAL CREATION ON A TASK - GETOWNER() METHOD BEHAVIOR * * CHANGED * **************************************************************** This was caused by IV82863 (affects WPMaterial) and IJ28532 (affects WPService)
Problem conclusion
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 number
IJ35103
Reported component name
MAXIMO ASST MGM
Reported component ID
5724R46AM
Reported release
761
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-09-21
Closed date
2021-11-24
Last modified date
2021-11-24
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
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]
Document Information
Modified date:
25 November 2021