|
| 1 | +--- |
| 2 | +title: No Fault Cause or Fault Remedy Error When Changing Work Order Lifecycle State |
| 3 | +description: Provides fault registration steps to ensure you receive the expected error when changing a work order lifecycle state in Microsoft Dynamics 365 Supply Chain Management. |
| 4 | +author: sorenbacker2 |
| 5 | +ms.author: sorenba |
| 6 | +ms.reviewer: kamaybac |
| 7 | +ms.date: 02/13/2025 |
| 8 | +ms.custom: sap:Asset management\Issues with asset management |
| 9 | +--- |
| 10 | +# Changing a work order lifecycle state doesn't generate a fault cause or fault remedy error |
| 11 | + |
| 12 | +This article provides the setup steps to ensure that the expected fault cause or fault remedy error is generated when you change a work order lifecycle state in Microsoft Dynamics 365 Supply Chain Management. |
| 13 | + |
| 14 | +## Symptoms |
| 15 | + |
| 16 | +When you change a [work order lifecycle state](/dynamics365/supply-chain/asset-management/setup-for-work-orders/work-order-lifecycle-states) that's set up to validate [fault causes](/dynamics365/supply-chain/asset-management/setup-for-work-orders/fault-management#create-fault-causes) and [fault remedies](/dynamics365/supply-chain/asset-management/setup-for-work-orders/fault-management#create-fault-remedies), the error you expect to be generated doesn't occur for a fault cause or fault remedy. This allows the lifecycle state to change despite the validation setup. |
| 17 | + |
| 18 | +## Cause |
| 19 | + |
| 20 | +A possible reason the expected error doesn't occur is that the fault cause and fault remedy can't be validated because they don't have a [fault registration](#create-a-fault-registration). |
| 21 | + |
| 22 | +## Resolution |
| 23 | + |
| 24 | +To ensure the expected error is generated, follow these steps to set up lifecycle states and work order types, and create a fault registration. |
| 25 | + |
| 26 | +### Set up lifecycle states and work order types |
| 27 | + |
| 28 | +1. Set up the lifecycle state to enable the validation of fault causes and fault remedies: |
| 29 | + |
| 30 | + 1. Go to **Asset Management module** > **Setup** > **Work orders** > **Lifecycle states**. |
| 31 | + 1. Select the work order lifecycle state in question, and then select **Edit**. |
| 32 | + 1. Under the **Validate** FastTab, set the message type to **Error**, and set the **Fault cause**, **Fault remedy**, and other related options to **Yes**. |
| 33 | + |
| 34 | +2. Set up the work order type to enable the validation of fault causes and fault remedies by making them mandatory for work orders: |
| 35 | + |
| 36 | + 1. Go to **Asset Management module** > **Setup** > **Work orders** > **Work order types**. |
| 37 | + 1. Select the work order type in question, and then select **Edit**. |
| 38 | + 1. Under the **General** FastTab, set the **Fault cause**, **Fault remedy**, and other related options to **Yes** in the **Mandatory** section. |
| 39 | + |
| 40 | +### Create a fault registration |
| 41 | + |
| 42 | +To make sure you receive the expected error message, follow these steps to create a fault registration: |
| 43 | + |
| 44 | +1. Go to **Asset Management** > **Work order** > **All work orders**. |
| 45 | + |
| 46 | +2. Select the work order in question. For simplicity, assume it's a new work order with the **Current lifecycle state** being **New**. |
| 47 | + |
| 48 | +3. In the Action Pane, go to the **Asset** group and select **Asset fault**. |
| 49 | + |
| 50 | +4. Expand the **Symptoms** FastTab and select **Add line**. |
| 51 | + |
| 52 | +5. In the **Fault symptom** field, select the relevant symptom from the dropdown list. Select **Save**, and then go back to the work order. |
| 53 | + |
| 54 | +6. In the Action Pane, go to the **Lifecycle state** group and select **Update work order state**. |
| 55 | + |
| 56 | +7. In the **Update work order state** window, select the **Lifecycle state** that has the validation setup (see [Set up lifecycle states and work order types](#set-up-lifecycle-states-and-work-order-types)). For simplicity, assume the **Lifecycle state** is **Released**. Then, select **OK**. |
| 57 | + |
| 58 | +8. Select the **Action Centre/notification bell** in the upper-right corner, and then select **Message details**. The **Message details** window shows "The fault cause for symptom X on asset Y is missing. Update has been cancelled." Close the **Message details** window. In the upper-right corner of the work order, the **Lifecycle state** is still shown as **New**. |
| 59 | + |
| 60 | +9. In the Action Pane of the work order, go to the **Asset** group and select **Asset fault**. |
| 61 | + |
| 62 | +10. Expand the **Causes for selected symptom** FastTab and select **Add line**. |
| 63 | + |
| 64 | +11. In the **Fault cause** field, select the relevant cause from the dropdown list. Select **Save**, and then go back to the work order. |
| 65 | + |
| 66 | +12. In the Action Pane, go to the **Lifecycle state** group and select **Update work order state**. |
| 67 | + |
| 68 | +13. In the **Update work order state** window, select the **Lifecycle state** that has the validation setup (see [Set up lifecycle states and work order types](#set-up-lifecycle-states-and-work-order-types)). For simplicity, assume the **Lifecycle state** is **Released**. Then, select **OK**. |
| 69 | + |
| 70 | +14. Select the **Action Centre/notification bell** in the upper-right corner, and then select the new **Message details** (mentioned in step 8). The **Message details** window shows "Fault remedy for cause Z on symptom X on asset Y is missing. Update has been cancelled." Close the **Message details** window. In the upper-right corner of the work order, the **Lifecycle state** is still shown as **New**. |
| 71 | + |
| 72 | +15. In the Action Pane of the work order, go to the **Asset** group and select **Asset fault**. |
| 73 | + |
| 74 | +16. Expand the **Remedies for selected symptom** FastTab and select **Add line**. |
| 75 | + |
| 76 | +17. In the **Fault remedy** field, select the relevant remedy from the dropdown list. Select **Save**, and then go back to the work order. |
| 77 | + |
| 78 | +18. In the Action Pane, go to the **Lifecycle state** group and select **Update work order state**. |
| 79 | + |
| 80 | +19. In the **Update work order state** window, select the **Lifecycle state** that has the validation setup (see [Set up lifecycle states and work order types](#set-up-lifecycle-states-and-work-order-types)). For simplicity, assume its **Lifecycle state** is **Released**. Then, select **OK**. |
| 81 | + |
| 82 | +20. Select the **Action Centre/notification bell** in the upper-right corner. The first two attempts to update the work order state result in error messages, and the **Lifecycle state** isn't updated. On the third attempt, no error message is generated, and the **Lifecycle state** is correctly updated to **Released**. |
0 commit comments