BMXAA3456E error is displayed while trying to run reorder manually or via crontask. Diagnosing the problem: Run the following query, replacing the XXXX by the Storeroom in question: SELECT * FROM REORDERMUTEX WHERE LOCATION='XXXX'; Resolving the problem: If that query returns any row, then delete the row by running: DELETE FROM REORDERMUTEX WHERE LOCATION='XXXX'; The REORDERMUTEX table is a locking mechanism to make sure no two users are running a MR, Direct Issue or Storeroom Reorder at the same time.... [More]
Java Security warning can continue even after applying Maximo Interim Fix containing newly signed applets as indicated in http://www-01.ibm.com/support/docview.wss?uid=swg21972870 . Solution: 1) Delete the WebSphere temporary file caches (temp and tranlog) following the procedure described in http://www-01.ibm.com/support/docview.wss?uid=swg21660821 2) Delete the web browser cache (internet temporary files and cookies) from every computer that accesses Maximo.
In the past the question has come up often regarding the best way to configure the error queue exception destination for the inbound continuous queue (CQINBD) and the inbound continuous error queue (CQINBDERR) used by the Maximo Integration Framework. There are many ways these exception destinations can be configured, and it really depends on how the Ingration Framework system is being used and what the preferred behavior would be. In most previous documents, my instructions stated specifying the name of the error queue CQINBDERR in the... [More]
It was recently brought to my attention by a customer who installed an Interim Fix for Maximo 126.96.36.199 that the Maximo Asset Management version number had been updated from Maximo 188.8.131.52 to 184.108.40.206. This was a cause for alarm which in term had them contact IBM to confirm the version of the application and look in to why it was showing incorrectly. After reviewing the system information which looked similar to the following, but not the same. (I don't have an environment with this versioning issue). Version Tivoli's... [More]
Hi, I just got 220.127.116.11 downloaded. It's really nice to find a comprehensive read me file that comes with the new fix pack. The read me contains info about the new work centers (with links that take me to some YouTube demo recording, steps for Watson integration, knowledge center for the work center users), new functionality by applications, installation steps with notes to use UI configuration tool to enable 18.104.22.168 work centers and a list of fixes by applications. I've attached the read me file here for... [More]
When you want to add a constraint between work orders the constraint icon from the toolbar is selected. The cross is visible in the Gantt view. Typically this is where work orders have constraints associated. However the constraint cannot be added between the parent-child work orders. Why would this be the case? The data retrieved by Scheduler needs to include all the components it requires. The parents also need to be displayed. Otherwise, it is not able to work with them as the underlying data is not... [More]
Eventually the Long Description field can be grayed out in all applications while using Maximo in Internet Explorer. Turn on the Compatibility View in Internet Explorer following the steps below: 1. Open Internet Explorer. 2. Go to Tools > Compatibility View Settings. 3. From Compatibility View Settings dialog: 3.1. Enter the Maximo URL in the Add This Website field. 3.2. Click on Add. 3.3. Click on Close.
Maximo SysAdm Times Welcome to the Sysadm Times !!!!!! LABTRANS.STARTDATE is non-persistent in Maximo 7.6 LABTRANS.STARTDATE field is not persistent in 22.214.171.124. Also the java class associated to this field is different, it's changed to psdi.app.labor.virtual.FldLabTransStartDateNP however in 7.5 it was psdi.app.labor.FldLabTransStartDate. In 7.6.x Go to Database Configuration --> LABTRANS -->STARTDATE is non-persistent and the java class associated to this field is psdi.app.labor.virtual.FldLabTransStartDateNP ... [More]
Transferring 100 Items on a 1/3 Conversion Should Not Mean That You Receive 99 Back When there is a conversion factor between two storerooms and the conversion is 1/3 units the consequence can be that after sending 100 items and return them, only 99 are returned with one lost. Understandably this happens because it is using a 1/3 conversion. This can be resolved by modifying the attribute Conversion value to have 4 decimal points instead of the out of the... [More]
Are you new to Maximo Spatial 7.6? No problem - Let's get started To get started, we will go through a few steps on how we can get your Spatial data set up to use Spatial 7.6. First task that I'll cover in this blog will refer to the creating the GIS Objects using the Feature Services. When using Spatial 7.6 - Creating GIS Objects is an important task to be able to get the full functionalities of Maximo Spatial. Creating the Objects used to be a tough task, but with Spatial 7.6 and Feature Services, it's actually very easy! Let me... [More]
Performance issue specifically when a field is entered that populates other fields. For example, in the Service Requests application after entering the Reported By it can take a few seconds to load the person details fields, such as Name, Phone, E-mail. Solution: 1. Go to Application Designer. 2. Bring up Service Requests application. 3. Go to the Service Request tab. 4. Right-click on Reported By field > Properties. 5. From the Text-box Properties dialog box, go to the Advanced tab. 6. Select the check-box "Always... [More]
I panicked. I could not find my popcorn. You know...the best popcorn in the whole wide world. Salty, sweet, full of crunch and at only 29.15 calories a cup...well...it just begs you to eat the whole bag all at once. As my stress levels rose in aisle 4 of my local supermarket, I lunged at the nearest stock boy and begged him to help me find the soul food of my existence. He casually rolled his eyes behind his head...and nonchalantly pointed to the center of the aisle.... directly in front of me. My... [More]
Some people might think that their Unit Cost field inside their reorder PR is being wrongly populated, when they could actually be looking at the wrong fields. After accessing the Inventory application, you'll see many cost fields in the first tab (Standard Cost, Average Cost, Last Receipt Cost), which aren't considered by Maximo whenever a reorder runs. If there is no primary vendor registered, the reordering process populates the Unit Cost from a vendor that is in the Reorder Details tab and, since it's an... [More]
In Maximo 7.6, the hover on the Asset field in the Service Requests application does not display the data if the Asset Status is Decommissioned. As a workaround, we need to add in RECHOVERS.XML a missing reference to Asset Relationship following the steps below: 1. Go to the Application Designer. 2. Select Action > Export System XML. 3. From the Export System XML dialog, select RECHOVERS and click on the Export XML icon. 4. Edit RECHOVERS.XML, changing the line below from: <recordhover id="asset_recordhover"> to: ... [More]