Workorder WMATL APPR INPRG status

The Work Order statuses in Maximo are defined as standard values, but it is mostly configured as per client's business.

WAPPR[Waiting for Approval] 

  It is an initial status where the work order is planned. It allows setting job plans and work plans. It does not allow entering actual information.

APPR [Approved] 
  It is used for Work orders approved to be started, but it has not started yet. 
Sometimes, it may be waiting for a labor, which has prevented this work from being started. It is for this reason, we could able to change WO status from APPR to WAPPR.

WMATL [Waiting for Material]

  It is equivalent of APPR status, but it may be waiting for a material to start the work. 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.

This is the status to facilitate the tracking of certain business scenarios that require a distinction between Approved and In Progress status.

INPRG [In Progress]

  It is next level from Approved condition. For example, once the material has arrived, the WMATL status gets relieved, and the work is now being done. 

WSCH [Waiting to be Scheduled]

  In most cases, PM Workorders will have WSCH as their default status.

WSCH denotes a condition where the necessary approvals and material are in place for a work order, but certain conditions ( labor availability, or plant environmental condition) are not letting it to proceed further and hence the work order is being rescheduled to a new start date. 

This status can be after APPR, or WMATL, or INPRG. 

Storeroom Material Status
http://www-01.ibm.com/support/docview.wss?uid=swg21683844

Reference:
http://www-01.ibm.com/support/docview.wss?uid=swg21569661
http://www-01.ibm.com/support/docview.wss?uid=swg21619886

Check points on Application Data Import

When we configure data Import from application, we need to look for some key points.

1. For any attribute that gets value from a sequence or auto numbering, Don’t include them in XML input file.

For Flat files, we must give unique values for auto key in the input file for supporting the conversion of Flat file to XML internally. The use of auto key or manual is decided by using the Restrict Attributes select action in Database Configuration at Object level or Inbound Setting Restrictions select action in Object Structure application. This setting will be considered for all integrations using this Object.

2.     For flat files, make last column of the file with value for each row. It will avoid problem of missing comma delimiter for some columns. 

Reference:  TPAE75_App+Import-Export.pdf

Custom Condition Class

Custom Condition Classes can be created by implementing the interface CustomCondition. It defines the interface for custom classes that can be used to do condition evaluations at WFCondition nodes.

We can write our conditions in Conditional Expression Manager application in Maximo 7.x. But, there are some cases, that can't be evaluated using SQL queries.
(For example, In workorder workflow, we like to compare a value between WorkOrder and Location applications).

In these cases, we implement psdi.common.condition.CustomCondition class to write the Custom Class, and override evaluateCondition(MboRemote mbo, Object arg1) method.

toWhereClause(Object arg0, MboSetRemote arg1)  Convert the condition to a where clause. If the condition class will be used for "QUALIFIED" object security type as shown in below screen shot, this method should return a where clause. If the condition should NOT be used for "QUALIFIED", it should throw an exception to indicate it is an error when attempted to be used.


The sample code can be referenced in this link.

http://www.maximokb.com/kb/index.php?View=entry&EntryID=115