Import Maintenance Work Orders
Oracle Fusion Cloud Maintenance enables you to create and update maintenance work orders in bulk using a File-Based Data Import (FBDI).
The Import Maintenance Work Orders scheduled process is used to:
- Create and update a work order header record and its core attributes, including the associated asset
- Create, update, and delete operations, operation materials and operation resources. This includes values for definable flexfields.
When to Use
The process is used to create and update maintenance work definitions in bulk using the File-Based Data Import. Therefore, the process is only run after you have uploaded the file using the Load Interface File for Import scheduled process.
The following are the major steps involved in a Maintenance Definitions import process:
- Download and update the latest spreadsheet for your update.
- Transfer data to the interface tables.
- Run the import maintenance work definitions scheduled process.
- Verify the process output logs.
Download and Update the Spreadsheet
Download the spreadsheet template that's available in the File-Based Data Import for Oracle SCM guide. Update the spreadsheet with the import data.
The spreadsheet template organizes the meter readings information in these tabs:
- Instructions and CSV Generation: Contains a brief procedure to import maintenance work orders using the spreadsheet. It also contains the Generate CSV File button to generate the .csv files from the spreadsheet with import data.
- Import Batch: Enables you to create the import batch in which the maintenance work order records are grouped for processing.
- Maintenance Work Order Headers: Enables you to provide the details of maintenance work order headers. The maintenance work order header information is uniquely identified by the header number within a batch. You can import maintenance work orders across organizations in a batch.
- Maintenance Work Order Assets: Enables you to provide the details of the assets associated with the maintenance work orders. For each asset number, you must provide the batch code, action code, and header number. A maintenance work order can have only one asset associated with it.
- Maintenance Work Order Operations: Enables you to provide the details of maintenance work order operations. The batch code, action code, header number, and sequence attributes are always required. Additionally, operation type, name, work center, start date, and completion date attributes are required during work order creation. All other attributes are optional.
- Work Order Operation Resources: Enables you to provide the details of maintenance work order operation resources. The batch code, action code, header number, operation sequence, resource sequence, and resource code attributes are always required. Additionally, usage rate attribute is required during work order creation. All other attributes are optional.
- Work Order Operation Materials: Enables you to provide the maintenance work order operation item information. You must provide the batch code, action code, header number, operation sequence, item sequence, and item. All other attributes are optional.
- Work Order Operation Resource Instances: Enables you to provide the details of work order operation resource instances. You must provide the batch code, header number, and operation sequence. All other attributes are optional.
Transfer Data to the Interface Tables
On the General Instructions tab, click the Generate CSV File button to transfer the data into a .zip file with one or more .csv files. Use the Load Interface File for Import scheduled process to upload the .zip file to the server for transferring the data to the interface tables. The scheduled process is also accessible from the Tasks pane on the Maintenance Management landing page.
Run the Import Maintenance Work Order Scheduled Process
The next step is to run the Import Maintenance Work Orders scheduled process to transfer the data from interface tables to the production tables. The process will reference the import batch number defined in the uploaded spreadsheet. The scheduled process is also accessible from the Tasks pane on the Maintenance Management landing page.
Review the output logs from the import process. If any errors where encountered, they will be contained in a separate log file.
Purge Batch Data from Maintenance Import Interfaces
The upload or import of data may result in a warning or error status sue to issues with the data. When this occurs, the data can't be further processed from the interface tables. In such a case, the Asset Administrator can run the Purge Maintenance Records from Interface process to delete the asset data from the interface tables from all or just a specific import process. The scheduled process can be run on demand or setup on a schedule as required by your business processes.
Privileges Required
Verify that you have the following privileges to upload the FBDI files using the Load Interface File for Import scheduled process :
- Privileges
- FUN_FSCM_FILE_TO_INTERFACE_PRIV
- FUN_FSCM_LOAD_INTERFACES_PRIV
- FND_MANAGE_FILE_IMPORT_AND_EXPORT_PRIV
- FUN_FSCM_TRANSFER_FILE_PRIV
Verify that you have the following privileges for the Import Maintenance Work Orders scheduled process:
- Privileges
- MNT_IMPORT_MAINTENANCE_WORK_ORDERS_PRIV
- WIP_PURGE_RECORDS_FROM_INTERFACE_PRIV
Specifications
Use these specifications when you run the scheduled process.
| Specification | Description |
|---|---|
| Job Type | Adhoc, you only run after importing an FBDI file for a unique import batch number. |
| Frequency | As needed after importing the FBDI file. |
| Time of Day | Any time. |
| Duration | Typically, less than a few minutes, depending on the volume of data being created or updated. |
| Compatibility | There should be only one instance of the job running at any one time for a unique import batch number. A new job should only be submitted for another unique batch number after the previous one has completed, and the output logs have been reviewed. |
Parameters
The process will typically be run adhoc by selecting the batch number.
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required |
|---|---|---|---|---|
| Batch (number) | Required | The unique import batch number in which the meter readings records are grouped for processing in the Interface tables. | A list of values will display all batch numbers that are ready for import. | None |
Troubleshooting Information
Try this:
- Import file creation:
- You must create the file directly from the source Excel template by following the instructions on the first tab of the file. This will create a .ZIP file that is used for import.
- File import using the Load Interface File for Import scheduled process:
- You will schedule a new adhoc process to select and load the file into the interface tables.
- You can view the status of the Load Interface File for Import job on the Scheduled Processes UI.
- The process will spawn multiple child processes to transfer the .ZIP file and load data from each of the .CSV files contained in the .ZIP file.
- If any of the processes end in Warning or Error status, review their output logs. You may need to correct the data in the Import File, define a new unique batch number, and start the process again by uploading the new .ZIP file.
- File processing using the Import Maintenance Work Orders schedule process:
- You will schedule a new adhoc process to select and load the file into the interface tables.
- You can view the status of the Import Maintenance Work Orders job on the Scheduled Processes UI.
- The process will spawn a child process to import the data and process it from the interface tables.
- If any of the processes end in Warning or Error status, review their output logs. You may need to correct the data in the Import File, define a new unique batch number, and start the process again by uploading the new .ZIP file and then processing the file.