2011 Sep 27 2:26 AM
Hi All,
We added a new custom field in schedule line tab. For which we added code in PAI and user exit MV45AFZZ. When we are adding a schedule line we are getting the following error message:
Schedule line 000010 0004 is missing in table YVBEP
Message no. V1506
The schedule line 0004 for the item# 000010 is having only 'confirmed qty' and 'rounded qty and order quantity' are both 0's. This schedule line was generated as there was no stock for the schedule line entered by user .
Please let me know what has to be done to resolve this issue.
Thanks,
Karuna.
2011 Sep 27 3:17 PM
Hi
See SAP Note 178328 - Problems due to incorrect user exits in SD.
This note says:
The Y tables play a role only for the change mode of document
processing. They contain the original status of those table entries
that have been changed during the current transaction. Therefore,
the entries in the Y table reflect the previous status of the
document in the database.
and
You add a table entry. There is only one entry in the X table
that has the update indicator I. There is no entry in the Y
table.
so, check in XVBEP that the field UPDKZ has the value 'I'.
Read carefully this note
Regards
Eduardo
Hi All,
We added a new custom field in schedule line tab. For which we added code in PAI and user exit MV45AFZZ. When we are adding a schedule line we are getting the following error message:
Schedule line 000010 0004 is missing in table YVBEP
Message no. V1506
The schedule line 0004 for the item# 000010 is having only 'confirmed qty' and 'rounded qty and order quantity' are both 0's. This schedule line was generated as there was no stock for the schedule line entered by user .
Please let me know what has to be done to resolve this issue.
Thanks,
Karuna.
2011 Sep 27 5:46 AM
Hi karuna,
use the right exit form in MV45AFZZ, ' ' is not the right one.
Regards
Clemens
2011 Sep 27 2:51 PM
Hi Clemens,
Thank you very much for the quick reply. Sorry i did not mention what form i am using from MV45AFZZ. I am using 'FORM USEREXIT_MOVE_FIELD_TO_VBEP'.
What I did is, i commented all my code and put a break-point in the above form. I was able to see the 000010-0004 entry in YVBEP at this point. I am not sure how my code is blocking this entry from adding to YVBEP. I am not sure if i can add this entry thru my code in this form.
Thanks,
Karuna.
2011 Sep 27 2:59 PM
Hi
Is there any other enhancement already? If yes, then check some other development may affecting your requirement.
Shiva
2011 Sep 27 3:01 PM
Hi
How do you move your entry?
YVBEP is the internal table with the old data for schedule lines
Max
2011 Sep 27 3:17 PM
Hi
See SAP Note 178328 - Problems due to incorrect user exits in SD.
This note says:
The Y tables play a role only for the change mode of document
processing. They contain the original status of those table entries
that have been changed during the current transaction. Therefore,
the entries in the Y table reflect the previous status of the
document in the database.
and
You add a table entry. There is only one entry in the X table
that has the update indicator I. There is no entry in the Y
table.
so, check in XVBEP that the field UPDKZ has the value 'I'.
Read carefully this note
Regards
Eduardo
2011 Sep 29 4:01 PM
Hi all,
Thank you very much for all your. My problem is resolved with the SAP Note 178328 - Problems due to incorrect user exits in SD.
I am closing this post.
Thanks,
Karuna.
2012 Nov 13 1:59 PM
Hi Karuna,
Can you please share which user exit you have used, instead of 'FORM USEREXIT_MOVE_FIELD_TO_VBEP' to resolve the issue.
it will be helpful
we are also facing same issue of
Schedule line 000010 0004 is missing in table YVBEP
Message no. V1506
Requirement:
based on pricing calculation we are blocking the schedule line in run time, we are calling the user exit in pricing routine.
2014 Sep 04 10:39 AM
Hello Karuna,
Could you please tell what did you do exactly to rectify this error, Any sample code will be appreciated ?
2014 Sep 04 11:33 AM
Hi Ravi,
Please don't re-open lots of old threads looking for an answer - please try to create a new discussion thread instead as there is more chance you will get a useful reply.
<Thread locked>
Cheers,
G.