Import Work Orders

You can use the Import Work Orders scheduled process to create and update manufacturing work orders using file-based data import (FBDI). It imports the work orders and the associated details from the open interface tables.

You can create and update all types (Standard, Nonstandard, Rework, Transform) of discrete work order entities such as, header, operations, operation materials, operation resources, operation resource instances, work order lots, work order serials, work order assembly component, material lots, and material serials. Also, you can create and update standard process work order entities such as, header, operations, operation materials, operation resources, operation resource instances, operation outputs, and work order lots.

When to Use

Creating or updating work orders using FBDI is a three-step process:

1. Prepare the data using either WorkOrderTemplate.xlsm for discrete manufacturing work orders, or ProcessWorkOrderTemplate.xlsm for process manufacturing work orders.
2. Load the data to the interface tables using the Load Interface File for Import process. This process validates that the data have been entered as per the expected data type, for example, number or date and time format.
3. Import the data from the interface tables to production tables using the Import Work Orders process. This process validates that the data satisfy the business rules.

You should run the Import Work Orders process after the Load Interface File for Import process completes successfully.

Privileges Required

Verify that you have the following privileges to run Load Interface File for Import process:

• Load File to Interface (FUN_FSCM_FILE_TO_INTERFACE_PRIV)
• Load Interface File for Import (FUN_FSCM_LOAD_INTERFACES_PRIV)
• Manage File Import and Export (FND_MANAGE_FILE_IMPORT_AND_EXPORT_PRIV)
• Transfer File (FUN_FSCM_TRANSFER_FILE_PRIV)

Verify that you have the following privilege to run Import Work Orders process:

• Import Work (WIS_IMPORT_WORK_PRIV)

Specifications

Use these specifications when you run the scheduled process.

Specification	Description
Job Type	As needed.
Frequency	As needed.
Time of Day	Any time.
Duration	Varies, depending on the volume of data that you import. If your import includes a lot of work order headers and child entities, then the process needs more time to finish.
Compatibility	There should be only one import job running at a given point of time. However, you can have as many batch codes as you like in the template. When submitting the import job, one batch can be selected, or submit without a batch selection can be done to process all batches that are ready.

Parameters

You must define at least a range of work order numbers or dates to process the report.

Parameter	Optional or Required	Description	Parameter Value	Special Combinations Required
Batch	Optional	User defined batch code identifying the group of work definitions that are being imported.	The user defined batch code to be imported.	If no batch is selected, then all the batches in the READY status will be considered.

Troubleshooting Information

• You can view the status of the process in the Scheduled Processes work area.
• The validation errors that prevented the creation of update of the work orders are displayed in the output file (.txt).
• Any interactive warning validations aren’t performed similar to the UI.
• When the program is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process as provided by the Scheduled Processes work area.
• You can use Correct Work Orders and Transactions for Import to correct any error records using the ADFdi (Application Development Framework Desktop Integration) spreadsheet. After correcting, you need to resubmit the import process.
• You can use Purge Records from Interface scheduled process to clear off any batches that are not required.