EAM Failure Sets Upload  Help

EAM Failure Sets Upload creates and updates Oracle EAM failure sets from Excel – the failure set header plus its asset-group / item associations and its failure / cause / resolution code combinations – in one multi-row spreadsheet, and lets you delete associations and combinations. A Row Type column on each row tells the upload which part of the set it represents.

When to use it

• Mass-create new failure sets and populate them with item associations and valid failure/cause/resolution combinations in one pass.
• Onboard asset classes by attaching failure sets to their asset-group / rebuildable items.
• Bulk-add or end-date failure/cause/resolution combinations within existing sets.
• Flag (or clear) “failure code required” on existing item associations.
• Remove obsolete associations or combinations from a set.
• Retire a whole failure set by end-dating it (since it can’t be deleted).

Before you start

• Blitz Report is installed and you are signed in to a responsibility that can maintain EAM failure sets.
• The individual failure / cause / resolution codes referenced on combination rows already exist – create them first with the EAM Failure Codes Upload.
• For association rows, the item exists and is an asset-group or rebuildable EAM item.

How the Row Type works

Each row represents one part of a failure set, chosen in the Row Type column. The Set Name repeats on every row of the same set, which can own many association and combination rows:

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

In Blitz Report, open EAM Failure Sets Upload, choose an Upload Mode (Create for an empty template, or Create, Update to download existing sets to edit), and optionally set the Set Name filter. Run the upload to download and open the Excel file. Each set, association and combination is automatically handled as a create or an update.

Step 2 – Enter the failure sets

Use one row per piece, repeating the Set Name on each and setting the Row Type. On a SET row enter the description; on an ASSOCIATION row enter the Inventory Item; on a COMBINATION row enter the Failure Code, Cause Code and Resolution Code. If you enter the first association/combination for a set that doesn’t exist yet (in Create), the upload creates the set header automatically.

Step 3 – Delete or end-date (optional)

Set Delete to Yes on an ASSOCIATION or COMBINATION row to remove it. A failure set itself cannot be deleted – end-date it by entering a SET row with the Set Effective End Date filled in.

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 applies each set and its child rows. When it finishes, a result report opens showing each row as success or error.

What’s produced

• Created and updated failure sets with their item associations and code combinations; deleted associations/combinations where flagged.
• A result report listing every row with a status (success or error) and a message.

Common questions

How do I put a set, its items and its codes in one spreadsheet?
Use one row per piece, repeating the Set Name on each, and set Row Type to SET, ASSOCIATION or COMBINATION. Keep rows for the same set together.

Do I have to add a SET row first?
Not always. On a Create run you can enter just the first ASSOCIATION or COMBINATION row – the upload creates the missing header from that row. A SET row is needed when you want to set header fields explicitly.

How do I delete a failure set?
You can’t delete the set itself. End-date it with a SET row that has a Set Effective End Date. You can delete its associations and combinations with Delete = Yes.

Why isn’t my new failure code selectable on a combination row?
The code must already exist and be active in EAM setup; create it first via the EAM Failure Codes Upload.

I re-uploaded an unchanged row – why does it say “No change”?
Update is only performed when a tracked field actually differs from what’s stored; identical rows are skipped.

Troubleshooting