Previous | Next | Contents | Index | Navigation | Glossary | Library |
You can manually implement revised items on an ECO or you can automatically implement each revised item on its effective date. Engineering updates the actual implementation date for each revised item when it is implemented. When all of the revised items on an ECO have been implemented, the ECO is completely implemented and can be purged.
Engineering implements an ECO over time from the earliest revised item effective date to the latest revised item effective date. When you spread multiple changes across several ECOs, you should ensure that the effective date ranges for the ECOs do not overlap. For example, if you implement changes to a bill of material across many ECOs, you should make sure that the revised item effective dates do not overlap. If you implement one change using the current revision, you should implement all other changes to the current revision before you implement changes against future revisions.
Attention: You must implement new revisions in ascending order. If you implement a later revision for an item on one ECO, Engineering ensures that you implement any subsequent revisions for the item in ascending order.
For example, if you manually implement a revised item that has a future effective date, Engineering changes the effective date to the current date and marks the revised item and all revised components as implemented.
Start the AutoImplement Manager process so Engineering implements scheduled changes daily.
Note: A warning message appears if the ECO does not have a Workflow process and the revised item's effective date is in the future.
Starting the AutoImplement Manager
Implementation of ECOs on Discrete Jobs and Repetitive Schedules
Previous | Next | Contents | Index | Navigation | Glossary | Library |