Why this error ?
This error or similar error happens because, all system
defined number sequences are prefixed with “<Data Area Id> –#####“ and many of them
has got same number format as well. Incidentally some of them are saved in
same table as primary key value such as GeneralJournalEntry. This error pops up when one
running sequence catches other sequence.
This coincidence is hardly possible in
test phase and likely to occur in production
scenario after a few days or weeks depending upon the transaction
volume.
In this case, (DEMO is a test company account which is smudged in the attached error screen) the voucher number sequence set up under IM
-> Inventory credit note costing (Inve_89 by auto number sequence assign
wizard) voucher intercepts with IM -> Inventory costing voucher (Inve_91) number sequence.
Solution
Very simple. Change the number sequence format of Inve_91 or
Inve_89 so that it has no possibility of interference in future.
No comments:
Post a Comment