How You Import Discrete Work Orders

Work order import is a method of creating and updating work orders through the user interface. You can use the cloud import framework to import the work order using spreadsheets. You can also provide the descriptive flexfields information during the work order import.

To import discrete work orders using the cloud import framework, you can download and use the WorkOrderTemplate.xlsm.template. The .xlsm template organizes the work order information in the following tabs:

• Instructions and CSV Generation: The procedure to import work orders using the .xlsm template.

• Import Batch: The batch identifies the group of work orders that are being imported.

• Work Order Headers: The work order header information is identified uniquely by a header number within a batch. You can import work orders across plants within a batch.

• Work Order Operations: You can optionally specify work order operation information against the batch code and header number.

• Work Order Operation Materials: You can optionally specify work order operation item information against the batch code, header number, and operation sequence.

• Work Order Operation Resources: You can optionally specify work order operation resources information against the batch code, header number, and operation sequence.

• Work Order Serial Numbers: You can optionally specify product serial information against the batch code and header number for serial-tracked work orders.

• Work Order Operation Resource Instances: You can optionally specify work order operation resource instances information against the batch code, header number, and operation sequence.

• Material Lots, Serials, Lots and Serials: Applicable only for rework work orders

Work orders can be imported in batches using create and update modes either by providing the basic work order header details or by providing the complete details of work order header, operation requirements, resource requirements, component requirements, and serial details.

The following table lists the various modes of import that enable you to create or update work orders:

User Preference	Header Action	Operations Action	Items and Resources Action	Serials Action	High-Level Considerations
To create work order with header only (standard work order or nonstandard work order with work definition)	CREATE	Not Applicable	Not Applicable	Not Applicable	You must specify the following with other necessary details: Work Definition details Allow Explosion =Y Scheduling method = DEFAULT_SCHEDULER
To create work order with header and details, and to allow the scheduling engine to determine the dates.	CREATE	CREATE	CREATE	ASSOCIATE_SERIAL	You must specify the following with other necessary details: Work Definition details (for Standard work orders) Allow Explosion = N Scheduling method = DEFAULT_SCHEDULER
To create work order with header and details with dates specified.	CREATE	CREATE	CREATE	ASSOCIATE_SERIAL	You must specify the following with other necessary details: Work Definition details (for Standard work orders) Allow Explosion = N Scheduling method = NO_SCHEDULING
To update the work order.	UPDATE	CREATE, UPDATE	CREATE, UPDATE	ASSOCIATE_SERIAL, DE_ASSOCIATE_SERIAL	Not Applicable

Tip: If the Plant parameter Automatically associate serial numbers during work order import is enabled during import, the serials are automatically generated and associated for serial-tracked work orders.

You can create, update, and query for a work order using a REST API.

The successfully imported work orders as well as the errors if any are displayed in the Schedule Process output.

Correct Work Orders for Import

You can use the Correct Work Orders and Transactions for Import task in the Work Execution work area to view all the file-based data import records that resulted in errors, and you can also export them into ADFdi spreadsheets to correct the errors. After you have corrected the errors in ADFdi, you can upload the spreadsheet to resubmit the records that returned errors for processing.

Note: You can use this task to correct errors only for transaction records where the mode of import was file-based data import. You can't correct errors for import transaction records created through REST API.

Follow these steps to correct the errors and resubmit the completed data for work order import:

1. In the Work Execution work area, select the Correct Work Orders and Transactions for Import task from the Tasks panel.

2. Use the filters to search for specific import transaction entries. You can use a combination of the following filters to search for the work orders import transactions:

   • Select the import transaction type as Work orders import.

   • Search for the unique batch code identifier of your import batch.

   • Search for the transaction based on the batch status. If the batch completed but has some errors that you must redress, you can search with Completed with errors. If the batch is still in process due to server failure or any other application error, you can search with In process.

   • Search for the transaction record based on the request identifier of the corresponding import work orders scheduled process.

3. The search results displays a list of all the relevant import transaction records. Click Manage in Spreadsheet to initiate the correction process through ADFdi.

4. The Work Orders Import ADFdi has separate worksheets for its various attributes. You can manually correct the errors and then set the batch status of the individual rows to Ready.

5. After you have corrected all the errors and saved the statuses as ready, click Upload to resubmit the corrected records for processing. You have to upload each worksheet individually.

6. You can refresh your search on the Correct Work Orders and Transactions for Import or search on the basis of the batch status as Ready to view if the corrected records were successfully processed.

Note: For more information about file-based data imports to import or update legacy and other data into Supply Chain Management Cloud from external applications, refer to the File-Based Data Import for Oracle Supply Chain Management Cloud Development Guide.

Note: Correct work orders for import is supported for both discrete and process manufacturing.