SAP mm transaction code Migo mobile type 561 error after saving -document number was already assigned

SAP MM Transaction code MIGO Mobile type 561 An error is reported after saving -document number ### was already assigned

1, Execute transaction code MIGO + Mobile type 561, Try to build some inventory for materials under a factory ,

After inputting relevant data , Click save , The following interface appears ,

Error message ：document number 4003 4900076934 2022 was already assigned.

This kind of problem is not common in project practice , But small probability will appear . The possible reasons are number range The settings have been incorrectly modified .

2, Execute transaction code Tcode FBN1  Go check relevant number range Set up .

Number range 49 The current number is 4900076933, The next number should be 4900076934, Unfortunately, this number is BSEG Inside and outside already exist , As shown in the figure below ：

3, The solution is ： In the transaction code FBN1  Interface , modify Number Range 49 The last number of .

As shown in the figure below ：

Enter the company code , Click button ‘NR Status’, Enter the following interface ,

find number range 49, You can see that the current number of this number is 4900076933, Change it to an appropriate number .

4, Number Range After setting changes , Re execute the transaction code MIGO+ Mobile type 561. Input relevant data and save ,

It can be posted normally .

- End -

Written in 2022-7-19.