From the Maximo Support Desk - Actual Tool Cost on a Work Order

October 25, 2017 TomRichardson

Maximo Users have asked if there is a field in the database that can be used to report the actual tool cost on a Work Order?  This question is based on the fact that several of the View Costs, or other report-type dialogs in Maximo applications do not get data from persistent fields.

There are a number of fields in the Maximo database that store costing data for Work Orders. Maximo Users or Administrators may need to create a report which includes a display of what the actual tool cost is on a Work Order. It may not be immediately apparent to the User which field(s) to use for this purpose.

image

 

The field which reflects the actual tool cost for the Work Order is TOOLTRANS.LINECOST.

Additional Notes:
There are two LINECOST fields in the TOOLTRANS table; LINECOST and LINECOST2. It may be possible to have values in both fields. The LINECOST attribute, as stated above, will reflect the actual tool cost in the Base Currency of the Organization. The LINECOST2 attribute is used to support multiple currencies in an Organization. This will be populated if a second currency is used in the Organization, and will reflect the actual tool cost of the Work Order in the second currency.

 


Tom Richardson is an IBM Maximo Support Engineer and frequent contributor to the Asset Management Blog community.  For a complete index of links to his articles, visit
Index of articles by Tom Richardson, Support Engineer

Previous Article
From the Maximo Support Desk - ACM Technical Record Creates Asset But No Work Order

Maximo clients have reported that in some scenarios, that the ACM Technical Record does not create the expe...

Next Article
From the Maximo Support Desk - Allowable Status Changes for Work Orders
From the Maximo Support Desk - Allowable Status Changes for Work Orders

It is not possible to change a Work Order Status to any other Status.  I've compiled a list here as a guide...

×

Want our latest news? Subscribe to our blog!

Last Name
First Name
Thank you!
Error - something went wrong!