on 2024 Aug 02 3:08 PM
Number range of material type is checked through MMNR, pls help
Request clarification before answering.
Check SAP KBA if relevant to your case 3289787 - Update termination occurs in t-code MM01/MM02
Another possibility you may have the number range mixed up where the material # that the system is trying to create is already exists -- you may want to start your number a little ahead of numbers that already in the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @SUSHABHAN_MM
The reason is that you care a material with automatic numbering. The system fetches next number from a number range assigned to the material type and tries to save the material with that number. However there is already another material created with the same number. Hence the dump.
You need to correct the number range and at least modify its status.
This kind of errors occurs mostly due to number range transports, as such transport import also number range status to the destination system. That's why transporting number ranges is not automatic and is discouraged. Nevertheless, I think it's ok to transport them with care.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @SUSHABHAN_MM
Go to ST22 and examine the dump.
Most probably you are creating a material with internal numbering, your number ranges are messed up and system is trying to create a material with an already used number.
That happens when internal number ranges are transported.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
9 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.