Skip to content

Commit 1bd2dea

Browse files
authored
Updates from editor
1 parent a9477e4 commit 1bd2dea

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

support/dynamics-365/supply-chain/asset-management/conversion-of-maintenance-schedule-to-workorder-is-failing.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
---
1+
---
22
title: Conversion of Maintenance Schedule to Work Orders Fails
33
description: Solves the errors that prevent you from creating work orders based on maintenance schedule in Microsoft Dynamics 365 Supply Chain Management.
44
author: sorenbacker2
55
ms.author: sorenba
6-
ms.date: 03/04/2025
6+
ms.date: 03/13/2025
77
ms.custom: sap:Asset management\Issues with asset management
88
---
99
# Can't create work orders based on your maintenance schedule
1010

11-
This article provides the setup steps to ensure the conversion of maintenance schedule lines to work orders isn't failing due to errors related to number sequence setup in Microsoft Dynamics 365 Supply Chain Management.
11+
This article provides the setup steps to ensure the conversion of maintenance schedule lines to work orders doesn't fail due to errors related to number sequence setup in Microsoft Dynamics 365 Supply Chain Management.
1212

1313
## Symptoms
1414

@@ -31,7 +31,7 @@ To resolve the issue and ensure the successful conversion of maintenance schedul
3131

3232
4. Go to the **Segments** FastTab. Find the line where the **Segment** column equals *Alphanumeric*. Ensure the corresponding field in the **Value** column has enough hash tags to match the desired length of the variable numeric part of the work order number sequence.
3333

34-
5. Go to the **General** FastTab. In the **Number allocation** field group, ensure that the **Largest** number matches (but is included in) the length of the variable numeric part of the work order number sequence set above. In other words, if the alphanumeric value from step 4 equals *######*, the largest number could be set as *999999*. Also, ensure that the number in the **Next** field is included in the range of the number sequence mentioned in step 4 and 5.
34+
5. Go to the **General** FastTab. In the **Number allocation** field group, ensure that the **Largest** number matches (but is included in) the length of the variable numeric part of the work order number sequence set earlier. In other words, if the alphanumeric value from step 4 equals *######*, the largest number can be set as *999999*. Also, ensure that the number in the **Next** field is included in the range of the number sequence mentioned in steps 4 and 5.
3535

3636
6. Select **Save** to save the changes to the number sequence.
3737

0 commit comments

Comments
 (0)