running reports

Reporting on Work Order Closing Codes

You’re are using EAM for work orders, they get entered, worked, and then closed. So, then what? How can you take closed work orders and report on them? After all, this is extremely helpful and can really impact your ROA on EAM.

Action Codes

You can create a Close Work Order report that includes your Closing Codes. EAM has Action Codes, Cause Codes, Problem Codes, and Failure Codes. These codes are very important when improving best practices for any Maintenance program. Creating reports with these codes can be especially helpful with trending, allowing you to trend your work orders and equipment failures. So let’s get to the reporting part of these Action codes.

When you are reporting on closed work orders there are a couple very important fields that sometimes can be tricky to report on. Those pesky closing codes! I’m going to show you how to get those codes to display in a report showing the Description of the code. Something useful that anyone can understand!

Here we go!

The Closing Codes in EAM have a “code” and a “Description”. When reporting,  you want to display the description, something that the average user can understand. To get the description of the Closing Codes we will use a built in function Cognos gives us: REPGETDESC(. This function will return the description of the item. To successfully use this function you need to know the Entity in EAM for the closing codes, but finding these can be a bit tricky. Good thing you found DigitalThinker because I’m going to give those to you right here!

The following entities are what is used for Closing Codes in EAM for work orders:

ACCO = Action Code

CAUS = Cause Code

FAIL = Failure Code

RECO = Problem Code

In this example, we will look at the Action Code for a Work Order.

Create a data item in Cognos for our report:

  1. Login to Cognos with an Author License
  2. Add a Data Item to your query
  3. In the Functions tab find the REPGETDESC( Function, (
  4. Drag the function to the Expression box
  5. Next use EN for English, the code for your closing code above and the field you pulling the description from
  6. Your Expression should look like this, REPGETDESC (‘EN’, ‘ACCO’, [EVT_ACTION], null, null)
  7. Next take the data item and add it to your report on the report page.
  8. This will display the Description of the Action Code of your Work Order

Voila! It is that easy to get all your Closing Code Descriptions to display on Work Order Reports. Remember, You just need swap out the code in your expression with ACCO, CAUS, FAIL, RECO. Of course, you also will have to change the field from the work order in your expression.

Let Us Help!

If you are new to reporting or find yourself running into issues trying to do this, please do not hesitate to contact us and we can certainly help you get this straightened out. We would love to help you get more from your EAM!

PM Schedules/Work Orders with Routed Equipment – Organizational Options

Are your PM Schedules or work orders created with equipment on a route? If so, then you may be wondering if all the equipment will be listed on the work order or just the main piece of equipment selected. Furthermore, maybe you aren’t sure if EAM will create work orders for all the equipment or does it just create a work order for the one main equipment record. Those questions can quickly be answered with 2 Organizational Options.

By remembering these 2 organizational options listed below, you’ll be able to select the way you want to capture the information. You can find them by going to Administration à Security à Organizations. You will likely have to click the “More” tab and click on options.

Organizational Options:

MEROUTWO Determines which equipment to copy to route-based PM work orders. Select ‘C’ for route equipment only, ‘H’ for header equipment only, or ‘B’ to have both header and route equipment copied.
ROUTEEOB If Y, the system will create Multiple Equipment Child type work orders for each route equipment when route based PM work orders are released.   They will be related to the parent job.

 

You can always play around with the options, set them one way then test it out, then change it and test again. That is what your training environment is for. If you change the options, you must close the released PM work order. Log out and back in then generate PM work orders again for the changes to take effect.

I hope some of these tips help! If you have any further questions or need any help, feel free to let me know. I am always happy to help.

Cascading Report Prompts on Custom Reports

When writing custom reports for customers, most of them will give us a list of prompts that they want to use when creating it. In this blog, I would like to quickly explain the usefulness of cascading prompts on your custom reports and why they can be beneficial. Below are a couple of common situations where cascading prompts will be helpful.

Issue:

Customer needs a report for labor hours for specific organization and wants to be able to select one or more employees to run the report on.

Solution:

Build the custom report with a prompt for organizations that also cascades (filters) for only the employees for that organization.

Issue:

Customer needs a report for Parts for a specific organization and supplier by store/bin location.

Solution:

Build a custom report that prompts for organization and cascading (filtering) prompts for parts in that organization and store/bin location for the parts.

 

These are just two common reports that we can write for customers. But report writing is limitless. We can discuss your needs and draft out a report that is customized for your specific needs. We can also continue customizing it until it is exactly what you want. Remember, writing reports and even revising versions of a report that you may already have in EAM can be tedious. During our discussions with you, we will be upfront with you on what it will take on our part to meet your expectations so we can either continue or scale it back a little and revise it at a later time.

We have lots of experience in working with custom reports. As a result, we have many ways of customizing them and making them work for you. As always, reach out to us for any questions, concerns, or for any further help on this topic. Thank you for reading!

 Are you having trouble running reports after you upgraded to Infor EAM v11.3?

A customer of ours recently had an issue running reports after recently upgrading to v11.3. The issues were with custom reports but also with some of the ‘canned’ (Infor) reports as well. I wanted to share the details of this specific issue and the simple solution to the problem.

Issue: When printing from the PO Receipt screen or running the report from the report menu, several PO Receipts were coming back as “No Records Found”.

Troubleshooting: Investigated the reports in Cognos to see if there was anything that would causing the errors. They used a modified version on the Goods Received Note, so we looked at the original version of Goods Received. We found there were issues running that report as well. At this point, since we were unable to identify any issues that would be causing these reports to error, we submitted an incident to InforXtreme.

Solution:

  1. Go to Administration | Setup | Reports
  2. Filter for Base Reports
  3. Find report SZRCVF
  4. Click on the Parameters Tab
  5. Find the Print report parameter
  6. Change the default value from blank to +
  7. Save the change

You will not see this parameter on the prompt page for the report when you run it from the menu in EAM. The only place to change this parameter is the parameter tab of the Report Setup. This is not something that customers have been made aware of. Therefore, we wanted to share the solution to keep you from getting frustrated by looking for an issue in the actual reports. If you do any report writing, you know how daunting and time consuming it can be to look for that needle in the haystack.

If you apply this solution and still are having issues, please reach out to us or your EAM support team.