Maximo Inventory Related Terminology

Safety Stock: This is the minimum stock balance that you want to have on hand at all times. The actual value will be heavily based on how critical the inventory item is to your operation.


Reorder Point (ROP): Reorder point is the balance level at which you want your inventory reorder to take place for the given item. The calculation is a forecast of demand over lead time plus a calculation of safety stock.

The ROP is used to trigger the reorder process for the item based on the following calculation:

Available Balance + Stock on Order =< (Equal to or less than)

(Available balance is the current balance - reserved quantity (reserved quantity is the quantity on all approved WO's referencing that item in the given storeroom) - expired stock)
(Stock on order is the quantity on all PR's and PO's for that item at that storeroom where PO/PR status is not closed or cancelled)

Note that when the work order has the "Required by Date" populated for the item the reorder process will not reorder if the SYSDATE + LEADTIME < REQUIREDBYDATE.

Setting the ROP to 0 will still reorder the item if the Available Balance + Stock on Order drops to 0.

If you want to prevent the reorder routine from ordering an item you should classify it as a non-stocked item.


Economic Order Quantity (EOQ): From a Maximo reorder point of view, this is the quantity that will be reordered once the reorder process has been triggered for the item.

EOQ refers to the optimum ordering quantity to keep inventory investments to a minimum. In other words, smaller ordering quantities would keep the inventory down, but would generate higher costs alternatively larger ordering quantities keep costs down but increase the cost of keeping the item in stock.

Maximo: How to launch Workflow from pushbutton ?

Maximo: How to launch Workflow from pushbutton ?: This documentation provides instructions needed to add the "Route Workflow" functionality using Push Button, in your Maximo environment Res...

How to launch Workflow from pushbutton ?

This documentation provides instructions needed to add the "Route Workflow" functionality using Push Button, in your Maximo environment

Resolving the problem

In order to add the "Route Workflow" functionality using Push Button  In any application, the following steps are needed :

1. Backup Your XML.

2. Add push Button in desired section

3. Open The properties of Push Button

mxevent="ROUTEWF" and

value="SRFORUSER",

where SRFORUSER - name of your WF

Save record.

Set

How to change “Welcome Message On Start Center Navigation Bar”?

To change the message that appears within the Start Center, please do the following:

Go To àSystem Configuration à Platform Configuration à Database Configuration

Select Action – click on Messages – within the dialog box – click on the Filter hyperlink – within the Message Key – search for 'welcomeusername':


Change the Value. Within this example – the Value will be changed to 'Welcome to TEST server, {0}:

Sign Out – Close Browser – Sign back into Maximo – the following will appear:

How to change Maximo Login Message?

Changing the Maximo Login Message

Out of the box the following message appears at the Maximo 7.5 login screen:

“Welcome to Maximo”

To change this message, follow the below steps:

1.      Log into Maximo with Administrative Privellage  

2.      Follow the Path

3.      Go To à System Configuration àPlatform Configuration àDatabase Configuration

4.      From select Action Menu click on “Message” click on the filter hyperlink and Search ‘welcomemaximomessage’ and expand the entry:

5.      Within the ‘Value’ textbox – change the entry from ‘Welcome to Maximo’ to the desired message. In this example, it will be changed to ‘Maximo Test Server ’

6.      Sign Out of Maximo and confirm that the changes have taken effect.

Any new setting should be implemented and fully tested in a test environment before making these changes in your production environment.

BMXAA2333E - Please narrow your results down to a maximum of 200 rows to perform this action

Issue:  BMXAA2333E - Please narrow your results down to a maximum of 200 rows to perform this action.

When: When a query is executed in a Maximo application, and the results of that query are shown on the List page, there is a checkbox in the lower left corner of the form called 'Select Records' that allows you to select a number of records (checking the top box above the first record will enable you to select all of them).

If more than 200 records are displayed in the results set, the user receives the following message:

"Please narrow your results down to a maximum of 200 rows to perform this action".

Reason:  By default value of  webclient.maxselectrows = 200.

The issue was resolved with the following suggestion provided to the customer:

There is a way to change the out-of-the-box limit of 200 records.

1.      Navigate to the MAXIMO\applications\maximo\properties\ folder and open the webclient.properties file.  { This path differ from maximo version to version better search for “webclient.properties”}

2. Using your favorite text editor, open the webclient.properties file
3. Search for  “webclient.maxselectrows”

4.      Change the webclient.maxselectrows= property entry from 200 to the desired limit.

5.      Save and rebuild EAR files for the changes to take effect.

WARNING: Setting the limit to too high a value may result in performance issues.

Any new setting should be implemented and fully tested in a test environment before making these changes in your production environment.

***************

Steps to be followed in Maximo 7.5

1.  Login with  required administrative privilege
2.  Navigate system configuration à Platform configuration à system properties
3.   Search for “webclient.maxselectrows”
4.  Change the webclient.maxselectrows= property entry from 200 to the desired limit.
5. Save and Live refresh for the changes to take effect

APPR And INPRG Status In Work Order Tracking

Question

Is there a difference between "Approved" and "In Progress" status on a work order?

Answer

What Is The Difference Between Approved and In Progress Status In Work Order Tracking?

APPR (Approved) is intended to be used in a scenario whereby the Work Order is approved and it has not started yet. This also provides for the functionality of WMATL (Waiting On Material) status. The assumption, and basis for this business logic, is that the Approved Work Order is okay to be started, but it has not started yet. There could also be a scheduling situation with labor, which has prevented
this work from being started.

INPRG (In Progress) is considered to be a progression from Approved status. For example, once the material has arrived, the WMATL status gets relieved, and the work is now being done.
There is a slight variation to be aware of in the scenario of Work Orders that get generated from PMs. When PM Work Orders get generated, and if there are tasks on them which have Direct Issue materials required, and not available, then the status of the main Work Order will be WSCH (Waiting To Be Scheduled)

Subsequently, when a PM-generated Work Order is changed to APPROVED status, and if those materials are still not available, then the TASK Work Order(s) will get a status of WMATL while the main Work Order stays as APPR. In other words, some of the tasks cannot be started due to a material deficiency.

The intent of the logic described above is only applicable to Work Orders that get their Status
changed to Approved, and it will not prevent or interfere with Users manually or deliberately changing a Work Order status to In Progress. This is a vehicle to facilitate the tracking of certain business scenarios that require a distinction between Approved and In Progress status.

How to Change the Drilldown limit

Overview :The Location Drilldown in Enterprise Suite is configured to display only the first 50 children for a parent. This document provides instructions on how to change that limit.

The Drilldown is a very effective tool when used to search through a symmetrically shaped hierarchy. For, example, using a classic 1 to 7 hierarchy, where Locations in a hierarchy have an average of 7 children, a 7 level hierarchy will contain 135,000 Locations. In this case, Locations can be found very quickly using the Location drilldown with just a few mouse clicks and very little scrolling. If a hierarchy is structured such that some individual Locations have a great number of child Locations, however, it may be easier to search using the Select Location action. The Select Location dialog allows you to use filters to quickly find a Location by specifying information contained in the Location code, the Location name and the Organization and Site ID, or combinations thereof.

To make it more efficient to browse through a hierarchy in the Drilldown, Maximo allows you to set a limit on the number of children that are displayed in each level in the hierarchy. By default, this limit is set at 50, meaning that if you have a Location that has more than 50 children, when you click on the plus sign to display that Locations children, Maximo will display the first 50 children of the Location and then will display a message informing you that there are more children in the hierarchy than those that are displayed for that parent.

If you desire, you may change the limit on the number of children displayed for a Location or an Asset in the Drilldown dialog:
1. Go to the Application Designer application
2. Select the Action "Export System XML"
3. Highlight the line Library in the Export System XML dialog and click on the Export XML icon,.

4. Using the "save as" option, save two copies of this file. Name one of them library.xml and the other library.xml.bk, which will serve as a backup.
5. Open library.xml in a text editor
6. Find the string <tree relationship="LOCATIONS"
7. insert maxchildren="200" directly after it.

Note: this will change the display limit for Location children to 200. You may designate another limit by selecting another numeric value.

Note: You should find only one "non commented" occurrence of the string

<tree relationship="LOCATION"

The changed section of the library.xml file should look like the section below. The inserted string is shown in bold:

8. Find the string <tree relationship="ASSET"
9. insert maxchildren="500" directly after it.

Note: this will change the display limit for Asset children to 500. You may designate another limit by selecting another numeric value.

Note: You should find only one “non commented” occurrence of the string

<tree relationship="ASSET"
10. Save library.xml
11. On the Application Designer main tab, select the Import icon, and browse to the library.xml file that you have updated.

12. Click OK to import the file.

Error Message While Using Locations Drilldown (Maximo 7.5)

Procedure:

- Login to Maximo

- Go to System Configuration > Platform Configuration > Application Designer

- Select Action > Export System XML

- From Export System XML box, select LIBRARY and click on Export XML icon.

- The XML file opens up in an other browser session. Save it in to the disk. Save it again in an other location, so you are going to have a backup of your original LIBRARY.XML.

- Open the XML using a text editor.

- Search for id="locations_tree" or relationship="LOCATIONS"

- To set the limit to 500, insert the text maxchildren="500" after relationship="LOCATIONS"

- Now the xml should be like this:
<tree beanclass="psdi.webclient.beans.common.DrilldownTreeBean" checkfornewnodes="true" height="150" id="locations_tree" ignorestructurechange="true" orderby="location asc" relationship="LOCATIONS" maxchildren="500" selectfirstnode="true" width="500">

- Save.

- Go to Application Designer and click on Import Application Definition icon.  

- From Import Application Definition box, browse for the XML file you just made changes to.

- Click OK to import the file.