on 01-10-2008 11:49 AM
hello, friends.
we have a situation where Billing type F2 settings were changed (using VOFA). specifically, in field "Assignment" i specified "E" (billing document). supposedly, the billing document number will be used as assignment allocation. there are already billing documents created.
when these settings were done, i started getting error message "express document update terminated". the system says error has something to do with ABAP/4 processor CONVT_NO_NUMBER.
when i execute ST22 or SM13 to look at the problem, it says the system cannot interpret "1111" which is why the update was terminated. here, "1111" is the material number.
i tried switching the settings of F2 back to standard but the errors continue.
why is the system getting the material number as number range?
your help will be greatly appreciated.
many thanks.
jty
Hi,
The most probable reasons could be:
1) Number range clash with other doucment which is having same number. this could be because of changing assigmnment of no. range object which is assigned to other doc types.
2) Changes in customization for statistical updates
regards,
Siddharth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello, friend.
i checked the other threads with similar subject, and i agree it may have something to do with number range. but i checked the number range of the billing document and i'm not sure i have the exact issue.
i suspect that when i changed the "Assignment" settings in VOFA, the synchronization with the Accounting Document (Allocation) number might have been affected. when i repeatedly tried to create billing document with reference to the same delivery document, the system uses a new billing document number when saving, but then this is lost.
would you think this is the more likely cause?
thanks.
jty
thanks.
hope to work with you guys sometime.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
yes the clash range is the most obvious reason of termination of the t:code VF01.
Plz check it out.
regards,
Siddharth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
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.