Skip to content

Commit 357af8f

Browse files
authored
Merge pull request #8336 from MicrosoftDocs/SorenbaEAM-ConvMaintSched
AB#4257: Conversion of Maintenance schedule to work orders failing
2 parents 36906f6 + 9ab6801 commit 357af8f

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: Conversion of Maintenance Schedule to Work Orders Fails
3+
description: Solves the errors that prevent you from creating work orders based on maintenance schedule in Microsoft Dynamics 365 Supply Chain Management.
4+
author: sorenbacker2
5+
ms.author: sorenba
6+
ms.date: 03/14/2025
7+
ms.custom: sap:Asset management\Issues with asset management
8+
---
9+
# Can't create work orders based on your maintenance schedule
10+
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.
12+
13+
## Symptoms
14+
15+
When you try to create work orders for the selected schedule items selected using the [Open maintenance schedule lines](/dynamics365/supply-chain/asset-management/preventive-and-reactive-maintenance/creating-work-orders#create-work-orders-based-on-your-maintenance-schedule) in **Asset Management**, you receive the following error message after selecting **OK** in the **Create work orders** dialog.
16+
17+
> Number sequence \<Number sequence> has been exceeded.
18+
> Number selection is canceled.
19+
20+
## Cause
21+
22+
This issue is caused by the setup of a number sequence. Specifically, the actual number sequence exceeds the configured range of the work order number sequence.
23+
24+
## Resolution
25+
26+
To resolve the issue and ensure the successful conversion of maintenance schedule lines to work orders, follow these steps to properly set up the number sequence:
27+
28+
1. Go to **Asset management module** > **Setup** > **Asset management parameters**.
29+
2. Select the **Number sequences** FastTab.
30+
3. Select **Work order** in the **Reference** column, and then select the corresponding link in the **Number sequence code** column.
31+
32+
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.
33+
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.
35+
36+
6. Select **Save** to save the changes to the number sequence.
37+
38+
By configuring the work order number sequence correctly, the conversion of maintenance schedule lines to work orders can proceed without being blocked by an error.
39+
40+
## More information
41+
42+
[Set up number sequences on an individual basis](/dynamics365/fin-ops-core/fin-ops/organization-administration/tasks/set-up-number-sequences-individual-basis)

support/dynamics-365/supply-chain/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@
66
href: asset-management/asset-id-not-editable-when-number-sequence-is-manual.md
77
- name: Changing work order lifecycle state doesn't generate fault cause or fault remedy error
88
href: asset-management/change-lifecycle-state-doesnt-create-fault.md
9+
- name: Can't create work orders based on your maintenance schedule
10+
href: asset-management/conversion-of-maintenance-schedule-to-workorder-is-failing.md
911
- name: Inventory costing and closing
1012
items:
1113
- name: An update conflict occurs when the inventory valuation method is either standard cost or moving average

0 commit comments

Comments
 (0)