EAM Failure Codes Upload  Help

EAM Failure Codes Upload creates, updates and deletes the three Oracle Enterprise Asset Management (eAM) failure code lists from Excel – Failure Codes, Cause Codes and Resolution Codes – which maintenance users pick to record what failed on an asset, why, and how it was fixed. One file can hold codes of all three types.

When to use it

• Load a standard set of failure, cause and resolution codes during an eAM implementation.
• Add new codes, for example new failure modes found in the field.
• Mass-update code descriptions.
• Deactivate obsolete codes by setting an effective end date, or reactivate them by clearing it.
• Delete codes created in error.

Before you start

• The codes are global: they do not belong to an organization or operating unit, so any responsibility with access to the upload can maintain them.
• To group codes into failure sets for asset groups, use the EAM Failure Sets Upload after loading the codes.

Step 1 – Set the parameters

Open EAM Failure Codes Upload in Blitz Report and set the parameters:

Step 2 – Run to download the Excel file

Click Run. The Excel file downloads and opens with one row per code, or an empty sheet.

Step 3 – Enter or change the codes

Each row is identified by Code Type (Failure Code, Cause Code or Resolution Code) and Code, which is unique within its code type. If the code exists it is updated, otherwise it is created.

Enter or change the Description. Set an Effective End Date to deactivate a code; clear it to make an end-dated code active again.

To delete an existing code, set Delete Record to Yes. Deleting takes priority over any other change on the row.

Step 4 – Validate and Save

Click Validate and Save. This checks for missing required values and saves the file. Correct any rows it flags before uploading.

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which creates, updates or deletes the code of each row.

Step 6 – Review the result report

When the request completes, a result report opens listing every uploaded row with its status and message.

What’s produced

• Failure, cause and resolution codes created, updated, end-dated or deleted, available to all maintenance organizations.
• A result report listing every row with a status (success or error) and a message.

Common questions

What is the difference between Failure, Cause and Resolution codes?
They are three separate lists used together on a work order completion: what failed (Failure Code), why it failed (Cause Code) and how it was fixed (Resolution Code). The Code Type column selects the list a row belongs to.

Are the codes specific to an organization?
No. They are shared by all organizations.

Should I delete a code or end-date it?
End-date codes that have been used, so failure history keeps its codes. Delete only codes created in error.

Can I rename a code?
No. Code and Code Type identify the row; a changed code is created as a new code. End-date or delete the old one.

A re-uploaded row says “unchanged” – is that an error?
No. The description and end date matched the stored values, so nothing was updated.

Troubleshooting