How I can close my requisitions automatically?

If you use the Desktop Requisition application and did a simple search on it, you may have noticed that you have a lot of useless requests there.

Well, requisitions can be closed in the following ways:                     
1) Direct Issue Materials that have a PO created. (line type = "Material" or "Service")                                               
This requisition will be closed when the PO is closed as well.         

2) Requisitions that have WO associated with them (Line type - other than "Material" or "Service")
These requisitions will be closed when the WO is closed as well        

3) You can create a new escalation or workflow to make the status change. You may change the requisition status to CLOSE or CANCEL
Regardless of what you choose to do this (WF or escalation), you must create a status change action for both.

Some Handy Links for Maximo 7.6

Hello again! This is a standalone blog entry, but I will also be adding it to a new blog post that is a compilation of the installation walk-through I posted in December 2014. Coming your way soon.

What to download for Maximo Asset Management

Maximo Upgrade Resources

Platform Configuration Matrix

Maximo Asset Management feature Packs

Version (links to technote)	Fix Central link
Maximo 7.6.0.1 Feature Pack	7.6.0.1-TIV-MAMMT-FP001
Maximo 7.6.0.2 Feature Pack	7.6.0.2-TIV-MAMMT-FP002
Maximo 7.6.0.3 Feature Pack	7.6.0.3-TIV-MAMMT-FP003
Maximo 7.6.0.4 Feature Pack	7.6.0.4-TIV-MAMMT-FP004
Maximo 7.6.0.5 Feature Pack	7.6.0.5-TIV-MAMMT-FP005
Maximo 7.6.0.6 Feature Pack	7.6.0.6-TIV-MAMMT-FP006
Maximo 7.6.0.7 Feature Pack	7.6.0.7-TIV-MAMMT-FP007
Maximo 7.6.0.8 Feature Pack	7.6.0.8-TIV-MAMMT-FP006

Installing a Feature Pack in Maximo 7.6

Installing an Interim Fix in Maximo 7.6

Maximo Best Practices for System Performance 7.6.x

Maximo Asset Management Wiki on developerWorks

Asset Management Forum on developerWorks

Maximo Request for Enhancement (RFE) Community

I will update this post periodically (and especially when new Feature Packs come out), so bookmark it!

Field required on Add to Storeroom screen

When you have an item record in Maximo, you have the option to Add Item to Storeroom, however, not every field is required.

For this example, we will use the IN20 field. If you would like to have the IN20 field in Inventory app to be required at the moment that you are adding the item to storeroom from Item app, here are some steps for you. 

All you have to do is this :

1. Go to Application Designer and search for ITEM app
2. Click on the Edit Dialogs button, on the toolbar
3. Select additemstostoreroom , which corresponds to Add Items to Storeroom
4. The dialog will appear for you to edit
5. Make sure you add a new table column for your required field (you can copy/paste an existing one and edit properties or add from Control Palette)
6. Change the properties of the new field to set :    Input Mode = Required
7. Save changes

Now, when you are in Item Master app and try to add an item to a Storeroom by using the Select Action > Add Items to Storeroom,  then Maximo will now require users to fill a value on that new field, which will be transferred over to Inventory app, preventing records with null values in that field.

See ya...

About grouping PM generation into to generate at a time

We were wondering how we could stagger PM generation within an organization across time zones and how we could further divide up the PM generation within a single large site. We would ideal like to be able to group our PM generation into even groups to generated at a certain hour within their time zone and use multiple Crontask to generate them. We can current only control the PM generation at the site configuration level. We seem to only be able to run all PMs with a single crontask with this configuration.

PMWoGenCronTask executes for all sites that the "user" has access to. When a PM Wogen crontask runs, it executes across all org/site combinations, which have automatic work order generation  for PM enabled and for which the where clause defined for the site returns records.

In that scenario, Maximo currently does not offer a functionality that allows you to do that, and some Maximo documents mention that it is important not to set up multiple instances which may contain the same sites within the users group, since this could cause errors when processing the records for generation. In other words, you cannot just set up multiple cron task instances to all process the same Site, or recordset as defined by the PM where clause.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM+Maximo+Asset+Management/page/Executing+PM+Wogen+Crontask+by+Site

However, if you still would like something to workaround this, I believe you can do the following :

NOTE :  This is just a try, I'm not sure if it will fully meet your needs, but feel free to try it on a TEST environment. :)

The PMWoGenCronTask could be divided across multiple JVMs by creating individual crontask instances, each assigned to an user restricted to see specific PM records from the same site. These specific users would have access to different PM records on the same site based on Security Restrictions / Object Restrictions defined in Security Groups app.
These users would be set as Run as User for each specific crontask instance for the PMWoGenCronTask.

In other words, you would create multiple administrative users that could run the PMWoGenCronTask, and each crontask instance would use a different value for Run As User.  The important, and implied detail, is that the crontask instances need to be selecting different record sets. 

See ya

BMXAA2256E - Field Signature Option is read-only.

You are trying to hide the following fields in Create Requisition (CREATEDR) application:
- Card Type
- Card#
- Card Verification Value
- Expiration Date

Listed below are the steps being taken in trying to achieve this task: 

1. Open CREATEDR in Application Designer
2. Click Select Action, Choose Add/Modify Signature Options
3. Create J_HIDECREDIT
4. Right-click Card Type Control, choose Properties
5. Click Advanced Tab
6. Select J_HIDECREDIT for Signature Option
7. Receive the following error: BMXAA2256E - Field Signature Option is read-only.
8. You receive the same error when you try to do the same through Configure Conditional Properties
9. You receive the same error when you try to do the same with the other fields   Card#, Card Verification Value, and Expiration Date.

It does appear these specific Control Properties are read-only and you have not found a way to change that.

You cannot modify some property settings in the fields from Charge Information section from CREATEDR app. You are trying to add a Signature Option on that, and getting : 

BMXAA2256E - Field Signature Option is read-only.

This is working as designed. The reason is because the worklog section is being included from the library.xml; the application designer does not support direct editing of those included
sections. You have to export the library.xml and edit it in there, then reimport the library.xml. Once you do that to include sigoption property to the desired controls in library.xml, and reimport library.xml into Application Designer, you will be able to hide the fields, after a Maximo server restart.

See ya

How to Delete Websphere Application Server Profile ?

How to Delete Websphere Application Server Profile ?

First list all profiles on a server:

List the profile using one of these commands

• Windows: was_install_dir\bin\manageprofiles.bat –listProfiles
• UNIX/Linux: was_install_dir/bin/manageprofiles.sh –listProfiles

Remove a WebSphere Application Server profile:

Delete the profile using one of these commands:

• On Windows: was_install_dir\bin\manageprofiles.bat –delete –profileName profile
• On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –delete –profileName profile

Ensure that references to the deleted profile are removed from the profile registry by running the following command:

• On Windows: was_install_dir\bin\manageprofiles.bat –validateAndUpdateRegistry
• On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –validateAndUpdateRegistry

Delete the profile directory tree (if it was not deleted by the previous action).

Delete the profile Directory using one of these commands:

• On Windows: was_install_dir\profiles\rmdir /s profileDirectory
• On UNIX/Linux: was_install_dir\profiles\rm -R profileDirectory

Security. Understanding People, User, and Labor Records in MAXIMO

Security. Understanding People, User, and Labor Records in MAXIMO

When you create records for individuals,the system requires the creation of additional records in the following cases:

Labor- You use the Labor application to create and manage labor records for employees and contractors who perform work on tickets and work orders. Labor records contain information about an individual’s skills and qualifications. These records are used toplan and schedule work, and to track labor costs for tickets and work orders.

A labor record must have a person record associated with it. A labor record needs a user record if the laborer is going to use the system to view work orders, report labor hours, and so forth. You can associate a labor and user with the same person record. As a best practice, you createcraft records for different job skills and qualification records for certifications, and record that information about the labor record. Other resources records are optional, but not required. For example, a labor record can have:

• One or more crafts
• One or more skill levels associated with a craft
• One or more qualifications

Person - You use the People application to create and manage records for individuals. A person record contains basic information about an individual’s name, address, contact information,and other generic information.

A person record does not require any other resource records, such as craft, labor, user, and so forth. However, you must create a person record when you create a user record or labor record. You can associate a single person record with both a labor and user record.

A person can be a user and a laborer or neither. For example, someone calling the service desk to make a service request does not need to be a user, but your company might require that a person record exist for that user.

As a best practice, create a person record for any individual whose name appears anywhere on a record. For example, someone calling the service desk might not need a user ID to access the system. However, you can use person records to check if the individual is authorized to make a service request.

To manage employee information, you can create person records for all of your employees and contractors. Alternatively, you can create person records for laborers and others who must access the applications as part of their jobs.

User - You use the Users application to create and manage records for users. User records contain user names, passwords, and security profiles that determine which applications, options, and data a user can access. A user must have a person record. A user record can be associated with only one person record, and a person record can be associated with only one user record. You can associate a labor record and user record with the same person record.

Other resource records (labor, craft, and so forth) are optional, but not required. If you create new user records and you do not specify a value in the Person field, the system prompts you to create a matching person record for the user record.

You create a user record for anyone who must log into the system to view create or manage records.