Quick Fixes

Booking Labor: How you book labor can change how you report time

We recently were asked if a report will show the hours team members book labor for during the previous shift. This seems very straight forward. They book hours, with a date, and you just need to report on past 24 hours, right? Well yes and no. Do they work from 12am to 12am? Then it may not always be that easy.

Here’s How It’s Done:

You can use Cognos to create offsets from the systems time to report on the information about yesterday’s shift. Or, you could improve your book labor accuracy by having your team book the hours with the time they worked on the work order. For example, instead of booking 4 hours, you could book 1:00pm to 5:00pm. If you are familiar with the mobile app this is super easy to do. Booking labor by time fields are right there to choose your start time and end time and voila! You have now successfully booked your time with the actual hours you worked.

In EAM (the application) there is some admin work that needs to happen…

Scenario:

We want to start booking labor using Start time and End Time.

NOTE: Screen designer is required

Solution:

  1. In the application go to Work | Work Orders | Book Labor tab
  2. Open Screen Designer for the user groups that need to book labor with Start time/End time
  3. Find the fields Start Time/End Time and make them available (or required)

Booking Labor Infor EAM

 

 

4. On the Book Labor tab the hours field will still be required, but now you can enter the Start Time and End Time of the labor you are booking.

Booking Labor EAM 2

 

That’s It!

For more help with booking labor in the application or the mobile app or anything else EAM don’t hesitate to contact us. We would love to help you improve your labor accuracy or reporting and KPIs!

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.

Change a Supplier on a PO

I have been asked this question a lot recently. We all know that sometimes the Requisition may request a part or parts from a Vendor, then the Buyer realizes there is a better Vendor for that part… “How can I change a supplier on a PO?” Well to the answer the question, you can’t… Good news is there is a way to fix your problem!

The idea is to delete the part lines from the PO and cancel the PO. Then you go to the Requisition and change status to “Unfinished” and then change the Supplier. You can approve the Requisition and generate another PO.  Here is the quick down and dirty way to get this PO to your vendor.

Scenario: Requisition is “Approved”, PO was generated. Buyer figures out the Supplier is incorrect.

Steps to correct the issue:

Buyer: Navigate to Purchasing | Purchase Orders

  1. Go to the PO that is incorrect, make sure the status is “Unfinished”
  2. On the Parts Tab, Delete the Part Lines from the PO
  3. Go to the record view of the PO and change the status to “cancelled”(Do not cancel the Requisition/Lines when the windows asks if you want to)

Requisitioner: Navigate to Materials | Requisitions

  1. Go to the Requisition with the incorrect Supplier
  2. Change status to “Unfinished”
  3. Go to the Part line with the incorrect supplier and choose the correct Supplier
  4. On record view change the status back to “Approved”

Buyer: Navigate to Purchasing | Process | Generate POs

  1. Enter the Orginator
  2. Enter the supplier in the Supplier field (this is not required, just narrows the results to help)
  3. Click on the Preview tab
  4. Select the Requisition lines you corrected the Supplier on
  5. Click the Generate button

Now you have corrected the Supplier and created a new PO. As always, if you need any help or more information on this topic, please reach out to us. We would be thrilled to help you out!

Custom vs User Defined Fields – Which is better?

Is it better to use custom fields or user defined fields? And really what is the difference? Can I create a lookup for a user defined field? Will they both show up on mobile? These are questions I often hear when users need a field to enter/collect data on Equipment, Parts, Work Orders, etc.. Unfortunately, the field is not offered in EAM. Really, the availability of both types of fields is great in EAM and there are some significant differences – which is why you need to know the difference before you choose which one to use.

Here is what you should know:

  • What you need to know about User Defined Fields:

    • You can have user defined character, number, or date fields. There are also user defined checkboxes and buttons.
    • You can define a default value or create a list of values for a lookup.
    • You can make the user defined fields available on mobile devices.
    • You can select if the field prints on work orders.
    • You can create them specific to one or multiple user groups of your choosing.
    • You can search based on the values in a user defined field.
    • User defined fields will only show on the screen it is created for. For example, if you create a UDF on the asset record view, you will not see that same UDF on a system, position, or location field.
  • What you need to know about Custom Fields:

    • You must create them for a specific entity (Equipment, Events (work orders, work requests), etc.)
    • You can create them for a specific class within that entity. For example, you can create a custom field that will only show up when someone looks up or creates an asset record for an asset with the class of motor or pump.
    • You can specify if the field is character, numeric, date, date/time, code+description, or entity.  Furthermore, you can require a specific minimum/maximum length and have it included on the grids (or list view).
    • You can define the lookup type and list of values of the lookup.
    • You can select if you print the custom field.
    • You can choose if users can update the field.

We are here if you need us!

I hope this quick list helps you understand and decide which field is best to use. However, if you still have questions please feel free to reach out and email me. I would be more than happy to answer your questions.

Can you duplicate primary key records across organizations?

One of the questions I am frequently asked when I upload data into a new Infor EAM environment is; “Can we use the same part, asset, cost codes if they are in different organizations?”

The Basics

Let me start out with some basic, but important information. When configuring a fresh EAM Environment, we go through several settings (install parameters and organization options). Then one of the big decisions need to be made about whether we want data to be held in together, in a common org, or separately by activating Multi-Organization settings. Most companies with several facilities will choose to activate multi-org on many items.

But then the question is asked – “I have this asset here but also at a different location, can I use the same asset code?” The initial answer might be, “No, you can’t. This is because EAM does not allow you to duplicate codes at all in the application”. But I would be completely wrong! Even with Multi-Org activated, EAM does allow you to duplicate a handful of key code fields.

These are some key record fields you can duplicate across organizations:

  • Assets
  • Classes
  • Locations
  • Parts
  • Suppliers
  • Systems

These are some key record fields you cannot duplicate across organizations:

  • Cost Codes
  • Departments
  • Manufacturers
  • PM Schedules
  • Stores
  • Task Plans
  • Trades

Now take a second and ask, “Why is this allowed? What benefit(s) does it offer?”

Benefit

This allows multiple organizations that may have the same equipment, parts, suppliers, etc. to keep their unique information for that equipment, part, or supplier in EAM. When it comes to the list of fields you cannot duplicate, this is because these are items that should be either unique for each organization or shared between all organizations. In some cases, Parts is kept common between organizations so that all organizations are using the same part numbers but can enter their own unique supplier information.

This is a topic that we discuss thoroughly with customers that will have multiple facilities sharing EAM so we can ensure that EAM is customized and meeting the demands of your specific business. If you have any further questions regarding this topic, please leave a comment or reach out to us by clicking here. We are always happy to help!

Are you experiencing a Cross Joins Error in Cognos Reporting?

If you have ever spent some time working with Cognos reports you more than likely had the error “Cross joins (between query subjects: SQL1…blah, blah….) are not permitted for the user who has the identity ‘*’.”

Why it happens:

This error occurs because there is no relationship between the tables at the model level in Cognos. It can be very frustrating when building reports. Before I learned this trick, the only way to get around it was to try and take a different approach to get the same results using different tables. The information required for the report may not always be available on different tables, so this is where the trick really comes in handy.

Easy Solution:

Open Cognos Report Studio and navigate to the query you are getting this error from and look under the Query Properties (left side, down low on screen). You will see the Property named ‘Cross Product Allowed’. Select the dropdown and choose ‘Allow’. Run the report to test it and Save the report. See screenshot below…

It’s as easy as that! This solution has worked wonderfully for me. So the next time you get the dreaded error message about cross joins, remember this simple trick to help get the data you want on the report.