EAM PM Schedule Upload creates and updates Oracle Enterprise Asset Management preventive maintenance schedule definitions from Excel, through the standard Oracle EAM public API: the schedule header, its activities, its scheduling rules (day interval, runtime meter and list date rules) and optional last service readings. Uploading defines the schedules; the work orders are generated by the Generate Preventive Maintenance Work Orders concurrent program.
When to use it
- Create preventive maintenance schedules for many assets at once instead of one at a time in the Preventive Maintenance Schedules window.
- Roll out a standard maintenance regime (same activity and interval) across a fleet of assets.
- Bulk-update schedule attributes such as effective dates, lead time, work order status, rescheduling and scheduling method.
- Load day interval, runtime meter or list date rules, and last service readings so the next due date calculates correctly.
Before you start
- You use a responsibility with access to the eAM-enabled maintenance organization.
- The asset number exists, and the activity is associated with it (EAM Asset Activity Association Upload or the Activity Association window).
- For meter rules and last service readings, the meter exists and is associated with the asset.
Step 1 – Set the parameters
Open EAM PM Schedule Upload in Blitz Report and set the parameters:
| Parameter | Meaning |
|---|---|
| Upload Mode | Create (default) opens an empty sheet; Create, Update downloads existing schedules for editing and lets you add new ones. |
| Organization | The maintenance organization to download schedules for. |
| Update Activities | Create, Update only: Yes (default) adds a row per activity of each schedule. |
| Update Rules | Create, Update only: Yes adds a row per scheduling rule. |
| Update Last Service | Create, Update only: Yes adds a row per last service meter reading. |
Step 2 – Run to download the Excel file
Click Run. The Excel file downloads and opens with the schedules of the organization: a header row per schedule, followed by its activity, rule and last service rows. In Create mode the sheet is empty.
Step 3 – Enter or change the schedules
All rows of a schedule repeat the header columns (Organization Code, Schedule Name, Asset Type, Asset Number, Activity and so on) and must stay together; Schedule Name, Asset Number and Activity identify the schedule. Existing schedules are updated, others created. Each row can add one activity (Act Activity, Act Interval Multiple, Act Allow Repeat…), one rule and one last service reading:
- Day interval rule: Rule Day Interval, with optional Rule Effective Date From / To. Required for Schedule Type Day Interval.
- Runtime meter rule: Rule Meter and Rule Runtime Interval, with optional effective readings.
- List date: Rule List Date and Rule List Date Desc. Required for Schedule Type List Dates.
- Last service: Lsi Meter, Lsi Last Service Reading, optionally Lsi Prev Service Reading and Lsi Wip Job.
A new Rule Based schedule needs at least one day interval or runtime meter rule; without an Act Activity, the header Activity becomes its activity. A single row is enough, as for the new C402 schedule in the screenshot. Set Use to Base Date or Base Meter Reading only together with Base Date or Base Reading. An unknown Set Name is created, using Set Name Description, Set Name End Date and Set Name Local Flag.
Validate and Save requires a rule on every changed row of a Rule Based schedule, so change header values such as Lead Time In Days or Effective To on the schedule’s rule row, not on its first row. The rule rows you upload replace all rules of the schedule, and activity rows replace all its activities; a schedule uploaded without rule or activity rows keeps its existing ones. If a schedule has several rules, upload all of its rule rows.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and the rules above, 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 or updates each schedule with all its rows in one step.
Step 6 – Review the result report
When the request completes, a result report opens listing every uploaded row with its status and message. If one row of a schedule fails, the whole schedule is rolled back and all its rows show the error.
What’s produced
- Preventive maintenance schedules created or updated with their activities, rules and last service readings, and any new PM set names.
- A result report listing every row with a status (success or error) and a message.
Common questions
I uploaded a schedule but no work orders appeared. Why?
Uploading only defines the schedule. Run the Generate Preventive Maintenance Work Orders concurrent program to create the work orders.
Can I create a schedule for an asset group?
No. Every schedule is for an asset number. Use one schedule per asset.
Will changing the header lose my existing rules?
A schedule uploaded without rule rows keeps its rules. Uploaded rule rows, including a rule row you changed only for a header value, become the schedule’s complete rule set, so include every rule row you want to keep.
Can I delete a schedule or a rule?
Schedules cannot be deleted. To drop a rule, upload the schedule’s remaining rule rows; to end a schedule, set Effective To.
My Activity is not in the list for the asset.
The activity must be associated with that asset number. Create the association first, then enter the row again.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Organization is not accessible for the current responsibility or is not EAM enabled. | The organization is not eAM-enabled or not assigned to your responsibility. | Upload from a responsibility with access to the maintenance organization. |
| Asset Number “<asset>” not found for the organization. | The asset number does not exist in the organization. | Pick the asset number from the list. |
| Activity “<activity>” is not associated with the selected asset. | The activity has no active association with the asset number. | Associate the activity with the asset first. |
| At least one Date Rule or Meter Rule is required for Rule Based PM schedules. | A changed row of a Rule Based schedule has no Rule Day Interval or Rule Meter. | Enter the change on the schedule’s rule row, or add a rule to the row. |
| Base Interval In Days is required when Schedule Type is Day Interval. | A Day Interval schedule row has no Rule Day Interval. | Enter Rule Day Interval. |
| Date is required when Schedule Type is List Dates. | A List Dates schedule row has no Rule List Date. | Enter Rule List Date. |
| Base Date is required when Use is Base Date. | Use is Base Date (or Base Meter Reading) without a base value. | Enter Base Date (or Base Reading). |
| Rule Meter is required for Runtime Meter rules. | Rule Runtime Interval is entered without a meter. | Pick the Rule Meter. |
| PM Set Name “<name>” could not be created: <Oracle message> | Oracle rejected the new set name. | Correct the set name columns, or use an existing Set Name. |
| Create_PM_Def failed: / Update_PM_Def failed: / PM header/rules validation failed: <Oracle message> | The Oracle EAM API rejected the schedule, for example overlapping rules or invalid dates. | Read the Oracle message, correct the row and upload again. |





