EAM Failure Codes Upload creates, updates and deletes the three global Oracle EAM code dictionaries from Excel – Failure Codes, Cause Codes and Resolution Codes – used to record why an asset failed.

When to use it

  • Initially load a standardized set of failure, cause and resolution codes during eAM implementation.
  • Bulk-add new codes (for example new failure modes) discovered in the field.
  • Mass-update code descriptions for clarity or translation cleanup.
  • Deactivate obsolete codes by setting an effective end date (preferred over deletion, to preserve history).
  • Reactivate a previously end-dated code by clearing or extending its end date.
  • Permanently remove codes created in error.

Before you start

  • Blitz Report is installed and you are signed in to a responsibility that can maintain EAM failure/cause/resolution codes.
  • These are global dictionaries – the codes are not specific to any organization or operating unit.
  • To delete a code, it must already exist.

Step 1 – Choose a mode, set the parameters and download

In Blitz Report, open EAM Failure Codes Upload, choose an Upload Mode (Create, Update – the default – downloads existing codes to edit; Create gives an empty template), and optionally set the Code Type filter (Failure Code / Cause Code / Resolution Code). Run the upload to download and open the Excel file. Each code is automatically handled as a create or an update depending on whether it already exists in its dictionary.

Step 2 – Enter the codes

On each row choose the Code Type, enter the Code and a Description, and optionally an Effective End Date to deactivate the code.

Step 3 – Delete codes (optional)

To permanently remove a code, set Delete Record to Yes on its row. To deactivate without removing, set an Effective End Date instead.

Step 4 – Validate and Save

Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.

Step 5 – Upload and view the result

Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates, updates or deletes each code. When it finishes, a result report opens showing each row as success or error.

What’s produced

  • Created, updated or deleted failure, cause and resolution codes.
  • A result report listing every row with a status (success or error) and a message.

Common questions

What’s the difference between Failure, Cause and Resolution codes?
They are three separate dictionaries used together to record an asset failure – what failed (Failure Code), why (Cause Code) and how it was fixed (Resolution Code). The Code Type column selects which dictionary a row targets.

Are these codes specific to an organization?
No. They are global dictionaries shared across all organizations – there is no organization context on this upload.

Should I delete a code or end-date it?
Prefer end-dating (set an Effective End Date) so existing failure history that references the code is preserved. Use Delete Record only to remove codes added in error.

How do I reactivate a code I previously ended?
Download in Create, Update mode and clear (or push out) its Effective End Date.

Why didn’t my update do anything?
If neither the description nor the effective end date differs from what’s stored, the row is reported as unchanged and no change is made.

Troubleshooting

MessageCauseWhat to do
Code Type is required / Code is requiredA required cell was left blank.Fill in the Code Type and the Code (unique within its Code Type).
Invalid Code TypeThe Code Type isn’t one of the three valid types.Pick Failure Code, Cause Code, or Resolution Code from the dropdown.
Code does not exist – nothing to deleteDelete Record = Yes on a code that isn’t in the dictionary.Remove the Delete flag, or correct the Code/Code Type to an existing code.
Code already exists and Upload Mode does not include UpdateEditing an existing code in Create-only mode.Re-run in Create, Update mode.
Code create/update/delete failed (Oracle message)The eAM API rejected the operation.Read the appended Oracle message and correct the data.