APAR status
Closed as program error.
Error description
Maximo 7.1.1.4 Mobile Maximo 7.1.1 On Mobile MaximoWO when you change the asset on the workorder in Mobile Maximo and then send the record back to Maximo. The asset and location update properly but the glaccount does not. I think this is more a CORE hotfix (to not provide a default behavior) than a mobile hotfix. In CORE Maximo Bring up a WAPPR WO and Modify the Asset, You receive these messages; First one is the following; BMXAA4722E - The specified asset is not in the current location. Do you want to update the location with this asset's location - BOSTON? If you do not want to apply changes to the location or asset, click Close. Then click on YES and receive the below one; BMXAA4510E - The location and asset combination you have entered would default a different GL account than is currently specified on the work order. Would you like to update the work orders GL account based on the new asset/location combination? Clicking Cancel will return you with no changes. If you click on YES it updates the GL Account and changes it, if Click NO it keeps the Same GL Account as it had before However, If the above is done within the Mobile Device the Messages do NOT appear and the GL does not get updated Internally, maximo checks if the user is interactive, in other words, is accessing the maximo from the webbrowser, before showing the messagebox. If it is not interactive, maximo does not show the messagebox, and also leave the GLAccount as is, and the mobile user is not interactive for maximo. That's why mobile does not change the gl account. This is a Maximo CORE issue and needs to be dealt within the CORe MAximo so that Mobile can work properly
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: ALL * **************************************************************** * PROBLEM DESCRIPTION: Maximo 7.1.1.4 * * * * Mobile Maximo 7.1.1 * * * * On Mobile MaximoWO when you change the * * asset on the workorder in * * * * Mobile * * * * Maximo and then send the record back to * * Maximo. * * * * The asset and location update properly * * but the glaccount does * * * * not. * * * * I think this is more a CORE hotfix (to * * not provide a default * * * * behavior) than a mobile hotfix. * * * * In CORE Maximo * * * * Bring up a WAPPR WO and Modify the * * Asset, * * * * You receive these messages; * * * * First one is the following; * * * * BMXAA4722E - The specified asset is not * * in the current location. * * * * Do you * * * * want to update the location with this * * asset's location - BOSTON? * * * * If you * * * * do not want to apply changes to the * * location or asset, click * * * * Close. * * * * Then click on YES and receive the below * * one; * * * * BMXAA4510E - The location and asset * * combination you have entered * * * * would * * * * default a different GL account than is * * currently specified on * * * * the work * * * * order. Would you like to update the * * work orders GL account based * * * * on the * * * * new asset/location combination? * * Clicking Cancel will return you * * * * with no * * * * changes. * * * * If you click on YES it updates the GL * * Account and changes it, if * * * * Click * * * * NO it keeps the Same GL Account as it * * had before * * * * However, If the above is done within * * the Mobile Device the * * * * Messages do NOT appear and the GL does * * not get updated * * * * Internally, maximo checks if the user * * is interactive, in other * * * * words, is accessing the maximo from the * * webbrowser, before * * * * showing the messagebox. * * * * If it is not interactive, maximo does * * not show the messagebox, * * * * and also leave the GLAccount as is, and * * the mobile user is not * * * * interactive for maximo. * * * * That's why mobile does not change the * * gl account. * * * * This is a Maximo CORE issue and needs * * to be dealt within the * * * * CORe MAximo so that Mobile can work * * properly * * * * LOCAL FIX: * * * * NONE * * * * * * * * * * * * Have Tallked to the following * * Recipients in regards to this issue * * * * * * * * * * * * Ricardo Lucio da Silva, Thadeu de Russo * * e Carmo and David Havican, if any * * furhter explanation is needed please * * contact them for any inquiries or mis * * understandings, * * * * * * * * * * * * Thanks, * * * * DP * * * **************************************************************** * RECOMMENDATION: * * * * * * * **************************************************************** GL ACCOUNT DOES NOT GET UPDATED ON WO WHEN ASSET IS MODIFIED FROM MOBILE
Problem conclusion
Fixed in code. The fix for this APAR is contained in the following maintenance package: | release\fix pack | REL 7.1.1.8 - BS
Temporary fix
Comments
APAR Information
APAR number
IZ77417
Reported component name
WORK ORDER TRAC
Reported component ID
5724R46WO
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-06-11
Closed date
2010-06-28
Last modified date
2010-06-28
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
WORK ORDER TRAC
Fixed component ID
5724R46WO
Applicable component levels
R711 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":"711","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
28 June 2010