on 12-10-2012 7:57 AM
Dear All,
I would like to update reason for rejection field of sales order item, from delivery creation T-code. If anybody had done something like this, please help me.
Thanks.
Regards,
Ravi
This question has already been asked several times before, please use Search. The same exact question posted just a few days ago: http://scn.sap.com/thread/3277904
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi ,
As per my uderstanding of your query, you want to set the reason for rejection of the sales order item when there is partial delivery and the trigger point should be from the delivery document. May be you can develop a custom program to set the reason of rejection. I am not sure whether we have any user-exit to handle this beacuse the trigger point is in delivery and the action is in sales order.
Please also consider that when you delete the delivery document, the reason of rejection should be set to "BLANK".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vinu,
Thanks for your post!
I am not sure whether we have any user-exit to handle this beacuse the trigger point is in delivery and the action is in sales order.
Please also consider that when you delete the delivery document, the reason of rejection should be set to "BLANK".
Interesting remarks!
Ravi,
When reason for rejection is given in the sales order, for a line item, then for that line item there would not be delivery created!
I would like to update reason for rejection field of sales order item, from delivery creation T-code.
Please explain your requirement, if delivery is created, for the ref. sales order line item put reason for rejection.
If reason for rejection is put in the sales order, line item then how delivery is created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Please refer the OSS Note 415716 - User exits in delivery processing
I guess, the below exit will be useful for you to handle your requirement. Consult your abaper and they can handle the sales order change through a BAPI.
FORM routine USEREXIT_SAVE_DOCUMENT (include MV50AFZ1)
Thanks,
Ravi Sankar
Can you please explain the scenario under which, you want this weird requirement ??
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If a sales order has been created with an item for quantity 10. At the time of delivery creation, if only 5 quanity is available, then the delivery creation person will set input a custom field at delivery item level. Whatever value has been set in the custom field, must be updated in sales order item reason for rejection field for reporting purpose.
There are no user exits, BADIs, BTE, etc.
Thanks.
Regards,
Ravi
Ravi,
Thanks for your reply!
Now I have more understanding on this requirement.
For reporting purposes in the sales order at line item why don't you consider Tab Additional B?
The field Reason for rejection would be applicable for 10EA (total amount of that line item). But your company has already delivered 5EA.
Thus for only 5EA that is not deliveried, you want to put a reason (not for 10EA).
Hi,
I have simulated a scenario where in i have created a sales order for quantity 10 EA. I have created a delivery of 5 EA. And then i have changed the sales order item, by putting the reason for rejection field to 'Out of Stock' and saved it. It worked. Now, when i do 'VL01N' , i get message 'No deliverable items'.
Hence, we can conclude that we can put reason for rejection to partial delivery items also.
Thanks.
Regards,
Ravi
Hi,
http://scn.sap.com/thread/2062796
Please have a look into above link.
Request : Please search in Google before posting this type of queries .you can get a lot of threads on this .
Thanks,
Naren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
12 | |
11 | |
6 | |
6 | |
4 | |
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.