Sync Work Definition Changes with Existing Work Orders

Use the Sync Work Definition Changes with Existing Work Orders scheduled process to propagate changes from work definitions to their corresponding work orders.

When a change is made to the work definition either manually or through the Process Item Structure Changes to Work Definition scheduled process, these changes can be propagated to existing unreleased and released work orders.

When to Use

Run this scheduled process when you need to propagate work definition changes to existing work orders, especially for manufacturers of products with long lead times where multiple open work orders may be active at any given time. The program can be scheduled to run automatically at fixed intervals or on demand.

Privileges Required

Sync Work Definition Changes with Existing Work Orders (WIS_SYNC_WORK_DEFINITION_CHANGES_TO_WORK_ORDER)

Specifications

Review these specifications before setting up this scheduled process:

Specification	Description
Job Type	Scheduled or as needed.
Frequency	Schedule to run automatically at fixed intervals, such as daily or weekly, or run on demand. The frequency depends on how often work definition changes occur in your organization and the criticality of applying these changes to work orders.
Time of Day	Run during, or after, work hours based on your organization's needs. For large scale updates affecting many work orders, consider running during off-peak hours to minimize impact on system performance.
Duration	Depends on the number of work orders being updated, the complexity of changes being applied, and the scope of work definitions selected. The duration can vary from a few minutes for small batches to several hours for organization-wide updates.
Compatibility	There should be only one instance of this job running at any time. Multiple concurrent instances may result in conflicts when updating the same work orders.

Parameters

Parameter	Optional or Required	Description	Parameter Value	Special Combinations Required	Notes
Manufacturing Organization	Required	Select the organization or manufacturing plant.	List of Values (Organization)	None	N/A
From Date	Required	Specify the From date. The job uses the work definition changes in the specified date range.	Date and Time	None	N/A
To Date	Required	Specify the To date. The job uses the work definition changes in the specified date range.	Date and Time	None	N/A
Work Definition Name	Optional	Select a specific work definition name from the list.	List of Values (Work Definition)	None	N/A
Item Category	Required	Select the item category to ensure that only relevant items are picked up.	List of Values (Item Category)	None	N/A
From Item	Required	Select the first item to include in the update process.	Item of the specified category	None	N/A
To Item	Required	Select the last item to include in the update process.	Item of the specified category	None	N/A
Work Definition As of Date	Read-only	Defaults to the To Date value provided in the date range parameter for the work definition changes. Determines which version of the work definition should be used.	Auto-populated from the date range	None	N/A
Sync All Work Orders	Optional	Determines if all work orders associated with the work definition must be considered for propagation or a select range of work orders should be used. If Yes, then all qualifying work orders are synced. If No, then the From/To Work Order fields are enabled.	Yes/No	None	N/A
Work Order From / To	Conditional	Specify work order range (editable and mandatory if Sync All Work Orders = No).	Work order numbers	None	N/A
Work Order Status	Optional	Select one or more work order statuses. Includes user-defined status mapped to released and unreleased work orders.	All, Released, Unreleased, or user-defined statuses	None	N/A
Exclude Firm Work Orders	Optional	Select Yes to exclude firm work orders from propagation.	Yes/No	None	N/A

Troubleshooting Information

• If the job performance is slower than expected, then check the following:
  • The number of work orders being updated.
  • The complexity of work definition changes.
  • System resource availability.
• If the job fails, review the output file to identify the work orders that failed and the specific error messages. Common issues include operations already started, existing resource/material transactions, or purchase requisitions/orders already created for OSP operations.
• Changes cannot be applied to operations that have already started execution or have recorded transactions, such as material issues, resource charges, or output transactions.