APAR status
Closed as program error.
Error description
1. Login to Maximo. 2. Go to Assets --> Location --> Create new Location DECOM Type : operating Status - DECOMMISSIONED 3. Save this record 4. Go to Work Order Tracking --> Create New WO 5. Go to Location field and type DECOM. - Maximo throws an error message saying DECOM is not a valid Location. - User cannot enter this location. 6. Go to Service Desk --> Service Requests --> Create New SR. 7. Go to Location field and type DECOM - Maximo accepts this location even though it is decommissioned - You can also save this SR record with this decommissioned location. SR application should behave exactly like the WO Tracking application and should display a similar error message when trying to enter a decommissioned location.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * yes * **************************************************************** * PROBLEM DESCRIPTION: * * Allowed decommissioned locations to be associated with a * * Service Request if entered manually rather than selected * * from the list. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fixed in 7.6.0.6 and 7.6.0.3 and future releases
Temporary fix
Comments
APAR Information
APAR number
IV90556
Reported component name
WORK ORDERS
Reported component ID
5724R46WO
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-09
Closed date
2017-02-06
Last modified date
2017-02-06
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
WORK ORDERS
Fixed component ID
5724R46WO
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPPU","label":"Work Order Tracking"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
06 February 2017